KB labels


Ticket Product Version

Ticket Category

Ticket Assignee


Hot Fixes

Published Fixes
Your Arcserve Support User Profile
First Name:
Last Name:
email:
Phone:
Company:*
Customer Type:
Language:

Country:
Region:

Time zone:
Follow

arcserve-KB : D2D deployment via Central Protection Manager fails - Initialization failed - Setup cannot start CheckProdInfo.exe

Last Update: 2016-04-25 14:33:46 UTC

Description:

The environment is Central Protection Manager - CPM 16 Update 8 on Windows 2008 R2.

Deployment of D2D to remote nodes fails as follows:

Error Message:

The following logs need to be collected in order to be analysed in such a case where a D2D deployment via CPM is failing:

The folder “C:\Windows\Temp\ARCserve\Setup\ARCserve Central Applications\” on the CPM machine, there will be files names GCDeploy_.log
The folder “C:\Program Files\CA\ARCserve Central Applications\Deployment\DeployStatus\” on the CPM machine.
The file “C:\Program Files\CA\ARCserve Central Applications\Deployment\DeployRetCode.ini” on the CPM machine.
The file “C:\Program Files\CA\ARCserve Central Applications\Deployment\ServerList.ini” on the CPM machine.
The log on the remote machine where D2D is to be deployed: “C:\Windows\Temp\CA_XXX\”. XXX is a random string. Please copy all the folders begin with “CA_”.

In the above case, the deployment was failing in the initial stage iteself. 

Extract from the log given below:

GCDeploy_20130812072555

2013-08-12 07:25:56    Launching process CheckProdInfo.exe...
2013-08-12 07:25:56    'D:\Program Files\CA\ARCserve Central Applications\deployment\CheckProdInfo.exe' 'D:\Program Files\CA\ARCserve Central Applications\deployment\ServerList.ini'
2013-08-12 07:25:56    Fail to launch process, Lasterror = 1314
2013-08-12 07:25:56    Fatal Error: Fail to run CheckProdInfo.exe

MS Error 1314 = A required privilege is not held by the client

Solution:

From the services manager on the CPM node, 'CA ARCserve Central Applications Service' is started with the account used to manage CPM.

This is changed so that the service is started with the 'Local System Account'

More Information:

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

Comments