Workflow service not starting on WinServer 2003 - any ideas, hitting a wall here!
-
Hi Everyone, If anyone has even a remote idea of what might be wrong, please let me know so that we can test it. We have written a Workflow service in C#, generated and then installed it. Problem is, it is not starting on the server. It starts up on my Dev machine fine, and on 2 other Dev pc's, but as soon as we install it to the server, I get the following error. "error 1053:the service did not respond to the start or control request in a timely fashion" I tried on my dev with the same service account used on the service, which didn't start until i added the account to the Administrator group. then it worked on my local dev. When adding the account to the server Admin group, still getting the same error... Anyone know anything we can try to get this up and running? Are there specific framework installs we need to add perhaps for workflow services? I literally can't think of anything else to try. Thanks, Yoken PS. My Dev machine runs : Win7, VS2008 | the server runs WinServ2003, all .net frameworks installed (1,2,3+)
-
Hi Everyone, If anyone has even a remote idea of what might be wrong, please let me know so that we can test it. We have written a Workflow service in C#, generated and then installed it. Problem is, it is not starting on the server. It starts up on my Dev machine fine, and on 2 other Dev pc's, but as soon as we install it to the server, I get the following error. "error 1053:the service did not respond to the start or control request in a timely fashion" I tried on my dev with the same service account used on the service, which didn't start until i added the account to the Administrator group. then it worked on my local dev. When adding the account to the server Admin group, still getting the same error... Anyone know anything we can try to get this up and running? Are there specific framework installs we need to add perhaps for workflow services? I literally can't think of anything else to try. Thanks, Yoken PS. My Dev machine runs : Win7, VS2008 | the server runs WinServ2003, all .net frameworks installed (1,2,3+)
I think you have already this patch (old one): http://support.microsoft.com/?kbid=839174[^] You can easily remotely debug your service: http://support.microsoft.com/kb/824344[^] I cann't help too much on it, I dind't write a service for while....
-
I think you have already this patch (old one): http://support.microsoft.com/?kbid=839174[^] You can easily remotely debug your service: http://support.microsoft.com/kb/824344[^] I cann't help too much on it, I dind't write a service for while....
thanks for the input Migounette, unfortunately those links didn't help much. The patch is allready loaded yes, and the remote debug only works once the service has started... which is the problem I'm having. I'll post any new developments related to this issue.
-
Hi Everyone, If anyone has even a remote idea of what might be wrong, please let me know so that we can test it. We have written a Workflow service in C#, generated and then installed it. Problem is, it is not starting on the server. It starts up on my Dev machine fine, and on 2 other Dev pc's, but as soon as we install it to the server, I get the following error. "error 1053:the service did not respond to the start or control request in a timely fashion" I tried on my dev with the same service account used on the service, which didn't start until i added the account to the Administrator group. then it worked on my local dev. When adding the account to the server Admin group, still getting the same error... Anyone know anything we can try to get this up and running? Are there specific framework installs we need to add perhaps for workflow services? I literally can't think of anything else to try. Thanks, Yoken PS. My Dev machine runs : Win7, VS2008 | the server runs WinServ2003, all .net frameworks installed (1,2,3+)
Hi All, Just to let you know, after how long of searching for an answer, in the end the problem was inside the code on initializing a public variable. instead of having [very rough]
public class myclass
{
workflowservicehost host = new workflowservicehost();public myclass(...) {}
}
I had to change it to
public class myclass
{
workflowservicehost host;public myclass(...)
{
host = new workflowservicehost();
}
}Doing this fixed the "Error 1053", and the service started without hassle! Now, if only I can find out WHY that worked on my dev machine (Win7, VS2008) and not when deployed to the server (WinServ2003), it sure would be great! My only thought is something to do with the underlying infrastructure, but any guess further that that is well.. yet another guess.