Home  >  Article  >  Database  >  How to handle SQL Server 2005 installation failure

How to handle SQL Server 2005 installation failure

巴扎黑
巴扎黑Original
2017-03-19 10:50:452038browse

[Introduction] Error case: A problem occurred when installing SQL Server 2005 Enterprise Edition downloaded from MSDN subscription on Microsoft Virtual PC 2007 and a laptop. The installation environment is Windows Server 2003 Enterprise Edition + sp1, and the other system is with sp2. The installation user uses

 Error case: Installing MSDN on Microsoft Virtual PC 2007 and a laptop A problem occurred while subscribing to the downloaded SQL Server 2005 Enterprise Edition. The installation environment is Windows Server 2003 Enterprise Edition + sp1. The other system is with sp2. The installation user uses the super administrator (Administrator). An installation error occurred during the installation of the "Integration Services" step, prompting "Error: -2146233087".
 The error record is as follows:

 Title: Microsoft SQL Server 2005 Setup

 ----------------- -------------

 Unable to install and configure assembly C:Program FilesMicrosoft SQL Server90DTSTasksMicrosoft.SqlServer.MSMQTask.dll in the COM+ directory. Error: -2146233087

Error message: Unknown error 0x80131501

Error description: To perform this task, you must have administrative credentials. Please contact your system administrator for assistance.

 For help information, click:

 go.microsoft.com/fwlink?LinkID=20476&ProdName=Microsoft

 +SQL+Server&ProdVer= 9.00.1399.06&EvtSrc=setup.rll&EvtID=

29549&EvtType=sqlca%5csqlassembly.cpp%40Do_sqlAssemblyReg

Svcs%40Do_sqlAssemblyRegSvcs%40x80131501

Prompt through the hyperlink page of the help information "You need to configure the Network Service account for the MS DTC service to run", but the author's MS DTC originally ran under the Network Service account.

After searching on Baidu and Google, many friends encountered similar error messages, but they did not get a good solution, so they had to look for clues to try. It is certain that the problem should appear in access permissions, and common problems in this area are generally access to file system directories and system registry. Search the Microsoft Customer Help and Support website for SQL Server related installation information. There is an article that mentions setting the permissions of "C:WINDOWSRegistration" and confirming that the directory and the clb and crmlog files in the directory have full read and write permissions. When installing SQL Server 2005 again, it still fails in the "Integration Services" step. It doesn't matter whether you use the built-in system account or use a domain user account when selecting a service account during installation.

It seems that the problem is not that simple. When installing in another system, the author enabled RegMon to monitor registry operations. After filtering, only the "msiexec.exe:484" process was monitored, and the error mentioned above was reported. Then save the monitoring log to a file.

Check the failure situation through the monitoring log. Because I didn't search carefully, I later realized that the problem should have been solved long ago through the technical support engineers of the Microsoft SQL Server group. The following is the fault point that I found after checking RegMon Trace again. From the log below, I can see that accessing the registry .HKCRMicrosoft.SqlServer.Dts.Tasks.MessageQueueTask.DataFileMessage item using the native Administrator was denied.

 11305 32.35072327 msiexec.exe:484 OpenKey HKCRMicrosoft.SqlServer.Dts.Tasks.MessageQueueTask.DataFileMessage ACCESS DENIED NBCN-ZZAdministrator

 11306 32.36096954 msiexec.exe:484 QueryKey HKCU SoftwareClasses SUCCESS Name: REGISTRYUSERS- 1-5-21-730333180-4162487032-3015738926-500_CLASSES

 11307 32.36102295 msiexec.exe:484 OpenKey HKCUSoftwareClassesMicrosoft.SqlServer.Dts.Tasks.MessageQueue NOTTask.DataFileMessage FOUND

 11308 32.36108017 msiexec. exe:484 OpenKey HKCR SUCCESS

 11309 32.36190796 msiexec.exe:484 CreateKey HKCRMicrosoft.SqlServer.Dts.Tasks.MessageQueueTask.DataFileMessage ACCESS DENIED NBCN-ZZAdministrator

 11310 32.36222076 msi exec.exe:484 CreateKey HKCRMicrosoft.SqlServer.Dts.Tasks.MessageQueueTask.DataFileMessage ACCESS DENIED NBCN-ZZAdministrator

Due to carelessness, I did a lot more work and checked whether there was any problem with the "Component Service" configuration of the system, but no exception was found.

After the installation problem occurs again, this time just click the "Ignore" button to continue installing other parts of SQL Server. After the installation is completed, it will prompt that the installation was successfully completed.

Run "dcomcnfg" to open the system component service. Expand the root directory of the console->Component Services->Computer->My Computer->COM+ application node. No Microsoft.SqlServer.MSMQTask node is found. It can be seen that the COM+ application is not installed.

Run the SQL Server 2005 installation program again to add, delete and install. It prompts that the installation is successful and you see "Microsoft.SqlServer.MSMQTask" in "Component Services". It seemed that the problem was solved, but at that time I didn't know where the problem was. Uninstalled SQL Server 2005 and found that "Microsoft.SqlServer.MSMQTask" was not uninstalled. The test only installed the Integration Services service of SQL Server 2005. As a result, the installation failed. Select "Abort" to cancel the installation and confirm again that the "Microsoft.SqlServer.MSMQTask" service exists.

Next, the author sent the error that occurred during the installation process to Microsoft and asked the technical support engineers of the SQL Server group to help solve it. In the process of the engineer finding the problem, although I have done many checkpoints, he has a clear idea of ​​​​finding, analyzing and solving the problem. I have listed a few steps below.

The above is the detailed content of How to handle SQL Server 2005 installation failure. For more information, please follow other related articles on the PHP Chinese website!

Statement:
The content of this article is voluntarily contributed by netizens, and the copyright belongs to the original author. This site does not assume corresponding legal responsibility. If you find any content suspected of plagiarism or infringement, please contact admin@php.cn