Today I went to SQL Server 2005 and installed it for research.
The installation process was not very smooth, mainly due to COM + errors. I searched the internet and solved the problem as follows:
The installation is successful as follows.
Warning for COM + directory problems during sql2005 Installation
The installation of sql2005 failed. I thought the problem was caused by the COM + directory Issue warning. I found a solution to this problem for a long time.
Experience in installation failure of sql2005_std_x86 on XP SP2
The soft environment is XP SP2, and sql2005_std_x86 is installed.
Fault prompt:
1. If the SQL Server installation fails, the installer rolls back the installed system, but may not delete all. manifest files. The solution is to rename these files and run the installer again. For more information, see "how to handle the failure of COM + check during SQL Server Installation ". If Microsoft Distributed Transaction Coordinator (ms dtc) is not running, or if ms dtc is not a cluster resource when Microsoft Cluster Server is used, a COM + error may occur. COM + depends on ms dtc, while Message Queue tasks in integration services depend on COM +. If a COM + error occurs, the Message Queue task in integration services is available only after the COM + system is correctly configured.
2. An error occurred while performing the System Configuration check on the registry value of the performance monitor counter. For more information, see "how to add counter registry key values for setup programs in SQL Server 2005" in the README file or in SQL Server books online ".
The installation is aborted.
Find the books online with the following prompt:
1. The Microsoft SQL Server 2005 installer checks whether COM + is correctly configured. If a configuration error is found, the installer continues, but the following warning is displayed in the System Configuration check (SCC) report:
"If the SQL Server installation fails, the installation will roll back the installation, but may not delete all. manifest files. The solution is to rename these files and run the installer again ."
If Microsoft Distributed Transaction Coordinator (ms dtc) is not running, or if ms dtc is not a cluster resource when Microsoft Cluster Server is used, a COM + error may occur. COM + depends on ms dtc, while Message Queue tasks in integration services depend on COM +. If a COM + error occurs, the Message Queue task in integration services is available only after the COM + system is correctly configured.
To use a Message Queue (also known as MSMQ), make sure that the ms dtc is running and configured correctly. If SQL Server is installed on a cluster, MS DTC must be a cluster resource.
Reinstall COM + as follows.
Install Component Service Management Unit
On the Windows desktop, click Start and then click Run ".
In the open box, type MMC and click OK ".
In the "console" window, click "Files" on the menu bar, and then click "Add/delete snap-in ".
In the Add/delete snap-in window, click Add ".
In the "add independent management unit" window, select "component service" from the management unit list, and click "add ".
Click Close to close the add independent unit window, and then click OK to close the Add/delete unit window.
In the "Console Root Node/component service" window, expand the "component service" tree. This is where the error message may occur when a problem occurs with COM +.
Run the SQL Server 2005 installation program again. If you receive an error message, reinstall COM +.
Reinstall COM +
From add or delete programs on the control panel, click Add/delete Windows Components ".
In the "Windows component wizard", if you do not make any changes to the selection, click "Next ".
Always click to complete the wizard, and then run the SQL Server 2005 installation program again.
2. Before SQL Server Installation starts, the installation configuration Checker (SCC) in the Microsoft SQL Server Installation Program verifies the value of the counter registry key. If the SCC cannot verify the existing registry key, or the SCC cannot run the lodctr.exe system program, the SCC check fails and the installation is blocked.
Incorrect registry editing can seriously damage your system. Before changing the registry key, we recommend that you back up all important data on your computer.
Manually set the increment of the counter registry key
On the Microsoft Windows 2003 or Windows XP desktop, click Start and run, type regedit.exe in open, and click OK ". In Windows 2000, use regedt32.exe to start the Registry Editor.
Go to the following registry key:
[HKEY_LOCAL_MACHINE/software/Microsoft/Windows NT/CurrentVersion/Perflib]
"Last counter" = DWORD: 00000ed4 (5276)
"Lasthelp" = DWORD: 00000ed5 (5277)
The "Last counter" value (5276) in the previous step must match the maximum value of the "counter" item "Perflib/009" in the following registry key, and the "last help" value (5277) in the previous step must match the maximum value of the "help" item of "Perflib/009" in the following registry key.
[HKEY_LOCAL_MACHINE/software/Microsoft/Windows NT/CurrentVersion/Perflib/009]
Note that is an example in English. The values of "Last counter" and "last help" are dynamically allocated by windows. These two values vary depending on the computer.
If necessary, modify the values of "Last counter" and "last help" in "/Perflib": In the right pane, right-click "Last counter" or "last help", click "modify", then click "base =" decimal ", and set the value in" value data, click OK ". Repeat the above process for another item if necessary, and then close the registry editor.
Run the SQL Server Installation program again.
Solution Process:
The COM + check fails, not to mention whether the component in the component message queue is not installed or the service is not started. No message queue is installed on the local machine. Find out the system disk and install the Message Queue component. When the component is installed, the system prompts that the MSDTC service has not been started. This process takes a long time, why can't mstdc be found in the service? I thought about whether it would be DTC (the mind is a bit dumb, but I should think of it from the name of MSMQ ), it turns out that there is Distributed Transaction Coordinator (DTC), but this service cannot be started. Later, find the relevant information: MSDTC (Distributed Transaction Coordinator) service must be run under the nt authority/NetworkService account; even nt authority/Network Service (note that there is a space between the network and service) does not work (as for the differences between the two accounts, it is not found on the Internet, but I hope you will not give me any further ). If the Logon account is changed, the MSDTC Service continues to run, but an error may occur during execution. In addition, the following error information can be found in the "application" of the event log:
The account that is running the ms dtc service is invalid. This happens if the service account information is changed using the service snap-in the Microsoft Management Console (MMC. The ms dtc service will continue to start. Confirm that ms dtc service account information is updated using component service manager.
To change to a correct Logon account, we can:
Find the Distributed Transaction Coordinator service in the service and select "properties ";
On the "Logon" tab, select "this account" and enter "nt authority/NetworkService" in the account name. The password is blank;
Click "OK" and restart the service.
Alternatively, run MSDTC-uninstall on the command line to uninstall the MSDTC Service;
Run MSDTC-install to install the MSDTC Service.
The mstdc service is successfully started, and the "COM + application" in the component service can be accessed. The above 2nd faults have not been solved. First, try to install them to see if there are any errors. It is surprising that the installation check is successful, 2nd errors are also fixed.
Of course, the process of solving the problem is also different from that of the system environment. Here we will talk about the small setbacks of my installation and hope to give some tips to those who encounter the same problem.
