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 : Deploying policy might fail with error "Unable to apply arcserve Central Host-Based VM Backup settings to proxy "[CA HBVM proxy servername]". (Error occurred during process request. Please try again.)"

Last Update: 2016-11-23 17:24:10 UTC

Description:

Deploying policy might fail with error 'Unable to apply CA ARCserve Central Host-Based VM Backup settings to proxy '[CA HBVM proxy servername]'. (Error occurred during process request. Please try again.)'

Environment:
- CA ARCserve Central Host-Based VM Backup r16.5 GA build 843 + CA D2D 16.5 build 1444 on Windows Server 2008 R2 SE SP1 (update from r16.0 U7)
- ESX VSPHERE 5.0

Solution:

- Uninstall CA ARCserve Central Host-Based VM Backup 16.5 GA from CA Central Host-Based VM Backup proxy.

- Uninstall CA D2D 16.5 GA and reboot

- After reboot remove following from Microsoft Registry and from installation path:

IMPORTANT: This article contains information about modifying the registry.
Before you modifying the registry, make sure to create a back up of the registry and ensure that you understand how to restore the registry if a problem may occur.
For more information about how to back up, restore and edit the registry, please review the relvant Microsoft Knowledge Base articles on support.microsoft.com

1- \Porgram Files\CA\ARCserve Central Applications\

2- \Porgram Files\CA\ARCserve D2D

3- HKEY_LOCAL_MACHINE\SOFTWARE\CA\ARCserve Central Applications

4- HKEY_LOCAL_MACHINE\SOFTWARE\CA\ARCserve D2D

5- Install CA ARCserve Central Host-Based VM Backup and CA ARCserve D2D r16.5 on Proxy.

6- Now create and deploy policies.

More Information:

1- Following was verified prior to implementing above solution.
    - Login to CA HBVM Backup Proxy server works OK
    - User is domain user with sufficient privileges
    - Ports 8014, 8015 and 443 are not being blocked by any firewall
    - Ping is successful from VCenter to HBVM Backup server proxy and vice versa
    - connectivity to Database works OK
    - Remove old policies assignment, created a new policy and assigned it. Note the result like 'deploy policy failed with error...'.
    - Verify that the port being used to communicate between VCenter Server and the ESX server is open and usable (port 902 is default).

2- Symptoms monitored.

    - In ARCAPP.log it was seen that upon deploying policy connection was established to a different server than backup proxy.
 
- Sample of ARCAPP log:
2013-01-04 10:40:15,734 PolicyDeployment.TaskAssignerThread [INFO]    Task assigner thread wake up, has tasks to do.
2013-01-04 10:40:15,741 PolicyDeployment.TaskAssignerThread [INFO]    Begin assigning policy deployment tasks.
2013-01-04 10:40:15,749 PolicyDeployment.TaskAssignerThread [INFO]    Complete assigning policy deployment tasks, wait for tasks completed.
2013-01-04 10:40:36,804 pool-2-thread-1 [ERROR]                    connectD2D() failed.
javax.xml.ws.WebServiceException: Failed to access the WSDL at: http://[server-name.subdomain:8014/WebServiceImpl/services/FlashServiceImpl?wsdl. It failed with:
Connection timed out: connect.
at com.sun.xml.ws.wsdl.parser.RuntimeWSDLParser.tryWithMex(RuntimeWSDLParser.java:162)
at com.sun.xml.ws.wsdl.parser.RuntimeWSDLParser.parse(RuntimeWSDLParser.java:144)
at com.sun.xml.ws.client.WSServiceDelegate.parseWSDL(WSServiceDelegate.java:265)
at com.sun.xml.ws.client.WSServiceDelegate.(WSServiceDelegate.java:228)
at com.sun.xml.ws.client.WSServiceDelegate.(WSServiceDelegate.java:176)
at com.sun.xml.ws.spi.ProviderImpl.createServiceDelegate(ProviderImpl.java:104)
at javax.xml.ws.Service.(Service.java:56)
at javax.xml.ws.Service.create(Service.java:680)
at com.ca.arcflash.webservice.WebServiceFactory.getFlassService(WebServiceFactory.java:52)
at com.ca.arcserve.edge.app.base.util.CommonUtil.getD2DForEdgeService(CommonUtil.java:671)
at com.ca.arcserve.edge.app.base.util.CommonUtil.getD2DForEdgeService(CommonUtil.java:653)
at com.ca.arcserve.edge.app.base.webservice.policymanagement.PolicyUtil.connectD2D(PolicyUtil.java:112)
at com.ca.arcserve.edge.app.base.webservice.policymanagement.PolicyManagementServiceImpl.deployPolicy(PolicyManagementServiceImpl.java:1599)
at com.ca.arcserve.edge.app.base.schedulers.policymanagement.policydeployment.deploytaskrunner.DefaultDeployTaskRunner.deployPolicy(DefaultDeployTaskRunner.java:281)
at com.ca.arcserve.edge.app.base.schedulers.policymanagement.policydeployment.deploytaskrunner.AbstractDeployTaskRunner.doTask(AbstractDeployTaskRunner.java:88)
at com.ca.arcserve.edge.app.base.schedulers.policymanagement.policydeployment.PolicyDeploymentTaskRunner.run(PolicyDeploymentTaskRunner.java:37)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
Caused by: java.net.ConnectException: Connection timed out: connect
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(Unknown Source)
at java.net.PlainSocketImpl.connectToAddress(Unknown Source)
at java.net.SocksSocketImpl.connect(Unknown Source)
at java.net.Socket.connect(Unknown Source)
at sun.net.NetworkClient.doConnect(Unknown Source)
at sun.net.www.http.HttpClient.openServer(Unknown Source)
at sun.net.www.http.HttpClient.openServer(Unknown Source)
at sun.net.www.http.HttpClient.(Unknown Source)
at sun.net.www.http.HttpClient.New(Unknown Source)
at sun.net.www.http.HttpClient.New(Unknown Source)
at sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient(Unknown Source)
at sun.net.www.protocol.http.HttpURLConnection.plainConnect(Unknown Source)
at sun.net.www.protocol.http.HttpURLConnection.connect(Unknown Source)
at sun.net.www.protocol.http.HttpURLConnection.getInputStream(Unknown Source)
at java.net.URL.openStream(Unknown Source)
at com.sun.xml.ws.wsdl.parser.RuntimeWSDLParser.createReader(RuntimeWSDLParser.java:804)
at com.sun.xml.ws.wsdl.parser.RuntimeWSDLParser.resolveWSDL(RuntimeWSDLParser.java:262)
at com.sun.xml.ws.wsdl.parser.RuntimeWSDLParser.parse(RuntimeWSDLParser.java:129)
... 17 more

2013-01-04 10:40:36,815 pool-2-thread-1 [ERROR]                deployPolicy(): Failed to connect to the node.
com.ca.arcserve.edge.app.base.webservice.policymanagement.PolicyManagementServiceImpl$ConnectD2DException
at com.ca.arcserve.edge.app.base.webservice.policymanagement.PolicyUtil.connectD2D(PolicyUtil.java:145)
at com.ca.arcserve.edge.app.base.webservice.policymanagement.PolicyManagementServiceImpl.deployPolicy(PolicyManagementServiceImpl.java:1599)
at com.ca.arcserve.edge.app.base.schedulers.policymanagement.policydeployment.deploytaskrunner.DefaultDeployTaskRunner.deployPolicy(DefaultDeployTaskRunner.java:281)
at com.ca.arcserve.edge.app.base.schedulers.policymanagement.policydeployment.deploytaskrunner.AbstractDeployTaskRunner.doTask(AbstractDeployTaskRunner.java:88)
at com.ca.arcserve.edge.app.base.schedulers.policymanagement.policydeployment.PolicyDeploymentTaskRunner.run(PolicyDeploymentTaskRunner.java:37)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)

2013-01-04 10:40:36,997 PolicyDeployment.TaskAssignerThread [INFO]    All tasks completed.

3- Final Assumption.
The update from CA ARCserve Central Host-Based VM Backup and CA ARCserve D2D r16.0 Update 7 to r16.5 GA was not successful due to the above monitored symptoms.

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

Comments