ASP.NET, SQL Server, WPF, C#, VB.NET

I don't know the answer but these tools may help you figure out what is  
  
happening.  
  
http://www.sysinternals.com/Utilities/Handle.html  
  
http://www.sysinternals.com/Utilities/ProcessExplorer.html  
  
http://www.sysinternals.com/Utilities/PsList.html  
  
http://www.sysinternals.com/Utilities/Regmon.html  
  
--  
  
Regards,  
  
Dave Patrick ....Please no email replies - reply in newsgroup.  
  
Microsoft Certified Professional  
  
Microsoft MVP [Windows]  
  
http://www.microsoft.com/protect  
  
"Eric Margheim" wrote:

What determines the limit on how many times a registry hive/key can be  
  
accessed/opened without being closed?  I am tracking down an issue that may  
  
be caused by a bunch of registry handles being opened by a process and not  
  
being closed until the process/service is stopped.   It doesn't happen on  
  
all servers that it runs on.   I'm trying to duplicate in a test environment  
  
and am trying to determine if there is a set limit per process, per hive,  
  
per server, etc.  
  
Thanks  
  
Eric

"Dave Patrick" <DSPatrick@nospam.gmail.com> wrote in message  
  
news:eNnnntn2FHA.400@TK2MSFTNGP09.phx.gbl...  
  
Thanks Dave.  
  
Yes I am using regmon and it's definitely showing that this service is not  
  
closing the keys it opens.   I just stopped the service and it showed 2000+  
  
keys being closed.    It's our code that is actually interacting with the  
  
registry in a DLL that is called by report creation code that runs under  
  
this 3rd party process.   I'm trying to determine why registry keys aren't  
  
being closed I think our code is behaving properly as we use the same  
  
methodology elsewhere and regmon shows closekeys all over the place.  
  
I'm hoping if I can determine the limit or even better find a registry entry  
  
that sets it I can duplicate this readily in our test environment and solve  
  
for good.