Search the VMware Knowledge Base (KB)
View by Article ID

vCenter Server logs report the error: SOAP session count limit reached (2004663)

  • 3 Ratings

Symptoms

  • Products, such as vCloud Director and Lab Manager, that utilize the SOAP API connections to vCenter Server log the error:

    SOAP session count limit reached

  • Connecting to vCenter Server using the vSphere Client fails with the error:

    The server could not interpret the clients request. (The remote server returned an error : 503 Server unavailable).

  • You cannot open a Remote Console (VMRC/MKS) using the vSphere Client.
  • Connecting to vCenter Server using the PowerCLI reports the error:

    Connect-VIServer : 17.01.2013 09:08:56 Connect-VIServer The request failed with HTTP status 503: Service Unavailable

  • You cannot create a new SOAP session when this issue is encountered.

Resolution

This issue is resolved in vSphere 5.0 and later. 

To resolve this issue on earlier releases, use one of these options:

Note: VMware recommends these resolutions if the vSphere Client connections continue to remain and are not cleared.
  • Configure both the timeout and max number of sessions in the vpxd.cfg file
  • Terminate active and idle sessions using the vSphere Client

Configuring both the timeout and maximum number of sessions in the vpxd.cfg file

To configure the timeout and maximum number of sessions:

  1. Open the vpxd.cfg file using a text editor.

    The vpxd.cfg file is located at:

    • Windows XP: C:\Documents and Settings\All Users\Application Data\VMware\VMware VirtualCenter\vpxd.cfg
    • Windows Server 2003: C:\Documents and Settings\All Users\Application Data\VMware\VMware VirtualCenter\vpxd.cfg
    • Windows Server 2008: C:\ProgramData\VMware\VMware VirtualCenter\vpxd.cfg

  2. Locate the <vmacore> tag within the file.
  3. Set the maxSessionCount and sessionTimeout parameters.

    For example:

    <vmacore>
    ...
      <soap>
        <maxSessionCount>500</maxSessionCount>
        <sessionTimeout>30</sessionTimeout>
      </soap>
    </vmacore>


    Note: The session timeout value is specified in minutes. In vCenter Server 2.5.x, the default values are 30 minutes and 100 sessions. You also may need to restart the VMware VirtualCenter Server service after making this change.

Terminating the Active and Idle sessions in vCenter Server 4.x or later

To terminate the Active and Idle sessions:
  1. Log in to vCenter Server using the vSphere Client.
  2. Click Home > Sessions.
  3. Right-click Active Status sessions or Idle Status sessions and click Terminate Session.
  4. Repeat steps 1 through 5 to terminate other active or idle sessions.
Note: Alternatively, you can manually clear the sessions from the vSphere Client sessions.

See Also

This Article Replaces

2041838

Update History

05/27/2013 - Correct issue with article number not appearing below Actions box. 06/18/2014 - Added a warning regarding the impact of applying this procedure to vSphere 5.x vCenter Servers, added VMware vCenter Server 4.x to products

Request a Product Feature

To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.

Feedback

  • 3 Ratings

Did this article help you?
This article resolved my issue.
This article did not resolve my issue.
This article helped but additional information was required to resolve my issue.

What can we do to improve this information? (4000 or fewer characters)




Please enter the Captcha code before clicking Submit.
  • 3 Ratings
Actions
KB: