I am not able to remove sql server 2008 from my machine.
I installed it in the past as a part of the installation of an application, this installed the runtime of sql server 2008 SP0. But now I cannot uninstall.
I tried to use the setup of SP0 and even of SP2 but it was not able to uninstall, by giving fatal errors when it does the preliminary checks.
This means that the only option I have is format my machine?
I cannot even intall a new instance, something is really corrupted.
Is it a way to remove it manually?
I fixed a similar issue by using Microsoft fixit tool
http://support.microsoft.com/mats/Program_Install_and_Uninstall/
I tried to uninstall 3 times and the third time it was succesful, anyway I was not able to install due to fatal errors in the installer.
By trial and error I found that the problem was a list of non existing files in the following registry key (Windows Vista):
HKLM\SYSTEM\CurrentControlSet\Control\SessionManager\PendingFileRenameOperations
So i simply deleted The key PendingFileRenameOperations and tried to install, it installed succesfully.
Anyway thinkinf of automatizing this is crazy, the best way to reinstall is to isntall on a new machine (I mean for customers).
This is part of my job which I've been doing for a few years now. I've probably uninstalled it about 200 / 300 times and find it difficult sometimes.
What errors are you getting?
Have you manually deleted it from
C:\Program Files\Microsoft SQL Server
If you can, do so (or just rename) and then try to add-remove. You most likely won't be able to so the next course of action will be to manually strip it from the registry or use CC Cleaner to strip it out.
Let me know if that doesn't work and i'll offer another suggestion. I believe MS has a tool to force removing programs from the list if the MSI isn't available.
Good Luck it's not the nicest thing to do!
Related
I get the error in the attachment during SQL Server 2017 installation. I would like some assistance please.
Look at the Pinal Dave post. It looks like he describes similar issue https://blog.sqlauthority.com/2016/03/07/sql-server-setup-closed-exit-code-0x80004005/
All I can see is that there is something wrong with .NET security. I
asked my .NET expert friend to know if there is any tool to reset the
permission? He told CASPOL.EXE can be used to reset the policies.
Caspol.exe (Code Access Security Policy Tool)
So, we went into following directory
“C:\WINDOWS\Microsoft.NET\Framework64\v2.0.50727” and ran this
command: – caspol.exe -machine -reset
C:\WINDOWS\Microsoft.NET\Framework64\v2.0.50727>caspol.exe -machine
-reset
If it would have been a 32-bit machine, we would have run the same
command under “C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727” folder.
After doing above, the setup was able to start and finish as well.
Have you simply tried fully uninstalling and reinstalling? Including the .net frameworks? Usually, if you completely remove everything that is related in some way to SQL and reinstall, it should complete successfully.
I am tearing my hair out because I was working on some SQL scripts and I executed them to ALTER stored procedure, however when I came in this morning I have lost all my work, it was showing the previous day's script. Somehow it didn't save even though I watched it Execute Successfully Completed!.
Now I thought that using Microsoft SQL Server Management Studio v17.7 there will be an auto recovery temp folder with SQL files somewhere, and from looking online its states to go here; C:\Users[User]\Documents\SQL Server Management Studio\Backup Files\Solution1\ and you will see Autorecovery.sql files lots of them.
However this is completely empty, and I got no idea where clever Microsoft has moved this new location too or removed it all together. I went to settings in my SQL studio under Tools->Options->Environment->AutoRecover and both are ticked for "Save AutoRecover Info every 5 minutes" and "keep autorecover info for 7 days". Which tells me it is somewhere on my PC.
I then thought that I might have lost my work and though it would be a good idea to test this scenario on some new scripts and guess what the folder path still shows empty whilst using MSSMS so I got no idea how to utilise this auto recovery feature for the future.
Any ideas.
Try searching in visual studio directories if you have it installed :
C:\Users\<your_user>\Documents\Visual Studio <your_version_visual_studio>\Backup Files\Solution1
SSMS 2017 seems to just keep the recovery files in %TEMP%\ (with name ~vsXXXX.sql)
I have realised the only way to make sure you are safe is to have a folder specified with all your scripts stored there.
This way the autosave only works when you have saved the file prior not unsaved files, so it will be a case of Save + Execute.
I have lost my work for now, but this is why people learn from there mistakes.
I have recently installed Microsoft SQL Server Management Studio 17. I worked on it for like 1 hour or so, created my own database and just as I was going to create a table, my laptop gave me a kind of BSOD screen (I have Windows 10 btw). Well it showed me that it was collecting data for the error and then restarted. Since then, I couldn't start SSMS ever again. It keeps giving me "cannot find one or more components, please reinstall error" and I tried literally everything to fix it. I reinstalled the program. I uninstalled VS Isolated Shell then repaired SSMS. I even removed the /14.0_config file from the registers, but still no result, I still can't enter the program anymore. Do you think I've done something wrong during these steps or should I try something else?
SQL Server Setup has encountered the following error:
MsiGetProductInfo failed to retrieve ProductVersion for package with Product Code = '{DF167CE3-60E7-44EA-99EC-2507C51F37AE}'. Error code: 1605..
What I've done so far:
Had to re-install Windows 7 because I kept getting a pop up that said my windows was unregistered, which it wasn't (known bug) so I re-installed as per MS recommendation.
Un-installed SQL Server 2008 + ran Microsoft Fix It tool.
Tried to re-install.
After I got the error I deleted all the registry entries per instructions available where others have posted this same problem.
When I continued to get the error I renamed the registry directory UpgradeCodes to UpgradeCodes.old.
I've rebooted after every step and I've repeated this many times...
In all cases when I try to re-install it fails with Error code: 1605. At this point when I search the registry for the reversed key it is not found. It's gone.
Not sure what to do next.
Any suggestions would be appreciated. Thanks
I have the same problem and following method which I got it from http://www.thewindowsclub.com/ worked for me:
Method 2
This method is a little risky but should work at the first attempt. Make sure you don’t reboot the system until we complete the process. In this method we will just make the UpgradeCodes unusable until we finish the SQL install.
First setup is exit the install and shutdown all the applications
Then go toregistry and create a backup of the registry.
Now go to HKEY_Classes_Root\Installer\UpgradeCodes.
Right click on UpgradeCodes and click on Export and type in UC.reg and save it somewhere (Maybe Desktop)
Then right click again and click on rename and rename to UpgradeCodes.old
Now attempt to install SQL again. This time it should work in first try. Make sure you don’t reboot the system because sometime other application like MS Office might stop working. Once the installation is complete, close the installer and find the file you saved UC.reg and double click on it and click OK.
Now we have up the UpgradeCodes back again.
I'm getting an error whenever I load Management Studio or open a folder in the server explorer, etc. Additionally, If I try to create a new database it constantly is updating and does not finish. I have attached a screenshot of the error. Please let me know what I can do to fix this because it's really aggravating.
Error Screen http://frickinsweet.com/databaseError.gif
From MSDN forum http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=120476&SiteID=1
My first guess would be Client Tool corruption.
I've occasionally had to uninstall my client tools and reinstall them. Boot after uninstall.
I had to add the registry file AND re-run "regsvr32 actxprxy.dll" This was a really odd and painful error. It only seemed to come into existence after installing VS SP1 but I really don't see why that would have happened.