Service hangs when starting on 2008 R2 server
i have a service that we have been installing on 2003 r2 32 bit server that works fine on 2003 server. When I install the the service on 2008 R2 server the service installs fine but hangs when I try to start it. The only error I get is "the service did not start in a timely fashion".
This very vague I understand but I don't have any errors to work with and need to get this service to start. Can anyone offer any suggestions on what I may need to do to get this service to start?
This very vague I understand but I don't have any errors to work with and need to get this service to start. Can anyone offer any suggestions on what I may need to do to get this service to start?
ASKER
It is a custom service for our application. It appears to be a DCOM permission issue but without an error message of some kind I am lost as to how to find the DCOM setting that needs to be modified.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thank You,
DCOM is enabled, The second link does not seem to apply.
I am now having the same problem with a 2003 r2 server that normally does not have any problems installing the service.
DCOM is enabled, The second link does not seem to apply.
I am now having the same problem with a 2003 r2 server that normally does not have any problems installing the service.
Jimmy
Have you looked at the event log especially the system log and application log
start service then look at both logs
what you get?
Have you looked at the event log especially the system log and application log
start service then look at both logs
what you get?
ASKER
Only say that the service did not start in a timely fashion.
Update, Problem solved. - The configuration found in the database was at fault. Once the corrections were made to the data base the service started. I did not know the service was dependant on the database configuration. :-(
Update, Problem solved. - The configuration found in the database was at fault. Once the corrections were made to the data base the service started. I did not know the service was dependant on the database configuration. :-(
ASKER
That was the problem with the 32 bit server, The 2008 R2 server will still not start the service.
When you try in on the 2008 server what does the event logs show?
ASKER
event logs show the service did not start in a timely manner.
Update: The problem was the database configuration on the 2008 server also.
Update: The problem was the database configuration on the 2008 server also.
ASKER
Clues in these links lead me to the solution.
Sounds like this service is not supported on 2008 server.
You service may not run on 64 bit server.