GenericService Resource offline fails if Service Control Manager fails to stop the GenericService

Article:TECH173239  |  Created: 2011-10-31  |  Updated: 2011-11-06  |  Article URL http://www.symantec.com/docs/TECH173239
Article Type
Technical Solution

Product(s)

Issue



Regardless of executing clean Entry point(EP) the GenericService failed to offline with error in the snips below.

 


Error



[SNIP from engine_A.txt]
2010/11/21 19:56:08 VCS NOTICE V-16-1-10300 Initiating Offline of Resource <GenericService Resource Name> (Owner: unknown, Group: <Service Group Name>) on System <Node Name>
2010/11/21 19:57:23 VCS ERROR V-16-2-13064 (<Node Name>) Agent is calling clean for resource(<GenericService Resource Name>) because the resource is up even after offline completed.
2010/11/21 19:57:23 VCS ERROR V-16-2-13069 (<Node Name>) Resource(<GenericService Resource Name>) - clean failed.
2010/11/21 19:58:23 VCS ERROR V-16-2-13077 (<Node Name>) Agent is unable to offline resource(<GenericService Resource Name>). Administrative intervention may be required.

 
[SNIP from GenericService_A.txt]
2010/11/21 19:57:22 VCS WARNING V-16-10051-6025 GenericService: <GenericService Resource Name>:offline:The service '<Service Name>' did not stop within the specified timeout. Error = 258.
2010/11/21 19:57:23 VCS ERROR V-16-2-13064 Thread(2832) Agent is calling clean for resource(<GenericService Resource Name>) because the resource is up even after offline completed.
2010/11/21 19:57:23 VCS WARNING V-16-10051-6023 GenericService: <GenericService Resource Name>:clean:The service '<Service Name>' is not in running state. Attempt to stop it might be unsuccessful.
2010/11/21 19:57:23 VCS ERROR V-16-10051-6024 GenericService: <GenericService Resource Name>:clean:The service '<Service Name>' did not stop. Error = 1061.
2010/11/21 19:57:23 VCS ERROR V-16-2-13069 Thread(2832) Resource(<GenericService Resource Name>) - clean failed.
2010/11/21 19:58:23 VCS ERROR V-16-2-13077 Thread(2832) Agent is unable to offline resource(<GenericService Resource Name>). Administrative intervention may be required.
 

Cause



The GenericService Resource conforms service status accessing Service Control Manager(SCM) using API provided by Operating System.

If, for some reason, SCM fails to offline the service (i.e. holding "Stopping" state), the GenericService also fails to offline, because by design VCS, does not gracefully terminate the process from the clean Entry point(EP). The root-cause of problem must be analyzed from OS perspective.
 


Solution



If you wish to terminate the process of the service forcefully using clean EP, create a respective <resource name> registry subkey "KillInClean" and set DataType as DWORD with value of 1 under "BundledAgents" subkeys. Please note, by default, VCS does not create subkeys "BundledAgents" and subsequent keys.

Warning:
Incorrect use of the Windows registry editor may prevent the operating system from functioning properly. Great care should be taken when making changes to a Windows registry. Registry modifications should only be carried-out by persons experienced in the use of the registry editor application. It is recommended that a complete backup of the registry and workstation be made prior to making any registry changes.

HKLM\SOFTWARE\VERITAS\VCS\BundledAgents\GenericService\<resource name>  
 

 




Article URL http://www.symantec.com/docs/TECH173239


Terms of use for this information are found in Legal Notices