(This is a brand new system where I installed multiple SQL Server 2014 components in order to demonstrate my approach of cleanly removing them without using the Control Panel or SQL Server's own setup, but rather using msiexec and the GUIDs for the products.) You can get the GUID associated with each installed product by searching around the registry, but I would rather use the MSI Inventory tool, which you can download ( msiinv_new.zip) from, and extract msiinv.exe to a folder, say C: temp. Summary This is not the most intuitive approach in the world, but I hope it helps some of you remove stubborn, sticky SQL Server components from your systems. I wanted to focus on a single run-through with the SQL Server components, since they are the ones that prove most problematic. Once that file is there, you can open a PowerShell console, and run the following code. Manually remove microsoft sql 2005 error.
0 Comments
Leave a Reply. |