VCA and Legacy VCA

[Kelly Beauchaine]

Hello,
I have one particular server that is using it's legacy version control agent instead of the current control agent. I have updated this server to the latest version of the Compaq Management Agents, but still shows v6.40, with v7.0 as the latest version available. The snmp settings are all correct but still getting the yellow indicator on the main CIM7 screen. The cpqsetup log on the problem server indicates Management Agents 7 are installed, those that were needed anyway. So how come CIM7 isn't recognizing that?
Hope I've given all needed info for an answer!
Thanks,
Kelly

[Rob Buxton]

The Software Version Status Polling task updates the main IM screen. It's not dynamic.
You can manually run it and it should update the SW Column.

[Kelly Beauchaine]

Well, I have been running that manually, but I just found this interesting tidbit. There was an error in the VC agent log that said the VCA service was not set to interact with the desktop. So, after checking the settings for the service, I see that it was set to log on with the 'admin' account. I switched that to use the local system account and now the service won't stay started! Below is the error that shows up in the Event Viewer. I have seen this b/4 but cannot remember what I did to fix it!

'The Version Control Agent service terminated unexpectedly. It has done this 5 time(s). The following corrective action will be taken in 0 milliseconds: No action. '

All I can say now is, hmmmmm . . . .

Kelly

[Rob Buxton]

Hmmmmnnn indeed, sorry I've not seen that.

FWIW the VCAgent here is set to Logon as System Account and the Interact with the desktop is checked. They seem to be the defaults.

[Rob Buxton]

Just to add whene there's been problems here I've sometimes restarted SNMP and all the dependent services.

[Kelly Beauchaine]

Well, I stopped and restarted snmp and all the agents. The version control agent service still only runs for about 10 seconds and then stops (though it's not indicating it's stopped in the services window).
I've uninstalled the agent and am going to reinstall after a reboot which I cannot do until I inform the customers as this is a production server.
I'll let you know how it turns out!
Thanks,
Kelly

[Kelly Beauchaine]

Well, I've gone from bad to worse! I reinstalled the vc agent service and now it won't even start up! I get the following error:

'Could not start vca service on local computer. Error: 1067 Process terminated unexpectantly.'

Here's the error that shows up in the application event log:

'The Version Control Agent Win32 service could not be started successfully. The service process could not connect to the service controller.' This has a source of 'cpqvcagent' and an event id of 604.

Here is the error that still shows up in the system event log:

"The Version Control Agent service terminated unexpectedly. It has done this 5 time(s). The following corrective action will be taken in 0 milliseconds: No action.' This has a source of 'Service Control Manager' and an event id of 7031.

I reinstalled with the default (local account and interact with desktop). It even asked me for the name of the repository manager server. Thought that was good sign! Oh well, stuff happens. I'm open to more ideas, suggestions, etc!
Kelly

[Rob Buxton]

After the initial upgrade, did you do a reboot? I don't think the VC Agent will work correctly without a reboot. Behaves a bit like you're seeing.

[Kelly Beauchaine]

Well Rob, no I did not. I was hoping when it didn't tell me I needed to reboot that it actually meant I could get away without rebooting! Silly me huh? I'll reboot as soon as I can and get back to you.
Thanks for all your help today. I'll be in touch!
Kelly

[Kelly Beauchaine]

Rebooting the server did not work. Version Control Agent service still fails after about 10 seconds.
I, again, reinstalled the agents and rebooted. And now, like before, if I have the service set to use the 'admin' Log On, it will remain running, but if I change it to the local account, it fails.
Software version is showing green now in Insight Manager, but the server is still using Legacy Version Control!!!! I don't get it, but I'm going to move on.
Thanks for all the suggestions and ideas!
Kelly

[Rob Buxton]

Seems as though there's a gremlin remaining behind.
You might need to remove all of the Agents rather than just reinstalling them. And then Install them from the VCRM. A pain but they do seem a bit damaged.
I would also recommend rebooting between these two actions. Certainly I've seen the VC Agent require a reboot. I've also never seen a full softpaq update not require a reboot.