Install, Upgrade and Uninstall CA ARCserve RHA › Uninstall CA ARCserve RHA

Uninstall CA ARCserve RHA

Uninstalling CA ARCserve RHA components is performed by a simple and standard activity through the Operating System's Add/Remove Programs in the Control Panel list. You need to uninstall each CA ARCserve RHA component separately.

• The un-install does not remove the default directory storing the user generated .xmc scenario files that have been set up by the CA ARCserve RHA Manager. The directory is: INSTALLDIR\ ws_scenarios.
• There are two additional methods to uninstall the CA ARCserve RHA Engine. These methods are best suited for uninstalling previous Engine versions:
  • Using the Remote Installer
  • Using the Setup.exe file

Uninstall CA ARCserve RHA for Microsoft Failover Cluster

Uninstalling CA ARCserve RHA does not delete the CA ARCserve RHA disk resource and resource type that stores your configuration.

To uninstall completely

1. Delete the CA ARCserve RHA disk resource from storage
2. Use the cluster command to delete the resource type while the cluster is running.

   cluster.exe restype "ARCserve Disk" /delete
   

You may also delete the resource type from the Microsoft Failover Cluster Manager.

Troubleshooting CAVSSSoftProv Error

Symptom:

I get the following error while installing or uninstalling the RHA engine:

Error 27508. Error installing COM+ application CAVSSSoftProv

Solution:

Do the following:

1. Restart the operating system.
2. Stop the CA ARCserve RHA Engine service.
3. Run install_engine.bat from the engine root path.
4. Run uninstall_engine.bat from the engine root path.
5. Remove the engine from add/remove programs.
6. Remove COM+ application CAVSSSoftProv application.
7. Reinstall CA ARCServe RHA Engine.

Troubleshooting RHA Engine Verification Issue

Symptom:

In windows 2008 workgroup server, when the server login user is a local account in the Administrator group, I get the Verification Failed error. I get this error while verifying the RHA engine.

Solution:

To resolve this issue, disable UAC or set the registry entry, LocalAccountTokenFilterPolicy, to 1.

For more information, see article 951016 on microsoft.com.