Re: SP2 on Windows 2003 Terminal Server getting "Low on Registry S

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

The size of SystemRoot%\System32\Config\System is 5MB. Time stamp is 7:51
AM, which probably when I rebooted. Next time before I reboot, I'll check
this file size and time/date stamp.

Regarding the other reply, the only error messages I have seen are what I
posted originally.

Thanks.

"Helge Klein" wrote:

The error message you posted is internally called
ERROR_REGISTRY_QUOTA_LIMIT. It effectively means that the system hive
of the registry is exceeding the pre-configured quota built into the
OS. You can do a quick check be looking at the size of the file
backing the hive:

%SystemRoot%\System32\Config\System

A size of more than 10-20 MB I would deem unusual. The quota is, as
far as I know, somewhere around 100 MB.

If that (too large system hive) is indeed your problem then you need
to find out:

a) where all that data is stored in the system hive
b) where that data comes from

A somewhat clumsy mechanism to answer question a) is to use regedit to
export the complete system hive (HKLM\System) to a .reg file. You can
then examine the contents of that file and you should be able to
determine where most of the data is stored.

Please post your findings - I am really interested in the results.

I hope this helps.

Helge

==================
Please visit my blog:
http://it-from-inside.blogspot.com
==================

On 9 Aug., 16:06, Dennis_S <Denn...@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
After installing SP2 on Windows 2003 Terminal Server I came in the next
morning and saw on the server "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."

Users logging onto TS get "Windows was unable to load the profile but has
logged on with the default profile system. Default - Insufficiant system
resources exist to complete the requested service."

It appears that up to six-eight users are able to log on before a user gets
the Unable to load profile. Log a couple users off and another is able to
log on.

If reboot the server and it is fine for 24 hours. After that the
application pop-up appears on the server the next day, we are back to the
same problem. Reboot the server, and again we are OK for 24 hours.

Has anyone else run into this? If so, how did you get it resolved?

Thanks much!



.

Relevant Pages

  • Re: Windows XP changing User Profile
    ... Created a restore point made the change to the registry and did a reboot. ... HP_owner and Administrator and the directories are still under C:\Documents ... *** profile folder) but you should really leave them alone. ...
    (microsoft.public.windowsxp.general)
  • Re: SP2 on Windows 2003 Terminal Server getting "Low on Registry S
    ... I am working with Microsoft support on this. ... more like a damaged registry file. ... MCSE, CCEA, Microsoft MVP - Terminal Server ... If reboot the server and it is fine for 24 hours. ...
    (microsoft.public.windows.terminal_services)
  • Re: HKLMSoftware key grayed out
    ... I hadn't originally thought about spyware or viruses, since this is a server ... get to the point of finding any processes that would have the registry ... I'm going to go ahead and reboot the ...
    (microsoft.public.win2000.registry)
  • Another disaster recovery exercise (but not yet)...
    ... I updated a client's Server. ... indeed, I reboot before updating, and after ). ... Chkdsk is all good on all drives. ... Enabling boot logging option at boot - well, ...
    (microsoft.public.backoffice.smallbiz2000)
  • RE: Event 19011: SBS Monitoring services wont auto-start
    ... automatically start when rebooting the SBS server. ... Let us ensure the MSSQL$SBSMONITORING service and the Microsoft Exchange ... Please clean the Event logs in event viewer and then reboot the server, ... This newsgroup only focuses on SBS technical issues. ...
    (microsoft.public.windows.server.sbs)