Input stream is not a valid binary format - Application Server - English - Foundation 22.1 - OnBase - external

Application Server
Platform
OnBase
Product
Application Server
Release
Foundation 22.1
License

When users attempt to log on to the Web Client, either of the following errors may be logged to the Diagnostics Console.

  • Input stream is not a valid binary format.

  • <title>Could not load file or assembly ‘System.Web.Extensions'...</title>

The first error is displayed if the Web Server is using remoting as its ServiceClientType. The second error is displayed if the Web Server is using SOAP.

On the login page, the following error is displayed:

  • The server encountered an error when logging in. If this problem persists, you should contact your administrator for resolution.

Similar errors are captured when users attempt to access the service.asmx page of the Application Server.

This issue may occur for several reasons.

  1. This issue may occur because the home directory at the Web site level has the option A directory located on this computer selected with the Local path pointing to a virtual directory (e.g., C:\DMS\AppNet). Because the Web Server and Application Server reside in two separate virtual directories, a virtual directory cannot be specified as the home directory at the Web site level. The Web site level home directory should point to the root rather than a specific virtual directory.
    To allow users accessing the Web site to go directly to the OnBase login page without having to specify the virtual directory, use redirection. For information about redirection, refer to the Microsoft ® TechNet Web site.
  2. The Application Server may be unavailable. Ensure that the Application Server's application pool is running. Then ensure that the Web Server is properly configured to communicate with the Application Server using remoting or SOAP.
  3. This issue may also occur if the Application Server's Web.config file has been directly modified to include an error, such as a duplicate section element. Contact your solution provider for help resolving this issue.
  4. A bin directory for a given application contains an invalid file. Remove any unnecessary files from the bin directory and recycle the application pool. Duplicate files should not exist in the bin directory even if one has been renamed (e.g., Hyland.Core.dll and Hyland.Core.dllold should not exist in the same directory).
  5. There may be an issue with the DNS settings or the host name on the server. If there are issues with DNS settings on a server, a temporary workaround is to change the Web Server's Web.config file to point to the IP address. The host name cannot contain an underscore character (_). If the server's machine name contains an underscore character, use its IP address instead, or change the machine name. For information about valid host names, see http://support.microsoft.com/kb/101785.
  6. There may be an issue with the security login accounts in the OnBase database. Contact your first line of support if you believe this to be the issue.
  7. The account running the application pools may not have the appropriate permissions. Grant the application pool's identity account Read permissions as described under Enabling Impersonation.
  8. There may be an issue with the impersonation account configured on the Web Server. Verify that the impersonation account has not expired and that the password has not changed. Verify that the impersonate attribute is appropriately set in the Web.config files for the Web Server and Application Server.