www.skelta.com
Home      Members   Calendar   Who's On

Welcome Guest ( Login | Register )
      

Home » BPM.NET 2007/Sharepoint Accelerator 2007 » BPM.NET 2007/Sharepoint Accelerator 2007 » Workflow Execution » Engine Services


Engine ServicesExpand / Collapse
Author
Message
Posted Friday, January 25, 2008
Senior Member

Senior MemberSenior MemberSenior MemberSenior MemberSenior MemberSenior MemberSenior MemberSenior Member

Group: Forum Members
Last Login: Tuesday, March 18, 2008
Posts: 9, Visits: 44
Hi there,

Im facing this error while trying to start the engine services.

" Could not start the SKELTA 2007- Notification Engine Service on Local ComputerError 1053: The service did not respond to the start or control request in the timely fashion."

How to solve this problem?

Thanks.

silver_angel

Post #422
Posted Friday, January 25, 2008
Supreme Being

Supreme BeingSupreme BeingSupreme BeingSupreme BeingSupreme BeingSupreme BeingSupreme BeingSupreme Being

Group: Forum Members
Last Login: Today @ 6:29 AM
Posts: 105, Visits: 556
Hi Angel,

Please check the SMTP,POP3, SMS configuration settings in the Form-Configuration-Wizard.

Something could be wrong in the configuration, which stops the Notification service to start.

Try iisreset before you start the services. If Issue persists, please send the screen-shot of the error in Skelta-Log-Console?

 

Regards,

Bineesh E Raghavan

Post #423
Posted Friday, January 25, 2008
Supreme Being

Supreme BeingSupreme BeingSupreme BeingSupreme BeingSupreme BeingSupreme BeingSupreme BeingSupreme Being

Group: Forum Members
Last Login: Saturday, April 26, 2008
Posts: 128, Visits: 422
Hi,
The  error will get logged in application event viewer. Can you post that information.
Start-> Run->  eventvwr
regards,

Moderator
Post #424
Posted Sunday, January 27, 2008
Senior Member

Senior MemberSenior MemberSenior MemberSenior MemberSenior MemberSenior MemberSenior MemberSenior Member

Group: Forum Members
Last Login: Tuesday, March 18, 2008
Posts: 9, Visits: 44
hi there,

I've already reset the iis. However the problems still occur. These are the problems view from the event viewer.

1) Notification Engine error:

Could not start the SKELTA 2007- Notification Engine Service on Local Computer.

Error 1053: The service did not respond to the start or control request in the timely fashion.

2) Client Services error:

The Skelta - Client Service service failed to start due to the following error:

The service did not respond to the start or control request in a timely fashion.

3) Workflow engine error:

The Skelta 2007 - Workflow Engine service failed to start due to the following error:

The service did not respond to the start or control request in a timely fashion.

4) Task scheduler error:

The Skelta 2007 - Task Scheduler service failed to start due to the following error:

The service did not respond to the start or control request in a timely fashion.

How to solve this problem?

Thanks

silver_angel

Post #431
Posted Monday, January 28, 2008
Supreme Being

Supreme BeingSupreme BeingSupreme BeingSupreme BeingSupreme BeingSupreme BeingSupreme BeingSupreme Being

Group: Forum Members
Last Login: Today @ 6:29 AM
Posts: 105, Visits: 556
Hi Angel,

We might need to dive deep to check this issue. I would suggest raising a support ticket for the same

Regards,

Bineesh E Raghavan

Post #433
Posted Monday, January 28, 2008
Supreme Being

Supreme BeingSupreme BeingSupreme BeingSupreme BeingSupreme BeingSupreme BeingSupreme BeingSupreme Being

Group: Forum Members
Last Login: Saturday, April 26, 2008
Posts: 128, Visits: 422
Hi,
There was a service timout issue in few environments for windows services which is taken care in the latest patch. However please try the below steps to increase the service timeout and let me know how it goes.this is an extract from microsoft article.Set the service start time to 3 Minutes

When a service starts, the service communicates to the Service Control Manager how long the service must have to start (the time-out period for the service). If the Service Control Manager does not receive a "service started" notice from the service within this time-out period, the Service Control Manager terminates the process that hosts the service. This time-out period is typically less than 30 seconds. If you do not adjust this time-out period, the Service Control Manager ends the process and the attached debugger while you are trying to debug. To adjust this time-out period, follow these steps:
a. In Registry Editor, locate, and then right-click the following registry subkey:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control
b. Point to New, and then click DWORD Value. In the right pane of Registry Editor, notice that New Value #1 (the name of a new registry entry) is selected for editing.
c. Type ServicesPipeTimeout to replace New Value #1, and then press ENTER.
d. Right-click the ServicesPipeTimeout registry entry that you created in step c, and then click Modify. The Edit DWORD Value dialog box appears.
e. In the Value data text box, type TimeoutPeriod, and then click OK

Note TimeoutPeriod is a placeholder for the value of the time-out period (in milliseconds) that you want to set for the service. For example, if you want to set the time-out period to 24 hours (86400000 milliseconds), type 86400000.
f. Restart the computer. You must restart the computer for Service Control Manager to apply this change.

http://support.microsoft.com/kb/824344

regards,


Moderator
Post #440
« Prev Topic | Next Topic »


Reading This TopicExpand / Collapse
-
Active Users: 1 (1 guest, 0 members, 0 anonymous members)
No members currently viewing this topic.

All times are GMT -5:00, Time now is 11:08pm

 
Execution: 0.172.9 queries.Compression Enabled.

Copyright © 2002 - 2007 Skelta Software. All rights reserved. Tel: 1 (703) 229-6732 | Email:sales@skelta.com
Skelta - A BPM Workflow Software Company