Low on Registry Space
Hi Experts,
I have a Terminal Server 2003 SP2, and when I logon I get an error:
"Windows - Low on Registry Space
The system has reached the maximum size allowed for the system part of the registry. Additional storage requests will be ignored."
Jim
I have a Terminal Server 2003 SP2, and when I logon I get an error:
"Windows - Low on Registry Space
The system has reached the maximum size allowed for the system part of the registry. Additional storage requests will be ignored."
Jim
ASKER
Thank TKs, however the article is a bit off the mark. It refers to items in the registry RegistrySizeLimit and PagedPoolSize. Further investigation shows
RegistrySizeLimit
This entry is not used by Windows Server 2003. In older versions of Windows Server, it specified the maximum amount of memory and disk space that the registry could consume. Since I am using Windows Server 2003, this does not apply.
PagePoolSize
There is some potential here, because it refers to Memory Management, and this has lead me to check the Virtual management settings, where I noted that it is set to Custom rather than System managed. I have changed this and the changes will only occur after a reboot (after hours).
I will add another comment after the reboot, to see if this has resolved the issue
Jim
RegistrySizeLimit
This entry is not used by Windows Server 2003. In older versions of Windows Server, it specified the maximum amount of memory and disk space that the registry could consume. Since I am using Windows Server 2003, this does not apply.
PagePoolSize
There is some potential here, because it refers to Memory Management, and this has lead me to check the Virtual management settings, where I noted that it is set to Custom rather than System managed. I have changed this and the changes will only occur after a reboot (after hours).
I will add another comment after the reboot, to see if this has resolved the issue
Jim
Hi Jim,
I found a couple other references that might help you troubleshoot this. Also, I made sure they relate to Windows Server 2003. It looks like after installing SP2 other people were having the same problem.
http://www.eggheadcafe.com/software/aspnet/30493930/sp2-on-windows-2003-termi.aspx
http://www.eggheadcafe.com/software/aspnet/29678204/windows--low-on-registry.aspx
http://www.microsoft.com/communities/newsgroups/en-us/default.aspx?dg=microsoft.public.windows.terminal_services&tid=addf1c90-7d93-4d7f-afeb-d62e32902c31&cat=&lang=&cr=&sloc=&p=1
I hope these help.
TK
I found a couple other references that might help you troubleshoot this. Also, I made sure they relate to Windows Server 2003. It looks like after installing SP2 other people were having the same problem.
http://www.eggheadcafe.com/software/aspnet/30493930/sp2-on-windows-2003-termi.aspx
http://www.eggheadcafe.com/software/aspnet/29678204/windows--low-on-registry.aspx
http://www.microsoft.com/communities/newsgroups/en-us/default.aspx?dg=microsoft.public.windows.terminal_services&tid=addf1c90-7d93-4d7f-afeb-d62e32902c31&cat=&lang=&cr=&sloc=&p=1
I hope these help.
TK
ASKER
Hi TK,
Thanks for these, I will check them out today.
Just a note...the things we learn. The Term Servers would not accept any logon this morning after changing the Virtual Memory to System. Changing it back to custom resloved this, and it looks like Term Servers MUST have custom managed Virtual memory
Jim
Thanks for these, I will check them out today.
Just a note...the things we learn. The Term Servers would not accept any logon this morning after changing the Virtual Memory to System. Changing it back to custom resloved this, and it looks like Term Servers MUST have custom managed Virtual memory
Jim
ASKER
Thanks TK, these links are really good. Generally it points to memory management. I note that the recommended pagefile for my server is 5374MB, but only 3819 is allocated.
The Pagefile settings are set to Custom with a Maximum size of 4092MB. I cannot increase this becuase I get a dialog
"Enter a maximum page file size that is greater than or equal to the initial page file size, and less than 4096MB"
As I described above if I set the seetings to "System managed size", the server will not accept remote desktop sessions.
I feel that this is the problem. Do you know if I can and how to increase the custom settings beyond 4096
Jim
The Pagefile settings are set to Custom with a Maximum size of 4092MB. I cannot increase this becuase I get a dialog
"Enter a maximum page file size that is greater than or equal to the initial page file size, and less than 4096MB"
As I described above if I set the seetings to "System managed size", the server will not accept remote desktop sessions.
I feel that this is the problem. Do you know if I can and how to increase the custom settings beyond 4096
Jim
Hi Jim,
The maximum supported RAM on 32-bit operating systems is 4GB's. That should be more than enough for your needs. I think "something" is gobbling up your memory.
1. How much RAM do you have in your server?
2. Have you tried cleaning out unnecessary programs and temp files. CCleaner is a good program for cleaning out temp files. (www.ccleaner.com.)
3. If 1 and 2 do not help, you could try compressing/optimizing the registry with a utility such as NTREGOPT (http://www.larshederer.homepage.t-online.de/erunt/)
Let me know if any of those suggestions help.
TK
The maximum supported RAM on 32-bit operating systems is 4GB's. That should be more than enough for your needs. I think "something" is gobbling up your memory.
1. How much RAM do you have in your server?
2. Have you tried cleaning out unnecessary programs and temp files. CCleaner is a good program for cleaning out temp files. (www.ccleaner.com.)
3. If 1 and 2 do not help, you could try compressing/optimizing the registry with a utility such as NTREGOPT (http://www.larshederer.homepage.t-online.de/erunt/)
Let me know if any of those suggestions help.
TK
ASKER
Hi TK,
You are spot on there is an updated application that is consuming huges amounts of RAM. I have isolated this application on a single dedicated server and the other Term Servers are now opperating without stress, leaving the isolated server to grasp for resources.
There is not much that can be done, except to wait for the program developers to release a fix.
Thanks for your help....you have certainly earned the points.
Jim
You are spot on there is an updated application that is consuming huges amounts of RAM. I have isolated this application on a single dedicated server and the other Term Servers are now opperating without stress, leaving the isolated server to grasp for resources.
There is not much that can be done, except to wait for the program developers to release a fix.
Thanks for your help....you have certainly earned the points.
Jim
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
I am facing this same issue on 2 win2003 Ent. SP2 terminal servers. Both have reported the log on registry space error. The 1st one hasn't done since i used NTREGOPT in safe mode, but now the 2nd is giving these errors and then needs a reboot.
How would i go about finding out wich program/service is causing this behavior ?
How would i go about finding out wich program/service is causing this behavior ?
GoBien,
Did you find what was causing this. I had the exact same problem and it surfaced at the same time as yours. I am suspecting an update but haven't narrowed it down. I don't have any application sucking up a huge amount of RAM.
I have tried compressing with NTREGOPT, cleaning the registry with JV16
I tired sfc to restore windows files
I removed the page files & rebuilt them.
Nothing has worked. I already have my page files set to custom size (you can go past the 4092 limit by using multiple physical drives) and the error only appears when I log onto the consol. A remote admin login does not generate this error.
Did you find what was causing this. I had the exact same problem and it surfaced at the same time as yours. I am suspecting an update but haven't narrowed it down. I don't have any application sucking up a huge amount of RAM.
I have tried compressing with NTREGOPT, cleaning the registry with JV16
I tired sfc to restore windows files
I removed the page files & rebuilt them.
Nothing has worked. I already have my page files set to custom size (you can go past the 4092 limit by using multiple physical drives) and the error only appears when I log onto the consol. A remote admin login does not generate this error.
@FJS159:
I have solved this problem by installing a microsoft tool called:
User Profile Hive Cleanup Service. http://www.microsoft.com/downloadS/details.aspx?FamilyID=1b286e6d-8912-4e18-b570-42470e2f3582&displaylang=en
This basicly makes it so that the registry from the users is correctly closed after they log off.
Good luck
I have solved this problem by installing a microsoft tool called:
User Profile Hive Cleanup Service. http://www.microsoft.com/downloadS/details.aspx?FamilyID=1b286e6d-8912-4e18-b570-42470e2f3582&displaylang=en
This basicly makes it so that the registry from the users is correctly closed after they log off.
Good luck
Thanks GoBieN,
I believe I have tracked my problem to Symantec Antivirus 10.2
I noticed shortly after my registry error there was a time out error in the log file for Symantec. I uninstalled it and all my errors went away. I reinstalled it and instantly I started getting memory errors and the registry full error resurfaced. The memory errors occur when Symantec is doing a startup or full system scan. Real time protection appears to be working. This doesn't come as much of a surprise. A while ago I discovered Symantec has a memory leak when scanning SQL data files. Apparently they knew this and just told me to set the files in the exclusion list. Why they didn't make it an automatic exclusion, I do not know. Anyways, I suspect it is having issues with another file now. This weekend I am installing Symantic Endpoint 11 and hoping the problem has been fixed. But this also explains why it only happens during consol logins, since different files are scanned at that time then when an RDP connection is made.
I believe I have tracked my problem to Symantec Antivirus 10.2
I noticed shortly after my registry error there was a time out error in the log file for Symantec. I uninstalled it and all my errors went away. I reinstalled it and instantly I started getting memory errors and the registry full error resurfaced. The memory errors occur when Symantec is doing a startup or full system scan. Real time protection appears to be working. This doesn't come as much of a surprise. A while ago I discovered Symantec has a memory leak when scanning SQL data files. Apparently they knew this and just told me to set the files in the exclusion list. Why they didn't make it an automatic exclusion, I do not know. Anyways, I suspect it is having issues with another file now. This weekend I am installing Symantic Endpoint 11 and hoping the problem has been fixed. But this also explains why it only happens during consol logins, since different files are scanned at that time then when an RDP connection is made.
On another Terminal Server I installed UPHClean, it was still running Symantec 10.2. I found the following information in my log files that confimed Symantec is my culprit.
Event Type: Information
Event Source: UPHClean
Event Category: None
Event ID: 1201
Date: 09/15/2008
Time: 7:11:05 AM
User: XXX
Computer: XXX
Description:
The following handles in user profile hive XXX have been closed because they were preventing the profile from unloading successfully:
Rtvscan.exe (1772)
HKCU\Software\Intel\LANDes
Event Type: Information
Event Source: UPHClean
Event Category: None
Event ID: 1201
Date: 09/15/2008
Time: 7:11:05 AM
User: XXX
Computer: XXX
Description:
The following handles in user profile hive XXX have been closed because they were preventing the profile from unloading successfully:
Rtvscan.exe (1772)
HKCU\Software\Intel\LANDes
http://www.tek-tips.com/viewthread.cfm?qid=845734
TK