Wednesday, June 22, 2011

SQL Server Installation Issues

OWC11 Installation Failure
Sample Error from errorlog-->MSI (s) (C4:C8) [19:04:30:953]: Product: Microsoft Office 2003 Web Components -- Error 1706. Setup cannot find the required files. Check your connection to the network, or CD-ROM drive. For other potential solutions to this problem, see C:\Program Files\Microsoft Office\OFFICE11\1033\SETUP.CHM.
Solution 1: Uninstall Sql server 2005 completely and then try to manually run the OWC11.msi file available in Tools folder of sql 2005.Then try to install sql 2005 freshly !
Solution 2: Just uninstall Office web components from Add \ Remove programs and then try to install sql 2005
Error message when you install SQL Server 2005: "There was an unexpected failure during the setup wizard" - Error 1603
Solution:To work around this problem, set the folders in the correct layout for the SQL Server 2005 installation. The SQL Server 2005 installation uses the following two folders:
  • Servers
  • Tools
These two folders must be under the same level of a folder or the root folder of a drive. The names of these folders must be exactly Servers and Tools. The Servers folder contains all the files that are required to install major SQL Server 2005 components, such as database engine. The Tools folder contains tools components and Books Online for SQL Server 2005.Then try installing sql from the path\servers\setup.exe
SP2 fails to install database services - MSP Error: 29512 "Unable to install Windows Installer MSP file"
Error Snippet :
MSP Error: 29512 SQL Server Setup was unable add user Clusteruser@FQDN (where FQDN is the actual fully qualified domain name - abbreviated here for security) to local group DOMAIN\SQL2005SQLAgents (where DOMAIN is the actual name of the domain). MSP returned 1603: A fatal error occurred during installation.
Solution: KB 926622 -- This article is for SP1 and also applicable to SP2 also.
To install SP2, try creating the following path, and restart SP2 setup:
DRIVE:\Microsoft SQL Server\MSSQL.2\MSSQL\FTData


The SQL Server 2005 Setup program may take a very long time to be completed.
Solution: Refer the link and follow the steps given to solve the issue
Error while creating Maintenance plan
Method not found: 'Void Microsoft.SqlServer.Management.DatabaseMaintenance.TaskUIUtils..ctor()'. (Microsoft.SqlServer.Management.MaintenancePlanWizard)
Solution : Apply SP2 with critical update. You can download @ SQL Server SP2

[Native Client]Encryption not supported on the client -- Error 29515
Error Snippet: Product: Microsoft SQL Server 2005 -- Error 29515. SQL Server Setup could not connect to the database service for server configuration. The error was: [Microsoft][SQL Native Client]Encryption not supported on the client. Refer to server error logs and setup logs for more information. For details on how to view setup logs, see "How to View Setup Log Files" in SQL Server Books Online.
Solution: I've got the below solution from one of the Microsoft forums
I had to import this, please note you do this AT YOUR OWN RISk. But it worked perfect for me.
When I was reloading my server, the native client "reinstall" wouldnt show. I knew I had uninstalled it so i was "wtf" its not uninstalling.
So I installed the native client, imported this into the registry and everything ran fine.
Before you import this you might want to just verify all these keys exists. If they do, your problem is elsewhere.





"Label"="Force protocol encryption"

"Label"="Trust Server Certificate"

"ProtocolName"="Named Pipes"

"Name"="Default Pipe"

"ProtocolName"="Shared Memory"


"Name"="Default Port"

"Name"="KEEPALIVE (in milliseconds)"

"Name"="KEEPALIVEINTERVAL (in milliseconds)"


"Name"="Default Server Port"

"Name"="Default Client NIC"

MSP Error: 29538 SQL Server Setup did not have the administrator permissions required to rename a file
Sample Error
Product : Database Services (MSSQLSERVER)
Product Version (Previous) : 1399
Product Version (Final) :
Status : Failure
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\SQL9_Hotfix_KB921896_sqlrun_sql.msp.log
Error Number : 29538
Error Description : MSP Error: 29538 SQL Server Setup did not have the administrator permissions required to rename a file: C:\Program Files\Microsoft SQL Server\MSSQL\Data\mssqlsystemresource1.ldf. To continue, verify that the file exists, and either grant administrator permissions to the account currently running Setup or log in with an administrator account. Then run SQL Server Setup again

You can run the install in repair mode and repair your RTM instance. After that, you should be able to install SP2. Take a look at Books Online or template.ini on the original media for repair mode options. Here's a sample snippet from template.ini to repair all files, reg keys, and shortcuts for a default instance.
11. Repair All files, registry keys and shortcuts for a default instance:

Reference :

Install SQL Express SP2
Sample Error
Microsoft SQL Server 2005 9.00.2047.00
OS Version : Microsoft Windows XP Professional Service Pack 2 (Build 2600)
Time : Installation time

Your system name : Unknown article Result.
SQL Server Setup failed. For more information, review the Setup log file in %ProgramFiles%\Microsoft SQL Server\90\Setup Bootstrap\LOG\Summary.txt.
*) Copy the below and paste in a notepad and save it as fix.cmd
@echo on
cd /d c:\temp
if not exist %windir%\system32\wbem goto TryInstall
cd /d %windir%\system32\wbem
net stop winmgmt
winmgmt /kill
if exist Rep_bak rd Rep_bak /s /q
rename Repository Rep_bak
for %%i in (*.dll) do RegSvr32 -s %%i
for %%i in (*.exe) do call :FixSrv %%i
for %%i in (*.mof,*.mfl) do Mofcomp %%i
net start winmgmt
goto End
if /I (%1) == (wbemcntl.exe) goto SkipSrv
if /I (%1) == (wbemtest.exe) goto SkipSrv
if /I (%1) == (mofcomp.exe) goto SkipSrv
%1 /RegServer
goto End
if not exist wmicore.exe goto End
wmicore /s
net start winmgmt
*) Execute the cmd file
*) Execute sqlncli.msi file from SQL 2005 setup folder or you can download the file from here
*) Then try installing SP2 pack


SQLEXpress installation error
Sample Error:
An instance with the same name is already installed on this computer. To proceed with SQL Server Setup, provide a unique instance name.
You can get this error if your previous uninstallation of SQLExpress doesn't uninstalled properly. You need to cleanup some registry keys to proceed with the installation of SQLExpress. Check out the link "How to clean up a SQL 2005 instance name"
Error MSP Error: 29537 while installing SQL Server 2005 SP3
Sample Error
Product                   : Database Services (MSSQLSERVER)
Product Version (Previous): 4035
Product Version (Final)   :
Status                    : Failure
Log File                  : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\SQL9_Hotfix_KB955706_sqlrun_sql.msp.log
Error Number              : 29537
Error Description         : MSP Error: 29537  SQL Server Setup has encountered the following problem: [Microsoft][SQL Native Client][SQL Server]CREATE DATABASE failed. Some file names listed could not be created. Check related errors.. To continue, correct the problem, and then run SQL Server Setup again.
I found this solution in MSDN forums and it's provided by Prashanth MSFT. I'm adding this since most of them might face this.
By default the setup creates the Temp_MS_AgentSigningCertificate_database Database
on specified default database location,
If the location doesn't exist, it fails to create the database and the setup fails.
1. In SSMS, go to Server Properties > Database Settings > Database Default
Locations ,check default location for Data and Log .
2. Try to access locations specified at Data and Log, Make sure files are available
3. If any of the files missing from above location , we hit the above error.
4. In that case, change the path to point to reall location of mdf/ldf files .
5. Setup should now succeed.

No comments:

Post a Comment

Note: Only a member of this blog may post a comment.

SQL Server Error Logs

* Error Logs maintains events raised by SQL Server database engine or Agent. * Error Logs are main source for troubleshooting SQL Server...

SQL Server DBA Training

SQL Server DBA Training
SQL Server DBA