SCORE!!!!!! Thanks Ben, I've been struggling with this off and on for months and this finally did the trick.
Process Monitor wouldn't work on the particular patch level on Win 2K I had, but it led me to find an old copy of RegMon. That enabled me to pin down the key "HKLM\System\CurrentControlSet\Control\SecurePipeServers\WinReg" as the culprit. A little googling told me that SYSTEM typically has full control over that key and it didn't in my case. I added that permission, ran the uninstall and it completed perfectly. The server is no longer showing up in ESM on my workstation and our email is flowing perfectly. A big public THANK YOU for your help, Michael's and everyone else's. Steve Hart Network Administrator 503.491.4343 -Direct | 503.492.8160 - Fax ________________________________ From: Sean Martin [mailto:seanmarti...@gmail.com] Sent: Wednesday, August 18, 2010 4:58 PM To: MS-Exchange Admin Issues Subject: Re: Uninstall Exchange 2000 Run it first on your Exch 2000 box before doing anything else. This will show you which processes are currently running and what you can filter from your capture when you do try the uninstall again. Makes it a lot easier to sift through the results. - Sean On Wed, Aug 18, 2010 at 3:29 PM, Steve Hart <sh...@wrightbg.com<mailto:sh...@wrightbg.com>> wrote: That's a new tool to me. Thanks I take it I should start it on the E2000 box, run the uninstall again and see what it flags? Steve Hart Network Administrator 503.491.4343 -Direct | 503.492.8160 - Fax -----Original Message----- From: Ben Scott [mailto:mailvor...@gmail.com<mailto:mailvor...@gmail.com>] Sent: Wednesday, August 18, 2010 4:23 PM To: MS-Exchange Admin Issues Subject: Re: Uninstall Exchange 2000 On Wed, Aug 18, 2010 at 7:10 PM, Steve Hart <sh...@wrightbg.com<mailto:sh...@wrightbg.com>> wrote: > I'm checking permissions on each of registry keys specified in KN > 260378, trying to determine why my uninstall is failing. Get a hold of Process Monitor from Microsoft Sysinternals, and filter on "ACCESS DENIED" and see what it's actually failing on. (If anything. Over the years, I've noticed that Microsoft reports a lot of things as "Access is denied" when it's something else entirely. It's like that error is their catch-all or something.) -- Ben
