Oops, you are right. The issue was resolved in FoxWeb 2.5, in that the error is ignored and a connection to the FoxWeb Broker is re-attempted by the channel -- usually successfully. In the past FoxWeb would try to re-start the channel, causing unnecessary load on the server.
The error is still logged in order to keep a complete log, but it can usually be safely ignored.
How ofter do you see this error in fwstart.log? If possible, please send us a copy of this file via email.
FoxWeb Support Team
support@foxweb.com email |
Sent by B Wagner on 07/28/2003 09:16:19 AM:
As the message said: FoxWeb2.5
Sent by FoxWeb Support on 07/28/2003 01:26:32 AM:
I believe that this issue was resolved in FoxWeb 2.5. Are you running an older version of FoxWeb? If yes, then simply upgrade to version 2.5.
FoxWeb Support Team
support@foxweb.com email |
Sent by B Wagner on 07/23/2003 02:15:35 PM:
We get the following error on a regular basis:
Error: 1440 Message: "OLE exception error: Exception code c0000005. OLE object may be corrupt" Program: "PROCEDURE FWMAIN D:\PROGRAM FILES\FOXWEB\FWSERVER.EXE" Line Number: 162 Channel: 4
Running FW2.5, What OLE object is it? It' associated with channels timing out.