SSIS fails to start after the Intel team performed windows patching. The service runs under "NT Authority\NetworkService" account. I tried to change the service account to "Local System, Local Service and even a domain account" but it get a pop-up when I click apply with WMI Provider Error "The service did not respond to the start or control request in a timely fashion. [0x8007041d]". The windows system log displays 2 errors as below: EventID 7009; Timeout (30000 milliseconds) waiting for the SQL Server Integration Services service to connect. EventID 7000; The SQL Server Integration Services service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion. Other SQL Services are running fine (they are running under a domain account). The problem we have with SSIS not running is that the maintenance plan jobs are failing. The instance is SQL Server 2005 Standard edition. The other issue I noticed is that SSMS throws an error when I try to connect to the SQL instance (I have attached the screen shot of the error). The list of updates they put on the machine are: Security Update for Windows Server 2003 x64 Edition (KB2659262)Security Update for Microsoft .NET Framework 2.0 SP2 on Windows Server 2003 and Windows XP for x64-based Systems (KB2604092)Security Update for Windows Server 2003 x64 Edition (KB2686509)Security Update for Microsoft .NET Framework 3.0 SP2 on Windows Server 2003 and Windows XP for x64-based Systems (KB2604110)Security Update for Windows Server 2003 x64 Edition (KB2676562)Security Update for Microsoft .NET Framework 3.0 SP2 on Windows Server 2003 and Windows XP for x64-based Systems (KB2656407) - This one failed with error "Installation Failure: Windows failed to install the following update with error 0x80070643"Security Update for Microsoft .NET Framework 3.5 SP1 on Windows XP, Server 2003, Vista, and Server 2008 for x64 (KB2604111) I would appreciate if anyone can advise if the issue because of patching ? How can the issue be resolved. Thank you in advance.Don

Hi, There's a couple of connect entries with similar faults to yours. You could see if either workaround/resolution helps... http://connect.microsoft.com/VisualStudio/feedback/details/510186/system-configuration-configurationerrorsexception-unrecognized-configuration-section-system-servicemodel-c-windows-microsoft-net-framework-v2-0-50727-config-machine-config-line-146 https://connect.microsoft.com/VisualStudio/feedback/details/323659/unrecognized-configuration-section-system-servicemodel-after-installing-visual-studio-2008 Thanks, Andrew Bainbridge SQL Server DBA Please click "Propose As Answer" if a post solves your problem, or "Vote As Helpful" if a post has been useful to you

Had the EXACT same problem (SSMS would not connect and SSIS would not start) after windows patching this weekend. Go to C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\CONFIG Backup machine.config Go to C:\WINDOWS\Microsoft.NET\Framework64\v2.0.50727\CONFIG Backup machine.config Connect to another server that IS working Copy the machine.config file from there and replace the above two files. All working for me after that.