Servicing Director Customer Self-Service Event Viewer Warning: "...The input stream is not a valid binary format..."

Servicing Director Customer Self-Service Event Viewer Warning: "...The input stream is not a valid binary format..."

Log Name:      Application
Source:        ASP.NET 4.0.30319.0
Date:          7/11/2016 11:02:51 AM
Event ID:      1309
Task Category: Web Event
Level:         Warning
Keywords:      Classic
User:          N/A
Computer:      <your server name>
Description:
Event code: 3005 
Event message: An unhandled exception has occurred. 
Event time: 7/11/2016 11:02:51 AM 
Event time (UTC): 7/11/2016 6:02:51 PM 
Event ID: bf13863d855a4f1286e76c725749937e 
Event sequence: 8 
Event occurrence: 2 
Event detail code: 0 
 
Application information: 
    Application domain: /LM/W3SVC/1/ROOT/ILSWeb-1-131127336467407198 
    Trust level: Full 
    Application Virtual Path: /ILSWeb 
    Application Path: C:\inetpub\wwwroot\ILSWeb\ 
    Machine name: <your server name>
 
Process information: 
    Process ID: 9556 
    Process name: w3wp.exe 
    Account name: IIS APPPOOL\ILSWeb1 
 
Exception information: 
    Exception type: SerializationException 
    Exception message: The input stream is not a valid binary format. The starting contents (in bytes) are: 3C-21-44-4F-43-54-59-50-45-20-48-54-4D-4C-20-50-55 ...

Server stack trace: 
   at System.Runtime.Serialization.Formatters.Binary.SerializationHeaderRecord.Read(__BinaryParser input)
   at System.Runtime.Serialization.Formatters.Binary.__BinaryParser.ReadSerializationHeaderRecord()
   at System.Runtime.Serialization.Formatters.Binary.__BinaryParser.Run()
   at System.Runtime.Serialization.Formatters.Binary.ObjectReader.Deserialize(HeaderHandler handler, __BinaryParser serParser, Boolean fCheck, Boolean isCrossAppDomain, IMethodCallMessage methodCallMessage)
   at System.Runtime.Serialization.Formatters.Binary.BinaryFormatter.Deserialize(Stream serializationStream, HeaderHandler handler, Boolean fCheck, Boolean isCrossAppDomain, IMethodCallMessage methodCallMessage)
   at System.Runtime.Remoting.Channels.CoreChannel.DeserializeBinaryResponseMessage(Stream inputStream, IMethodCallMessage reqMsg, Boolean bStrictBinding)
   at System.Runtime.Remoting.Channels.BinaryClientFormatterSink.SyncProcessMessage(IMessage msg)

Exception rethrown at [0]: 
   at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
   at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
   at ILSBusInterfaces.IUserDataProvider.IsCustomerSelfServiceLicensed()
   at ILSWebCommon.SessionObjects.<get_IsCSSLicensed>b__0(String name)
   at ILSWebCommon.GlobalVariables.Get(String name, Func`2 updateCacheFunction)
   at ILSWebCommon.SessionObjects.get_IsCSSLicensed()
   at ILSWebCommon.WebPageUser.ValidateUserName(String userName, Boolean redirectValidateAccess, String& error, Boolean singleSignOnUser)
   at ILSWeb.LogOn.btnNext_Click(Object sender, EventArgs e)
   at System.Web.UI.WebControls.Button.OnClick(EventArgs e)
   at System.Web.UI.WebControls.Button.RaisePostBackEvent(String eventArgument)
   at System.Web.UI.WebControls.Button.System.Web.UI.IPostBackEventHandler.RaisePostBackEvent(String eventArgument)
   at System.Web.UI.Page.RaisePostBackEvent(IPostBackEventHandler sourceControl, String eventArgument)
   at System.Web.UI.Page.RaisePostBackEvent(NameValueCollection postData)
   at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)

 Request information: 
    Request URL: https://<your server name>/ILSWeb/Logon.aspx 
    Request path: /ILSWeb/Logon.aspx 
    User host address: <your server address>
    User:  
    Is authenticated: False 
    Authentication Type:  
    Thread account name: IIS APPPOOL\ILSWeb1 
 
Thread information: 
    Thread ID: 3 
    Thread account name: IIS APPPOOL\ILSWeb1 
    Is impersonating: False 
    Stack trace:    at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
   at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
   at ILSBusInterfaces.IUserDataProvider.IsCustomerSelfServiceLicensed()
   at ILSWebCommon.SessionObjects.<get_IsCSSLicensed>b__0(String name)
   at ILSWebCommon.GlobalVariables.Get(String name, Func`2 updateCacheFunction)
   at ILSWebCommon.SessionObjects.get_IsCSSLicensed()
   at ILSWebCommon.WebPageUser.ValidateUserName(String userName, Boolean redirectValidateAccess, String& error, Boolean singleSignOnUser)
   at ILSWeb.LogOn.btnNext_Click(Object sender, EventArgs e)
   at System.Web.UI.WebControls.Button.OnClick(EventArgs e)
   at System.Web.UI.WebControls.Button.RaisePostBackEvent(String eventArgument)
   at System.Web.UI.WebControls.Button.System.Web.UI.IPostBackEventHandler.RaisePostBackEvent(String eventArgument)
   at System.Web.UI.Page.RaisePostBackEvent(IPostBackEventHandler sourceControl, String eventArgument)
   at System.Web.UI.Page.RaisePostBackEvent(NameValueCollection postData)
   at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)

Root Cause:

This Windows Event Viewer Application log ASP.NET warning message indicates an error communicating with your Customer Self-Service business application server. 
The Customer Self-Service borrower web server or investor web server communicates with the business application server you defined in the web server Client.Config file.  You defined the business application server when the installation or upgrade guide led you to edit the Client.Config file. 

The exact root cause of the error communicating is not shown by this error detail, but generally speaking the business application server has responded to the web server with a Microsoft IIS (Internet Information Server) or HTTP level error, returning an error message instead of readable data.

Workaround:

Have your system administrator or local IT review the following:

  1. Confirm the hostname you entered when editing the web server Client.Config is correct, and it is the server where the Customer Self-Service business application server product (ILSWebBus) is installed.
  2. Locate the attempt by your web server to communicate to the business application server in the Microsoft-provided IIS logs on the business application server. The log record for the communication should show a Status value, which would be the HTTP code for the error in the communication.  Microsoft support resources can cross reference their HTTP code you found in the log to a fuller description of the code and perhaps lead you to the Microsoft recommended troubleshooting.
  3. Search the business application server Windows Event Viewer Application logs for ASP.NET errors also related to the failures to communicate, which can also lead your next troubleshooting steps.
  4. If you would like to troubleshoot and review your findings, submit a case through Case Management and attach your findings to the case.

ArticleNumber:

000043977