Article ID: 953612 - View products that this article applies to.
This article has been archived. It is offered "as is" and will no longer be updated.
RAPID PUBLISHING ARTICLES PROVIDE INFORMATION DIRECTLY FROM WITHIN THE MICROSOFT SUPPORT ORGANIZATION. THE INFORMATION CONTAINED HEREIN IS CREATED IN RESPONSE TO EMERGING OR UNIQUE TOPICS, OR IS INTENDED SUPPLEMENT OTHER KNOWLEDGE BASE INFORMATION.
On a Windows Server 2003 based computer that has Patchlink Update Server installed, you may experience the following symptoms:
1. The server randomly stops responding.
2. If this is a file server, users cannot access the shares on this server. The following error occurs:
The network path was not found.
3. If this is a terminal server, users cannot log on to the server through the terminal service. The following error occurs:
The client could not connect to the remote computer:
Remote connection might not be enabled or computer might be too busy to accept new connection.
4. In the event log, Netlogon event 5719 is logged:
Event Type: Error
Event Source: NETLOGON
Event Category: None
Event ID: 5719
This computer was not able to set up a secure session with a domain controller in domain <domainname> due to the following:
Not enough storage is available to process this command.
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.
5. If you open Task Manager and check the "Processes" tab, you see that the GravitixService.exe process uses a lot of memory.
NOTE: To launch Task Manager, click Start>Run, type "taskmgr" (without the quotation marks) and click OK.
However, when the computer is rebooted, these symptoms temporarily disappear.
This issue may occur due to a problem with the Patchclink (GravitixService) service.
To resolve this issue, contact the manufacturer for assistance. For more information about how to upgrade the product, or for further assistance from the vendor, please visit the link below:
By the time of May 2008, they have provided “PatchLink Update Server 6.4 Service Pack 1” (Answer ID 537). This contains a hotfix which resolves the issue.
MICROSOFT AND/OR ITS SUPPLIERS MAKE NO REPRESENTATIONS OR WARRANTIES ABOUT THE SUITABILITY, RELIABILITY OR ACCURACY OF THE INFORMATION CONTAINED IN THE DOCUMENTS AND RELATED GRAPHICS PUBLISHED ON THIS WEBSITE (THE “MATERIALS”) FOR ANY PURPOSE. THE MATERIALS MAY INCLUDE TECHNICAL INACCURACIES OR TYPOGRAPHICAL ERRORS AND MAY BE REVISED AT ANY TIME WITHOUT NOTICE.
TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, MICROSOFT AND/OR ITS SUPPLIERS DISCLAIM AND EXCLUDE ALL REPRESENTATIONS, WARRANTIES, AND CONDITIONS WHETHER EXPRESS, IMPLIED OR STATUTORY, INCLUDING BUT NOT LIMITED TO REPRESENTATIONS, WARRANTIES, OR CONDITIONS OF TITLE, NON INFRINGEMENT, SATISFACTORY CONDITION OR QUALITY, MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE, WITH RESPECT TO THE MATERIALS.
(http://go.microsoft.com/fwlink/?LinkId=151500)for other considerations.
Article ID: 953612 - Last Review: January 16, 2015 - Revision: 2.0