Unable to edit a DCR

Hello,

I am working on TeamSite 6.7.2. I am getting following error while trying to edit a DCR/create new one. Same DCT works fine in other branches. Does anyone have any idea about this and how to solve this?

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

Root cause:
SAX Parse:The entity "uuml" was referenced, but not declared.

Details...

com.interwoven.ui.datacapture.core.dct.InlineCallout$InlineCalloutException: SAX Parse:The entity "uuml" was referenced, but not declared.
at com.interwoven.ui.datacapture.external.InlineCalloutProcessor.evaluateInlineCallouts(InlineCalloutProcessor.java:178)
at com.interwoven.ui.formspub.datacapture.DCRPredicate.buildDCRDocument(DCRPredicate.java:199)
at com.interwoven.ui.formspub.datacapture.NewDCRPredicate.execute(NewDCRPredicate.java:64)
at com.interwoven.ui.formspub.datacapture.NewDCRCommand.execute(NewDCRCommand.java:338)
at com.interwoven.ui.base.impl.command.CommandHandler.doExecuteCommand(CommandHandler.java:917)
at com.interwoven.ui.base.impl.command.CommandHandler.tryRunCommandDescriptor(CommandHandler.java:753)
at com.interwoven.ui.base.impl.command.CommandHandler.tryRunCommandID(CommandHandler.java:628)
at com.interwoven.ui.base.impl.command.CommandHandler.runCommand(CommandHandler.java:418)
at com.interwoven.ui.base.impl.command.CommandCallbackContextImpl.callback(CommandCallbackContextImpl.java:45)
at com.interwoven.ui.base.wizard.WizardCommand.execute(WizardCommand.java:116)
at com.interwoven.ui.base.impl.command.CommandHandler.doExecuteCommand(CommandHandler.java:917)
at com.interwoven.ui.base.impl.command.CommandHandler.tryRunCommandDescriptor(CommandHandler.java:753)
at com.interwoven.ui.base.impl.command.CommandHandler.tryRunCommandID(CommandHandler.java:628)
at com.interwoven.ui.base.impl.command.CommandHandler.runCommandLoop(CommandHandler.java:233)
at com.interwoven.ui.base.impl.command.CommandServlet.doGet(CommandServlet.java:163)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:690)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:269)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188)
at com.interwoven.ui.base.impl.auth.AuthenticationFilter.doFilter(AuthenticationFilter.java:203)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:215)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188)
at com.interwoven.ui.base.util.SetRequestEncodingFilter.doFilter(SetRequestEncodingFilter.java:106)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:215)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:174)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:117)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:108)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:151)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:874)
at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:665)
at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:528)
at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:81)
at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:689)
at java.lang.Thread.run(Thread.java:595)

Thanks,
_Uttara

Find more posts tagged with

Comments

nipper

Do you use inline callouts:

ut$InlineCalloutException: SAX Parse:The entity "uuml" was referenced, but not declared.

multival_crosstab.rptdesign

Uttara

Hi nipper,

Thanks for your reply.

Yes, we do use inline callouts. But I am not sure what to look for in there. I know that the call-out scripts are working fine as 1. They are working for other branches/DCTs 2. They have not been modified since 2005.

Thanks
_Uttara

nipper

Hi nipper,

Thanks for your reply.

Yes, we do use inline callouts. But I am not sure what to look for in there. I know that the call-out scripts are working fine as 1. They are working for other branches/DCTs 2. They have not been modified since 2005.

Thanks
_Uttara

I assume if you click new form entry, you get the same result or is it different ?

That is a hard one because we know nothing of the inlines. They are your custom code. Most likely there is a config file missing somewhere.

I would comment out an item at a time (items that use callouts) and just click new form entry, hopefully you can narrow down the offending callout. If it is multiple callouts broken, it makes things harder.

Also you can open a command shell. CD to the DCT location and run the inline from the command line (iwperl /apps/iw-home/local/bin/someipl.ipl) and see which ones do not print out XML

ISCBorisB

Hi nipper,

Thanks for your reply.

Yes, we do use inline callouts. But I am not sure what to look for in there. I know that the call-out scripts are working fine as 1. They are working for other branches/DCTs 2. They have not been modified since 2005.

Thanks
_Uttara

Somewhere within your DCT you are using HTML entity ü ( ü - lower case u umlaut ),
either coded directly into DCT or coming from the inlines' substitutions.

Although this is correct HTML Entity (ie, Browsers understand it) it is certainly not
correct XML Entity (ie, XML Parser has no idea what to do with it).

The easiest way to fix that is to use numeric XML Entity instead, like this: ü or in hex format ü - same thing.
Alternatively, you can declare your own XML Entity "uuml" thus making your XML valid.

Uttara

Thanks again nipper.

I guess you are right. I just checked all the custom code once again and realised that the inline call-outs are fine, but one of the config file that the call-out uses was recently updated by a user. She put in special characters in there (German). I think those characters are messing up the whole DCT.

Is there a way to treat special characters? This inline basically populates a select list for the DCT.

Thanks,
_Uttara

nipper

Bo posted just before you did. That should help. If you still have questions, post again.