asked
SQL 2005: Add SSIS after Service Pack?
I have an SQL 2005 installation with SP3. I need SSIS but it's not installed. I tried to install it but it failed; I suspect it's because of the presence of the service pack. Can anyone confirm that? If this is in fact the problem, I presume I'll have to backup the databse, un-install, reinstall with SSIS, re-apply the service pack (I think SP4 is out?) and then restore the database. Does that sound correct? I've tried to confirm my assumption via Google but no luck. Sorry if this is a newbie question, but that's kinda what I am. Thanks in advance for any help. bimplebean
what error did you get trying to install it? Were you going through Add/Remove and adding a new feature?
SSIS should be able to be installed after the fact (and then the SP applied to that component) so I would assume you have a different issue. Can you get the install logs attached to your question?
Feeling rather foolish - I'm going to go through the install again and try to capture the error log(s) in question - there are so many... I *did* run the installer via Add/Remove programs - find SQL 2005 and hit the 'change' button. I presume that's correct? I'll post more info in a few minutes. Thanks in advance for your help...
I ran this from Add/Remove programs. Summary Log only shows failure of MSXML 6 Service Pack 2. No mention of SSIS at all. Setup Progress finished, reported failure of both MSXML6SP2 and SSIS. The Core.log file contained this nugget: Error: Action "LaunchPatchedBootstrapAction" threw an exception during execution. Error information reported during run: "C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\setup.exe" finished and returned: 1603 Aborting queue processing as nested installer has completed Message pump returning: 1603 Summary Log Folows. I'm going to Google this 1603 error - that number sounds familiar. ----------------- Microsoft SQL Server 2005 9.00.4035.00 ============================== OS Version : Microsoft Windows XP Professional Service Pack 3 (Build 2600) Time : Fri Feb 10 11:11:13 2012 PCSLAB04 : To change an existing instance of Microsoft SQL Server 2005 to a different edition of SQL Server 2005, you must run SQL Server 2005 Setup from the command prompt and include the SKUUPGRADE=1 parameter. Machine : PCSLAB04 Product : Microsoft SQL Server Setup Support Files (English) Product Version : 9.00.4035.00 Install : Successful Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0010_PCSLAB04_SQLSupport_1.log -------------------------------------------------------------------------------- Machine : PCSLAB04 Product : Microsoft SQL Server Native Client Product Version : 9.00.4035.00 Install : Successful Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0010_PCSLAB04_SQLNCLI_1.log -------------------------------------------------------------------------------- Machine : PCSLAB04 Product : Microsoft Office 2003 Web Components Product Version : 11.0.6558.0 Install : Successful Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0010_PCSLAB04_OWC11_1.log -------------------------------------------------------------------------------- Machine : PCSLAB04 Product : Microsoft SQL Server 2005 Backward compatibility Product Version : 8.05.2312 Install : Successful Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0010_PCSLAB04_BackwardsCompat_1.log -------------------------------------------------------------------------------- Machine : PCSLAB04 Product : MSXML 6 Service Pack 2 (KB954459) Product Version : 6.20.1099.0 Install : Failed Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0010_PCSLAB04_MSXML6_1.log Error Number : 1603 --------------------------------------------------------------------------------
I *think* found the solution. Evidently MSXML6.0 SP2 does not play nicely with others. The advice I found and followed was to use the MS Windows Installer Cleanup Utility to remove references to it in Windows. At that point the setup completed successfully. HOwever, now that I try to connect to Integration Services on the server I'm told "The service did not respond to the start or control request in a timely fashion." I'm going to poke around some more, but suggestions are still welcome...
We still recommend installing the SP.. or, at a minimum, starting it and seeing what it believes needs updating.
Not yet -- amazingly, the server had no internet access, which could have caused the problem (See [here][1].) Working on that now. I'm in a virtual world, big bureaucracy, and everyone just went to lunch! [g] I'm not even sure I have to apply the service pack.. once connectivity is restored, I'll find out and post back here. [1]:
http://support.microsoft.com/kb/918644
Okay, the server is now on the internet. SSIS is installed and runs fine. Thanks everyone!
4 People are following this question.
