Service Fails to Finish Starting - Revision history

Gityerfix: Reverted edits by Agegeleruvy (Talk); changed back to last version by Gityerfix

2010-11-30T05:27:50Z

Reverted edits by Agegeleruvy (Talk); changed back to last version by Gityerfix

Agegeleruvy at 03:15, 24 November 2010

2010-11-24T03:15:10Z

Gityerfix at 05:52, 6 August 2008

2008-08-06T05:52:49Z

Gityerfix at 18:59, 26 July 2008

2008-07-26T18:59:03Z

Gityerfix at 05:18, 26 July 2008

2008-07-26T05:18:46Z

Gityerfix at 21:29, 25 July 2008

2008-07-25T21:29:13Z

Gityerfix at 13:59, 18 July 2008

2008-07-18T13:59:38Z

Gityerfix: New page: Category:Miscellaneous NOTOC This article provides procedures to follow if the Service Desk Service fails to start and remains in the ''Starting'' state.
--Article prov...

2008-07-08T02:59:09Z

New page: Category:Miscellaneous __NOTOC__ This article provides procedures to follow if the Service Desk Service fails to start and remains in the ''Starting'' state. --Article prov...

New page

[[Category:Miscellaneous]]
__NOTOC__
This article provides procedures to follow if the Service Desk Service fails to start and remains in the ''Starting'' state. 
--Article provided by [[User:Nero Le Velu|Nero Le Velu]].

== Hanging Service ==

You may likely encounter a situation where you started the Service Desk Service but it fails to start completely and remains in the ''Starting'' state. Often this is caused by an error in configuration file, or a timeout when trying to access a resource such as the database or a Secondary Server. When your system gets in this state the first thing to do is to stop the hanging service.

# Perform a [[pdm_halt]]
# Kill process from Windows Task Manager (especially the java one) and all bop_* pdm_*, sql_agent (orcl or db agent)
# Set the service to manual and reboot the server

== stdlog Files ==

Once the service has stopped, or the server has rebooted, analyze the most recent stdlog to find the culprit. Starting at the bottom of the stdlog look for ERROR, WARNING and FATAL entries.

*If there are errors referring to a Secondary Server, try recycling the Service Desk Proctor on that Server.

*If there are errors pertaining to a database connection, try pinging the database. If the database is there, try accessing the database using the same account Service Desk is configured to use.

*If there are errors regarding a custom .spl file, try removing the file.

If dealing with a Productions system, it is advised to contact CA Support if the culprit of the problem is not obvious to you within a reasonable amount of time. Be sure to forward them your most recent stdlog because they will most certainly ask for it.

== Windows Event Manager ==

If still struggling for answers, check out the Windows Event Manager which may contain some good information for problems that are not to blame on Service Desk.

== Automatic vs Manual ==

It is usually desired to have the Service Desk Service start automatically on a server reboot. While this sounds good in theory, it is often a bad idea. Often services that Service Desk depends on are not fully started when the Service Desk Service starts resulting in a hanging service. Additionally, the more complex your Service Desk installation, the likelihood that problems will be encountered each and every time the service starts automatically. A workaround in this case is to make it start later using a batch file or creating dependency from one service to another to ensure they start in the correct order.

@@ Line 1: / Line 1: @@
 __NOTOC__
 [[Category:r6]]
@@ Line 15: / Line 7: @@
 == Overview ==
-This article provides procedures to follow if the Service Desk Service fails to start and remains in the ''Starting'' state. &lt;br&gt;
+This article provides procedures to follow if the Service Desk Service fails to start and remains in the ''Starting'' state. <br>
 == Hanging Service ==

@@ Line 1: / Line 1: @@
 __NOTOC__
 [[Category:r6]]
@@ Line 7: / Line 15: @@
 == Overview ==
-This article provides procedures to follow if the Service Desk Service fails to start and remains in the ''Starting'' state. <br>
+This article provides procedures to follow if the Service Desk Service fails to start and remains in the ''Starting'' state. &lt;br&gt;
 == Hanging Service ==

@@ Line 1: / Line 1: @@
 __NOTOC__
-[[Category:Miscellaneous]]
+[[Category:r6]]
 {{Global Header}}
 {{Global Announcement}}

@@ Line 1: / Line 1: @@
 __NOTOC__
 [[Category:Miscellaneous]]
-<div align='center'><font color="green">To make corrections or additions to this article, select the ''edit'' tab above.<br>
+{{Global Header}}
-To discuss or ask questions about this article, select the ''discussion'' tab above.</font></div>
+{{Global Announcement}}
 == Overview ==

@@ Line 13: / Line 13: @@
 # Kill process from Windows Task Manager (especially the java one) and all bop_* pdm_*, sql_agent (orcl or db agent)
 # Set the service to manual and reboot the server
 == stdlog Files ==
@@ Line 25: / Line 24: @@
 If dealing with a Productions system, it is advised to contact CA Support if the culprit of the problem is not obvious to you within a reasonable amount of time. Be sure to forward them your most recent stdlog because they will most certainly ask for it.
 == Windows Event Manager ==
 If still struggling for answers, check out the Windows Event Manager which may contain some good information for problems that are not to blame on Service Desk.
 == Automatic vs Manual ==
 It is usually desired to have the Service Desk Service start automatically on a server reboot. While this sounds good in theory, it is often a bad idea. Often services that Service Desk depends on are not fully started when the Service Desk Service starts resulting in a hanging service. Additionally, the more complex your Service Desk installation, the likelihood that problems will be encountered each and every time the service starts automatically.  A workaround in this case is to make it start later using a batch file or creating dependency from one service to another to ensure they start in the correct order.