| || |
Windows Test Machines - registry
We've got a new lab setup and we're having major problems with our machines in sense that we constantly have long time to shutdown machines. This is screwing up automation tools that use reboot scripts. We check event viewer for windows 2000 and it say that system can't 'unload the registry' at all. We thought this was because we installed automation tools since problems happened then but it doesn't appear to be the case.
So now we in the process of testing our own test machines to see what is wrong!!! Anyone else have this problem or familiar with it? Actually more concerned if someone know how to SOLVE it. It greatly affect our testing machines not only because of automation but also because our product does some things with registry and we can't test it on our test machines!
Re: Windows Test Machines - registry
Well, there could be a couple of issues here but I think I know the one you are dealing with.
What it probably is not...
If you are using software that "protects" your registry in some fashion, you can have this problem. This might be the case with some firewalls. If you have a firewall that writes MDB files to the Internet Logs, you might try deleting everything from %systemroot%/Internet Logs as just one possible mitigator. However, with that said, I do not think that is your problem, particularly since you say you are on Windows 2000. (To be certain, you might try running something like RegClean and seeing if it errors out. If it does, your issue is likely a "stuck registry", which applies to what I talk about below.)
What it probably is...
The whole "unloading" problem with the registry comes in with the Windows 2000 "hotfix" known as (Pre-SP4) Q329170. The issue here is that certain registry keys are being left open and the group profiles are not being updated correctly. One way around this that is very unpalatable (to me, anyway) is to simply wipe out the profiles and allow them to be recreated. I would advise against that in fairly strong terms. So, since there is no "fix", per se, you can do one of two things: uninstall that hotfix or change your group policy.
If you want to uninstall, simply go to your Control Panel, Add/Remove Programs and select that hotfix. If you happen to need and/or want that particular hotfix, you can alter the group policy. The easiest way I know of is to just go to Start > Run and then type in gpedit.msc. (You can also select this via your Administrative Tools from the Start > Programs menu.) Once there, choose the Administrative Templates folder, then choose the System folder, then choose the Logon folder. In there you will see a section of policies that correspond to event firings for the logon procedure. One of those will be titled "Maximum retries to unload and update user profile". It might show up as being "Not configured". That is fine. Simply double-click on that entry. On the popup that appears, select the Enabled radio button. Then in the "Max retries" text field enter in something other than 60 (which is the default). Do not enter 0 as you have to give Windows at least one chance. I would set it somewhere between 3 and 7.
Note: as one last attempt to be comprehensive, you might have a problem with winspool.drv, which is stored in %systemroot%\System32. This "spooler" waits for performance data to be collected. Note, however, that the hotfix I mentioned does "fix" win32spl.dll, wlnotify.dll, and winspool.drv. So it is probably the exact same issue anyway.
Final note: You might also have a problem with Q328310. This is another one of those pre-SP4 hotfixes. Again, both of these are security patches so you have to decide if you want to remove them. If you do, the problem should go away. If you do not, simply change the group policy as I mentioned above. (Keep in mind you have to sign in as an Administrator if oyu want to change group policies.)