Searched on Google with the first line of a JAVA stack trace?

We can recommend more relevant solutions and speed up debugging when you paste your entire stack trace with the exception message. Try a sample exception.

Recommended solutions based on your search

Solutions on the web

via Oracle Community by Kumar_Jaga, 1 year ago
RC-50014: Fatal: Execution of AutoConfig was failed
via Oracle Community by 542838, 1 year ago
RC-50014: Fatal: Execution of AutoConfig was failed
via Oracle Community by 821674, 1 year ago
RC-50014: Fatal: Execution of AutoConfig was failed
via Oracle Community by 495265, 1 year ago
RC-50014: Fatal: Execution of AutoConfig was failed
via Oracle Community by 734907, 1 year ago
RC-50014: Fatal: Execution of AutoConfig was failed
via Oracle Community by User287063, 1 year ago
RC-50014: Fatal: Execution of AutoConfig was failed
java.lang.Exception: RC-50014: Fatal: Execution of AutoConfig was failed	at oracle.apps.ad.clone.ApplyDatabase.checkAutoConfigErr(ApplyDatabase.java:2825)	at oracle.apps.ad.clone.ApplyDatabase.runAutoConfig(ApplyDatabase.java:2620)	at oracle.apps.ad.clone.ApplyDatabase.(ApplyDatabase.java:595)	at oracle.apps.ad.clone.ApplyDatabase.(ApplyDatabase.java:328)	at oracle.apps.ad.clone.ApplyDatabase.(ApplyDatabase.java:304)	at oracle.apps.ad.clone.ApplyDBTier.(ApplyDBTier.java:154)	at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)	at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)	at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)	at java.lang.reflect.Constructor.newInstance(Constructor.java:501)	at oracle.apps.ad.clone.util.CloneProcessor.run(CloneProcessor.java:68)	at java.lang.Thread.run(Thread.java:637)