Failed to get session for session id - Application Server - English - Foundation 22.1 - OnBase - external

Application Server

Platform
OnBase
Product
Application Server
Release
Foundation 22.1
License

When users are working in the OnBase Web Client or another OnBase Web application like DocPop, the application may become unresponsive. The OnBase Event Log records the “Application End” and “Application Start” events, which are followed by a series of errors. The Diagnostics Console logs the following error message

  • Failed to get session for session id.

The Web Client also may display either of the following messages:

  • Message: Required property: SessionID is unavailable.

  • Error processing request.

Modifying the contents of the Web Server or Application Server's virtual directory will cause these applications to restart. When this occurs, connected users will lose their sessions and their applications will become unresponsive. This behavior occurs because the OnBase Web Server and Application Server are ASP.NET Web Applications. ASP.NET detects file changes, including changes to file system attributes and time stamps, and restarts the application if a change is detected. You can view the shut down message of the “Application End” event in the OnBase Event Log to determine why the application stopped. (For example, the virtual directory contents or Web.config settings have been changed.)

Unintended application restarts can occur when virus scanning software, backup software, or indexing services access the contents of an application's virtual directory. These processes don't modify the contents of an application's files, but they can modify the files' attributes, which is enough for ASP.NET to restart the application. To properly configure virus scanning, backup software, or indexing service software, follow these guidelines:

  • Exclude the virtual directories for the OnBase Web Server and Application Server and the ASP.NET Temporary Files directory from antivirus, backup, or indexing service scanning. The ASP.NET Temporary Files directory is below:

    • 32-bit installations:

      C:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files

    • 64-bit installations:

      C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Temporary ASP.NET Files

      If these files are scanned by antivirus, backup, or indexing software, IIS will restart the application pool for the OnBase application. When an application pool restarts, all existing OnBase sessions are reset, causing errors for connected users.

  • Real-time scanning of script execution, which is available in some antivirus software, should only be engaged according to the software manufacturer's instructions. Some manufacturers do not intend this functionality to be used on servers.

Consult your antivirus, backup, or indexing service software's documentation for other recommended settings for Web servers. Ensure that any virus scanning, backup or indexing service changes will not be overwritten by the automatic policy settings configured for your network.

The Microsoft Knowledge Base describes this issue in greater detail. For more information, refer to the following articles:

  • http://support.microsoft.com/kb/821438

  • http://support.microsoft.com/kb/312592/en-us?spid=8940&sid=global

  • http://support.microsoft.com/kb/316148/EN-US/