June 11, 2012 at 10:36 am
Hi All,
I've just taken over as admin of a small network and am having some issues with our SQL installs.
We have a server running SQL express 2008 as part of a third party application, but in the background there is an instance of 2005 running.
I've stopped the server and seen no effect on users and there appears to be no applications associated with it so I figured it would be ok to uninstall..
Here's where the fun starts, it appears the original setup files were copied to a drive which is long since defunct.. and since the msi files are gone the uninstall fails with error 1612. I thought I would try and be clever and simply extract the files from the setup package however I still get the same error about missing msi files.
I've followed the instructions on several blog posts (including this site) about manual removal of SQL 2005 all with much the same results..
ANY help with this would be very much appreciated as it's driving me mad..
Thanks,
Jeff
Database Engine
[Version: 9.2.3042.00 Edition: Express Edition Patch level: 9.2.3042 Language: English (United States)]
Common components
Workstation Components
[Version: 9.2.3042.00 Edition: Express Edition Patch level: 9.2.3042 Language: English (United States)]
June 11, 2012 at 10:48 am
I would think if you could locate a SQL 2005 install disk you could run the installer and select an uninstall option to remove the instance.
But if it were me and the 2008 instance hosted production data, I would just backup, archive & drop the 2005 DBs, then go into SQL Server Configuration Manager and disable the 2005 instance. That way it's not doing anything except occupying some HD space.
June 11, 2012 at 11:07 am
Ah Dan, thanks for the reply..
That is exactly what I would have done if it were not for our latest phone software.. it needs to run 2005 and as it runs through the install it fails at the point where it tries to install a new instance of SQL (same error 1612).
I have made some progress (possibly!?) and tracked down the msi file ( 6cb10309.msi ) that was referenced in the install fail log.. error 1612 has now changed to
MSI (s) (38:9C) [17:59:30:399]: APPCOMPAT: looking for appcompat database entry with ProductCode '{2AFFFDD7-ED85-4A90-8C52-5DA9EBDC9B8F}'.
MSI (s) (38:9C) [17:59:30:399]: APPCOMPAT: no matching ProductCode found in database.
with the exit code 1603..
Any takers.. while I still have hair that is not torn out!!!
Cheers again.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply