Document ID: 269426
http://support.veritas.com/docs/269426 E-Mail Colleague IconE-Mail this document to a colleague

While doing a remote Intelligent Disaster Recovery (IDR), the message: "There was an error installing RAWS. Please examine Bedrwiz.log for details" appears on the remote machine that is being recovered.
Exact Error Message
There was an error installing RAWS. Please examine Bedrwiz.log for details

Details:
When performing a remote Intelligent Disaster Recovery (IDR), the message "There was an error installing RAWS. Please examine Bedrwiz.log for details" appears on the remote machine that is being recovered. This error message appears after providing the details of the backup server and clicking Next (Figure 1).

Figure 1
 

This error occurs because the remote agent could not be installed correctly. Follow the steps given below to resolve this issue :

Note:  If the first step does not resolve the issue then proceed to the next step.

Step 1.  Install the remote agent locally on the remote server that is being recovered:

1.  On the server being recovered, go to the command prompt and check for the presence of the folder rant32

%SYSTEM ROOT%\system32\BKUPEXEC\rant32

2.  Check if the following two files are present in the rant32 folder: setup.exe and instmsiw20.exe

3.  Try installing the remote agent by running the following command:

setup.exe /RANT32 : -s

Step 2.  Verify if the services are running and silent installation of the Remote agent:

Note: The following commands are to be run on the remote server which is being recovered remotely.

1.  Share the Rant32 folder on the media server

2.  While performing the Intelligent Disaster Recovery (IDR),  press <F1> to go to the command prompt. After sharing the Rant32 folder from the media server (backup server) (Path= <Drive name>\Program Files\Backup Exec\NT\Agents\Rant32) map it to a drive through the command prompt on the remote server, e.g. type in the following command to map a "folder" which is on the server ServerName to the drive X with the username= "user_name" in the domain "Domain_name."

net use X: \\ServerName\folder /user: user_name\Domain_name

Syntax:

net use <drive name>: \\Remote_server_name\<path of the shared folder> /user: <Domain_name\user_name>

3.  Copy the Rant32 folder to the system root drive (it is recommended to copy it to the system partition, do not run setupaa  from the mapped drive, e.g. C: )

E.g. Run the following command:

copy <path of the source or file to be copied>  <path of the location of the destination>

In the command prompt, change to the folder <system drive>\rant32,  then run  setupaa.

Step 3.  Verify if the remote agent has been installed:

To verify if the remote agent has been installed properly, check if the service is started on the remote server that is being recovered.
To check the service through the command prompt, type the command as shown below in Figure 2.

net start

Figure 2
 

If the name Backup Exec Remote Agent for Windows Servers is not listed, then the remote agent service is not started or not installed properly.

Step 4.  Starting the remote agent service manually:

To start the remote agent service manually, run the following command (Figure 3) in the command prompt:

net start backupexecagentaccelerator

Note: backupexecagentaccelerator = Backup Exec Remote Agent for Windows Servers

Figure 3
 

If the remote agent is not installed or there is an error starting the remote agent, the following tips might be useful:

A.  The following is observed in the bedrwiz.log file:

==========================================================================

Error 1231 returned from WNetAddConnection2. ExitCode not 0 for C:\WINNT\System32\BKUPEXEC\RANT32\setup.exe /RANT32: -s not, ExitCode = 1603.

==========================================================================


B.  The following is observed in the bkupinst.log file:

==========================================================================
07-10-2004,10:56:41 : === logging ended: 10.07.2004 10:56:41 ===
07-10-2004,10:56:41 :
07-10-2004,10:56:41 : Windows Installer return code: 1603
07-10-2004,10:56:41 : A fatal error occurred during installation on server 'SF-T2K-01'.
==========================================================================
OR
==========================================================================
ERROR: Service "BackupExecAgentAccelerator" (BackupExecAgentAccelerator) could not be started. Check if you have sufficient rights to start the system service
07-10-2004,10:56:41 : Action ended on 10:56:41: InstallFinalize. return value 3.
==========================================================================

Step 5.  Verify the registry sub key Image path on the remote server:
Check the registry sub key Image path on the remote server under the following key:
Note: The registry can be opened on the remote server by running the following on the remote server itself:
1.  Click Start | Run
2.  In the Run window, next to Open: type regedit32 to open the registry editor
3.  Find the following key:
HKEY_LOCAL_MACHINE\SYSTEM\Currentcontrolset\services\backupexecagentaccelerator

Warning: Incorrect use of the Windows Registry Editor may prevent the operating system from functioning properly. Great care should be taken when making changes to a Windows registry. Registry modifications should only be carried out by persons experienced in the use of the registry editor application. It is recommended that a complete backup of the registry and workstation be made prior to making any registry changes.

4.  Under the above key, the sub key Image path should have a value of the correct path of the file beremote. So the value of image path should be <System partition>:\ Program files\Veritas\Backup Exec\RANT.

Step 6.  Replacing the missing DLL file:
While starting the remote agent service, if an error message is displayed saying that there is a DLL file missing, then copy that DLL from your media server to the remote server that is being restored to the correct path. If needed, register the copied DLL  in the remote server using the following command through the command prompt:
regsvr32 <path of the dll to be registered>\file.dll


Products Applied:
 Backup Exec for Windows Servers 10.0, 10.0 5484, 10.0 5484 SP1, 10.0 5484 SP2, 10.0 5520, 10d (10.1), 10d (10.1) 5629, 9.1, 9.1 4691, 9.1 4691 SP1, 9.1 4691 SP2
Last Updated: October 17 2005 10:40 AM GMT
Expires on: 365 days from publish date
Subscribe Via E-Mail IconSubscribe to receive critical updates about this document

Subjects:
 Backup Exec for Windows Servers
   Application: Intelligent Disaster Recovery
   Equipment: Idr

Languages:
 English (US)

Operating Systems:
Windows 2000

Advanced Server, Advanced Server SP1, Advanced Server SP2, Advanced Server SP3, Advanced Server SP4, Server, Server SP1, Server SP2, Server SP3, Server SP4

Windows Server 2003

Enterprise Server, Enterprise ServerSP1, Standard Server, Standard Server SP1