I was then able to install the final release of VS 2005 without any problems but now I cannot install the SQL Server 2005 because it finds the beta components that must be uninstalled before proceeding. I tried using "Add/Remove Programs" but when I selected any of the SQL "CTP" programs that were there, I received a message that there was nothing to uninstall but I could have the "entry" removed from the "Add/Remove Programs" screen -- which I did.
I now have nothing related to the VS or SQL Server CTP's showing in "Add/Remove Programs". So it looks like I have to figure out how to unintall the SQL CTP components "manually". I have no idea how to proceed with this, however.
Any help in removing these CTP components would be greatly appreciated. Thank you.There is a tool under your "setup tools" folder on your beta media made for this purpose. I would try the one for SQL Server september CTP if you have that available.|||Thanks for the suggestion but it did NOT work. When I ran the "build uninstall" from the Sept CTP, it gave me the same error messages when I tried to uninstall the four Apr CTP components it found:
"A component failed to uninistall. The file specified by the link could not be found."
Status: "(13) The data is invalid."
Any other suggestions?|||Too bad.
Well this is a little backwards, but how about reinstalling april (just the prereq and engine) then run the uninstall tool?
This might potentially do more harm then good, but I would try.|||This is a problem for me, too.
You cannot reinstall the April beta version, but you can't remove it either.
For one thing, the beta versions of SQL Server 2005 are impossible to remove manually, and the uninstall beta tool from Microsoft assumes that you do this first. I tried all kinds of different things to remove it, but nothing worked.
In the forums, people have even come up with programs to uninstall the betas, unfortunately, none of them uninstall SQL Server 2005 beta. If Microsoft can come up with all this great software, why can't they come up with a tool that can uninstall one of the old beta versions of SQL Server 2005?
Considering how many other people have had this same problem, could someone at Microsoft please look into this? SQL Server 2005 could be the best database product in the world, but if you can't install it ( without reinstalling your operating system first ), what's the point ?
|||Guys .... If you have problems with Sep CTP you MUST use Sep CTP Build Uninstall Tool ...
If you still have problems start uninstalling things .... Last install first ...
/h|||I believed I have a workaround on how to uninstall Sep CTP. After so many tries, the SQLBUW.exe on the Sep CTP was also not working. This program requires that all the SQL Server 2005 Sep CTP components are there before it would work.
As suggested by the released SQL Server 2005 readme file, I used the Control Panel Add/Remove program tool to remove a bunch of SQL server 2005 Sep CTP components in the order suggested by the readme file. Using Add/Remove, however, does not actually uninstall the SEP CTP and just removed the signature of these components from a list . Then after searching, I found out about SQLBUW.EXE (sql server uninstall wizard), but since I did some manual remove, the sqlbuw.exe was not working for me either.
To get SQLBUW.EXE to work correctly, I reinstalled all these SQLServer 2005 Sep CTP components and to make sure all the SQL Server 2005 services are running. Then run sqlbuw.exe again, and this time the uninstall wizard worked. Several hours of my time is wasted on a problem that MSFT could have easily solved. This makes me worry about the overall quality of this release. It seemed that a simple problem like this was not addressed makes me wonder.
Rgds, Thuyen|||I had the same problem, I ran across a blog that pointed to this utility http://support.microsoft.com/default.aspx?scid=kb;en-us;290301. It appears the VS 2005 uninstall removes SQL 2005 CTP Tools from the add/remove programs but does not really unistall. You can verify which product is causing the problems by going to %programfiles%\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\%CORE%. You should see the GUID and the program name.
If you run the "WIndows Installer CleanUp Utility" and remove the programs it will work, now I wonder which to install first VS 2005 Pro or SQL Server 2005 Dev?
Michael
|||Thanks, this post helped me clean out the beta registry entries.
I simply searched the registry for all keys containing the offending Guid and wiped them, after which I was able to install the final versions (I went with the SQL Server Express edition this time - the full product boggles down the desktop more than I need it)!
Yours,
Morten
|||I've been on vacation for the past week or so and I just returned to work yesterday to, once again, face my SQL Server 2005 installation problems.
The previous suggestions I had tried did not work so I started over using your suggestion.
First, I ran the "Windows Installer Cleanup Utility" to remove any existing instances of the SQL 2005 beta programs. This actually worked. I was then able to install the released version of SQL 2005 -- except for Analysis Services.
Next, I tried to install the released version of Visual Studio 2005 Pro. Unfortunately, the installer found some instances of the VS 2005 beta programs that had to be removed before continuing. I "should" have checked for this before doing the SQL 2005 install, especially because using the "Installer Cleanup Utility" wanted to remove some SQL 2005 componets that would no doubt "break" my SQL 2005 install. Therefore, I decided to "uninstall" SQL 2005 using "Add/Remove Programs" and then use the "Installer Cleanup Utility" to remove any remaining pieces of VS 2005 beta.
I then reinstalled SQL 2005 without incident (except for "Analysis Service" which would not install because of a "supposedly" existing instance of the same name).
After installing SQL 2005, I was then able to install VS 2005 without receiving any error messages. I did receive one error message when starting VS for the first time (something about an assembly that wouldn't load -- which I bypassed). It seems to be working okay.
SLQ 2005 is also working except for Analysis Services. However, although I can connect to my local version of SQL 2005 and to the SQL 2000 databases on our SQL Server, I "cannot" connect to the SQL 2005 databases on our SQL Server that were created using the SQL 2005 April CTP. I can connect to those databases directly from the Server (which still has the April CTP loaded) but NOT from my workstation using the "released" version of SQL 2005. The error I receive is:
--
An exception occurred by executing a Transact-SQL statement or batch (Microsoft.SqlServer.ConnectionInfo)
Additional Information: Insert Error: Column name or number or number of supplied values does not match table definition. (Microsoft SQL Server, Error: 213)
Shouldn't the "released" version of SQL 2005 be able to connect to a database created by the April CTP?
Thanks very much for everyone's help in solving my install problems.|||Morten,
Thanks for this post it was a simple solution that I didn't think of before and it was able to solve my problem as well.
-Brandon
No comments:
Post a Comment