Storage Resource Manager Enterprise Edition Installation Guide

Storage Resource Manager Enterprise Edition C–7
SRM Troubleshooting Guide
If the service is running, open Task Manager and sort on Image Name. Look for
SRProcmgr.exe. Below it should be SRMServer.exe. If SRMServer.exe is not there, or if
it is there briefly then disappears, and continues to do this, check the following
registry key using REGEDT32:
HKL-Software-HighGround-SRManager-<version>-Server-Options
Once you’ve highlighted this OPTIONS key, from the menu bar at the top of the
window, select Security then select Permissions. The SRM Server Service account
MUST be listed here as having FULL CONTROL over this key. If not, the
SRMServer.exe process will not start.
Reports do not show recently updated data
This could be because of a few reasons. Perform the following steps:
Cache Contains Old Data
To make sure that you're not getting old data from the browser's cache, click the
Refresh or Reload button.
One or More Jobs Has Hung
1. Go to the following URL:
<SRMServerName>/storageresourcemanager/scans/srmsched.asp
This is the schedule page that will show what jobs are running and the schedules for
the other jobs.
NOTE: If a group is set to Scan On Demand Only, it will not show in this page.
2. Check the Start times to see if there are jobs that have been running for a long
time: days or even weeks. If so, chances are that those jobs are hung.
Check the agents that are contained within these groups to see if their SRMAgent
processes are getting any CPU time, meaning that they are active. If a job is not active,
you can stop the SRM Service on both the Server and the appropriate Agents to kill
that job. The SRM Server will automatically restart this job when the SRM Service is
restarted.
If a job continues to hang, you may need to run a trace. See “SRM Traces, Logs, and
Dumps” on p.C-14.