Server Management (Insight Manager 7)
1844423 Members
2491 Online
110233 Solutions
New Discussion

IM7-SP2 Version Control Agent Error Message

 
Stephen_79
Occasional Contributor

IM7-SP2 Version Control Agent Error Message

When ateempting to lauch the VCA on a server, IM7 Server reports "Insufficient Storage for Version Control Agent" followed by "The Version Control Agent encountered an error while obtaining the software and firmware inventory" and "Not enough storage is available to process this command. An error occurred while performing an operating system specific operation. VCA1071461015.

Anyone seen this before or have any ideas?
5 REPLIES 5
Bill Lane
Frequent Advisor

Re: IM7-SP2 Version Control Agent Error Message

Sounds to me like your C: drive (assuming your on Windows) is running out of space. [sorry for stating what may be the bl*ding obviouse]
I think it all uses your default temp dirictory so you could try changing that to a drive with more space.
Nicole_16
Advisor

Re: IM7-SP2 Version Control Agent Error Message

Yes, I'm getting it on 3 servers I just installed. I have plenty of disk space on all drives.

Did you ever discover a solution?

Re: IM7-SP2 Version Control Agent Error Message

Re: VCA encountered an error...I believe I got this error if one of the sysservices settings under the snmp service (under the agent tab) wasn't checked (not sure - we generally have them all checked) - Physical - Applications - Datalink / Subnetwork - Internet - End-toEnd

Re: Not enough storage...
I've gotten that error or very similar before while trying to view a remote server (for example dir \\server\c$).

I believe it may have something to do with 1 or two reg settings that control memory. One is the IRPstackSize and the other is pagedpoolsize (check out JSI or search google).
Ed Cox
Respected Contributor

Re: IM7-SP2 Version Control Agent Error Message

Upgrade from VCA 1.0 to 2.0...the problem goes away.
Ed Cox
David Claypool
Honored Contributor

Re: IM7-SP2 Version Control Agent Error Message

This also can be an erroneous error caused by READ-ONLY as the setting for the SNMP service and/or not having SNMP sets enabled...