Storage Resource Manager Enterprise Edition Installation Guide

C–8 Storage Resource Manager Enterprise Edition
SRM Troubleshooting Guide
Cruft Data
Data that no longer exists and is showing in grayed out boxes in the UI, does not get
removed automatically as it should.
There is a setting under Options-Report Sizes where you can specify how long “old”
resources should be kept. There is a Maintenance job that continuously runs within the
SRM Server that monitors this and removes data from the database.
If this time has passed and the data is still in the database, check the
SRMSCHED.ASP page, as noted above, and look at the Maintenance job. If the
Maintenance job is running, check the Last Start and Last End Time to see if it has
completed recently. If the job hasn’t completed, there may be other jobs that are hung,
causing this Maintenance job to wait. The Maintenance job will not run while other
jobs, such as scans, are running.
Scanning an Agent Fails With Error Code 6e4, 6ba, or 6d9
Verify that the SRM Server Service account is granted Full Control over the following
registry key on the remote Agent machine (use REGEDT32):
HKL-Software-HighGround-SRManager-<version>-Agent-Security
During the Agent installation, the SRM Server Service account is granted Full Control
over this key. If the SRM Server Service account is changed, this key needs to be
changed to reflect the new account on ALL Agents.
Generic Scan Failure
Verify that the SRM Server machine can resolve the Agent machine name, and
vice-versa.
Security
Most problems with SRM are related to security. Below are the security requirements
to allow SRM to run smoothly.
SRM Service Account
The SRM Service Account MUST be a member of the Local Administrators NT
security group on the SRM Server machine. If not, the local agent (if installed) will
not be able to access all the information it needs for its scans. If this happens, you will
not be able to submit remote install jobs, as well as other problems that may arise.