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 User287063, 1 year ago
RC-50014: Fatal: Execution of AutoConfig was failed
via Oracle Community by muneer.ngha.ksa, 1 year ago
RC-50014: Fatal: Execution of AutoConfig was failed
via Oracle Community by Adam, 1 year ago
RC-50014: Fatal: Execution of AutoConfig was failed
via Oracle Community by 871455, 1 year ago
RC-50014: Fatal: Execution of AutoConfig was failed
via Oracle Community by 495265, 2 years ago
RC-50014: Fatal: Execution of AutoConfig was failed
via Oracle Community by 542838, 2 years 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:3192) at oracle.apps.ad.clone.ApplyDatabase.runCVMAndAutoConfig(ApplyDatabase.java:3010) at oracle.apps.ad.clone.ApplyDatabase.doConf(ApplyDatabase.java:649) at oracle.apps.ad.clone.ApplyDatabase.doApply(ApplyDatabase.java:473) at oracle.apps.ad.clone.ApplyDatabase.<init>(ApplyDatabase.java:366) 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:67) at java.lang.Thread.run(Thread.java:637)