Skip to content

Web Application Error Messages

Web Application Errors List

See Also: Finding Specific Errors

  • 300 - Invalid web application ApplicationName. Please verify that the spelling is correct and that the specific web application has been correctly configured. More Info

  • 301 - Invalid web application ApplicationName. Please verify that the spelling is correct and that the specific web application has been correctly configured. More Info

  • 302 - Application: ApplicationName Session: SessionId From: IPAddressOfRequest
    Failed to establish communication source with child process %4: %5. More Info

  • 303 - Unable to handle endpoint request. Server may be too busy, or there may be too many concurrent sessions. %1. More Info

  • 309 - Error starting service: Reason. More Info

  • 311 - DataFlex Web Application Server panic, cause: %1, location: %2. More Info

  • 312 - Application: ApplicationName Session: SessionId From: IPAddressOfRequest
    Session failed to initialize: %4. More Info

  • 315 - Failed to establish endpoint communication source. %1. More Info

  • 316 - Second chance failure to establish endpoint communication source. %1. Shutting down service abnormally. More Info

  • 317 - Failed to initialize application event log: Unable to create LogFileNameIncludingPath. More Info

  • 318 - Failed to write to application event log ApplicationName. Log message: %2. More Info

  • 319 - Application: ApplicationName Session: SessionId From: IPAddressOfRequest
    No remote node currently available. All remote nodes appear offline or busy. More Info

  • 320 - Unable to initialize load balancing master node TCP/IP socket connection. %1. More Info

  • 321 - Failed to set keep-alive socket option for connection with slave node. %1. More Info

  • 322 - Application: ApplicationName Session: SessionId From: IPAddressOfRequest
    Attempt to invoke unsupported endpoint subsystem operation, %4. More Info

Detailed Error Messages

300 - Invalid web application ApplicationName

The requested Web Application does not exist. The most probable cause is that the Web Application name in global.asa doesn't match the Web Application name as entered in the DataFlex Web Application Server Administrator.

Make sure that the name of the Web Application in global.asa matches the name used in the DataFlex Web Application Server Administrator. Either correct the name in global.asa, or in the Administrator by deleting the Web Application and creating it again.

301 - Application: ApplicationName Session: SessionId From: IPAddressOfRequest

Failed to establish communication source with child process %4: %5.

Internal communication source could not be established. This occurs if the system resources are low or under very high server load.

302 - Application: ApplicationName Session: SessionId From: IPAddressOfRequest

Failed to start child process %4: %5.

The child process did not start properly. This can occur if internal communication was not established or if the DataFlex program is not a Web Application.

303 - Unable to handle endpoint request

Server may be too busy, or there may be too many concurrent sessions. %1.

309 - Error starting service: Reason

For example:
Error starting service: Your evaluation period of DataFlex Web Application Server has expired. Please run the product registration program and register your DataFlex Web Application Server license.

311 - DataFlex Web Application Server panic

Cause: %1, Location: %2.

Internal error, should not normally occur.

312 - Application: ApplicationName Session: SessionId From: IPAddressOfRequest

Session failed to initialize: %4.

Session failed to initialize due to the following reason.

315 - Failed to establish endpoint communication source

%1.

316 - Second chance failure to establish endpoint communication source

%1. Shutting down service abnormally.

317 - Failed to initialize application event log

Unable to create LogFileNameIncludingPath.

Occurs when the application log file could not be opened/created. The log file might be corrupt, an invalid log file path specified, or insufficient access rights to the underlying file system.

This error can also be caused by multiple versions of DataFlex Web Application Server attempting to share the same log file.

If the log file is corrupt, you can remove the file, and the next time the DataFlex Web Application Server is started, a new log file will automatically be created.

318 - Failed to write to application event log ApplicationName

Log message: %2.

319 - Application: ApplicationName Session: SessionId From: IPAddressOfRequest

No remote node currently available. All remote nodes appear offline or busy.

320 - Unable to initialize load balancing master node TCP/IP socket connection

%1.

321 - Failed to set keep-alive socket option for connection with slave node

%1.

322 - Application: ApplicationName Session: SessionId From: IPAddressOfRequest

Attempt to invoke unsupported endpoint subsystem operation, %4.