Registry built-up

  • Thread starter Thread starter io
  • Start date Start date
I

io

Hi guys, I wonder if you ever faced a weird registry problem like this (see
below) and if you did whether you ever managed to fix it somehow?

We have a system that runs on three servers - Web Server, Application Server
and Database Server. It's ASP-based with COM+ components running on App.
server being used by Web server pages through the proxy COM+ applications.
The problem is that the registry on both Web server and App. server builds
up to the maximum size quite regularly (about every month, sometimes more
often) and the only cure is to reboot the server - it brings the registry
back to its initially allocated cize (12Mb on Web server and 25Mb on App.
server). We increased the maximum registry size a couple of times and it is
now 200 Mb on both servers, but it doesn't help. As soon as trouble happens
it's up to 200 Mb and the only thing you're left with is too reboot again.

We cannot find even a trace of anything that may cause this. Event log only
starts displaying user profile loading errors - but that's when the trouble
is already there.

All those servers run on Windows 2000 (5.00.2195) Service Pack 3

Any info is much appriciated, thanks in advance
 
Thanks Dave, I'll give it a try

Dave Patrick said:
This tool may help you figure out what application is causing this.
http://www.sysinternals.com/ntw2k/source/regmon.shtml

--
Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft MVP [Windows NT/2000 Operating Systems]

io said:
Hi guys, I wonder if you ever faced a weird registry problem like this (see
below) and if you did whether you ever managed to fix it somehow?

We have a system that runs on three servers - Web Server, Application Server
and Database Server. It's ASP-based with COM+ components running on App.
server being used by Web server pages through the proxy COM+ applications.
The problem is that the registry on both Web server and App. server builds
up to the maximum size quite regularly (about every month, sometimes more
often) and the only cure is to reboot the server - it brings the registry
back to its initially allocated cize (12Mb on Web server and 25Mb on App.
server). We increased the maximum registry size a couple of times and it is
now 200 Mb on both servers, but it doesn't help. As soon as trouble happens
it's up to 200 Mb and the only thing you're left with is too reboot again.

We cannot find even a trace of anything that may cause this. Event log only
starts displaying user profile loading errors - but that's when the trouble
is already there.

All those servers run on Windows 2000 (5.00.2195) Service Pack 3

Any info is much appriciated, thanks in advance
Click to expand...
Click to expand...
 
Thanks Dave, I'll give it a try

Dave Patrick said:
This tool may help you figure out what application is causing this.
http://www.sysinternals.com/ntw2k/source/regmon.shtml

--
Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft MVP [Windows NT/2000 Operating Systems]

io said:
Hi guys, I wonder if you ever faced a weird registry problem like this (see
below) and if you did whether you ever managed to fix it somehow?

We have a system that runs on three servers - Web Server, Application Server
and Database Server. It's ASP-based with COM+ components running on App.
server being used by Web server pages through the proxy COM+ applications.
The problem is that the registry on both Web server and App. server builds
up to the maximum size quite regularly (about every month, sometimes more
often) and the only cure is to reboot the server - it brings the registry
back to its initially allocated cize (12Mb on Web server and 25Mb on App.
server). We increased the maximum registry size a couple of times and it is
now 200 Mb on both servers, but it doesn't help. As soon as trouble happens
it's up to 200 Mb and the only thing you're left with is too reboot again.

We cannot find even a trace of anything that may cause this. Event log only
starts displaying user profile loading errors - but that's when the trouble
is already there.

All those servers run on Windows 2000 (5.00.2195) Service Pack 3

Any info is much appriciated, thanks in advance
Click to expand...
Click to expand...
 
Hi guys, I wonder if you ever faced a weird registry problem like this
(see below) and if you did whether you ever managed to fix it somehow?

We have a system that runs on three servers - Web Server, Application
Server and Database Server. It's ASP-based with COM+ components
running on App. server being used by Web server pages through the
proxy COM+ applications. The problem is that the registry on both Web
server and App. server builds up to the maximum size quite regularly
(about every month, sometimes more often) and the only cure is to
reboot the server - it brings the registry back to its initially
allocated cize (12Mb on Web server and 25Mb on App. server). We
increased the maximum registry size a couple of times and it is now
200 Mb on both servers, but it doesn't help. As soon as trouble
happens it's up to 200 Mb and the only thing you're left with is too
reboot again.

We cannot find even a trace of anything that may cause this. Event log
only starts displaying user profile loading errors - but that's when
the trouble is already there.

All those servers run on Windows 2000 (5.00.2195) Service Pack 3

Any info is much appriciated, thanks in advance
Click to expand...

You need to figure out what section of the registry is growning and
therefore what program is causing it to grow. We know the system hive is
not getting that large because the system would not boot. You can check
the physical sizes of the individual files that make up the registry by
looking at them in winnt\system32\config. I imagine it it is the
software hive. Run regedit and start exporting major software keys. Look
at the sizes of the exported files to find one that is very large and
you will have your problem program.

Leonard Severt

Windows 2000 Server Setup Team
 
Hi guys, I wonder if you ever faced a weird registry problem like this
(see below) and if you did whether you ever managed to fix it somehow?

We have a system that runs on three servers - Web Server, Application
Server and Database Server. It's ASP-based with COM+ components
running on App. server being used by Web server pages through the
proxy COM+ applications. The problem is that the registry on both Web
server and App. server builds up to the maximum size quite regularly
(about every month, sometimes more often) and the only cure is to
reboot the server - it brings the registry back to its initially
allocated cize (12Mb on Web server and 25Mb on App. server). We
increased the maximum registry size a couple of times and it is now
200 Mb on both servers, but it doesn't help. As soon as trouble
happens it's up to 200 Mb and the only thing you're left with is too
reboot again.

We cannot find even a trace of anything that may cause this. Event log
only starts displaying user profile loading errors - but that's when
the trouble is already there.

All those servers run on Windows 2000 (5.00.2195) Service Pack 3

Any info is much appriciated, thanks in advance
Click to expand...

You need to figure out what section of the registry is growning and
therefore what program is causing it to grow. We know the system hive is
not getting that large because the system would not boot. You can check
the physical sizes of the individual files that make up the registry by
looking at them in winnt\system32\config. I imagine it it is the
software hive. Run regedit and start exporting major software keys. Look
at the sizes of the exported files to find one that is very large and
you will have your problem program.

Leonard Severt

Windows 2000 Server Setup Team
 
Thanks Leonard, I'll keep an eye on that winnt\system32\config directory. I
have been checking registry size via System settings for a few days, but the
thing never happens when you watch
 
Thanks Leonard, I'll keep an eye on that winnt\system32\config directory. I
have been checking registry size via System settings for a few days, but the
thing never happens when you watch
 
Back
Top