Message "Trying XBeans path engine..." while viewing the agent definitions
search cancel

Message "Trying XBeans path engine..." while viewing the agent definitions

book

Article ID: 248016

calendar_today

Updated On:

Products

CA Workload Automation DE

Issue/Introduction

The desktop client returns following message while viewing the agent definition. The same message can also be found in the server side trace log.

[Thu Jun 30 10:14:16 CST 2022] [SERVER01] - Retrieve AGENT SYSAGENT1

[Thu Jun 30 10:14:16 CST 2022] [SERVER01] - List AGENTGRP

[Thu Jun 30 10:14:16 CST 2022] [SERVER01] - Agent SYSAGENT1 successfully read

[Thu Jun 30 10:14:16 CST 2022] [SERVER01] - Agentgrps successfully listed

[Thu Jun 30 10:14:16 CST 2022] [SERVER01] -  Trying XBeans path engine... Trying XQRL... Trying XDK... Trying delegated path engine... FAILED on declare namespace ns='http://dto.wa.ca.com/agentgrp';$this//ns:agent[*]

[Thu Jun 30 10:14:26 CST 2022] [SERVER01] - Retrieve AGENT SYSAGENT2

[Thu Jun 30 10:14:26 CST 2022] [SERVER01] - List AGENTGRP

[Thu Jun 30 10:14:26 CST 2022] [SERVER01] - Agent SYSAGENT2 successfully read

[Thu Jun 30 10:14:26 CST 2022] [SERVER01] - Agentgrps successfully listed

[Thu Jun 30 10:14:26 CST 2022] [SERVER01] -  Trying XBeans path engine... Trying XQRL... Trying XDK... Trying delegated path engine... FAILED on declare namespace ns='http://dto.wa.ca.com/agentgrp';$this//ns:agent[*]

This problem is only seen after upgrading the server to the latest release 12.3 3625

Environment

Release : 12.3

Component : CA WORKLOAD AUTOMATION DE (DSERIES)

Cause

It is due to an issue while starting the services using the services console after an in place upgrade from lower releases

Resolution

This problem might appear post upgrading the DE server to 12.3 if the server service has been started from the windows services manager.

To resolve the issue,  Open the file "<USER_INSTALL_DIR>/conf/windows.service.properties" in any text-editor. Search for "saxon9he.jar" and replace it with "saxon.jar".

Start the server from services.

Additional Information

Workaround: 

Start the server using binary USER_INSTALL_DIR/bin/startServer.exe