Problem Note 61972: Configuration of the SAS® Job Monitor Administration component fails with the error "Unable to delete the metadata object(s): No valid. . ."
The configuration fails for the Job Monitor Administration component when you deploy it from a Rev. 940_17w16 or later installation depot. When this failure occurs, you see the following error in the configuration log:
BUILD FAILED
D:\SASHomeM4\SASJobMonitorAdministration\2.2\Config\jobmntrhyp_config.xml:42: The following error occurred while executing this line:
D:\SASHomeM4\SASJobMonitorAdministration\2.2\Config\jobmntrhyp_config.xml:572: The following error occurred while executing this line:
D:\SASHomeM4\SASDeploymentManager\9.4\products\cfgwizard__94478__prt__xx__sp0__1\Utilities\loadMetadata.xml:765: Unable to delete the metadata object(s): No valid object id to delete
at org.apache.tools.ant.ProjectHelper.addLocationToBuildException(ProjectHelper.java:541)
at org.apache.tools.ant.taskdefs.MacroInstance.execute(MacroInstance.java:394)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:288)
at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:105)
at org.apache.tools.ant.Task.perform(Task.java:348)
at org.apache.tools.ant.taskdefs.Sequential.execute(Sequential.java:62)
at net.sf.antcontrib.logic.IfTask.execute(IfTask.java:197)
at sun.reflect.GeneratedMethodAccessor29.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:105)
at org.apache.tools.ant.TaskAdapter.execute(TaskAdapter.java:134)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:288)
at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:105)
at org.apache.tools.ant.Task.perform(Task.java:348)
at org.apache.tools.ant.taskdefs.Sequential.execute(Sequential.java:62)
at net.sf.antcontrib.logic.IfTask.execute(IfTask.java:197)
at sun.reflect.GeneratedMethodAccessor29.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:105)
at org.apache.tools.ant.TaskAdapter.execute(TaskAdapter.java:134)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:288)
at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:105)
at org.apache.tools.ant.Task.perform(Task.java:348)
at org.apache.tools.ant.Target.execute(Target.java:357)
at org.apache.tools.ant.Target.performTasks(Target.java:385)
at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1329)
at org.apache.tools.ant.Project.executeTarget(Project.java:1298)
at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41)
at org.apache.tools.ant.Project.executeTargets(Project.java:1181)
at org.apache.tools.ant.Main.runBuild(Main.java:698)
at org.apache.tools.ant.Main.startAnt(Main.java:199)
at org.apache.tools.ant.launch.Launcher.run(Launcher.java:257)
at org.apache.tools.ant.launch.Launcher.main(Launcher.java:104)
The configuration fails when you click Retry during a migration or upgrade.
To work around this problem, you need to manually edit the jobmntrhyp_config.xml file, whic his located in the $SASHome\ SASJobMonitorAdministration\2.2\Config folder. In the file, change the jobmntrhyp.softwarecomponent.id reference to jobmntrhyp.servercomponent.id and remove the <elseif><istrue value="${wizard.retry}" block of code.
After you modify and save the jobmntrhyp_config.xml file, click Retry. The configuration should complete successfully
Click the Hot Fix tab in this note to access the hot fix for this issue.
Operating System and Release Information
SAS System | SAS Job Monitor | Microsoft® Windows® for x64 | 2.2 | | | |
64-bit Enabled AIX | 2.2 | | | |
64-bit Enabled Solaris | 2.2 | | | |
HP-UX IPF | 2.2 | | | |
Linux for x64 | 2.2 | | | |
Solaris for x64 | 2.2 | | | |
*
For software releases that are not yet generally available, the Fixed
Release is the software release in which the problem is planned to be
fixed.
When it is deployed from a Rev. 940_17w16 or later installation depot, the configuration for the SAS Job Monitor Administration component fails. The failure occurs when you click "Retry" during an migration or upgrade.
Type: | Problem Note |
Priority: | high |
Date Modified: | 2018-04-25 11:05:17 |
Date Created: | 2018-03-14 08:42:16 |