SP2 on Windows 2003 Terminal Server getting "Low on Registry Space

[Guest Dennis_S]

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!

[Guest Vera Noest [MVP]]

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

 

Ay profile unload errors in the registry?

If so, install UPHClean

http://www.microsoft.com/downloads/details.aspx?FamilyId=1B286E6D-

8912-4E18-B570-42470E2F3582

_________________________________________________________

Vera Noest

MCSE, CCEA, Microsoft MVP - Terminal Server

TS troubleshooting: http://ts.veranoest.net

*----------- Please reply in newsgroup -------------*

 

=?Utf-8?B?RGVubmlzX1M=?= <DennisS@discussions.microsoft.com> wrote

on 09 aug 2007:

> 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!

[Guest Helge Klein]

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

 

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...@discussions.microsoft.com> 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!

[Guest Dennis_S]

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

 

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

 

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...@discussions.microsoft.com> 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!

>

>

>

[Guest PRMolina]

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

 

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

 

Dennis:

 

How much disk space do you have left when you get these error messages? Is

something chewing up free space on your drives?

 

-Paul

[Guest Dennis_S]

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

 

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

 

Before rebooting this morning, the %SystemRoot%\System32\Config\System file

was 5,120 KB. The file size remains the same before and after rebooting.

Again the error is logged in the event viewer at right around the 24 hour

time frame each day since upgrading to SP2. Never had this happen prior to

SP2.

 

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...@discussions.microsoft.com> 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!

>

>

>

[Guest Vera Noest [MVP]]

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

 

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

 

There must be warnings in the EventLog on the server when this

happens.

Can you post all EventID's and Sources? Those are easier to search

for, like on http://www.eventid.net/search.asp

_________________________________________________________

Vera Noest

MCSE, CCEA, Microsoft MVP - Terminal Server

TS troubleshooting: http://ts.veranoest.net

___ please respond in newsgroup, NOT by private email ___

 

=?Utf-8?B?RGVubmlzX1M=?= <DennisS@discussions.microsoft.com> wrote

on 10 aug 2007 in microsoft.public.windows.terminal_services:

> Before rebooting this morning, the

> %SystemRoot%\System32\Config\System file was 5,120 KB. The file

> size remains the same before and after rebooting. Again the

> error is logged in the event viewer at right around the 24 hour

> time frame each day since upgrading to SP2. Never had this

> happen prior to SP2.

>

> 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...@discussions.microsoft.com>

>> 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!

[Guest Dennis_S]

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

 

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

 

Two Event IDs 26 & 333

Source - Application Popup (for both IDs)

 

Event ID 333 - An I/O operation initiated by the Registry failed

unrecoverably. The Registry could not read in or write out or flush one of

the files that contain the system's image of the Registry. This is in the

error log, but there is no popup.

 

For the last five days, Event ID 26 (applcation popup) which shows on the

screen saying Low on Registry space. The system has reached the maximum size

allowed... happens almost on the hour every 24 hours.

 

When I reboot the file in the config folder update to the current date and

time. BTW, there is plent of disk space.

 

"Vera Noest [MVP]" wrote:

> There must be warnings in the EventLog on the server when this

> happens.

> Can you post all EventID's and Sources? Those are easier to search

> for, like on http://www.eventid.net/search.asp

> _________________________________________________________

> Vera Noest

> MCSE, CCEA, Microsoft MVP - Terminal Server

> TS troubleshooting: http://ts.veranoest.net

> ___ please respond in newsgroup, NOT by private email ___

>

> =?Utf-8?B?RGVubmlzX1M=?= <DennisS@discussions.microsoft.com> wrote

> on 10 aug 2007 in microsoft.public.windows.terminal_services:

>

> > Before rebooting this morning, the

> > %SystemRoot%\System32\Config\System file was 5,120 KB. The file

> > size remains the same before and after rebooting. Again the

> > error is logged in the event viewer at right around the 24 hour

> > time frame each day since upgrading to SP2. Never had this

> > happen prior to SP2.

> >

> > 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...@discussions.microsoft.com>

> >> 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!

>

[Guest Vera Noest [MVP]]

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

 

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

 

Ough! That doesn't sound like a "normal" profile load error, sound

more like a damaged registry file.

 

Have a look at the suggestions on EventID.net for this error.

Unfortunately, the concensus seems to be to install hotfix 898060,

but since that is already included in SP2, it's not applicable to

your server. But there are some other ideas there that might apply

(anti-virus software, disk quota, hard disk error):

 

http://www.eventid.net/display.asp?eventid=333&eventno=5757

&source=Application%20Popup&phase=1

 

_________________________________________________________

Vera Noest

MCSE, CCEA, Microsoft MVP - Terminal Server

TS troubleshooting: http://ts.veranoest.net

___ please respond in newsgroup, NOT by private email ___

 

=?Utf-8?B?RGVubmlzX1M=?= <DennisS@discussions.microsoft.com> wrote

on 13 aug 2007 in microsoft.public.windows.terminal_services:

> Two Event IDs 26 & 333

> Source - Application Popup (for both IDs)

>

> Event ID 333 - An I/O operation initiated by the Registry failed

> unrecoverably. The Registry could not read in or write out or

> flush one of the files that contain the system's image of the

> Registry. This is in the error log, but there is no popup.

>

> For the last five days, Event ID 26 (applcation popup) which

> shows on the screen saying Low on Registry space. The system

> has reached the maximum size allowed... happens almost on the

> hour every 24 hours.

>

> When I reboot the file in the config folder update to the

> current date and time. BTW, there is plent of disk space.

>

> "Vera Noest [MVP]" wrote:

>

>> There must be warnings in the EventLog on the server when this

>> happens.

>> Can you post all EventID's and Sources? Those are easier to

>> search for, like on http://www.eventid.net/search.asp

>> _________________________________________________________

>> Vera Noest

>> MCSE, CCEA, Microsoft MVP - Terminal Server

>> TS troubleshooting: http://ts.veranoest.net

>> ___ please respond in newsgroup, NOT by private email ___

>>

>> =?Utf-8?B?RGVubmlzX1M=?= <DennisS@discussions.microsoft.com>

>> wrote on 10 aug 2007 in

>> microsoft.public.windows.terminal_services:

>>

>> > Before rebooting this morning, the

>> > %SystemRoot%\System32\Config\System file was 5,120 KB. The

>> > file size remains the same before and after rebooting. Again

>> > the error is logged in the event viewer at right around the

>> > 24 hour time frame each day since upgrading to SP2. Never

>> > had this happen prior to SP2.

>> >

>> > 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...@discussions.microsoft.com> 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!

[Guest Dennis_S]

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

 

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

 

I am working with Microsoft support on this. Wednesday night we ran chkreg

in recovery console. That reduced the System hive file by about 2 MB. Came

in this morning and had the same error message. Log entry was created 48

hours almost to the minute from the last one. Probably would have happened

in 24 hours, but we rebooted the system when working on the registry Wed

night.

 

"Vera Noest [MVP]" wrote:

> Ough! That doesn't sound like a "normal" profile load error, sound

> more like a damaged registry file.

>

> Have a look at the suggestions on EventID.net for this error.

> Unfortunately, the concensus seems to be to install hotfix 898060,

> but since that is already included in SP2, it's not applicable to

> your server. But there are some other ideas there that might apply

> (anti-virus software, disk quota, hard disk error):

>

> http://www.eventid.net/display.asp?eventid=333&eventno=5757

> &source=Application%20Popup&phase=1

>

> _________________________________________________________

> Vera Noest

> MCSE, CCEA, Microsoft MVP - Terminal Server

> TS troubleshooting: http://ts.veranoest.net

> ___ please respond in newsgroup, NOT by private email ___

>

> =?Utf-8?B?RGVubmlzX1M=?= <DennisS@discussions.microsoft.com> wrote

> on 13 aug 2007 in microsoft.public.windows.terminal_services:

>

> > Two Event IDs 26 & 333

> > Source - Application Popup (for both IDs)

> >

> > Event ID 333 - An I/O operation initiated by the Registry failed

> > unrecoverably. The Registry could not read in or write out or

> > flush one of the files that contain the system's image of the

> > Registry. This is in the error log, but there is no popup.

> >

> > For the last five days, Event ID 26 (applcation popup) which

> > shows on the screen saying Low on Registry space. The system

> > has reached the maximum size allowed... happens almost on the

> > hour every 24 hours.

> >

> > When I reboot the file in the config folder update to the

> > current date and time. BTW, there is plent of disk space.

> >

> > "Vera Noest [MVP]" wrote:

> >

> >> There must be warnings in the EventLog on the server when this

> >> happens.

> >> Can you post all EventID's and Sources? Those are easier to

> >> search for, like on http://www.eventid.net/search.asp

> >> _________________________________________________________

> >> Vera Noest

> >> MCSE, CCEA, Microsoft MVP - Terminal Server

> >> TS troubleshooting: http://ts.veranoest.net

> >> ___ please respond in newsgroup, NOT by private email ___

> >>

> >> =?Utf-8?B?RGVubmlzX1M=?= <DennisS@discussions.microsoft.com>

> >> wrote on 10 aug 2007 in

> >> microsoft.public.windows.terminal_services:

> >>

> >> > Before rebooting this morning, the

> >> > %SystemRoot%\System32\Config\System file was 5,120 KB. The

> >> > file size remains the same before and after rebooting. Again

> >> > the error is logged in the event viewer at right around the

> >> > 24 hour time frame each day since upgrading to SP2. Never

> >> > had this happen prior to SP2.

> >> >

> >> > 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...@discussions.microsoft.com> 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!

>

[Guest Helge Klein]

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

 

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

 

This sounds very strange indeed. I am sorry I have no more

recommendations, but please keep us posted on your findings.

 

Helge

 

==================

Please visit my blog:

http://it-from-inside.blogspot.com

==================

 

On 17 Aug., 14:24, Dennis_S <Denn...@discussions.microsoft.com> wrote:

> I am working with Microsoft support on this. Wednesday night we ran chkreg

> in recovery console. That reduced the System hive file by about 2 MB. Came

> in this morning and had the same error message. Log entry was created 48

> hours almost to the minute from the last one. Probably would have happened

> in 24 hours, but we rebooted the system when working on the registry Wed

> night.

>

>

>

>

>

> "Vera Noest [MVP]" wrote:

> > Ough! That doesn't sound like a "normal" profile load error, sound

> > more like a damaged registry file.

>

> > Have a look at the suggestions on EventID.net for this error.

> > Unfortunately, the concensus seems to be to install hotfix 898060,

> > but since that is already included in SP2, it's not applicable to

> > your server. But there are some other ideas there that might apply

> > (anti-virus software, disk quota, hard disk error):

>

> >http://www.eventid.net/display.asp?eventid=333&eventno=5757

> > &source=Application%20Popup&phase=1

>

> > _________________________________________________________

> > Vera Noest

> > MCSE, CCEA, Microsoft MVP - Terminal Server

> > TS troubleshooting: http://ts.veranoest.net

> > ___ please respond in newsgroup, NOT by private email ___

>

> > =?Utf-8?B?RGVubmlzX1M=?= <Denn...@discussions.microsoft.com> wrote

> > on 13 aug 2007 in microsoft.public.windows.terminal_services:

>

> > > Two Event IDs 26 & 333

> > > Source - Application Popup (for both IDs)

>

> > > Event ID 333 - An I/O operation initiated by the Registry failed

> > > unrecoverably. The Registry could not read in or write out or

> > > flush one of the files that contain the system's image of the

> > > Registry. This is in the error log, but there is no popup.

>

> > > For the last five days, Event ID 26 (applcation popup) which

> > > shows on the screen saying Low on Registry space. The system

> > > has reached the maximum size allowed... happens almost on the

> > > hour every 24 hours.

>

> > > When I reboot the file in the config folder update to the

> > > current date and time. BTW, there is plent of disk space.

>

> > > "Vera Noest [MVP]" wrote:

>

> > >> There must be warnings in the EventLog on the server when this

> > >> happens.

> > >> Can you post all EventID's and Sources? Those are easier to

> > >> search for, like onhttp://www.eventid.net/search.asp

> > >> _________________________________________________________

> > >> Vera Noest

> > >> MCSE, CCEA, Microsoft MVP - Terminal Server

> > >> TS troubleshooting: http://ts.veranoest.net

> > >> ___ please respond in newsgroup, NOT by private email ___

>

> > >> =?Utf-8?B?RGVubmlzX1M=?= <Denn...@discussions.microsoft.com>

> > >> wrote on 10 aug 2007 in

> > >> microsoft.public.windows.terminal_services:

>

> > >> > Before rebooting this morning, the

> > >> > %SystemRoot%\System32\Config\System file was 5,120 KB. The

> > >> > file size remains the same before and after rebooting. Again

> > >> > the error is logged in the event viewer at right around the

> > >> > 24 hour time frame each day since upgrading to SP2. Never

> > >> > had this happen prior to SP2.

>

> > >> > 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...@discussions.microsoft.com> 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!

[Guest anders.larsson@rixmail.se]

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

 

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

 

Hello.

 

Since we have the exact same problem on three of our TS-Serv2k3-SP2, I

was just wondering..

 

Have you found a way to solve this problem?

 

Hopefully

 

Anders

[Guest coryheins@gmail.com]

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

 

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

 

We are having the same issue too.

 

Anyone got a fix yet?

[Guest coryheins@gmail.com]

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

 

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

 

On Aug 27, 9:09 am, coryhe...@gmail.com wrote:

> We are having the same issue too.

>

> Anyone got a fix yet?

 

KB 312362

[Guest PM]

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

 

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

 

 

"Dennis_S" <DennisS@discussions.microsoft.com> wrote in message

news:0EDB705D-52B1-4A43-88A5-59473DBAE268@microsoft.com...

> I am working with Microsoft support on this. Wednesday night we ran

chkreg

> in recovery console. That reduced the System hive file by about 2 MB.

Came

> in this morning and had the same error message. Log entry was created 48

> hours almost to the minute from the last one. Probably would have

happened

> in 24 hours, but we rebooted the system when working on the registry Wed

> night.

 

On my system it isn't the System file that is large but the Software file -

it's 150MB+

 

Comparing the HKLM/Software key with another Win 2003 SP2 server, the 'good'

server's Software file size is around 50MB.

 

Further investigation shows that there are zillions of entries in the 'bad'

server's HKLM\Software\Classes\Interface key that aren't in the good

server's. (Exporting the Interface branch from the good server gives a .reg

file of 14MB, the bad server is 86MB).

 

The 'bad' server's extra entries are like this:

 

 

 

[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Interface\{02C548A5-03EC-4EE1-8EA6-FF20

C74F0BE2}]

@="_�PBrowse11"

 

[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Interface\{02C548A5-03EC-4EE1-8EA6-FF20

C74F0BE2}\ProxyStubClsid]

@="{00020420-0000-0000-C000-000000000046}"

 

[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Interface\{02C548A5-03EC-4EE1-8EA6-FF20

C74F0BE2}\ProxyStubClsid32]

@="{00020420-0000-0000-C000-000000000046}"

 

[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Interface\{02C548A5-03EC-4EE1-8EA6-FF20

C74F0BE2}\TypeLib]

@="{53E4C544-4AEC-4A77-94F8-DD7A10B09D5D}"

"Version"="1.3"

 

 

 

The interface ID (IID) changes each time (otherwise it would only be 1 entry

I guess), the name is _?Pbrowsenn where ? is 0x01 (hex 01) and nn is a

number.

 

The ProxyStubClsid and ProxyStubClsid32 are always

"{00020420-0000-0000-C000-000000000046}".

Looking in Classes\CLSID this has a name of PSDispatch and lists the

InprocServer32 entry as oleaut32.dll.

 

oleaut32.dll was updated in the KB921503 patch (MS Security Bulletin

MS07-043 : Moderate security rating for Win2003)

 

 

So my SP2 server that hasn't had the KB921503 patch is OK, the SP2 server

that has had the KB921503 patch has the problem.

 

I haven't uninstalled the patch, but the registry is borked anyway. I am

going to try a pre-patch restore to a different box and see if I can

reproduce the problem.

However I would be interested to know if others have the same v.large

Software file, if they have the same oleaut32.dll file (v.5.2.3790.4098

dated 13.Jun.07) and if anyone can suggest further action?

[Guest Craig Bell]

Windows 2003 Terminal Server getting "Low on RegistrySpace

 

Windows 2003 Terminal Server getting "Low on RegistrySpace

 

We had the exact same problem. For months we have persisted with this problem, doing nightly restarts of the server so users can log on the next day. There is a registry edit Microsoft recommends which we implemented and for a few weeks we had blissful peace without the need to restart the server. However it began to re-occur again. After trying all sorts of suggestions, in the end we decided to re-create every users profile. Lo and behold, the error has stopped. I can only assume that some users profiles were either getting too large or had become corrupted somehow. Anyway, we no longer get the "Low on registry space" error and all users can happily log on without having to log another off.

[Guest JL BERNARD]

Windows 2003 Terminal Server getting "Low on RegistrySpace"

 

Windows 2003 Terminal Server getting "Low on RegistrySpace"

 

Please check this KB from Microsoft :

http://support.microsoft.com/kb/906952/en-us

 

Hotfix proposed is not applicable for 2003 SP2, but the workaround at the end can help.

[Guest JL BERNARD]

Windows 2003 Terminal Server getting "Low on RegistrySpace"

 

Windows 2003 Terminal Server getting "Low on RegistrySpace"

 

The solution proposed by Craig Bell worked for me.

 

I just renamed the NTUSER.DAT file (the registry hive corresponding to HKEY_CURRENT_USER) in each profile in c:\Documents and settings, in order to preserve the other profile elements such as desktop and favorites.

 

After rebooting, these NTUSER.DAT files were automatically re-created at login time, and the "Low on Registry Space" error did not appear again.