Subject | Re: [IBO] Exception when trying to connect to database |
---|---|
Author | Helen Borrie |
Post date | 2005-12-15T22:57:54Z |
At 10:03 PM 15/12/2005 +0000, you wrote:
it can't open a file that the server (or the API) asks it to open.
Depending on when this happens, it could be one or more of the following:
1. the security database (isc4.gdb or security.fdb, depending on version)
2. server log (interbase.msg/firebird.msg)
3. hostname.lck (substitute your hostname)
4. the database file itself
Possibly someone there has deleted something from the server's root
directory structure....
Could be just that they're running the server as an application and the
Windows user doesn't have permissions to the server's root dir.
They're not actually running the server you think they are, so that the
server isn't finding the right registry key to get to the root directory.
Anyway, if it worked before and doesn't now, someone has snafu'ed something...
Helen
>I have a user getting the following exception when connecting to aIt's a generic exception returned by the DB server when the OS reports that
>database. It has worked before on the system. What is the cause of
>this exception?
>
>Thanks
>Ed Dressel
>
>exception class : EIB_ISCError
>exception message : ISC ERROR CODE:335544373ISC ERROR
>MESSAGE:operating system directive CreateFile failedThe system cannot
>find the file specified.
it can't open a file that the server (or the API) asks it to open.
Depending on when this happens, it could be one or more of the following:
1. the security database (isc4.gdb or security.fdb, depending on version)
2. server log (interbase.msg/firebird.msg)
3. hostname.lck (substitute your hostname)
4. the database file itself
Possibly someone there has deleted something from the server's root
directory structure....
Could be just that they're running the server as an application and the
Windows user doesn't have permissions to the server's root dir.
They're not actually running the server you think they are, so that the
server isn't finding the right registry key to get to the root directory.
Anyway, if it worked before and doesn't now, someone has snafu'ed something...
Helen