VCRM not showing on Server Links page

[Ali C]

Hi, I'm running HPSIM v4.2 SP1 on W2K Server SP4. I have installed the Version Control Repository Agent on the same machine with Proliant Support pack 7.3 A. The problem I have is that HPSIM doesn't seem to pick up the Version Control Repository Agent, when selecting Options | Version Control Repository, the following error is displayed:

Error, the Version Control Repository Manager (VCRM) was not found on any discovered systems. If the VCRM is installed, be sure it is running and that the system it is running on has been discovered by HP Systems Insight Manager. To verify the VCRM is identified, view the Links tab on the system's Device Page. If the system is discovered, but the VCRM does not appear on the systems' Links tab, run an Identify Systems task to that system.

I have done the things listed in the error with no joy, the VCRM is not listed on the links page and running Identify on the system hasn't helped.
If I go into the local System Homepage then all is fine. I have looked though the other posts and tried re-installing the agents and VCRM with no Joy. Any ideas really appreciated. Thanks, A

[Ananthak23]

Try restarting System Management Homepage service and then run identification task.

-Anantha

[Ali C]

Thanks Anatha, but no joy. (no Stdout and no Stderr data). All the other systems have the following links:

System Management Homepage
HP Server Agent Configuration History Reports (Survey Utility)
Version Control Agent
HP Insight Diagnostics
HP Network Configuration Utility
Insight Management Agents
HP NIC Agent
HP Storage Agent
Data Collection Report
System Protocol Settings
Edit System Properties
Suspend/Resume Monitoring

This one just has:

Data Collection Report
System Protocol Settings
Edit System Properties
Suspend/Resume Monitoring

So the Identify job doesn't appear to be picking up most of the links even though this server has the same Support pack installed as all the others (7.3 A). I'm logged in as the account used to install HPSIM so it's not permissions. How about editing the SQL tables? Any other ideas appreciated. Thanks, A