0

Reconfiguration succeeded without any errors or warnings.

1

Cannot load recfgsvr.dll. Verify that the DLL exists under the Arcserve Backup install directory.

2

Cannot locate required procedure address in recfgsvr.dll. Verify that the DLL is not corrupt.

3

Cannot launch this utility while the Arcserve Backup Manager is running. Close the Arcserve Backup Manager and launch the utility again.

4

Another instance is already running. Only one instance of the utility can be running at the same time.

11

The -username option is not specified. This option is a required field and must be provided.

12

Invalid parameters are found in the command line string.

15

The current Windows user does not have local administrator privileges.

16

The Windows user name or password is invalid.

17

The specified Windows user in the -username option does not have local administrator privileges.

18

The Windows user password cannot be empty. Set a secure password for the specified Windows user.

20

The Arcserve Backup Server cluster-aware installation is not supported.

21

The current server is not a stand-alone/ primary server. This utility must be run on a stand-alone/primary server.

22

Using SQL Server as the Arcserve Backup server database is not supported. Only using SQL Express as the Arcserve Backup Backup server database is supported.

30 ~ 45

An error occurs when calling functions exported by another DLL. Record the return code, collect the log file, and contact support.

61 ~ 64

Failed when manipulating the Arcserve Backup registry keys. Record the return code, collect the log file, and contact support.

69

Failed to launch ca_auth.exe. Check if ca_auth.exe exists under the Arcserve Backup install directory.

70

Adding equivalence for provided Windows user failed.

71 ~ 74

Setting the CAROOT password for the new domain failed. Record the return code, collect the log file, and contact support.

75 ~ 77

Failed to update data in the database. Record the return code, collect the log file, and contact support.

80

Failed to update the domain name, the primary server name, or both in the configuration file. Record the return code, collect the log file, and contact support.

85 ~ 86

Failed to manipulate the temporary files. Record the return code, collect the log file, and contact support.

87

The CAROOT password specified in the -carootpassword option is invalid.

200

Failed executing cstart.bat /cstop.bat. Verify that the files exist in the Arcserve Backup install directory.

-10

Jobs other than "ASDB Protection" and "DB Pruning" exist in the job queue. These jobs can become invalid after server reconfiguration.

-11 ~ -13

Errors occurred when verifying the SQL database. This error is not a critical problem, and you can still use the Arcserve Backup server as usual. For further information, record the return code, collect the log file, and contact support.

-14

At least one member is attached to the current Arcserve Backup domain. Configure this member server manually after server reconfiguration to add it to the current domain.

-15

No existing "ASDB Protection"/"DB Pruning" job is found in the job queue. You can create these jobs manually using the Server Admin.

-16 ~ -17

Failed to clear previous activity log messages. Check if ca_log.exe exists under the Arcserve Backup install directory. This error is not a critical problem, and you can still use the Arcserve Backup server as usual. For further information, record the return code, collect the log file, and contact support.

-46 ~ 57

An error occurs when calling functions exported by another DLL. For further information, record the return code, collect the log file, and contact support.

-63

The Arcserve Backup database SQL Agent is not detected. Verify that it is installed and configured properly. Without the Arcserve Backup database SQL Agent, you cannot protect the Arcserve Backup database.

-76 ~ -77

An error occurred when verifying the existence of the member server. This error is not a critical problem, and you can still use the Arcserve Backup server as usual. For further information, record the return code, collect the log file, and contact support.