Error Message

The following errors might be evident in the server logs:

Application log:

06/14/2014         01:12:02 AM       INFORMATION   1001(0x000003e9)          Windows Error Reporting               server.name.fqdn         

Fault bucket , type 0

Event Name: APPCRASH

Response: Not available

Cab Id: 0

Problem signature:

P1: xprtld.exe

P2: 5.0.196.0

====

System log:

06/14/2014         01:22:42 AM       ERROR      7034(0xc0001b7a)        Service Control Manager               server.name.fqdn

The Veritas Storage Foundation Messaging Service service terminated unexpectedly.  It has done this 1 time(s).

=====

sfmh debug.log

2014-04-23 07:49:23 [NOTICE] tags , maxsize 5242880, count 0

2014-04-23 07:49:24 [NOTICE] xprtld 5.0.196.0 started on port(s) 5634, serving C:\Program Files\Veritas\VRTSsfmh\web

2014-04-23 07:57:44 [NOTICE] tags , maxsize 5242880, count 0

2014-04-23 07:57:44 [NOTICE] xprtld 5.0.196.0 started on port(s) 5634, serving C:\Program Files\Veritas\VRTSsfmh\web

2014-04-23 08:07:45 [NOTICE] tags , maxsize 5242880, count 0

2014-04-23 08:07:46 [NOTICE] xprtld 5.0.196.0 started on port(s) 5634, serving C:\Program Files\Veritas\VRTSsfmh\web

=================

sfmh error.log:

ERROR: 0:AT profile set failed

ERROR: Could not set AT profile (err=14)

Missing configuration parameters under HKEY_LOCAL_MACHINE\SOFTWARE\Symantec\SFMH 

This behavior can be experienced on rare ocassions, after performing multiple manipulations with Storage Foundation or Netbackup products, such as installing, uninstalling and then running a repair on either of the software installation

Some registry key parameters might get corrupted or disappear from the server's registry as a result, thus causing the Veritas Storage Foundation Messaging Service to malfunction

1) Veritas Operation Manager (Host Component) can be reinstalled, by uninstalling the product from "Programs and Features" and then installing it back from either the cached VRTSsfmh.msi package (stored in C:\Program Files\Veritas\Veritas Shared\VPI\{F834E070-8D71-4c4b-B688-06964B88F3E8}\pkgs\common\x64) or the product installation media (stored in \Pkgs\Common\x64)

2) Alternatively a comparison of registry keys can be done between a working node with the service and the problematic one to determine the cause.

Most importantly, the following registry key and all of its subkeys need to be checked: HKEY_LOCAL_MACHINE\SOFTWARE\Symantec\SFMH

If on the problematic server, the key and subkeys there are found not to have any parameteres listed, the whole HKEY_LOCAL_MACHINE\SOFTWARE\Symantec\SFMH registry key can be exported from the working node and then imported on the problematic one and it should resolve the issue.

Every customer's environment is different however, so the solution provided might not work, in which case please feel free to contact Veritas Technical support for further assistance

Applies To

SFW HA - 6.0.1

Veritas Operation Manager (Host Component) - 5.0.0196

Windows Server 2008 R2