Server Error
If accessing a dynamic application, such as the w3Admin, and the browser reports a Server Error, the FlashConnect servers have probably not been set up correctly. See the documentation for WWW-STATUS, WWW-START and WWW-STOP.
Unknown line in configuration file: xxxx
When the FCService starts, it reads the FlashConnect.conf file. At this time, if an unexpected line is found, the above message is printed.
To recover, correct or remove the unexpected line and restart the FCService.
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 example shows the error:
http://w3lib.rainingdata.com/cgi-bin/fccgi.exe?w3ClosingPage=!url
This URL 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.
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 URL example shows the error:
http://w3lib.rainingdata.com/cgi-bin/fccgi.exe?w3exec=wrongapp&w3ClosingPage=!url
This URL 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.
See Also