Hi Andrew - I have seen this a couple times and have not yet been able to determine the actual application causing the issue, but I can tell you how to work around it.
What is happening is a file that the installer is trying to upgrade is in use, but it cannot get the name of the process which actually has it locked.
Would you mind sending me the output to the command line app Tasklist.exe so that I can try to correlate a commonality?
- Start->Run->type 'MSConfig'->OK
- In the general tab, select 'selective startup', and uncheck 'Load startup items'
- In the services tab, check "Hide All Microsoft Services", then click the "Disable All" button.
- Click OK and Reboot.
- Install 10.3.
- Run MSConfig and reverse the previous steps.
You should be good to go.
(Supplementary MSConfig info can be found at: http://support.microsoft.com/kb/310353)
This server is an Orion server, so I tried stopping all Solarwinds services, but it still would not work. Rather than disable all non-MS services and reboot as you suggested, I fired up ProcessExplorer and searched for all file handles with "solarwinds". It looks like the culprit was w3wp.exe (the IIS Worker Process). Even though you stop the World Wide Web Publishing Service, it looks like the w3wp.exe stays alive. I killed the process in Task Manager and the Toolset 10.3 install completed normally. After the install I fired up the Orion services and the W3SVC service. So, it looks like something in the Orion web interface is using a shared file that the Toolset wanted to upgrade.
Hey Andrew - thanks for your investigation; I am glad you were able to get that figured out.
FWIW: I have seen this occur on non-Orion servers, so for those folks that might encounter this, the steps I listed above should get you through it.