SSIS will not start after SQL Server 2005 SP1 upgrade

SSIS will not start after SQL Server 2005 SP1 upgrade

• JD Li

  I was reading this post before I installed SP1.
  
  I'm using SQL Server 2005 Standard Edition (x86) on Server 2003 SP1.
  
  I have the same problem.
  
  Start SP1 install.
  
  Patch of Integration Services fails with "A recently applied update, KB913090, failed to install."
  Screenshot
  
  Patch install continued for the rest of the Products ok.
  
  Checked the services after the patch completed (before reboot) and Integration Services service has login set to "Network Service". Changed it to "Local System" (just trying a different login as I have read that others with this problem had success changing the login to a domain acount, I thought I would try "Local System" first and see what happens) and rebooted.
  
  Integration Service failed to start on reboot.
  
  Went into services and Integration Service login was still set as "Network Service" left it as that.
  
  Reapplied the patch.
  
  Patch completes without error and all Products show as successful but when I look at the patch log file I notice that all the Products show "- Not Applied", Including Integration Service. This makes me wonder if the patch applied to the Integration Service at all (remember the patch failed on this the first time).
  
  Went into services and changed the Integration Service to login as Domain Administrator.
  
  Start the Integration Service and it starts ok.
  
  I reboot the server and all the SQL services start ok.
  
  Just on a hunch I re-run SP1. I still curious to see if Integration Services will show up as "- Success" in the SP1 log file.
  
  During the reapplication of the patch I get the "A recently applied update, KB913090, failed to install." error same as the first time I ran the patch. This is with the service running as the Domain Administrator account before SP1 is started.
  Screenshot
  
  I go into services and the Integration Service now has it's login changed to "Network Service"
  
  Somehow SP1 changed the service login from the Domain Administrator account to "Network Service"
  Screenshot
  
  I changed the login for the service back to the Domain Administrator account and the Integration Service starts fine.
  
  My question is has SP1 been applied to the Integration Services Product Why does SP1 change the login of the service to "Network Service" during the patch. Integration Services will not start when the service login is set to "Network Service".
  
  I'll bet that for the people who have changed the login for the Integration Service to a domain account, if they re-run SP1 it will blow up on the Integration Service with the "KB913090" error same as what is happening to me and others.
  
  I can post log files if needed but it appears there is a problem with SP1.
  
  
  For what its worth, SQL2005 SP1 installed just fine on my WinXP machine and the SSIS is running as "Network Service"
  
  
  
  

• f00biebletch

  Funny... I'm not sure how to attach either. :) Are you able to paste the MSP file into the window I've responded to several other posts where people are able to paste in a good chunk of the log file. My guess is that your MSP log file contains a text string consisting of "return value 3". If you can paste in the portion of the log file surrounding that section (+/- 20 lines on each side), we may be able to track it down.

  Thanks,
  Samuel Lester (MSFT)

  
  
  

• xcv

  Thanks for the suggestion, Dan. Was anyone able to try changing the account to get the services to start again I haven't been able to repro this issue internally, so I appreciate the feedback from those who are hitting this.

  Thanks,
  Samuel Lester (MSFT)

  
  
  

• Glen - Mobiform

  Hi Samuel,

  Thanks for the response. I am new to these forums, and can't seem to find a way to attach the log file. I tried pasting it into a comment and the forum page returned an error. Was there a specific part of the log file I could paste in for you

  Edward

  
  

• Andrew Piper

  Hi Samuel,

  I have sent through the logs just now as "PostID358514_Hotfix.zi_", I had to rename the ZIP file to sneak it through our mail system. Thanks for looking into this, and please let me know if I can provide you with any additional information,

  Edward

  
  

• Jack Profit

  Hi Edward, can you attach the MSP log from HotFixDTS\Files\sqlrun_dts.msp This may contain more debug info for us to help out.

  Thanks,
  Samuel Lester (MSFT)

  
  
  

• john cov

  Hi Ryan,

  You are experiencing the exact same thing I have. Except when I set my service to a domain user that is a local admin, it still fails to start. The account is the same one that runs the SQL Server and SQL Agent services, so permissions should be fine. I might have another look tomorrow though, as the service startup account seems to have fixed this problem for everyone else.

  Would be interested to see if this will be a confirmed bug, I have SQL Server 2005 servers in production, and am a little nervous at this stage about deploying the service pack, as I have seen two different hot fix errors on the two test servers I have tried so far,

  Edward

  
  

• MarkHarris

  Hi guys,

  Thankyou for all of the responses, it looks like this may not be an isolated problem. I have tried setting the service startup account to a domain user, but my SSIS service still will not start. Samuel, I also looked in the log, and could not find any "return value 3" records in the log files. Can I please confirm which log file you wanted, under the C:\WINDOWS\Hotfix\DTS9\Logs directory, I have the following log files:

  • DTS9_Hotfix_KB913090.log
  • DTS9_Hotfix_KB913090_0.log
  • DTS9_Hotfix_KB913090_sqlrun_dts.msp.log
  • DTS9_Hotfix_KB913090_sqlrun_dts.msp.out
  • DTS9_Hotfix_KB913090_sqlrun_dts.msp_0.log
  • DTS9_Hotfix_KB913090_sqlrun_dts.msp_0.out
  • DTS9_Hotfix_KB913090_sqlrun_dts.msp_1.log
  • DTS9_Hotfix_KB913090_sqlrun_dts.msp_2.log

  Thanks,

  Edward

  
  

• S.S. Ahmed

  Well lucky for me mine is not production. I'm going to copy the database to my laptop and then just reload the entire box from scratch without SP1. I don't want to put this thing into production with a botched SQL patch. I think I'll wait for SP1a.
  
  

• Daniel Corbett

  Thanks for the reply, Edward. We're been having a difficult time trying to repro this, so your logs would be very helpful. Can you zip up your logs from %windir%\hotfix folder as well as your event viewer logs and send them to me at samles at microsoft dot com

  We will try to dig through them tonight and supply you with a response (which I'll post here once we have solved).

  Thanks,
  Samuel Lester (MSFT)

  
  
  

• Kwanhong Young

  Try changing the "Log On As" to a domain user account. I had the same issue after installing SP1 when using a Built-in Network Service account. After changing it to a domain user account I was able to get the services to start.
  

• Cesar Estrada

  Experiencing exactly the same issue:

  only difference in my scenario:

  • Windows Server 2003 Standard Edition SP1 DE
  • SQL Server 2005 Developer Edition (x86) DE

  The Log extract looks equivalent to mine.

  Help is really appreciated

  
  

• CSved

  Hi guys,

  I'm experiencing the exact same problem after the sql 2005 sp1 update on a clean install of sql 2005.

  Here's a last portion of the DTS9_Hotfix_KB913090_sqlrun_dts.msp.log logfile:

  Property(S): RSGUIDVALUE = {8eba2195-141c-45c2-a0b5-b0a0c166af32}
  Property(S): DTS200532Hotfix2047 = C:\WINDOWS\Installer\2e70386c.msp
  MSI (s) (70:74) [10:32:59:079]: Note: 1: 1728
  MSI (s) (70:74) [10:32:59:079]: Transforming table Error.

  MSI (s) (70:74) [10:32:59:079]: Transforming table Error.

  MSI (s) (70:74) [10:32:59:079]: Note: 1: 2262 2: Error 3: -2147287038
  MSI (s) (70:74) [10:32:59:079]: Transforming table Error.

  MSI (s) (70:74) [10:32:59:095]: Transforming table Error.

  MSI (s) (70:74) [10:32:59:095]: Note: 1: 2262 2: Error 3: -2147287038
  MSI (s) (70:74) [10:32:59:095]: Product: Microsoft SQL Server 2005 Integration Services -- Configuration completed successfully.

  MSI (s) (70:74) [10:32:59:095]: Attempting to delete file C:\WINDOWS\Installer\943f4.msp
  MSI (s) (70:74) [10:32:59:110]: Cleaning up uninstalled install packages, if any exist
  MSI (s) (70:74) [10:32:59:110]: Post-install cleanup: removing installer file 'C:\WINDOWS\Installer\943f4.msp'
  MSI (s) (70:74) [10:32:59:126]: MainEngineThread is returning 0
  MSI (s) (70:88) [10:32:59:126]: Destroying RemoteAPI object.
  MSI (s) (70:E0) [10:32:59:126]: Custom Action Manager thread ending.
  === Logging stopped: 4/20/2006 10:32:59 ===
  MSI (c) (08:F0) [10:32:59:173]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
  MSI (c) (08:F0) [10:32:59:188]: MainEngineThread is returning 0
  === Verbose logging stopped: 4/20/2006 10:32:59 ===

  Thanks,

  Jurgen Schouten

  
  

• Anthony Alvarado

  Samuel Lester - MSFT wrote:

  Was anyone able to try changing the account to get the services to start again

  That actually did the trick! Good Workaround, thanks Dan.

  Greetings Monte

  
  
• SSIS will not start after SQL Server 2005 SP1 upgrade