Installation guide
Windows Platform Error Messages
FlashCONNECT Administrator’s Guide 209
This URL shows the correction:
http://w3lib.rainingdata.com/cgi-bin/fccgi.exe?w3exec=app&w3ClosingPage=!url
This message indicates an application setup error and not a run-time error, and thus
should not be visible to the user during normal operations. It is not kept in the
system messages file.
ERROR - Invalid or stale cookie(000)
This message displays to the user when a previously established connection is no
longer valid. This happens when a connection times out or when the user attempts
to reload a cached page. Restart the connection to recover from this state.
"xxxx" is an illegal command
This message displays if the application name specified in the w3exec parameter
does not exist in the w3Apps file. Assuming the application name is app, this
example shows the error:
http://w3lib.rainingdata.com/cgi-bin/
fccgi.exe?w3exec=wrongapp&w3ClosingPage=!url
This example shows the correction:
http://w3lib.rainingdata.com/cgi-bin/fccgi.exe?w3exec=app&w3ClosingPage=!url
This message indicates an application setup error and not a run-time error, and thus
should not be visible to the user during normal operations. It is not kept in the
system messages file.
Socket message
• Verify that the Web server and the database component are both running
compatible versions of FlashCONNECT.
• For D3: If WWW-STATUS shows all lines with a status of sockets, verify that D3
7.1 or later is running.
No FlashCONNECT Services available at this time
• If you do not specify w3ServerPool, verify that there is a default server pool.
• If you do specify a server pool, verify that there are ports available.
• Verify that all applications are not going to the debugger.
• Verify that all applications return to WWW-IRUN and do not end.
• Check to see if all ports are consumed by applications using persistent
connections. If all ports are consumed, either modify the application to not use
persistent connections, or allocate more ports.