Topics | How To | Troubleshoot | Related Topics
All Data Collection jobs fail for a new SRM Client
All Data Collection jobs fail for an existing SRM Client
Exchange Data Collection job fails
Not all Exchange Mailboxes are reported
Not all Exchange Objects are reported
NAS Volume or Share Details not Collected
Not all File Systems are reported
Oracle Data Collection job fails or stops responding
Solaris Data Collection for NFS data hangs
SRM Data Collection restart fails on Windows 2000 Server
If you have just successfully installed a SRM Client, but all data collection jobs fail for that client, check for DNS resolution issues if you entered a short name for the SRM Server during the SRM Client installation.
If all Data Collection jobs start failing for an existing SRM Client, check the following:
If the client has become permanently unavailable (e.g., due to hardware failure), you need to release the client's license(s), thereby letting the SRM Server know that the client no longer exists, since it was not properly uninstalled. For directions, see Uninstalling Components.
If an Exchange Agent Data Collection job fails unexpectedly, check the following:
To correct this problem on the Exchange Server, perform the following procedure:
- On the Exchange Server, open Active Directory Users and Computers
- Right-click the user whose Mailbox attributes you want to remove
- Select Exchange Tasks
- Remove Exchange Attributes
If some of the objects on the Exchange Server, such as Stores, Storage Groups, Mailboxes, etc., are not being reported, verify that Active Directory replication has been completed after all new Storage Groups were created.
When you create new objects on the Exchange Server, the SRM Exchange Agent will not collect information about them until Active Directory replication has been completed on the Exchange Server.
The same will hold true for deleted objects -- their reported status will not be updated by the SRM Exchange Agent until Active Directory replication has been completed on the Exchange Server, at which time the SRM Exchange Agent will mark them as deleted.
If NAS data collection fails, check the following:
If a NAS volume is not shared at root level and there are no shares for this volume without quota restriction, the Volume Details cannot be collected, and the associated reports will show values of "0". You must either share the volume at the root level, or have at least one share on the volume for which there is no quote restriction.
If some file systems on a computer are being reported, but not all, verify on that particular computer that all logical partitions are mounted. File Systems residing on logical partitions that are not mounted are not reported by a SRM File System Agent.
If an Oracle data collection job fails or stops responding, check the following:
Solaris data collection for NFS data hangs whenever the NFS server is down or not accessible. To prevent this problem, do the following:
If SQL Server data collection fails, check the following:
If the SQL Instance spelling is incorrect, the instance must be removed then added with the proper spelling. |
For more information on adding a SQL Server Instance, see Add/Edit a SQL Server Instance.
These verifications apply for both types of data collections.
An SRM Data Collection job fails to restart after going in suspended mode due to failed to connect WMI on Windows 2000 Server. Make sure WMI services are up and running. You will also need a patch from Microsoft to fix the issue, for more information, please refer to http://support.microsoft.com/kb/884578/en-us.