Hi everyone,
I've a problem which I think a lot of SQL Server 2005 users had already ...however I didn't found any answers so far. Maybe anyone of you might know. 
I have installed SP1 for SQL Server 2005 on 2 systems, one is an Enterprise Edition (english) on a Win. 2003 SP1 system and one is a Developer Edition (also english) on a Win. XP Prof. system.
On both systems the installation process of the SP1 worked fine except that it gave me the message "Reboot required" on the step installation of SQL Server Native Client.
After my reboot I reexecuted the installation of SP1 with the result of no error nor reboot message. Everything seemed fine....
However when I checked the status of the services I recognized that the SSIS has switched from LOG ON AS ...my specific login.... to NT AUTHORITY\NetworkService and the automatic startup failed.
I tried to change the login to my previous login which also failed. It tried to change it to any other possible login but the startup with all logins failed with the error message:
The service did not respond to the start or control request in a timely fashion.
The event log of the system does tell me the same error message. The summary log of the SP1 installation doesn't show any error or warning message except "Failed to read registry key: Debug". Enclosed is the log file:
05/02/2006 22:11:09.609 ================================================================================
05/02/2006 22:11:09.625 Hotfix package launched
05/02/2006 22:17:22.296 Attempting to install instance: SQL Server Native Client
05/02/2006 22:17:22.312 Attempting to install target: MHPA0F7C
05/02/2006 22:17:22.312 Attempting to install file: sqlncli.msi
05/02/2006 22:17:22.328 Attempting to install file: e:\de43f41a74855a4cfc41014b760758\HotFixSqlncli\Files\sqlncli.msi
05/02/2006 22:17:22.328 Creating MSI install log file at: D:\WINNT\Hotfix\Redist9\Logs\Redist9_Hotfix_KB913090_sqlncli.msi.log
05/02/2006 22:17:22.343 Successfully opened registry key: Software\Policies\Microsoft\Windows\Installer
05/02/2006 22:17:22.343 Failed to read registry key: Debug
05/02/2006 22:17:38.437 MSP returned 3010: A restart is required to complete the install. This message is indicative of a success. This does not include installs where the ForceReboot action is run. This error code is not available on Windows Installer version 1.0.
05/02/2006 22:17:38.515 Successfully opened registry key: Software\Policies\Microsoft\Windows\Installer
05/02/2006 22:17:38.515 Failed to read registry key: Debug
05/02/2006 22:17:38.515 Pending reboot, successfully installed file: e:\de43f41a74855a4cfc41014b760758\HotFixSqlncli\Files\sqlncli.msi
05/02/2006 22:17:38.515 Successfully installed target: MHPA0F7C
05/02/2006 22:17:38.515 Successfully installed instance: SQL Server Native Client
05/02/2006 22:17:38.515
05/02/2006 22:17:38.515 Product Status Summary:
05/02/2006 22:17:38.515 Product: SQL Server Native Client
05/02/2006 22:17:38.515 SQL Server Native Client (RTM ) - Reboot Required
05/02/2006 22:17:38.515
05/02/2006 22:17:38.515 Product: Setup Support Files
05/02/2006 22:17:38.515 Setup Support Files (RTM ) - Not Applied
05/02/2006 22:17:38.531
05/02/2006 22:17:38.531 Product: Database Services
05/02/2006 22:17:38.531 Database Services (RTM 1399 ENU) - Not Applied
05/02/2006 22:17:38.531 Analysis Services (RTM 1399 ENU) - Not Applied
05/02/2006 22:17:38.531 Reporting Services (RTM 1399 ENU) - Not Applied
05/02/2006 22:17:38.531
05/02/2006 22:17:38.531 Product: Notification Services
05/02/2006 22:17:38.531 Notification Services (RTM 1399 ENU) - Not Applied
05/02/2006 22:17:38.531
05/02/2006 22:17:38.531 Product: Integration Services
05/02/2006 22:17:38.531 Integration Services (RTM 1399 ENU) - Not Applied
05/02/2006 22:17:38.531
05/02/2006 22:17:38.531 Product: Client Components
05/02/2006 22:17:38.531 Client Components (RTM 1399 ENU) - Not Applied
05/02/2006 22:17:38.531
05/02/2006 22:17:38.531 Product: MSXML 6.0 Parser
05/02/2006 22:17:38.531 MSXML 6.0 Parser (RTM ) - Not Applied
05/02/2006 22:17:38.531
05/02/2006 22:17:38.562 Product: SQLXML4
05/02/2006 22:17:38.593 SQLXML4 (RTM ) - Not Applied
05/02/2006 22:17:38.687
05/02/2006 22:17:38.687 Product: Backward Compatibility
05/02/2006 22:17:38.687 Backward Compatibility (RTM ) - Not Applied
05/02/2006 22:17:38.687
05/02/2006 22:17:38.687 Product: Microsoft SQL Server VSS Writer
05/02/2006 22:17:38.687 Microsoft SQL Server VSS Writer (RTM ) - Not Applied
05/02/2006 22:17:38.687
I know there are a lot more LOG files in the directory ..\HotFix.. which might tell more about the problem. However I don't know in which file I have to look.
Can anyone help me
Regards,
Stefan
SSIS doesn't start’anymore after SP1 installation
Freddie2
Jackrv
Sorry but any kind of proxy configuration won't help be since this server doesn't have any internet access not proxy access. It doesn't even have access to intranet. This server and some other of this kind are high security server which don't have any external access except those which explicitly allowed.
In this case post 5 helped with the information of changing the registry key
[HKEY_USERS\S-1-5-20\Software\Microsoft\Windows\CurrentVersion\WinTrust\TrustProviders\SoftwarePublishing]
"State"=dword:00023e00
However it doesn't really satisfy me to do this!!!
Ryan Chapman
http://support.microsoft.com/kb/918644
Geof The Canuck
http://lab.msdn.microsoft.com/productfeedback/viewfeedback.aspx feedbackid=e16d718b-e7a0-4071-bada-4c836eced395
In a nutshell change your registry as follows:
[HKEY_USERS\S-1-5-20\Software\Microsoft\Windows\CurrentVersion\WinTrust\TrustProviders\SoftwarePublishing]
"State"=dword:00023e00
dudu460
Hi Ryan,
many thanks that really works. Of course in my case I had to look under a different registry key since I'm using a different user to startup the SSIS ...but it works now.
Attn. Microsoft:
If somebody from MS is reading this message please, please think about the fact that some servers are not allowed to have access to the internet.
I my case there are a couple of servers which are for security reasons completely isolated from any network access. Only dedicated and explictly permitted communication is allowed.
Regards,
Stefan
D5