While attempting to uninstall Microsoft Exchange server;
Setup can’t continue with the uninstall because the powershell (PID) has open files. Close the process, and then restart setup.
Solution
Seems to be a common error, and is usually caused because someone has the Exchange Web Management page open, (probably in another user session);
In some cases you may need to reboot, but in my case I was simply being a doofus, look at the window I’m running the command from! Open an administrative command window and try again 😉
Related Articles, References, Credits, or External Links
As you are probably already aware this is because either an install/upgrade/uninstall has failed, and you are attempting to get the process going again, (or someone else has, and left it ‘broken’!)
This is happening because as Exchange performs installs/upgrades/uninstalls it creates some values in the registry as it progresses. And if you attempt to restart the process, it can see these entries, and that’s what causes the error.
So you simply need to remove them;
Open the registry editor (Windows Key+R > Regedit {Enter}).
Where you navigate to, depends on your version of Exchange;
[box]
HKLM\Software\Microsoft\ExchangeServer\v14\ (Exchange 2010)
HKLM\Software\Microsoft\ExchangeServer\v15\ (Exchange 2016 and 2013)
[/box]
Within all the sub keys (i.e. below v14 or v15) there will be a ‘Value’ thats within the role that was being installed/upgraded/uninstalled, when the process ‘fell-over’. That value will be called ‘Action‘ locate and delete it.
Also be on the lookout for a value called ‘Watermark’ if you see that, remove it also, and Exchange will start a fresh, install/upgrade/uninstall.
When you have checked all the sub keys, restart your install/upgrade/uninstall.
Related Articles, References, Credits, or External Links
XBMC was running quite happily, but whenever I tried to use Icefilms or navigate though the menus I was getting the following error.
Icefilms Import Failure
Failed to import Metahandlers
A component needed by Icefilms is missing on your system
Please visit www.xbmcchub.com for support
Solution
I did a complete remove and reinstall but the problem persisted. There are a couple of extra steps needed.
1. To uninstall, navigate to;
[box]
C:Program Files(x86)XBMC
[/box]
Run the Uninstall.exe file > Once complete, delete the entire XBMC directory (if it remains).
While trying to deploy a Windows XP Pool yesterday, I hit upon this problem. Windows 7 works fine, but as soon as I tried to roll out a Windows XP pool, they stopped like this;
After a couple of hours, the whole operation timed out, and each machine shows as;
Status
{Date}{Time} o’clock {Time-Zone}:
Customization operation timed out
I tried to deploy the pool with both ‘quick prep’ and ‘sysprep’, but the results were the same. The replica is created, the pool creates the machines, but they DO NOT join the domain.
Solution
Despite my best efforts, I had to admit defeat and call VMware. Turns out they knew what the problem was straight away.
1. In my case the pool was going to be a linked clone pool. Go to the reference XP machine that you are using for this pool, and power it on.
2. Start > Run > appwiz.cpl {Enter}.
3. Locate and uninstall the VMware View Agent software.
6. Reboot the machine, (or the next step will fail and ask for a reboot!)
7. Reinstall the VMware View Agent.
8. Now if you are creating a linked clone pool, release the IP address > shut down the guest machine > snapshot the guest machine > recreate your pool.
Conclusion
VMware tell me that this is well documented in this kb article. But both at the time, and since, I’ve analysed the logs on the connection server, and the agent logs on the deployed machines, and found no mention of the following error,
“View Composer agent initialization state error (18): Failed to join the domain”
Hopefully this will help out someone stuck in the same position.
Related Articles, References, Credits, or External Links
Tried to upgrade my VMware Workstation Version 8 today, then my laptop has a BSOD with a NETIO.SYS error, I bought it back up again, and attempted to manually install the newer version. This failed with an obscure .msi error. Even running the installer for the older version would not help.
Solution
Rather than picking it out of the registry, you can run remove it by running the install .exe file with a “/clean” switch.
1. Navigate to the directory that has the setup file in it, and run it from command line or via the Search run box in the start menu, with the /clean switch.
2. Follow the on screen instructions.
3. When complete, reboot your machine, and then you can re-attempt an install/upgrade.
Related Articles, References, Credits, or External Links
Seen today while installing Veeam 6.5 Backup and Recovery on Windows Server 2008 R2
The setup was unable to install new instance of Microsoft SQL server. Make sure this server meets minimum system requirements, or try installing it manually.
Solution
1. Press Windows Key+R > appwiz.cpl {enter} > Uninstall ALL references to SQL Server and Veeam (Warning: Obviously if the server is using SQL, SQL Express or MSDE for another reason then DON’T DO THIS).
2. Download and install SQL Express (SQLEXPR_x64_ENU.exe). Run the install and select default instance (accept the default name). I set the database for mixed mode authentication but you will probably be OK with Windows authentication.
3. This time it should complete without error.
4. Now run the Veeam setup again, and it will detect the already installed instance and run through without error.
Related Articles, References, Credits, or External Links
While working on a badly Malware affected server the other day, I tried to resurrect the Trend Micro Security Agent. It refused to run, so I attempted to remove it. Then I could reinstall it cleanly. (I knew the password that it required for removal). However this it what happened when I tried;
Trend Micro Worry-Free Business Security Agent Setup
Unable to Uninstall
An error has stopped the removal of the Trend Micro Worry-Free Business Security Agent. No changes have been made to this computer. Please contact Trend Micro for help.
Click the button below to close this window.
Solution
This procedure was carried out on Worry-Free Business Security Version 7.
1. Download and extract this zip file, (password novirus) to your desktop.
2. Run the SA_Uninstall_2360.exe file, it will create a folder on your desktop called SA_Uninstall.
3. Open that folder and run the ‘uninstall.bat’ file.
4. Press a key when prompted, then enter ‘Y’ to reboot.
5. Post reboot, I went back to Add/Remove programs, and it was still there! however now it let me uninstall it without error.
6. I now went to the server running the Worry-Free console, and pushed out a fresh agent to this machine, updated it, and did a full manual scan.
Related Articles, References, Credits, or External Links
I was finishing off a domain migration this week and was changing the clients over to McAfee. On one machine I found it had Symantec AntiVirus. When I tried to remove it, it asked for a password.
One of the other machines had Symantec Endpoint Protection installed and this did the same.
As expected, no one knew what this password was, and the default password ‘symantec’ didn’t work.
Solution
The same fix worked for both of them, and its painfully easy. While still being asked for the password, do the following.
1. Launch Task Manager, (Press Ctrl+Alt+Delete, Or right click the taskbar, or simply run Taskmgr.exe).
2. Select the processes tab, Locate the MSIEXEC.EXE service. Note: There may be more than one, if so select the one that running under the user account that you a logged on as DO NOT select it is it is running under the SYSTEM account. End the process.
3. Now the password request box will have disappeared, and the uninstall process will complete on its own.
Related Articles, References, Credits, or External Links
The ‘Ask Toolbar’ is a swear word in my office this morning, I noticed it in my “Add Remove Programs” today, and it refused to be removed.
All Chrome browser windows should be closed in order to complete the uninstallation. Please close all Chrome bowser windows. Click OK if you are ready to proceed with the uninstallation.
Solution
Well there were no Chrome windows open, (so I thought). I tried to use a software uninstaller and it stopped in the same place.
1. Right click the task-bar an launch ‘Task Manager’.
2. Scroll down and locate any Google Chrome processes, right click and ‘End Task’ for each one.
3. Attempt to remove the Ask Toolbar again.
Afterthoughts
<rant> If your wondering where it came from, it comes bundled with other products (like Adobe Flash). Annoyingly if you didn’t untick the option to install it, it will get installed. I think this is a very shabby approach. I fail to see the difference between this, and a piece of malware! I’m disappointed with Ask, and even more disappointed that a respected vendor like Adobe is pushing this down also. Their defence will be “But you only have to untick it if you don’t want it”, the point is, if I wanted it I’d go and install it!.
And why cant they programatically shut down these processes during uninstall? Or at least provide a button to do it. </rant>
Related Articles, References, Credits, or External Links
I saw this whilst installing Office on a machine today.
Solution
1. In my case I had just removed Office 2010 x64, (I needed the x32 bit version for some PST/MAPI stuff). So I knew that there was not a version of office installed.
Note: If you are unsure, click Start > appwiz.cpl {enter} and MAKE SURE. Remember most PC’s come with a trial version of Office these days, and that’s the most likely culprit!
2. Once you have discounted the obvious, make sure you DO NOT have any ‘Collaboration and Data Objects’ still installed, if so remove them (that was my problem).
Related Articles, References, Credits, or External Links
