Rost
17 years agoLevel 2
Error with Veritas Action Agent on w2008 x64
Windows 2008 STD x64 (fresh installed) + SFW 5.1 (fresh installed)
Veritas Enterprise Administrator (VEA) starts, but can not connect to server (Connection to server is broken)
look service launched: Veritas Action Agent service is not running. Try to run as described in the article (Document ID: 297398 "How to restart StorageAgent if it is not running" )
see the error in the event viewer:
- ERROR ID: 7031 Veritas Storage Agent service terminated unexpectedly. This occurred 1 time (s). The following corrective action will be taken through 60000 milliseconds: Restart the service.
- Application popup ID:26 (At the same time as the previous error)
Program: ...iles (x86)\Veritas\VRTSobc\pal33\bin\vxpal.exe
A buffer overrun has been detected which has corrupted the program's
internal state. The program cannot safely continue execution and must
now be terminated.
I tried to reinstall SFW. Was exactly the same result.
I tried it on a virtual machine to simulate this issue. was exactly the same result on w2008 x64 configuration. but the configuration w2003r2 x64 works perfectly.
any idea?
Veritas Enterprise Administrator (VEA) starts, but can not connect to server (Connection to server is broken)
look service launched: Veritas Action Agent service is not running. Try to run as described in the article (Document ID: 297398 "How to restart StorageAgent if it is not running" )
see the error in the event viewer:
- ERROR ID: 7031 Veritas Storage Agent service terminated unexpectedly. This occurred 1 time (s). The following corrective action will be taken through 60000 milliseconds: Restart the service.
- Application popup ID:26 (At the same time as the previous error)
Program: ...iles (x86)\Veritas\VRTSobc\pal33\bin\vxpal.exe
A buffer overrun has been detected which has corrupted the program's
internal state. The program cannot safely continue execution and must
now be terminated.
I tried to reinstall SFW. Was exactly the same result.
I tried it on a virtual machine to simulate this issue. was exactly the same result on w2008 x64 configuration. but the configuration w2003r2 x64 works perfectly.
any idea?