01-22-2009 08:43 AM
Just rebooted one of my VBR Agent machines (Windows 2003 Server) for black Monday's Windows Updates.
Now the VBR Agent Service fails to start successfully.
Event Viewer lists a failure code of 4096 and a message:
"The Java Virtual Machine has exited with a code of 1, the service is being stopped."
Reapplied VBR 6.5.1 patch; no change.
Any ideas?
Solved! Go to Solution.
01-22-2009 10:41 AM
David,
You should definitely apply VBR 6.5.1.1. The Error and skipped file collection is now done at the same time as the Job data. This caused the VBR agent in some cases to run out of memory (Java Heap). There is an explicit fix in VBR 6.5.1.1 for this issue. If you still see the issue (check the VBR agent logs), you can up the Java Heap size for the VBR agent in the Windows registry, HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\VBRAgent\Parameters\JVM Option Number 2. It is set to 256 MB. You can raise it but do not exceed physical memory. 512 should be plenty even at our largest customers.
Tony
01-22-2009 10:41 AM
David,
You should definitely apply VBR 6.5.1.1. The Error and skipped file collection is now done at the same time as the Job data. This caused the VBR agent in some cases to run out of memory (Java Heap). There is an explicit fix in VBR 6.5.1.1 for this issue. If you still see the issue (check the VBR agent logs), you can up the Java Heap size for the VBR agent in the Windows registry, HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\VBRAgent\Parameters\JVM Option Number 2. It is set to 256 MB. You can raise it but do not exceed physical memory. 512 should be plenty even at our largest customers.
Tony
01-22-2009 11:08 AM
Thanks Tony,
Looks like I put 6.5.1.1 on the Master but neglected the Agents.
Service is running happily again!
DP