Session Timeout setting for CA Asset Portfolio Management
search cancel

Session Timeout setting for CA Asset Portfolio Management

book

Article ID: 43738

calendar_today

Updated On:

Products

CA IT Asset Manager ASSET PORTFOLIO MGMT- SERVER CA Service Management - Asset Portfolio Management

Issue/Introduction

After configuring SSO in Asset Portfolio Manager initial functionality tests are successful. 

When users are actually using the product, they experience an error stating:

Server Error in '/ITAM' Application

Value cannot be null

Parameter name: stringToEscape

Source Error

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.

[ArgumentNullException: Value cannot be null.
Parameter name: stringToEscape]

This is resolved temporarily by removing reloading the original SSO URL or clearing browser cache, but the issue still occurs later on.

How can we resolve this permanently?

Environment

All versions of Asset Portfolio Manager

Cause

The Idle Time out (minutes) setting in IIS is less than the corresponding session in the configured SSO solution.

Resolution

The session timeout is controlled from a setting in Internet Information Systems (IIS) named: Idle timeout (in minutes)

This setting controls how long the user interface remains idle before a timeout occurs and the user must log back into the application.

For example, if the setting is 20 minutes, when the user interface is idle for more than 20 minutes, the next time the user clicks on the screen, they will be prompted to login again to regain access. 

To change the idle timeout setting: 

1. Launch the Internet Information Systems Manager (IIS Manager) and  expand the IIS server name node

2.  Highlight application pools, then select the ITAM application pool

3.  Click on advanced settings and view the 'idle timeout (in minutes)' setting. 

4.  The default is normally 20 minutes.  Increase this value to match or slightly greater than configured in SSO.

5.  Perform an IISRESET for the changes to take effect.