Skip to main content

Uninstall 64 bit and reinstall 32 bit SQL Server

For reason's beyond the scope of this post I needed to uninstall a 64 bit version of SQL server standard edition (Including Integration Services ) and re-install the 32 bit SQL Server standard edition.

The uninstall seemed to complete successfully so I went on my merry way and I attempted the re-install of the 32 bit version:

The database engine installed perfectly well but when the installation got to Integration services, it  failed with the following error:

Failed to install and configure assemblies E:\Program Files (x86)\Microsoft SQL Server (x86)\90\DTS\Tasks\Microsoft.SqlServer.MSMQTask.dll in the COM+ catalog. Error: -2146233087
Error message: Unknown error 0x80131501
Error description: One or more of the components being installed are already registered as 64 bit components in the target application. You must install the 32 bit versions of the components being installed in a different COM+ application, or delete the existing 64 bit versions of the components being installed from the target COM+ application prior to attempting install of the 32 bit versions. COM+ applications cannot contain bit neutral components.

After a few expletives and a google search I found this post on the MSDN forums, I had got the exact same error as the OP in this post:

so I followed the proposed answer by Ekrem Onsoy:

- Open: Start\Programs\Administrative Tools\Components Services,
- Expand "Component Services" -> "My Computer" -> "COM+ Applications",
- You'll see "Microsoft.SqlServer.MSMQTask" component. Right click on it and Delete it.
- If that dialog box is open which poped up during SQL Server Setup then click Retry, otherwise start over and this problem will be gone.

My next attempt at a reinstall resulted in a different error:

"Failed to install and configure assemblies E:\Program Files (x86)\Microsoft SQL Server (x86)\90\DTS\Tasks\Microsoft.SqlServer.MSMQTask.dll in the COM+ catalog. Error: -2146233087
Error message: Unknown error 0x80131501
Error description: FATAL: Could not find component 'Microsoft.SqlServer.Dts.Tasks.MessageQueueTask.ServCompMQTask' we just installed."

All other components including the database engine seem to install correctly.

I tried the proposed fix above and the component was not there. I rebooted the machine and started again and the install completed successfully.


Post a Comment

Popular posts from this blog

Always Encrypted

By David Postlethwaite

Always Encrypted is new features in SQL Server 2016 and it is also available in Azure SQL Database. Here you can encrypt columns in a table with a master key and a certificate so that they will appear as encrypted strings to those who don’t have the required certificate installed on their pc.
Once the certificate is installed on the computer then the unencrypted data can then be seen as normal.

The data passes from database to your application as the encrypted value, only the application with the correct certificate can unencrypt the data so it is secure across the wire. This will go some way to resolving the concern of people worried about putting their sensitive data on a shared server in the cloud such as Microsoft Azure and accessing the data across the Internet.

At the time of writing Always Encrypted is only supported with ADO.NET 4.6, JDBC 6.0 and ODBC 13.1 but expect other driver to become available.

The calling application (including SSMS) must also hav…

SQL Server 2012 and Virtual Service Accounts

This post is written by David Postlethwaite
If you are using SQL Server 2012 you will probably have noticed that the default account for the SQL services has changed from that used in previous versions. With SQL 2005 and 2008 the default account for SQL service and SQL Agent service was “NT Authority\System”. This is one the built in accounts on a Windows machine, managed by the machine and selectable from a dedicated dropdown list

The Network Service account was introduced in Windows 2003 as an alternative to using the LocalSystem account, which has full local system privileges on the local machine, a major security concern.
The Network Service has limited local privileges easing these security concerns but when many services on a machine use the Network Service account it becomes harder to track which service is actually accessing resources and performing actions, because all the services are using the one Network Service account.
Also, this account, by default, has sysadmin per…

SQL Server Express v SQL Server Developer Edition

SQL Server Express v  SQL Server Developer Edition
Over the weekend I received the following in an email from Ali Ahmad who asked me some questions about learning SQL Server. We exchanged a couple of emails so I have boiled this down to the most salient points.

Goal: I want to learn SQL Server inside out… for career progression as DBA/BI/data mining. I'm a data analyst and want to learn inside out about data warehousing.
•I understand relational database concepts...
•I have SQL Server 2014 express installed…
•I need to download the adventure works sample in order to play with it.
•So much knowledge on Microsoft website it's easy to get lost… where do I begin?

SQL Server Express v SQL Server Developer
This is interesting. If you want to learn SQL Server inside out including the Business Intelligence suite of applications I would suggest downloading the developer edition of SQL Server which since 2016 has been made available free of charge. Prior to that there was a f…