DCT wont open error (New form entry)

Hey Guys,

I've been trying to create new form from datacapture.cfg file on dev server. I've checked and compared same file to other staging server and all files and path seem to be the same but i get this error on dev server. How can I create new form and resolve this error below:

A problem was encountered trying to read the datacapture.cfg file for type list. Please contact your system administrator.

Hide Details... Close

Root cause:
SAX Parse:Content is not allowed in prolog.

Details...

com.interwoven.ui.datacapture.core.dct.InlineCallout$InlineCalloutException: SAX Parse:Content is not allowed in prolog.
at com.interwoven.ui.datacapture.external.InlineCalloutProcessor.evaluateInlineCallouts(InlineCalloutProcessor.java:169)
at com.interwoven.ui.formspub.datacapture.DCRPredicate.buildDCRDocument(DCRPredicate.java:188)
at com.interwoven.ui.formspub.datacapture.NewDCRPredicate.execute(NewDCRPredicate.java:63)
at com.interwoven.ui.formspub.datacapture.NewDCRCommand.execute(NewDCRCommand.java:325)
at com.interwoven.ui.base.impl.command.CommandHandler.doExecuteCommand(CommandHandler.java:915)
at com.interwoven.ui.base.impl.command.CommandHandler.tryRunCommandDescriptor(CommandHandler.java:752)
at com.interwoven.ui.base.impl.command.CommandHandler.tryRunCommandID(CommandHandler.java:629)
at com.interwoven.ui.base.impl.command.CommandHandler.runCommand(CommandHandler.java:419)
at com.interwoven.ui.base.impl.command.CommandCallbackContextImpl.callback(CommandCallbackContextImpl.java:45)
at com.interwoven.ui.base.wizard.WizardCommand.execute(WizardCommand.java:115)
at com.interwoven.ui.base.impl.command.CommandHandler.doExecuteCommand(CommandHandler.java:915)
at com.interwoven.ui.base.impl.command.CommandHandler.tryRunCommandDescriptor(CommandHandler.java:752)
at com.interwoven.ui.base.impl.command.CommandHandler.tryRunCommandID(CommandHandler.java:629)
at com.interwoven.ui.base.impl.command.CommandHandler.runCommandLoop(CommandHandler.java:234)
at com.interwoven.ui.base.impl.command.CommandServlet.doGet(CommandServlet.java:163)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:689)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at com.interwoven.ui.base.impl.auth.AuthenticationFilter.doFilter(AuthenticationFilter.java:204)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at com.interwoven.ui.base.util.SetRequestEncodingFilter.doFilter(SetRequestEncodingFilter.java:105)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869)
at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664)
at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:80)
at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684)
at java.lang.Thread.run(Thread.java:595)

Find more posts tagged with

Comments

nipper

Check your DCT, it is very likely an issue with it. You can trim it down ot almost nothing and see if it works.

Post results if you need more help.

ISCBorisB

I saw that couple times with the <inline> returning malformed XML. Also, check TeamSite Error Reading Templating.cfg

begood321

Thanks Guys after doing a further comparison of both servers I realised I had to remove or comment out a print statement in CTUtils.pm module on my dev server after comparing compiliation warnings in my callout of both dev and staging servers.