Subject | Re: Need help with errors |
---|---|
Author | csswa |
Post date | 2002-05-30T04:08:09Z |
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...
The server crashed.
The guardian immediately resurrected the server.
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.
shutdown.
Server bombed because it was once again locked out of the database
file.
Guardian kicks in immediately.
This one is a manual shutdown of the server (e.g. via control panel).
No, I get this error message too. It's not related to event log.
Guardian comes to the rescue again.
Regards,
Andrew Ferguson
-- Keeping an eye on things till the apes take over.
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 2002ignore these as insignificant -- unless you get a lot.
> INET/inet_error: read errno = 10054
> NTSERVER (Client) Wed May 22 08:59:26 2002abnormally
> C:\Program Files\InterBase\Bin\ibserver.exe: terminated
The server crashed.
> NTSERVER (Client) Wed May 22 08:59:28 2002Files\InterBase\Bin\ibserver.exe
> Guardian starting: C:\Program
The guardian immediately resurrected the server.
> NTSERVER (Server) Wed May 29 11:50:38 2002Another process grabbed the file! This is very suspicious and is
> 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.
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 2002Not sure if this indicates a manual shutdown of server or a system
> Database: C:\PROGRA~1\FILOPTO4\DATA\FILOPTO.FDB
> database shutdown
shutdown.
> NTSERVER (Server) Wed May 29 11:53:07 2002This could be related to the earlier file-access lock.
> Fatal lock manager error: invalid lock id (0), errno: 0
> NTSERVER (Client) Wed May 29 11:53:07 2002abnormally
> C:\Program Files\InterBase\Bin\ibserver.exe: terminated
Server bombed because it was once again locked out of the database
file.
> NTSERVER (Client) Wed May 29 11:53:08 2002Files\InterBase\Bin\ibserver.exe
> Guardian starting: C:\Program
Guardian kicks in immediately.
> NTSERVER (Client) Wed May 29 12:07:09 2002shutdown
> C:\Program Files\InterBase\Bin\ibserver.exe: normal
This one is a manual shutdown of the server (e.g. via control panel).
> NTSERVER (Client) Wed May 29 12:07:09 2002full.
> Control services error 1061
> I'm guessing that this error is because the Windows event log is
No, I get this error message too. It's not related to event log.
> NTSERVER (Client) Wed May 29 12:07:20 2002Files\InterBase\Bin\ibserver.exe
> Guardian starting: C:\Program
Guardian comes to the rescue again.
Regards,
Andrew Ferguson
-- Keeping an eye on things till the apes take over.