SYMPTOM:
When an administrative user attempts to connect to the Cache Monitor in Strategy Developer from the Strategy Intelligence Server machine, the following error message is received:
The connection to this project has been lost or the Administrator has logged you out from this project. All the open windows for this project will be closed.
Upon further investigation of the DSSerrors.logs the following messages are seen:
2008-05-07 11:15:22.800-05:00 MSINetStream::net_read(), socket recv() error, error code = 10055
2008-05-07 11:15:22.800-05:00 Network: Lost connection to Strategy Intelligence Server when receiving message. Possible reasons: a) network down b) Server down or c) Server reached maximum connection capacity, d) Server is loading project(s).
2008-05-07 11:15:23.300-05:00 Network: Please retry task due to network request timeout. If problem persists, contact your network administrator.
2008-05-07 11:15:23.409-05:00 Network: Not Connected to Strategy Intelligence Server.
2008-05-07 11:15:23.409-05:00 Network: Failure to communicate with Strategy Intelligence Server.
CAUSE:
The error 10055 is a network buffer error from the Winsock component indicating that an operation on the socket could not be performed because the system lacked sufficient buffer space or because a queue was full. This is a generic error denoting some system level resource issue. This error may be seen more frequently while running the Strategy Intelligence Server on a machine with the 4GT mode enabled. This setting reduces the amount of address space available to the OS resulting in smaller buffer sizes and an increased potential for this issue.
ACTION:
This issue is related to the operating system behavior and is outside of the support that is offered by Strategy Technical Support. Typically, restarting the machine on which the Intelligence Server is hosted may resolve this issue for a while. Microsoft has a Technical note related to this error message for Windows 2003 Servers (Article 917114) that may also be useful:
Other Strategy users have had success by following the steps below:
By default, Microsoft Windows supports 5000 ephemeral TCP ports. Users can increase this range, by navigating to the following location in the registry:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters
Users may add a dword value named MaxUserPort and set it to some decimal number in the range of 5000 - 65534. Additionally, once a port is closed, it takes 4 minutes (240 seconds) before the system will reuse it. This behavior can be altered by navigating to the registry:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters
Users may add a dword value named TcpTimedWaitDelay and set it to some decimal number in the range of 30 - 300 seconds.
Registry Modification:
WARNING:
Modifying registry values incorrectly may cause serious, system-wide problems that may require the re-installation of Microsoft Windows NT. Any edit of the registry is done at the user's own risk. Since these are user-initiated changes, they are not covered by any Strategy warranty. If using Microsoft Windows NT, the user should backup the registry and/or update an Emergency Repair Disk (ERD) prior to alterations.
