Editing JOBS objects using AWI v12 results in "Error during XRequest" message

Document ID : KB000087612
Last Modified Date : 14/04/2018
Show Technical Document Details
Issue:
Error Message :
Error during XRequest com.uc4.webui.communication.requests.OpenObjectAdapter

Editing some of the JOBS objects from the Automic Web Interface (AWI) v12 results in the popup error message as shown above.

From the Stack trace the following errors can also be seen.

Object view could not be loaded.
Hide Details
(Stacktrace)
(No Message)
java.lang.NullPointerException
com.uc4.ecc.ae.commons.content.uc4objectview.UC4ObjectContext.toObjectReference(UC4ObjectContext.java:116) com.uc4.ecc.ae.commons.content.uc4objectview.UC4ObjectPresenter.load(UC4ObjectPresenter.java:792) com.uc4.ecc.ae.commons.content.uc4objectview.UC4ObjectPresenter.access$200(UC4ObjectPresenter.java:92) com.uc4.ecc.ae.commons.content.uc4objectview.UC4ObjectPresenter$3.loadWithNullAsDefault(UC4ObjectPresenter.java:686) com.uc4.ecc.ae.commons.content.uc4objectview.UC4ObjectPresenter$3.loadWithNullAsDefault(UC4ObjectPresenter.java:682) com.uc4.webui.common.async.NullAsDefaultLoader.load(NullAsDefaultLoader.java:10) com.uc4.webui.common.async.NullAsDefaultLoader.load(NullAsDefaultLoader.java:6) com.uc4.ecc.framework.core.async.BaseRequestCoordinator$1$1.call(BaseRequestCoordinator.java:214) com.uc4.ecc.framework.core.pool.ContextAwareExecutorService$CallableImplementation.call(ContextAwareExecutorService.java:72) java.util.concurrent.FutureTask.run(Unknown Source) java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) java.lang.Thread.run(Unknown Source) 

Cause:
Cause type:
Other
Root Cause: The issue is coming from a corrupted export file which could be cause by exporting using the old AE API or ECC. There were several issues with the export/import function which were corrected in v12.
Resolution:
This field was added on 30/03/2017. This article has not been updated yet. Refer to the "Description" or "Workaround" sections for solution information.

Fix Status: No Fix

Additional Information:
Workaround :
When you open the export.xml you find the following lines where the closing tag is missing.================================================= <?xml version="1.0" encoding="ISO-8859-1"?><!DOCTYPE Content [ <!ELEMENT Content ( #PCDATA ) > ]> <Content>https://urldefense.proofpoint.com/v2/url?u=http-3A__mars_demoulas_ ================================================= If you add this ending tag and re-import the object you can then open it in the AWI as well. Syntax with the closing tag added:================================================= <?xml version="1.0" encoding="ISO-8859-1"?><!DOCTYPE Content [ <!ELEMENT Content ( #PCDATA ) > ]> <Content>https://urldefense.proofpoint.com/v2/url?u=http-3A__mars_demoulas_</Content> =================================================