J
Jeremy
Hi,
Is there a recommended setting for PagedPoolSize on a Windows 2003
Terminal Server.
I'm getting an error that states that the "System could not allocate
the required space in a registry log" when writing to the
"HKEY_CURRENT_USER\Software\..." key. From what I have read the
registry size is governed by the PagedPoolSize. Even though the
registry size under Windows 2003 is supposed to be dynamic, and the
RegistrySizeLimit key no longer needs to be set, I think it still has
a limit.
From the Windows 2000 world, the registry can not exceed 80% of the
PagedPoolSize. Therefore if PagedPoolSize=128MB, max registry size is
128MB * .80 = 102MB. Does this still apply to Windows 2003?
Interestingly, I have found that a reboot clears the problem, so I'm
unsure what it is I should be looking for.
The servers in this farm are HP DL360 G4s & DL380 G4s with at least
2GB of RAM.
Cheers,
Jeremy.
Is there a recommended setting for PagedPoolSize on a Windows 2003
Terminal Server.
I'm getting an error that states that the "System could not allocate
the required space in a registry log" when writing to the
"HKEY_CURRENT_USER\Software\..." key. From what I have read the
registry size is governed by the PagedPoolSize. Even though the
registry size under Windows 2003 is supposed to be dynamic, and the
RegistrySizeLimit key no longer needs to be set, I think it still has
a limit.
From the Windows 2000 world, the registry can not exceed 80% of the
PagedPoolSize. Therefore if PagedPoolSize=128MB, max registry size is
128MB * .80 = 102MB. Does this still apply to Windows 2003?
Interestingly, I have found that a reboot clears the problem, so I'm
unsure what it is I should be looking for.
The servers in this farm are HP DL360 G4s & DL380 G4s with at least
2GB of RAM.
Cheers,
Jeremy.