Error 1067
If starting the FlashConnect server on the Web server host produces this error, shut down and restart the server.
Unable to attach to shared memory segment.
Please refer to the diagnostic message Unable to connect to FCService in Diagnostic Messages Displayed On the Browser.
Failed to open semaphore
There is a version mismatch between fccgi.exe and FCService. The versions must match. Reinstalling both the D3 and Windows components may be necessary. To determine the version of fccgi.exe and FCService refer to the topic Determining Release Levels. (Entering -V from MS-DOS no longer performs this function.)
Sorry no FlashConnect servers are available at this time
Try again in a few moments. There are no available FlashConnect connections. Possible causes:
There are no connections started.
No phantoms are available.
No database licenses are available.
They are all in use.
ERROR - Missing required elements in form
This message displays if the URL starting a FlashConnect application is missing either a w3Exec parameter or a w3SessionId parameter. This also happens if the calls to w3HtmlFormBeg or w3HtmlFormEnd are missed.
This URL shows the error:
http://w3lib.rainingdata.com/cgi-bin/fccgi.exe?w3ClosingPage=!url
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.
See Also