Subject Re: Need help with errors
Author csswa
Daniel, some of these were addressed in earlier posts. From a quick
search of the group archives it seems nobody was able to give you a
definitive answer, but there were serveral leads provided for you to
follow up on your own.

You can help yourself to find the answer by:

* google search on the error phrases encountered;
* ditto search this group archive;
* if you don't have the MERS archive address, get if from the group
database ('links for new users')

as for the other error messages in your log...

> NTSERVER (Server) Wed May 22 07:14:31 2002
> INET/inet_error: read errno = 10054

ignore these as insignificant -- unless you get a lot.

> NTSERVER (Client) Wed May 22 08:59:26 2002
> C:\Program Files\InterBase\Bin\ibserver.exe: terminated
abnormally

The server crashed.

> NTSERVER (Client) Wed May 22 08:59:28 2002
> Guardian starting: C:\Program
Files\InterBase\Bin\ibserver.exe

The guardian immediately resurrected the server.

> NTSERVER (Server) Wed May 29 11:50:38 2002
> Database: C:\PROGRA~1\FILOPTO4\DATA\FILOPTO.FDB
> I/O error for file "C:\PROGRA~1\FILOPTO4\DATA\FILOPTO.FDB"
> Error while trying to access file
> The operation completed successfully.

Another process grabbed the file! This is very suspicious and is
likely the source of your other corruption -- as mentioned by Helen
in an earlier reply to your posts. You need to examine what other
process/activities are potentially touching your database files. I
not very familiar with Win2000 so someone else may be able to help
you with this.

> NTSERVER (Server) Wed May 29 11:53:06 2002
> Database: C:\PROGRA~1\FILOPTO4\DATA\FILOPTO.FDB
> database shutdown

Not sure if this indicates a manual shutdown of server or a system
shutdown.

> NTSERVER (Server) Wed May 29 11:53:07 2002
> Fatal lock manager error: invalid lock id (0), errno: 0

This could be related to the earlier file-access lock.

> NTSERVER (Client) Wed May 29 11:53:07 2002
> C:\Program Files\InterBase\Bin\ibserver.exe: terminated
abnormally

Server bombed because it was once again locked out of the database
file.

> NTSERVER (Client) Wed May 29 11:53:08 2002
> Guardian starting: C:\Program
Files\InterBase\Bin\ibserver.exe

Guardian kicks in immediately.

> NTSERVER (Client) Wed May 29 12:07:09 2002
> C:\Program Files\InterBase\Bin\ibserver.exe: normal
shutdown

This one is a manual shutdown of the server (e.g. via control panel).

> NTSERVER (Client) Wed May 29 12:07:09 2002
> Control services error 1061
> I'm guessing that this error is because the Windows event log is
full.

No, I get this error message too. It's not related to event log.

> NTSERVER (Client) Wed May 29 12:07:20 2002
> Guardian starting: C:\Program
Files\InterBase\Bin\ibserver.exe

Guardian comes to the rescue again.

Regards,
Andrew Ferguson
-- Keeping an eye on things till the apes take over.