Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Guide That Contains This Content
[+] Expand All
[-] Collapse All

    Changing the Report Generation Timeout

    Use this procedure to change the time that the PSM client waits for the PSM server to finish generating a report.

    Report generation might require the PSM server to collect information from all network elements in the network. This might take some time, especially In slow networks. If the PSM client times out while waiting for report generation to complete, you can adjust the PSM client timeout value to be more appropriate for your network.

    You do not need to change the timeout value if report generation works for your network.

    When report generation fails due to a timeout, you will see an error icon in the lower right corner of the PSM client window. If you click on the error icon, you will see the following generic error indicating PSM client-server communication problems:

    Figure 1: PSM Client Communication Timeout

    PSM Client
Communication Timeout

    The parameter that dictates how long the PSM client waits for the report is found on the PSM client machine.

    1. Locate the file in the <PSM_client_installation_folder>/psmclient folder.
    2. Open the file using a text editing application such as WordPad and change the ems.client.reports.socket.timeout parameter. The units are in milliseconds.

      For example, this sets the timeout to 900000 milliseconds or 15 minutes: ems.client.reports.socket.timeout = 900000

      Note: If you installed the PSM client using the supplied installer, you might need to edit this file as an administrator. In Windows 10, click on the Start menu and go to All apps>Windows Accessories and scroll down to WordPad, right-click and select More>Run as administrator. Then open the file from within the WordPad application.

    3. Save and close the file.

      Note: The updated setting takes effect the next time you launch the PSM client.

    4. Close and relaunch the PSM client.

    Modified: 2016-12-20