Configuring Microsoft Sql Server Error Code 1603
Contents |
(Русский)ישראל (עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) HomeLibraryLearnDownloadsTroubleshootingCommunityForums Ask a question Quick access Forums home Browse forums users FAQ Search related threads Remove From My error 1603 installing microsoft sql server 2005 Forums Asked by: error 1603 installing microsoft sql server 2005 error 1603 installing microsoft sql server 2005 setup support files setup support files SQL Server > SQL Server Setup & Upgrade Question 0 Sign
Error 1603 Installing Microsoft Sql Native Client
in to vote I'm attempting to install the standard version of SQL server 2005 on XP SP2. I'm getting the following:Errors occurred during the
Installation Success Or Error Status 1603 Windows 7
installation:Error 1603 installing Microsoft SQL Server 2005 setup support files. Wednesday, February 13, 2008 4:19 AM Reply | Quote All replies 0 Sign in to vote Are you installing from dumbs? Check if this is your case... http://support.microsoft.com/kb/916760 Madhu Wednesday, February 13, 2008 8:36 AM Reply | mainenginethread is returning 1603 Quote Moderator 0 Sign in to vote I am not sure if this KB will help, http://support.microsoft.com/kb/916760May be if it nothing works, its better you can completely uninstall using Windows installer Cleanup utility and try the installation once again, http://support.microsoft.com/kb/290301. Refer this link to manually remove Sql Server 2005, http://support.microsoft.com/kb/909967- Deepak Wednesday, February 13, 2008 8:37 AM Reply | Quote Moderator 0 Sign in to vote I'm not clear on what dumbs are. I'm installing from two iso images from MSDN download library. I have two CD's as a result. I read the KB and I don't think this is the problem. I'm copying an excerpt from the log file. I noticed that it is having an issue insalling support files. Here it is:WorkDir=D:}} {t:\yukon\sql\setup\sqlcu\dll\scusetupmgr.cpp:365}
WITH ERROR 1603 ★★★★★★★★★★★★★★★ Parikshit SavjaniFebruary 11, 20093 0 0 0 Many times we need to reinstall a
Error Code 1603 Sql Server 2012
sql server instance due to number of reason. Whenever you reinstall sql server database services setup failed 2005 the sql server instance the success of the installation of the new sql server instance primarily depends on how to uninstall sql server 2005 completely the whether the previous uninstall of the sql server was clean so that all the registry keys and the related folders are deleted. If the un-installation is done primarily https://social.msdn.microsoft.com/Forums/sqlserver/en-US/d8817b8e-d13c-4705-a7d2-f9eb324d2b16/error-1603-installing-microsoft-sql-server-2005-setup-support-files?forum=sqlsetupandupgrade from GUI and if it is successful we can say that the uninstall was clean, however if you go for manual un-installation you need to ensure that all the related registry keys and folders are deleted. We can refer to the following KB article to manually cleanup the sql server instance http://support.microsoft.com/kb/909967 However if the previous un-installation was not https://blogs.msdn.microsoft.com/sqlserverfaq/2009/02/11/sql-server-2005-instance-failing-to-install-after-trying-to-reinstall-with-error-1603/ clean, when trying to reinstall the sql server instance the installation may fail with error 1603. As we have mentioned in our previous post whenever an setup installation fails we need to first check the Summary.txt to check for the Error Message which caused the failure. ----------------------------------------------------- Machine : NODE01 Product : Microsoft SQL Server 2005 Product Version : 9.00.1399.06 Install : Failed Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup001_NODE01_SQL.log Error Number : 1603 ----------------------------------------------------- Machine : NODE02 Product : Microsoft SQL Server 2005 Product Version : 9.00.1399.06 Install : Failed Log File : \\NODE01\C$\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup001_NODE02_SQL.log Error Number : 1602 ----------------------------------------------------- We checked the SQLSetup001_NODE01_SQL.log which is mentioned above and looked for “Return Value 3” and reached the following part of the log which leads us to the root cause of the error SQLSetup001_NODE01_SQL.log ======================= MSI (s) (34:E4) [02:35:53:642]: Doing action: CAResolveInstanceName.68C6D15C_77E0_11D5_8528_00C04F68155C Action ended 02:35:53: SQLLicensing.D20239D7_E87C_40C9_9837_E70B8D4882C2. Return value 1. MSI (s) (34:A0) [02:35:53:642]: Invoking remote custom action. DLL: C:\WINDOWS\Installer\MSI32F.tmp, Entrypoint: ResolveInstanceName Action start 02:35:53: CAResolveInstanceName.68C6D15C_77E0_11D5_8528_00C04F68155C. FTECa.DLL: INFO: FTE: ResolveInstanceName(), Entering… FTECa.
error 1603 ★★★★★★★★★★★★★★★ HarshDeep_SinghMarch 19, 20121 0 0 0 Ran into this interesting issue recently. https://blogs.msdn.microsoft.com/sqljourney/2012/03/19/sql-server-patch-installation-fails-with-error-1603/ I was trying to install a patch on SQL, and it failed. I searched in the hotfix.log (since this was a SQL 2005 instance), and found these messages:- 02/03/2012 03:01:03.649 Installing file: sqlrun_sql.msp 02/03/2012 03:01:03.696 Copy Engine: Creating MSP install log file at: C:Program Files (x86)Microsoft SQL Server90Setup BootstrapLOGHotfixSQL9_Hotfix_KB2494113_sqlrun_sql.msp.log 02/03/2012 03:01:03.696 Registry: sql server Opened registry key "SoftwarePoliciesMicrosoftWindowsInstaller" 02/03/2012 03:01:03.696 Registry: Cannot read registry key value "Debug", error 0 02/03/2012 03:01:04.226 MSP returned 1603: A fatal error occurred during installation. From here, you can determine which component failed (in this case it was sqlrun_sql). In case of SQL 2008 and R2, the summary.txt will point you to microsoft sql server the relevant component's log file:- Log with failure: C:Program FilesMicrosoft SQL Server100Setup BootstrapLog20111228_093034SQL8sql_fulltext_Cpu64_1.log Upon opening the log of the particular component, you will see something like this:- MSI (s) (F0:84) [09:38:53:925]: Opening existing patch ‘C:WindowsInstaller278e8021.msp'. MSI (s) (F0:84) [09:38:53:925]: SequencePatches starts. Product code: {F233AB42-A61A-4FAB-82A5-A0EBEE94176E}, Product version: 10.50.1600.1, Upgrade code: {5A5E4CCE-8348-4EF8-8FA1-2B5524329CF5}, Product language 1033 MSI (s) (F0:84) [09:38:53:926]: PATCH SEQUENCER: verifying the applicability of minor upgrade patch p:c5316177906c8cf6c8a3248b50ccx64setupsql_fulltext.msp against product code: {F233AB42-A61A-4FAB-82A5-A0EBEE94176E}, product version: 10.50.1600.1, product language 1033 and upgrade code: {5A5E4CCE-8348-4EF8-8FA1-2B5524329CF5} MSI (s) (F0:84) [09:38:53:926]: Note: 1: 2262 2: _Tables 3: -2147287038 MSI (s) (F0:84) [09:38:53:926]: Note: 1: 2262 2: _Columns 3: -2147287038 MSI (s) (F0:84) [09:38:53:926]: PATCH SEQUENCER: minor upgrade patch p:c5316177906c8cf6c8a3248b50ccx64setupsql_fulltext.msp is applicable. MSI (s) (F0:84) [09:38:53:926]: SequencePatches returns success. MSI (s) (F0:84) [09:38:53:926]: Final Patch Application Order: MSI (s) (F0:84) [09:38:53:926]: {2E7EB973-48D5-43CA-9360-CA011FAE81EE} - p:c5316177906c8cf6c8a3248b50ccx64setupsql_fulltext.msp MSI (s) (F0:84) [09:38:53:926]: Other Patches: MSI (s) (F0:84) [09:38:53:926]: Internal Exception during install operation: 0xc0000005 at 0x0