Date:  06/22/2012 01:49:27 PM Msg ID:  004480
From:  Martin Martin Thread:  004478
Subject:  Re: Could Not Connect to FoxWeb Broke
I done all my update, reboot ...
A lot of trafic today .. 
The problem do not appear since then.
Sent by FoxWeb Support on 06/20/2012 05:38:53 PM:
The first error may indicate that your server's CPU (or some other resource) is overloaded, preventing the FoxWeb Broker from handling incoming requests. Have you tried rebooting?
The errors in the Windows Event Log indicate that your channels occasionally crash. This should not happen under normal circumstances. I have seen such crashes causes by bugs in COM/DLL components, or OLEDB/ODBC drivers. I have also seen corrupted data files cause similar issues.
FoxWeb Support Team email
Sent by Martin Martin on 06/20/2012 04:50:55 PM:
Today I'm having a strange problem with foxweb. Randomly when I click on links(script) that I never get any problem with before, I start to receive error:
Could Not Connect to FoxWeb Broker.  
Broker has probably not been started.
Within the same few seconds, I click again and the script display the page instantly like nothing happen.
When I check SHOW_CHANNELS all channels are waiting.
When I go to ErrorLog in FW control Center... no error was loged.
FWstart.log have nothing
What can cause this and what can I look at to try to locate the problem? 
I don't know if it's important to mention but I see 1 error in the windows Event Viewer for today. The time do not correspond with any "FoxWeb Broker" message I receive:
Application Error, EventID 1000 (100) 
Faulting application name: fwserver.exe, version:, time stamp: 0x47139f24
Faulting module name: unknown, version:, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x00cb69e4
Faulting process id: 0x4994
Faulting application start time: 0x01cd4f06a8a21bfa
Faulting application path: c:\program files (x86)\foxweb\fwserver.exe
Faulting module path: unknown
Report Id: 160eb8c2-bb04-11e1-9695-d4ae527abe7d 
thank you