search cancel

Service Desk Manager Connector fails to install. Errors in log: "Resource does not exist at path /topology/physical/10_CatalystServer/reconciler/reconciledViews.xml"


Article ID: 17873


Updated On:


CA IT Asset Manager CA Software Asset Manager (CA SAM) ASSET PORTFOLIO MGMT- SERVER SUPPORT AUTOMATION- SERVER CA Service Desk Manager - Unified Self Service CA Service Desk Manager CA Service Management - Asset Portfolio Management CA Service Management - Service Desk Manager



When installing the Service Desk Manager Connector and it fails the Catalyst_SDMConnector_InstallDebug.log should be reviewed, the logs may contain an error like:

 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) 
 at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
 at java.lang.reflect.Method.invoke(Unknown Source)
 at Source)
 at com.zerog.ia.installer.actions.CustomAction.installSelf(DashoA10*..)
 at com.zerog.ia.installer.InstallablePiece.install(DashoA10*..)
 at com.zerog.ia.installer.InstallablePiece.install(DashoA10*..)
 at com.zerog.ia.installer.InstallablePiece.install(DashoA10*..)
 at com.zerog.ia.installer.GhostDirectory.install(DashoA10*..)
 at com.zerog.ia.installer.InstallablePiece.install(DashoA10*..)
 at com.zerog.ia.installer.Installer.install(DashoA10*..)
 at com.zerog.ia.installer.actions.InstallProgressAction.n(DashoA10*..)
 at com.zerog.ia.installer.actions.ProgressPanelAction$*..)
 Caused by: org.wso2.carbon.registry.core.exceptions.
 ResourceNotFoundException: Resource does not exist at path 	/topology/physical/10_CatalystServer/reconciler/reconciledViews.xml       
 ... 15 more
 Caused by: org.wso2.carbon.registry.core.exceptions.ResourceNotFoundException: Resource does not exist at
 path 	/topology/physical/10_CatalystServer/reconciler/reconciledViews.xml 


Of particular note in the errors above is the path:


During the install of the Catalyst Container it is required to specify information related to the Catalyst Server, including the name. The name specified is used to build a path for the Catalyst Registry. By it's default The Catalyst Server path expects the server's name to be specified. If an IP address is specified during the Container install it will fail to install correctly, because the installer will assume that the Registry path is everything prior to the first period within the name specified. If an IP is used, like "", all information after the first period is cut off and the Registry path is assumed to be "10", which would not be valid.

To resolve the problem the Catalyst Server's host name should be specified during the Container install. If the server is unable to connect to the Catalyst Server by host name, an entry should be created in the Windows "Hosts" file to link the host name to an IP address.

It is NOT possible to get around this limitation to only use IP address.


Release: UAPMAC990JPP-12.9-Asset Portfolio Management-Asset Configuration