Analysis for Office timeout issues (HTTP request unouthorized)

SAP BusinessObjects 4.0/4.1 Analysis for Office 1.4

If you try to connect to a new data source and you notice after an inactivity time of 30 minutes the following error message, you may have to increase the timeout parameter in your web.xml file of your dswsbobje-service.

- Error: General .NET Exception: 
The HTTP request is unauthorized with client authentication scheme 'Anonymous'. The authentication header received from the server was 'Negotiate'.The remote server returned an error: (401) Unauthorized. 

>> General .NET Exception: 
System received an expired SSO ticket 
at SAP.Middleware.Connector.RfcConnection.ThrowRfcErrorMsg() 
at SAP.Middleware.Connector.RfcConnection.ReadBytes(Byte* buffer, Int32 count) 
at SAP.Middleware.Connector.RfcConnection.ReadRfcIDBegin(Int32& length) 
at SAP.Middleware.Connector.RfcConnection.ReadUpTo(RFCGET readState, RfcFunction function, RFCID toRid) 
at SAP.Middleware.Connector.RfcConnection.RfcReceive(RfcFunction function) 
at SAP.Middleware.Connector.RfcConnection.ConnectAsClient(RfcDestination destination, Boolean forRepository)

It's is quite common and well documented to increase the timeout value for Launch Pad, but you can do this also for the dswsbobje-service to overcome that error.

To do that, open your web.xml-file (\SAP BusinessObjects\tomcat\webapps\dswsbobje\WEB-INF) and add the following lines inside the web-app-tag to increase the timeout parameter to 120 minutes in this example.

    <session-config>
        <session-timeout>120</session-timeout>
    </session-config>

Restart your Tomcat-Service.