"name and id required" when trying to import application's runtime config | Community
Skip to main content
S
sangjmoon
March 9, 2020
Solved

"name and id required" when trying to import application's runtime config

  • March 9, 2020
  • 3 replies
  • 2945 views

I exported the runtime config from my dev AEM Forms 6.5 machine and after deploying the application lca on our test server with exact same configuration, I imported the runtime configuration file, but I get "name and id required" error message on the screen. The following is seen in the app server log:

 

15:50:32,570 SEVERE [com.adobe.repository.ui.aac.struts.actions.CommandProcessorAction] (default task-84) Application Administration: name and id required: java.lang.RuntimeException: name and id required
at com.adobe.repository.ui.aac.struts.actions.SelectApplicationAction.execute(SelectApplicationAction.java:116) [webapp.jar:6.5.0.0.20190329.336802]
at com.adobe.repository.ui.aac.struts.actions.CommandProcessorAction.execute(CommandProcessorAction.java:213) [webapp.jar:6.5.0.0.20190329.336802]
at sun.reflect.GeneratedMethodAccessor661.invoke(Unknown Source) [:1.8.0_232]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.8.0_232]
at java.lang.reflect.Method.invoke(Method.java:498) [rt.jar:1.8.0_232]
at ognl.OgnlRuntime.invokeMethod(OgnlRuntime.java:899) [ognl-3.1.15.jar:]
at ognl.OgnlRuntime.callAppropriateMethod(OgnlRuntime.java:1544) [ognl-3.1.15.jar:]
at ognl.ObjectMethodAccessor.callMethod(ObjectMethodAccessor.java:68) [ognl-3.1.15.jar:]

...

 

The exported runtime config xml file contents matches the deployed application. Why is this happening?

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by Kosta_Prokopiu1

This is a known problem and I think has been resolved from 6.5.3 onwards. I tested it in 6.5.5 and could not replicate it. You may want to update your AEM Forms installation.

3 replies

Mayank_Gandhi
Adobe Employee
Mayank_GandhiAdobe Employee
Adobe Employee
March 11, 2020

Please share the steps sequence, I will test on my local instance and confirm. Also, is this happening with all the LCA or just one?

 

Thanks,

Mayank

G
gloganathan
August 3, 2020
Hi All - I'm also facing same issue while export and import runtime config file; My application version is Version 6.5.0, GM. This is happening for ALL LCA. Could you please suggest me?
Mayank_Gandhi
Adobe Employee
Mayank_GandhiAdobe Employee
Adobe Employee
March 12, 2020

Based on my internal check you should apply latest CFP on 6.5 and test the issue. It seem to be already addressed on the latest CFP.

Kosta_Prokopiu1
Adobe Employee
Kosta_Prokopiu1Adobe EmployeeAccepted solution
Adobe Employee
August 4, 2020

This is a known problem and I think has been resolved from 6.5.3 onwards. I tested it in 6.5.5 and could not replicate it. You may want to update your AEM Forms installation.

    Terms & ConditionsAccessibility statement

    Loading footer...