SSIS service fails to start

Question

SSIS service fails to start

Sahin Kaya

SSC-Addicted

Points: 461
More actions
June 4, 2007 at 5:08 am

#153615

Hello,

I have an SSIS package which calls so many SSIS packages in order. It was perfectly working; all the ETL job was finishing in 1,3 hrs. However suddenly something happened and it became very very much slow (Now it tooks 12+ hrs to complete). The package is in a server at a contractor company. Their administrators do not have any idea what happened also.

I checked first the event viewer. When SSIS is started we get the following system error in the event viewer continuously.
"Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7000
Date:  31.05.2007
Time:  10:04:00
User:  N/A
Computer: ACORNDB
Description:
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.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp."
Then I noticed that the SSIS service in the Services is not working. When I try to restart it, it gives the following message:
"Could not start the SQL server integration services service on Local Computer.
Error 1053: The service did not respond to the start or control request in a timely fashion."
I checked several sources on internet and reached that similar problem can be faced during the SP1 update. However this is not our case since SP1 was already installed during the creation of the SSIS package and "its perfect" run.
We are in a contract based project and deadline is approaching. This package and SSIS is very critical for us. Your suggestion on the resolution of the problem very very much appreciated.

Thanks a lot in advance.

Best regards,
Sahin.

Viewing 4 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic. Login to reply

Tommy Bollhofer SSChampion Points: 14940 More actions · Answer 1

Have you verified the MsDtsSrvr.exe executable? i.e. Is it still in "C:\Program Files\Microsoft SQL Server\90\DTS\Binn\MsDtsSrvr.exe"? Can you launch from the command line and connect via management studio?

Tommy

Follow @sqlscribe

SQLBill SSC Guru Points: 51440 More actions · Answer 2

SP1 had many problems....you really should install SP2.

Also, you might want to consider this:

Configure SSIS to allow remote user access

1.If the user is not a member of the local Administrators group, add the user to the Distributed COM Users group. You can do this in the Computer Management MMC snap-in accessed from the Administrative Tools menu.

2.Open Control Panel, double-click Administrative Tools, and then double-click Component Services to start the Component Services MMC snap-in.

3.Expand the Component Services node in the left pane of the console. Expand the Computers node, expand My Computer, and then click the DCOM Config node.

4.Select the DCOM Config node, and then select MsDtsServer in the list of applications that can be configured.

5.Right-click on MsDtsServer and select Properties.

6.In the MsDtsServer Properties dialog box, select the Security tab.

7.Under Launch and Activation Permissions, select Customize, then click Edit to open the Launch Permission dialog box.

8.In the Launch Permission dialog box, add or delete users, and assign the appropriate permissions to the appropriate users and groups. The available permissions are Local Launch, Remote Launch, Local Activation, and Remote Activation. The Launch rights grant or deny permission to start and stop the service; the Activation rights grant or deny permission to connect to the service.

9.Click OK to close the dialog box.

10.On the same security tab, under Access Permission, select Customize, then click Edit to open the Access Permission dialog box

11.In the Access Permission dialog box, add or delete users, and assign the appropriate permissions to the appropriate users and groups. The available permission are Local Access, and Remote Access. The easiest is to add the local DCOM Distributed Users Group.

12.Click okay to close the dialog box.

13.The final set of permissions applied on the DCOM application is controlled by the Access Limits on the COM Security of the computer. In the Component Services configuration screen, right Click "My Computer" and select properties. Then select the COM Security Tab.

14.Even though the security permission can be set on the individual DCOM application, the final permission set has to fall within the Limits specified with in the COM Security Configuration. Click "Edit Limits.." and add the domain user or group to which the you want to give SSIS access. Ensure that you have given Remote Launch and Remote Activation permissions to the newly added User or Group.

15.Click okay to close the dialog box. Close the MMC snap-in

16.Restart the Integration Services service.

-SQLBill

Sahin Kaya SSC-Addicted Points: 461 More actions · Answer 3

Thank you very much for your comments and guidance for the solution.

I am informed by the contractor company hosting the server about that the standard Microsoft patches ( for SP1 update SSIS problems) are installed and the problem is solved.

Thanks again.

Best regards,

Sahin.