Tuesday, March 27, 2012
Cannot reinstall MSDE on XP after uninstall it
did apply SP3a to the previous install of MSDE 2000 on the same XP machine.
Some of the component in an application did not work well so I had to
uninstall the MSDE 2000 SP3a completely. I removed all folders and even
registry entries. I kept getting this message, "Setup failed to configure the
server. Refer to the server error logs and setup logs for more information".
Unfortunately, those error and setup logs were useless. So, I used the /L*v
parameter to generate the setup log but it did not pinpoint why it failed. It
always fail at the last 4 seconds install period.
I ran the same setup on another XP machine. After uninstalled MSDE, removed
folders and registry entries, I was able to reinstall MSDE 2000 again.
Any help will be greatly appreciated.
Thank you.
KC
Here's a Knowledge Base article with instructions on how to manually
uninstall MSDE 2000.
http://support.microsoft.com/default...b;en-us;320873
Good luck,
Tony Sebion
"KC" <KC@.discussions.microsoft.com> wrote in message
news:F3C2F678-813C-46EA-A216-9469F13777C3@.microsoft.com:
> I have trouble reinstalling MSDE 2000 on a XP machine after uninstalled it. I
> did apply SP3a to the previous install of MSDE 2000 on the same XP machine.
> Some of the component in an application did not work well so I had to
> uninstall the MSDE 2000 SP3a completely. I removed all folders and even
> registry entries. I kept getting this message, "Setup failed to configure the
> server. Refer to the server error logs and setup logs for more information".
> Unfortunately, those error and setup logs were useless. So, I used the /L*v
> parameter to generate the setup log but it did not pinpoint why it failed. It
> always fail at the last 4 seconds install period.
> I ran the same setup on another XP machine. After uninstalled MSDE, removed
> folders and registry entries, I was able to reinstall MSDE 2000 again.
> Any help will be greatly appreciated.
> Thank you.
> KC
|||Thank you for the reply. First, I looked for those registry entries mentioned
in the article. None of them exists. So, I installed Windows Support Tools
for XP on the machine, ran the msizap with GUID, it found nothing.
The setup still fails with the same error message. What's next?
Thank you for the article though.
"Tony Sebion" wrote:
> Here's a Knowledge Base article with instructions on how to manually
> uninstall MSDE 2000.
> http://support.microsoft.com/default...b;en-us;320873
>
> Good luck,
> Tony Sebion
>
> "KC" <KC@.discussions.microsoft.com> wrote in message
> news:F3C2F678-813C-46EA-A216-9469F13777C3@.microsoft.com:
>
>
|||hi
KC wrote:
> Thank you for the reply. First, I looked for those registry entries
> mentioned in the article. None of them exists. So, I installed
> Windows Support Tools for XP on the machine, ran the msizap with
> GUID, it found nothing.
> The setup still fails with the same error message. What's next?
>
sometimes this is due to MDAC mess, so you have to fix it...
you can try reinstalling the used MDAC stack and, in case of WinXP sp2, fix
it as described in http://www.macropool.com/en/download/mdac_xp_sp2.html
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.15.0 - DbaMgr ver 0.60.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||KC wrote:
> I have trouble reinstalling MSDE 2000 on a XP machine after uninstalled it. I
> did apply SP3a to the previous install of MSDE 2000 on the same XP machine.
> Some of the component in an application did not work well so I had to
> uninstall the MSDE 2000 SP3a completely. I removed all folders and even
> registry entries. I kept getting this message, "Setup failed to configure the
> server. Refer to the server error logs and setup logs for more information".
> Unfortunately, those error and setup logs were useless. So, I used the /L*v
> parameter to generate the setup log but it did not pinpoint why it failed. It
> always fail at the last 4 seconds install period.
> I ran the same setup on another XP machine. After uninstalled MSDE, removed
> folders and registry entries, I was able to reinstall MSDE 2000 again.
> Any help will be greatly appreciated.
> Thank you.
> KC
Hi,
A had the same problem. I found that there isn't uninstalled
MSSQLServerADHelper service. I searched in registry and deletet
(almost;-) everything which contained MSSQL. That works (at least at my
PC). Maybe it'll work at yours too.
ukasz
|||Okay...Finally, I got it to reinstall after many tries. Thank you all for
your helps. First, MDAC was messed up. It was sqlsrv32.dll. Because I
upgraded my initial MSDE installed to SP3a, that DLL file got upgraded. I
replaced that DLL file from a good known XP machine. Then, re-registered all
MDAC using MDAC Repair Util. That didn't work. Later, I found out that there
were three DLLs missing from the System32 folder: sqlsrv32.rll, SQLWID.DLL &
SQLWOA.DLL. I copied them from a known good XP machine. Reinstalled MDAC 2.8
completely. After that, it installed just fine...Thank you.
"Andrea Montanari" wrote:
> hi
> KC wrote:
> sometimes this is due to MDAC mess, so you have to fix it...
> you can try reinstalling the used MDAC stack and, in case of WinXP sp2, fix
> it as described in http://www.macropool.com/en/download/mdac_xp_sp2.html
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.15.0 - DbaMgr ver 0.60.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
>
Wednesday, March 7, 2012
Cannot Install SQL Server Management Studio after removing Express edition
I'm trying to upgrade my management studio to the full version, I uninstalled Express edition and started the install for the full version, but I get an error stating "you cannot install this component because it is already installed". I had a word with one of the guys in the office and he said the only way he's ever been able to get round this is by flattening the entire PC and starting again. Obviously I want to avoid that!
Hey Parrotboy,
You asked awesome question , I never had this problem but I had something like this.
At first tell me Do you have any SQL Server on your desktop ? if so what version is that?
and review your Regedit to find SQL Server directory there is some setting that you can change them and I hope you will able to set that up.
|||I don't have SQL on my desktop nope.
I took a look in the registry and the only settings I can find that look at all relevant are in HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SQL Redist. Theres a folder called 1.00.00 with a default token with no value, and a folder called Setup with a default token (no value) and a REG_DWORD called ExitCode with 0x000000 (0) as the value.
I can't see how they would be interfering really, is it worth deleting the whole SQL Redist folder?
Hi Parrotboy,
So, you have sql server management studio express installed on your machine(without database engine installed) and now, you want to update(anyway, i don't think it can be count as "update")management studio to a "full" version--develope version or enterprise version or standard version or whatever. Correct me if my understanding is wrong.
Open your control pannel and click "add or remove programms", then select sql server, click the change button. All the sql component you have installed are listed there. Just check if you have uninstalled management studio express successfully. And if not, select it and choose "next", "remove".
Hope my suggestion helps
|||I've tried that. There is no entry in add/remove for SQL Server, I have already uninstalled it from this route. Thats why its baffling me, there must be something left after the uninstall which is stopping the install for the new version, but I can't find it.
I wish I'd never decided to upgrade now, I'm stuck using the server explorer in VS2005 which is OK, except that I need to use table/field extended properties which can't be modified through VS. :(
I am having this same problem. I was wondering if you ever found a solution? I had Mgmt Studio Express installed and removed it. I had a version of Visual Studio installed and removed it. There were some errors during de-installation, and I think that has left my system in a sort of install limbo, with maybe registry entries and some shared files still installed. Apparently the SQL Server installer is tripping over those files/entries and not allowing me to upgrade. I checked the logs and changed the settings in template.ini for the installer to upgrade the Tools and skip upgrade blockers, but that didn't work. I really don't want to re-image my machine to get past this problem. Does anyone know the files/registry entries that the installer is checking? I will just delete them by hand if I have to. Why does Microsoft have to make this so complicated?
Nope I never found a solution, aparently the ONLY option is to wipe the PC and start again, which simply is not an option for me. So now I'm stuck writing any complex update to the DB in pure SQL...
|||Sorry its a little late but take a read of
http://blogs.msdn.com/publicsector/archive/2007/10/26/installing-sql-server-management-studio-when-you-already-have-management-studio-express-installed.aspx
Hope its helpful
Cannot install SQL Server Express
My system had a beta version of Visual Studio 2005 Express on it which I uninstalled. Apparently not correctly, as I can not install SQL Server 2005 Express. I have tried to removal procedures which either give me an error message or I cannot find the items in the Add/Remove program list that are requested. That is, it looks like the system should accept SQL Server 2005 Express, but it does not.
I have successfully installed Visual C++ 2005 Express. I have no clue as to what to do next and there is no documentation on what to do. I have looked at the various postings here, tried several of them, to no avail.
When I search the registry there are some 70 entries that have the string “SQLEXPRESS” in the entry. I am unsure if these are related to my previous beta install or related to the system (a475c HP Pavilion) needs. I am reluctant to start removing those entries.
So now what do I do? Is this really that difficult? And what if I decided to buy Visual Studio 2006, whenever it may be introduced? Will I not be able to install it?
Here is the log file that was generated yesterday, my latest attempt.
= = =
Microsoft SQL Server 2005 9.00.2047.00
==============================
OS Version : Microsoft Windows XP Home Edition Service Pack 2 (Build 2600)
Time : Sun Nov 05 17:32:58 2006
HOME-HP-XP : SQL Server 2005 Setup has detected incompatible components from beta versions of Visual Studio, .NET Framework, or SQL Server 2005. Use Add or Remove Programs to remove these components, and then run SQL Server 2005 Setup again. For detailed instructions on uninstalling SQL Server 2005, see the SQL Server 2005 Readme.
SQL Server Setup failed. For more information, review the Setup log file in %ProgramFiles%\Microsoft SQL Server\90\Setup Bootstrap\LOG\Summary.txt.
Time : Sun Nov 05 17:33:51 2006
List of log files:
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0002_HOME-HP-XP_Core.log
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0002_HOME-HP-XP_Datastore.xml
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Summary.txt
= = =
Thanks
Thomas
Examine the log at C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0002_HOME-HP-XP_Core.log. This should give you the actual name of the incompatable components that are on your computer. You will need to remove those. If you can't find them in ARP you'll need to manually removing them using msiexec.exe /x <productID>. The product ID is in the log.
Mike
|||Mike,
Thanks for the information.I am not there yet, but it looks like progress is being made!
I followed your instructions, looked in the file you mentioned and found a product ID and attempted to remove it by using
msiexec.exe /x <productID>
I got a dialog box error.It was entitled "Microsoft SQL Server 2005 Express Edition CTP" with the following contents:
= = =
The setup has encountered an unexpected error in the datastore.The action is RestoreSetupParams.The error is :Failed to read property "Installlds" {"MachineConfiguration", "", "HOME-HP-XP"} from cache
Unable to write property into cache: IsClustered
Unable to write property into cache: "IsClustered"
XmIRW Error: Failure Loading xmlrw.dll
CheckAllProcedures() returned: 2
= = =
What next?
Thanks.
Thomas
|||
The problems I was having have been expertly and enjoyably addressed by two posts on Aaron Stebner's WebLog at
http://blogs.msdn.com/astebner/archive/2005/07/01/434814.aspx
http://blogs.msdn.com/astebner/archive/2005/12/08/501885.aspx
I found these to be absolutely first rate explanations and the installation of SQL Express went through without problems after following these clear instructions.
Since I have been trying to solve this problem on and off for 6 months I have to wonder why this information is not posted on the Visual Studio 2005 Express Support page at
http://msdn.microsoft.com/vstudio/express/support/uninstall/
When those instructions failed there is no clue as to what to do next.
Thomas
Cannot install SQL Server Express
My system had a beta version of Visual Studio 2005 Express on it which I uninstalled. Apparently not correctly, as I can not install SQL Server 2005 Express. I have tried to removal procedures which either give me an error message or I cannot find the items in the Add/Remove program list that are requested. That is, it looks like the system should accept SQL Server 2005 Express, but it does not.
I have successfully installed Visual C++ 2005 Express. I have no clue as to what to do next and there is no documentation on what to do. I have looked at the various postings here, tried several of them, to no avail.
When I search the registry there are some 70 entries that have the string “SQLEXPRESS” in the entry. I am unsure if these are related to my previous beta install or related to the system (a475c HP Pavilion) needs. I am reluctant to start removing those entries.
So now what do I do? Is this really that difficult? And what if I decided to buy Visual Studio 2006, whenever it may be introduced? Will I not be able to install it?
Here is the log file that was generated yesterday, my latest attempt.
= = =
Microsoft SQL Server 2005 9.00.2047.00
==============================
OS Version : Microsoft Windows XP Home Edition Service Pack 2 (Build 2600)
Time : Sun Nov 05 17:32:58 2006
HOME-HP-XP : SQL Server 2005 Setup has detected incompatible components from beta versions of Visual Studio, .NET Framework, or SQL Server 2005. Use Add or Remove Programs to remove these components, and then run SQL Server 2005 Setup again. For detailed instructions on uninstalling SQL Server 2005, see the SQL Server 2005 Readme.
SQL Server Setup failed. For more information, review the Setup log file in %ProgramFiles%\Microsoft SQL Server\90\Setup Bootstrap\LOG\Summary.txt.
Time : Sun Nov 05 17:33:51 2006
List of log files:
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0002_HOME-HP-XP_Core.log
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0002_HOME-HP-XP_Datastore.xml
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Summary.txt
= = =
Thanks
Thomas
Examine the log at C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0002_HOME-HP-XP_Core.log. This should give you the actual name of the incompatable components that are on your computer. You will need to remove those. If you can't find them in ARP you'll need to manually removing them using msiexec.exe /x <productID>. The product ID is in the log.
Mike
|||Mike,
Thanks for the information.I am not there yet, but it looks like progress is being made!
I followed your instructions, looked in the file you mentioned and found a product ID and attempted to remove it by using
msiexec.exe /x <productID>
I got a dialog box error.It was entitled "Microsoft SQL Server 2005 Express Edition CTP" with the following contents:
= = =
The setup has encountered an unexpected error in the datastore.The action is RestoreSetupParams.The error is :Failed to read property "Installlds" {"MachineConfiguration", "", "HOME-HP-XP"} from cache
Unable to write property into cache: IsClustered
Unable to write property into cache: "IsClustered"
XmIRW Error: Failure Loading xmlrw.dll
CheckAllProcedures() returned: 2
= = =
What next?
Thanks.
Thomas
|||
The problems I was having have been expertly and enjoyably addressed by two posts on Aaron Stebner's WebLog at
http://blogs.msdn.com/astebner/archive/2005/07/01/434814.aspx
http://blogs.msdn.com/astebner/archive/2005/12/08/501885.aspx
I found these to be absolutely first rate explanations and the installation of SQL Express went through without problems after following these clear instructions.
Since I have been trying to solve this problem on and off for 6 months I have to wonder why this information is not posted on the Visual Studio 2005 Express Support page at
http://msdn.microsoft.com/vstudio/express/support/uninstall/
When those instructions failed there is no clue as to what to do next.
Thomas
Cannot install 'SQL Server 2005 Express Edition with Advanced Services'
I tried to install 'SQL Server 2005 Express Edition with Advanced Services'. First, I uninstalled the old version thru Add/Delete Programs in the Control Panel.
My first problem was I didn't have IIS installed on my computer, but, I could not find it in the downloads section.
Then the installation aborted because old version databases were in C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data. But, it would not let me delete them, saying that they were being used, even though nothing was running at the time that I tried to delete them.
Hi,
"But, it would not let me delete them, saying that they were being used, even though nothing was running at the time that I tried to delete them."
I guess you still have a SQL Server installed on the system. If you want to install this, there has to be another option in the Add/Remove software panel for this instance. look in the service, if another service is running with SQL Server in its name (depending on the version you are using) you still have one installed.
"My first problem was I didn't have IIS installed on my computer, but, I could not find it in the downloads section."
IIS is part of the Windows installation, it can be installed by choosing the Add/remove Software icon in the control panel, choosing then the "Add/remove Windows Components" and then then "Internet Information Services (IIS).
HTH, Jens Suessmeyer.
http://www.sqlserver2005.de
|||
I went into:
Control Panel
Add / Remove Programs
Add / Remove Windows Components
IIS was not one of the options there!
HTH, jens Suessmeyer.
http://www.sqlserver2005.de
|||
Windows XP Home Edition.
|||IIS is not included within Home Edition, any hack which enables you to use
it, wouldn′t comply with the license agreement within
the EULA.
HTH, Jens Suessmeyer.
http://www.sqlserver2005.de
|||I upgraded to Windows XP Professional. I installed IIS.
When I attempt to run my app, I get an error message. I have had this problem occasionally before, the problem is that the SQL Server is not running. I went into Start/Run/c:\sseutil.exe -l. It said "The service MSSQL$SQLExpress" is not started. Would you like to start the service?" I replied "y". It said "Starting service....", but, it just hung there, it never actually succeeded in starting the service.
Before upgrading to XP Pro, my app ran, but, I would frequently have to go into sseutil.exe to start up SQL Server. After upgrading to XP Pro, I cannot get SQL Server to start.
I went into Control Panel/Add remove Programs and tried to uninstall Microsoft SQL Native Client. It said "This installation package cannot be installed by the Windows Installer service. You must install a Windows Service Pack that contains a newer version of the Windows Installer Service."
|||Hi,if an error occured during the startup process of the SQL Server Service, it is logged in the event log, try to see what happened here and post back the event log entries if you are not familiar with debugging these.
HTH, Jens Suessmeyer.
http://www.sqlserver2005.de
|||I un-installed and re-installed SQL Server 2005 Express Edition with Advanced Services. The install appeared to work correctly. My app no longer will run! sseutil.exe says "'MSSQL$SQLExpress' is not started. Would you like to start the service?", when I reply "y", it just hangs and never starts the service!|||Hi,
like I already said, look in the event log which will give you a more detailed information than the service starting message box. There has to be a problem during the start. The problem can vary so for trouleshooting the exact error message will be needed.
HTH, Jens Suessmeyer.
http://www.sqlserver2005.de
Cannot Install SQL Server 2005 [SOLVED]
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
Cannot Install SQL Server 2005 [SOLVED]
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
Cannot Install SQL Server 2005
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
Cannot Install SQL Server 2005
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
Saturday, February 25, 2012
Cannot install or uninstall
Our instance in SRS was playing up basically so I uninstalled it.
When I now try to reinstall via the original CD it still thinks the product
is installed. If I try to uninstall it tells me no features have changed
and exits.
When I try to reinstall or uninstall via control panel and changing the
items installed and that gives me an error of "Could not find a package to
install on the installation media".
Any help would be appreciated.
ChubblyI have now completely removed the instance of SQL Server, run a registry
cleaner to remove any erroneous entries and then tried to reinstall SQL
Server. It still thinks however that Reporting Services are already there.
I continued with the installation which threw up numerous other errors,
installed the SQL 2005 patch from Microsoft update and then tried to change
the installed components of SQL Server. To no avail. I still receive
"Could not find a package to install on the installation media".
If I try to manually run the SqlRun_RS.msi file I get the following error:
"An instance with the same name is already installed on this computer. To
proceed with SQL Server Setup, provide a unique instance name."
I'm stumped and don't particularly want to have to rebuild the whole server.
Chubbly
"Chubbly Geezer" <chubbly_geezer@.newsgroup.nospam> wrote in message
news:eyJQY9wPHHA.4484@.TK2MSFTNGP02.phx.gbl...
> We have a 2003 server with SQL Server 2005.
> Our instance in SRS was playing up basically so I uninstalled it.
> When I now try to reinstall via the original CD it still thinks the
> product is installed. If I try to uninstall it tells me no features have
> changed and exits.
> When I try to reinstall or uninstall via control panel and changing the
> items installed and that gives me an error of "Could not find a package to
> install on the installation media".
> Any help would be appreciated.
> Chubbly
>
>
Cannot install no matter what I do!
Occasionally, this has proven to be quite a headache.
Here is the list of steps and things to check that I walk through. Be precise and dilligent to check/do every one. Don't assume that it is 'almost' the same as something else you have checked/done.
Hopefully, there will be something here that will help you.
Remove -Error message when you install SQL Server 2005: "Beta components detected"
http://support.microsoft.com/?kbid=919394
Remove -How do I remove previous versions of SQL Server 2005 / Whidbey?
http://www.aspfaq.com/sql2005/show.asp?id=15
Remove -How to manually remove SQL Server 2000 default, named, or virtual instance
http://support.microsoft.com/?kbid=290991
Remove -How to uninstall an instance of SQL Server 2005 manually
http://support.microsoft.com/?kbid=909967
Remove -How to Uninstall SQL Server 2005 Beta
http://go.microsoft.com/?linkid=1396133
Remove -How to uninstall SQL Server Management Studio
http://support.microsoft.com/default.aspx?scid=kb;EN-US;909953
Remove -How to use the Add or Remove Programs item in Control Panel to add
or remove components for stand-alone installations and clustered
installations of SQL Server 2005 (KB: 922670)
http://support.microsoft.com/default.aspx?scid=kb;EN-US;922670
Remove -How to: Uninstall SQL Server Express
http://msdn2.microsoft.com/en-us/library/ms143505.aspx
Remove -The error is: Fatal error during installation"
http://support.microsoft.com/?kbid=919945
Remove -Uninstall Applications NOT in Install/Remove Programs List
http://blogs.msdn.com/astebner/archive/2005/10/30/487096.aspx
Remove –Windows Installer Clean-Up Tool
http://download.microsoft.com/download/E/9/D/E9D80355-7AB4-45B8-80E8-983A48D5E1BD/msicuu2.exe