We upgraded our Test single Node cluster to the version 6 with cp2.
After the installation and reboot all of the mountv resource are in a failed state.
in the mountv_a.txt logfile i found this line: monitor:Blockmountpointaccess not configur...
Ive made a custom ressource with a script. This Script trigger another script which needs Runas Admin rights.
The Cluster cannot not start the second script as admin how can i manage this? I dont want to deactivate the UAC on the Server.
Today i upgraded our Test-environment from 5.1 SP1 to SP2. All went smothly through the installation process, but after the reboot, the eventlog is full of this messages and i cannot start the mountV resources:
I cannot open the VEA Console, the error "Error V-39-53247-7 error while connecting to localhost" appears.
The suggested Website is empty http://entsupport.symantec.com/umi/V-39-53247-7
Then i found this site:
After the upgrade from 5.1 to 5.1 SP1 on a Windows2008 Server i have this error efverytime i login to the server...
Problem Event Name: APPCRASH
Application Name: SFWConfigPanel.exe
Application Version: 5.1.10000.214
the problem with the mounting appears right after the update with the cumulative hotfix update 2 (cp2) on v6.0
Everything is working fine after the upgrade from 5.1 sp2 to v6.0
2012/09/06 14:53:10 VCS DBG_21 V-16-50-0 MountV:LOGS:monitor:*** Start ...
Well, i made this test with the types.cf from a other server which was freshly installed with Sp2.
i replaced the old types.cf with the new one and everything works fine now.
I guess this is not the supported way to solve this error?