Message Error Occurred Processing File Toc.xml
in creating Default Configuration 6 replies Latest Post - 2010-10-21T11:16:27Z by Dave.Yorn Display:ConversationsBy Date 1-7 of 7 Previous Next SystemAdmin 110000D4XK 4179 Posts Pinned topic Error in creating Default Configuration 2009-02-04T05:57:13Z | Tags: Answered question This question has been answered. Unanswered question This question has not been answered yet. Hi, I just installed MessageBroker ToolKits 6.1 (trail version) for windows (2003). Tried to create a default Configuration, but it stopped in half way through. Here is the error log: !SESSION 2009-02-04 12:45:02.470 eclipse.buildId=unknown java.fullversion=J2RE 1.5.0 IBM J9 2.3 Windows Server 2003 x86-32 j9vmwi3223-20071007 (JIT enabled) J9VM - 20071004_14218_lHdSMR JIT - 20070820_1846ifx1_r8 GC - 200708_10 BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US Framework arguments: -product com.ibm.etools.msgbroker.tooling.ide Command-line arguments: -os win32 -ws win32 -arch x86 -product com.ibm.etools.msgbroker.tooling.ide !ENTRY org.eclipse.help 4 0 2009-02-04 12:53:16.220 !MESSAGE Error occurred processing file toc.xml. !STACK 0 java.lang.RuntimeException: toc label==null at org.eclipse.help.internal.toc.Toc.
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support
MQSeries.net Forum Index » WebSphere Message Broker Support » default configuration manager not created default configuration manager not created « View previous topic :: View next topic » Author Message mrgate Posted: Thu Apr 26, 2007 8:13 am Post https://www.ibm.com/developerworks/forums/thread.jspa?threadID=250139 subject: default configuration manager not created CenturionJoined: 28 Feb 2007Posts: 141Location: India Hi, I am tring to create default configuration manager WBRK6_DEFAULT_CONFIGURATION_MANAGER in my system and after starting the wizard, the default database DEFBKDB6 was created and after this while the configuration manager was going to be created an error has occured showing the following: Task: Creating http://www.mqseries.net/phpBB/viewtopic.php?p=176177&sid=a9d1c24d0fd46dbcfdd3fdba460bbeba the Configuration Manager. [WBRK6_DEFAULT_CONFIGURATION_MANAGER] failed If you can manually fix the issues that caused this task to fail, do so and then click Yes. If you click Yes, the wizard starts the task again. If you click No, the wizard rolls back all completed tasks, if roll-back is possible. To establish why the task failed, examine this wizard's log file which can be found in the workspace directory [C:\Documents and Settings\ABC\IBM\wmbt6.0\workspace2\.metadata]. after going to the workspace workspace2\.metadata folder and after viewing the log file, the contents of the log file are as follows: !SESSION Apr 26, 2007 21:38:00.627 --------------------------------------------- eclipse.buildId=I200406192000 java.fullversion=J2RE 1.4.2 IBM J9 2.2 Windows 2000 x86-32 j9n142-20040917 (JIT enabled) J9VM - 20040916_0908_lHdSMR JIT - r7_level20040915_1801 BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US Command-line arguments: -plugincustomization C:\Program Files\IBM\MessageBrokersToolkit\6.0\eclipse\plugins\com.ibm.etools.msgbroker.tooling_6.0.0\plugin_customization.ini !ENTRY org.eclipse.help 4 0 Apr 26, 2007 21:38:00.627 !MESSAGE Error occurred processing file toc.xml. !STACK 0 java.lang.RuntimeException: toc label==null at org.eclipse.help.internal.toc.Toc.Now Sales FAQ Register Code Resellers Resources Documentation Videos Blog Download Oxygen SDK License Server Spell Checking https://www.oxygenxml.com/forum/topic13431.html Other Resources Logo Resources Support Sales Support Technical Support Forum Mailing Lists Contact Us Testimonials Company Partners Events About Us Customers Quotes Case Studies Careers News Legal Oxygen XML Forum Skip to content Search Advanced search Home Quick links Unanswered posts Active topics Search Forums Members The team FAQ Login message error Register Search Login Register Home Board index
/Users/miklosduma/oxygenAuthor/frameworks/dita/DITA-OT2.x/plugins/com.oxygenxml.webhelp/build_dita.xml:434: Fatal error during transformation using /Users/miklosduma/oxygenAuthor/frameworks/dita/DITA-OT2.x/plugins/com.oxygenxml.webhelp/xsl/dita/tocDita.xsl: I/O error reported by XML parser processing file:/Users/miklosduma/DITA/temp/webhelp/oxygen_dita_temp/TopicRoot/Glossary/transaction_glossentry.dita: /Users/miklosduma/DITA/temp/webhelp/oxygen_dita_temp/TopicRoot/Glossary/transaction_glossentry.dita (No such file or directory); SystemID: file:/Users/miklosduma/oxygenAuthor/frameworks/dita/DITA-OT2.x/xsl/common/dita-utilities.xsl; Line#: 450; Column#: -1I tried it with glossrefs as well, and it did work with DITA OT 1.8.5 At the moment my glossary looks like:Code: Select all