Error in DTD

Can anyone explain why is this happening and what's the solution.
I am trying to parse an XML file from an Java applet. When the parse(URL) method is called, it returns an error (Error opening external DTD). This is the line for de DTD in the XML: <!DOCTYPE MALTED SYSTEM "../../templates/dtd/Course.dtd">.
My html file (codebase) is in ./MaltedApplet.html.
My xml file is in ./projects/Colours/xml/Colours.xml.
My dtd file is in ./projects/templates/dtd/Course.dtd.
What is wrong?
null

Would you check SampleMain.java you are using? Currently, all of our class generator examples use:
import oracle.xml.parser.v2.*;
instead of
import oracle.xml.parser.* in your file.
Would you change your code and using xmlparserv2.jar and try?
Thanks.

Similar Messages

Error with DTD duplicated SYSTEM inclusion

I'm working with one of the latest releases
Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit Production
PL/SQL Release 11.2.0.1.0 - Production
"CORE 11.2.0.1.0 Production"
TNS for Linux: Version 11.2.0.1.0 - Production
NLSRTL Version 11.2.0.1.0 - Production
I'm trying to insert xml into an XMLType table, and validate it with a DTD. To achieve this i created a folder /xmlmine/dtd and applied this acl to it
<acl description="dilbertacl" xmlns="http://xmlns.oracle.com/xdb/acl.xsd" xmlns:dav="DAV:" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://xmlns.oracle.com/xdb/acl.xsd http://xmlns.oracle.com/xdb/acl.xsd" shared="true">
 <ace>
 <grant>true</grant>
 <principal>DILBERT</principal>
 <privilege>
 <dav:all/>
 </privilege>
 </ace>
 </acl>i then uploaded this dtd to play.dtd with
DECLARE
b BOOLEAN;
BEGIN
b := DBMS_XDB.createResource('/xmlmine/dtd/play.dtd',bfilename('dtds', 'play.dtd'));
END;and i can see it with
select xdburitype('/xmlmine/dtd/play.dtd').getCLOB() from dual;



<!ENTITY amp "&">
<!ELEMENT PLAY (TITLE, FM, PERSONAE, SCNDESCR, PLAYSUBT, INDUCT?, PROLOGUE?, ACT+, EPILOGUE?)>
<!ELEMENT TITLE (#PCDATA)>
<!ELEMENT FM (P+)>
<!ELEMENT P (#PCDATA)>
<!ELEMENT PERSONAE (TITLE, (PERSONA | PGROUP)+)>
<!ELEMENT PGROUP (PERSONA+, GRPDESCR)>
<!ELEMENT PERSONA (#PCDATA)>
<!ELEMENT GRPDESCR (#PCDATA)>
<!ELEMENT SCNDESCR (#PCDATA)>
<!ELEMENT PLAYSUBT (#PCDATA)>
<!ELEMENT INDUCT (TITLE, SUBTITLE*, (SCENE+|(SPEECH|STAGEDIR|SUBHEAD)+))>
<!ELEMENT ACT (TITLE, SUBTITLE*, PROLOGUE?, SCENE+, EPILOGUE?)>
<!ELEMENT SCENE (TITLE, SUBTITLE*, (SPEECH | STAGEDIR | SUBHEAD)+)>
<!ELEMENT PROLOGUE (TITLE, SUBTITLE*, (STAGEDIR | SPEECH)+)>
<!ELEMENT EPILOGUE (TITLE, SUBTITLE*, (STAGEDIR | SPEECH)+)>
<!ELEMENT SPEECH (SPEAKER+, (LINE | STAGEDIR | SUBHEAD)+)>
<!ELEMENT SPEAKER (#PCDATA)>
<!ELEMENT LINE (#PCDATA | STAGEDIR)*>
<!ELEMENT STAGEDIR (#PCDATA)>
<!ELEMENT SUBTITLE (#PCDATA)>
<!ELEMENT SUBHEAD (#PCDATA)>when i proceed to insert with
INSERT INTO sestable VALUES (XMLType(bfilename('xmls', 'all_well.xml'),nls_charset_id('AL32UTF8')));the top of the xml document looks like
<?xml version="1.0" encoding="WINDOWS-1252"?>
<!DOCTYPE PLAY SYSTEM "/xmlmine/dtd/play.dtd" [
<!ELEMENT PLAY (TITLE, FM, PERSONAE, SCNDESCR, PLAYSUBT, INDUCT?, PROLOGUE?, ACT+, EPILOGUE?)>
<!ELEMENT TITLE (#PCDATA)>
<!ELEMENT FM (P+)>
<!ELEMENT SUBTITLE (#PCDATA)>
<!ELEMENT SUBHEAD (#PCDATA)>
]>



<PLAY>
<TITLE>All's Well That Ends Well</TITLE>
<FM>
 Text placed in the public domain by Moby Lexical Tools, 1992.
 <STAGEDIR>Exeunt</STAGEDIR>
 </EPILOGUE>
</ACT>
</PLAY>but when i try to query the table with something like
select xtab.COLUMN_VALUE
from sestable, XMLTable('let $i := /PLAY/ACT/SCENE/SPEECH[SPEAKER eq "DUKE"]/LINE
 return count($i)' PASSING OBJECT_VALUE) xtab;i get an error
LPX-00107:Warning: element "PLAY" has multiple declaration
if i remove the SYSTEM keyword and simply inline the DTD everything works just fine.
I suspect the parser is inlining the DTD but not removing the SYSTEM directive, thus including the DTD twice, hence the error. Any suggestion on how to solve this?
Thanks in advance

What should I do now, since binary XML does not seems to validate? Is there any other way to validate the XML document with a DTD besides directly copying and pasting the DTD in the file?Well, as a workaround, you can disable DTD validation after the document has been inserted in the table.
SQL> select storage_type from user_xml_tables where table_name = 'PLAYS2';
STORAGE_TYPE
CLOB
SQL> SELECT count(*)
2 FROM plays2 p
3 , XMLTable( '/PLAY/ACT/SCENE/SPEECH[SPEAKER eq "DUKE"]/LINE'
4 passing p.object_value ) x
5 WHERE XMLExists( '/PLAY[TITLE=$title]'
6 passing p.object_value
7 , 'All''s Well That Ends Well' as "title" )
8 ;
SELECT count(*)
ERROR at line 1:
ORA-31011: XML parsing failed
ORA-19202: Error occurred in XML processing
LPX-00107: Warning: element "PLAY" has multiple declarations
Error at line 24
Error at line 7
SQL> alter session set events '31156 trace name context forever, level 2';
Session altered.
SQL> SELECT count(*)
2 FROM plays2 p
3 , XMLTable( '/PLAY/ACT/SCENE/SPEECH[SPEAKER eq "DUKE"]/LINE'
4 passing p.object_value ) x
5 WHERE XMLExists( '/PLAY[TITLE=$title]'
6 passing p.object_value
7 , 'All''s Well That Ends Well' as "title" )
8 ;
COUNT(*)
 19
If this is a bug should I report it or you can do / have already done that?I didn't see anything in the documentation regarding DTD validation vs. binary XML, so yes I think you should report it to Oracle Support.

XML File not found error

Hi Guys,
I have an xml file that says something like below:
<?xml version ="1.0">
<!DOCTYPE test SYSTEM "/dtd/tester.dtd">
<test>
<testing>hello world</testing>
<test>
Thr problem is that my dtd folder inside the same place as my test.class file. but I'm calling my test.class from the root directory using java -cp . It keeps failing with error FileNotFoud:/dtd/tester.dtd. As I understood its looking for dtd folder in the root dir. But it cannot find it there so its failing. Any solution to this problem?????
Thanks

Any example would be geart, I'm using a DOM parser to validate see below:
String parsed = null;
DocumentBuilderFactory dbf = null;
try {
dbf =
DocumentBuilderFactory.newInstance();
dbf.setValidating(true);
dbf.setNamespaceAware(true);
dbf.setIgnoringElementContentWhitespace(true);
} catch (Exception e) {
// Parse the input to produce a parse tree with its root
// in the form of a Document object
try {
DocumentBuilder builder = dbf.newDocumentBuilder();
builder.setErrorHandler(new XmlErrorHandler());
Reader readFile = new StringReader(xmlDocument);
InputSource is = new InputSource(readFile);
doc = builder.parse(is);
DOMParse((Node) doc, "");
parsed = constants.XMLSUCESS;
} catch (SAXException e) {
xmlLogging.setServereLog("SAXExceptoin @DeviceHandlerXmlParser82 " +
e);
parsed = constants.XMLFAIL;

Error in installation

I am installing Solution Manager 4 R2 with MaxDB, I have "j2sdk1.4.2_09" at the start of the machine's presenting me java errors, they attached the contents of the "sapinst.log
INFO 2008-11-22 20:46:13
Copied file 'C:/Program Files/sapinst_instdir/SOLMAN/SYSTEM/ADA/CENTRAL/AS/inifile.xml' to 'C:/Program Files/sapinst_instdir/SOLMAN/SYSTEM/ADA/CENTRAL/AS/inifile.2.xml'.
INFO 2008-11-22 20:46:13
Copied file 'C:/Program Files/sapinst_instdir/SOLMAN/SYSTEM/ADA/CENTRAL/AS/inifile.xml' to 'C:/Program Files/sapinst_instdir/SOLMAN/SYSTEM/ADA/CENTRAL/AS/inifile.3.xml'.
INFO 2008-11-22 20:46:24
Execute step
Component W2K_ServicePack_Check|ind|ind|ind|ind
Preprocess of component |NW_Onehost|ind|ind|ind|ind|0|0|NW_First_Steps|ind|ind|ind|ind|0|0|W2K_ServicePack_Check|ind|ind|ind|ind|2|0.
INFO 2008-11-22 20:46:48
Copied file 'C:/Program Files/sapinst_instdir/SOLMAN/SYSTEM/ADA/CENTRAL/AS/keydb.xml' to 'C:/Program Files/sapinst_instdir/SOLMAN/SYSTEM/ADA/CENTRAL/AS/keydb.2.xml'.
INFO 2008-11-22 20:46:49
Execute step startJava of component |NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CI_Instance|ind|ind|ind|ind|11|0|NW_CI_Instance_StartJava|ind|ind|ind|ind|5|0.
WARNING 2008-11-22 20:46:51
Connect to message server (SOLMAN/3901) failed: NIECONN_REFUSED.
WARNING 2008-11-22 20:46:54
Connect to message server (SOLMAN/3900) failed: NIECONN_REFUSED.
WARNING 2008-11-22 20:46:55
Connect to message server (SOLMAN/3900) failed: NIECONN_REFUSED.
INFO 2008-11-22 20:46:55
Starting instance SOL/SCS01...
WARNING 2008-11-22 20:46:56
Connect to message server (SOLMAN/3901) failed: NIECONN_REFUSED.
INFO 2008-11-22 20:46:57
Creating file C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\ADA\CENTRAL\AS\stop_SOL_SCS01.log.
INFO 2008-11-22 20:46:59
Output of C:\usr\sap\SOL\SYS\exe\uc\NTI386\stopsap.exe name=SOL nr=01 SAPDIAHOST=SOLMAN is written to the logfile stop_SOL_SCS01.log.
INFO 2008-11-22 20:47:20
Execution of the command "C:\usr\sap\SOL\SYS\exe\uc\NTI386\stopsap.exe name=SOL nr=01 SAPDIAHOST=SOLMAN" finished with return code 0. Output:
STOPSAP executed succesfully
WARNING 2008-11-22 20:47:21
Connect to message server (SOLMAN/3901) failed: NIECONN_REFUSED.
INFO 2008-11-22 20:47:21
Creating file C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\ADA\CENTRAL\AS\start_SOL_SCS01.log.
INFO 2008-11-22 20:47:21
Output of C:\usr\sap\SOL\SYS\exe\uc\NTI386\startsap.exe name=SOL nr=01 SAPDIAHOST=SOLMAN is written to the logfile start_SOL_SCS01.log.
INFO 2008-11-22 20:47:49
Execution of the command "C:\usr\sap\SOL\SYS\exe\uc\NTI386\startsap.exe name=SOL nr=01 SAPDIAHOST=SOLMAN" finished with return code 0. Output:
STARTSAP continues...
INFO 2008-11-22 20:47:49
Connect to message server (SOLMAN/3901) succeeded.
INFO 2008-11-22 20:47:49
Disconnect from message server (SOLMAN/3901) succeeded.
INFO 2008-11-22 20:47:49
State of instance SOL/SCS01 changed from UNKNOWN to ACTIVE.
INFO 2008-11-22 20:47:49
Startup of instance SOL/SCS01 finished: [ACTIVE]. Elapsed time: 0:00 minutes.
INFO 2008-11-22 20:47:49
Starting instance SOL/DVEBMGS00...
WARNING 2008-11-22 20:47:50
Connect to message server (SOLMAN/3900) failed: NIECONN_REFUSED.
INFO 2008-11-22 20:47:50
Connect to message server (SOLMAN/3901) succeeded.
INFO 2008-11-22 20:47:50
Disconnect from message server (SOLMAN/3901) succeeded.
INFO 2008-11-22 20:47:50
Connect to message server (SOLMAN/3901) succeeded.
INFO 2008-11-22 20:47:50
Disconnect from message server (SOLMAN/3901) succeeded.
INFO 2008-11-22 20:47:52
Creating file C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\ADA\CENTRAL\AS\stop_SOL_DVEBMGS00.log.
INFO 2008-11-22 20:47:52
Output of C:\usr\sap\SOL\SYS\exe\uc\NTI386\stopsap.exe name=SOL nr=00 SAPDIAHOST=SOLMAN is written to the logfile stop_SOL_DVEBMGS00.log.
INFO 2008-11-22 20:48:02
Execution of the command "C:\usr\sap\SOL\SYS\exe\uc\NTI386\stopsap.exe name=SOL nr=00 SAPDIAHOST=SOLMAN" finished with return code 0. Output:
STOPSAP executed succesfully
INFO 2008-11-22 20:48:03
Connect to message server (SOLMAN/3901) succeeded.
INFO 2008-11-22 20:48:03
Disconnect from message server (SOLMAN/3901) succeeded.
INFO 2008-11-22 20:48:03
Connect to message server (SOLMAN/3901) succeeded.
INFO 2008-11-22 20:48:03
Disconnect from message server (SOLMAN/3901) succeeded.
WARNING 2008-11-22 20:48:04
Connect to message server (SOLMAN/3900) failed: NIECONN_REFUSED.
INFO 2008-11-22 20:48:05
Creating file C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\ADA\CENTRAL\AS\start_SOL_DVEBMGS00.log.
INFO 2008-11-22 20:48:05
Output of C:\usr\sap\SOL\SYS\exe\uc\NTI386\startsap.exe name=SOL nr=00 SAPDIAHOST=SOLMAN is written to the logfile start_SOL_DVEBMGS00.log.
WARNING 2008-11-22 20:51:43
Execution of the command "C:\usr\sap\SOL\SYS\exe\uc\NTI386\startsap.exe name=SOL nr=00 SAPDIAHOST=SOLMAN" finished with return code -1. Output:
STARTSAP failed
Details are written to C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\ADA\CENTRAL\AS\startSOL.log
INFO 2008-11-22 20:51:55
Connect to message server (SOLMAN/3901) succeeded.
INFO 2008-11-22 20:51:55
Disconnect from message server (SOLMAN/3901) succeeded.
INFO 2008-11-22 20:51:55
Connect to message server (SOLMAN/3901) succeeded.
INFO 2008-11-22 20:51:55
Disconnect from message server (SOLMAN/3901) succeeded.
INFO 2008-11-22 20:52:10
Connect to message server (SOLMAN/3901) succeeded.
INFO 2008-11-22 20:52:10
Disconnect from message server (SOLMAN/3901) succeeded.
INFO 2008-11-22 20:52:10
Connect to message server (SOLMAN/3901) succeeded.
INFO 2008-11-22 20:52:10
Disconnect from message server (SOLMAN/3901) succeeded.
INFO 2008-11-22 20:52:12
Connect to message server (SOLMAN/3900) succeeded.
INFO 2008-11-22 20:52:12
Disconnect from message server (SOLMAN/3900) succeeded.
INFO 2008-11-22 20:52:12
Connect to message server (SOLMAN/3900) succeeded.
INFO 2008-11-22 20:52:12
Disconnect from message server (SOLMAN/3900) succeeded.
INFO 2008-11-22 20:52:12
State of instance SOL/DVEBMGS00 changed from ABAP: UNKNOWN, Java: UNKNOWN to ABAP: UNKNOWN, Java: UNKNOWN.
INFO 2008-11-22 20:52:31
Connect to message server (SOLMAN/3901) succeeded.
INFO 2008-11-22 20:52:31
Disconnect from message server (SOLMAN/3901) succeeded.
INFO 2008-11-22 20:52:31
Connect to message server (SOLMAN/3901) succeeded.
INFO 2008-11-22 20:52:31
Disconnect from message server (SOLMAN/3901) succeeded.
INFO 2008-11-22 20:52:32
Connect to message server (SOLMAN/3901) succeeded.
INFO 2008-11-22 20:52:32
Disconnect from message server (SOLMAN/3901) succeeded.
INFO 2008-11-22 20:52:32
Connect to message server (SOLMAN/3901) succeeded.
INFO 2008-11-22 20:52:32
Disconnect from message server (SOLMAN/3901) succeeded.
INFO 2008-11-22 20:52:32
Connect to message server (SOLMAN/3900) succeeded.
INFO 2008-11-22 20:52:32
Disconnect from message server (SOLMAN/3900) succeeded.
INFO 2008-11-22 20:52:32
Connect to message server (SOLMAN/3900) succeeded.
INFO 2008-11-22 20:52:32
Disconnect from message server (SOLMAN/3900) succeeded.
INFO 2008-11-22 20:52:32
State of instance SOL/DVEBMGS00 changed from ABAP: STARTING, Java: (dispatcher: RUNNING, server0: UNKNOWN) to ABAP: STARTING, Java: (dispatcher: RUNNING, server0: UNKNOWN).
ERROR 2008-11-22 20:52:35
CJS-30151 Java process server0 of instance SOL/DVEBMGS00 [ABAP: ACTIVE, Java: (dispatcher: RUNNING, server0: UNKNOWN)] did not start after 4:00 minutes. Giving up.
ERROR 2008-11-22 20:52:36
FCO-00011 The step startJava with step key |NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CI_Instance|ind|ind|ind|ind|11|0|NW_CI_Instance_StartJava|ind|ind|ind|ind|5|0|startJava was executed with status ERROR .
INFO 2008-11-22 20:54:02
An error occured and the user decided to retry the current step: "|NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CI_Instance|ind|ind|ind|ind|11|0|NW_CI_Instance_StartJava|ind|ind|ind|ind|5|0|startJava".
INFO 2008-11-22 20:54:10
Connect to message server (SOLMAN/3901) succeeded.
INFO 2008-11-22 20:54:10
Disconnect from message server (SOLMAN/3901) succeeded.
INFO 2008-11-22 20:54:10
Connect to message server (SOLMAN/3901) succeeded.
INFO 2008-11-22 20:54:10
Disconnect from message server (SOLMAN/3901) succeeded.
INFO 2008-11-22 20:54:37
Connect to message server (SOLMAN/3900) succeeded.
INFO 2008-11-22 20:54:37
Disconnect from message server (SOLMAN/3900) succeeded.
INFO 2008-11-22 20:54:37
Connect to message server (SOLMAN/3900) succeeded.
INFO 2008-11-22 20:54:37
Disconnect from message server (SOLMAN/3900) succeeded.
INFO 2008-11-22 20:54:45
Connect to message server (SOLMAN/3901) succeeded.
INFO 2008-11-22 20:54:45
Disconnect from message server (SOLMAN/3901) succeeded.
INFO 2008-11-22 20:54:45
Connect to message server (SOLMAN/3901) succeeded.
INFO 2008-11-22 20:54:45
Disconnect from message server (SOLMAN/3901) succeeded.
INFO 2008-11-22 20:54:52
Connect to message server (SOLMAN/3900) succeeded.
INFO 2008-11-22 20:54:52
Disconnect from message server (SOLMAN/3900) succeeded.
INFO 2008-11-22 20:54:52
Connect to message server (SOLMAN/3900) succeeded.
INFO 2008-11-22 20:54:52
Disconnect from message server (SOLMAN/3900) succeeded.
INFO 2008-11-22 20:55:19
RFC parameter CLIENT set to value 001.
INFO 2008-11-22 20:55:20
RFC parameter USER set to value DDIC.
INFO 2008-11-22 20:55:20
RFC parameter LCHECK set to value 1.
INFO 2008-11-22 20:55:20
RFC parameter PCS set to value 1.
INFO 2008-11-22 20:55:20
RFC parameter LANG set to value EN.
INFO 2008-11-22 20:55:20
RFC parameter ASHOST set to value solman.
INFO 2008-11-22 20:55:20
RFC parameter SYSNR set to value 00.
INFO 2008-11-22 20:55:20
RFC connection information checked successfully.
INFO 2008-11-22 20:55:26
RFC connection opened successfully.
INFO 2008-11-22 20:55:26
Setting new application function RFC_SYSTEM_INFO.
INFO 2008-11-22 20:55:26
Generating interface for remote function.
INFO 2008-11-22 20:55:31
Function call was successful.
INFO 2008-11-22 20:55:31
Function interface generated successfully.
INFO 2008-11-22 20:55:31
Technical properties of function set successfully.
INFO 2008-11-22 20:55:31
Information for application function RFC_SYSTEM_INFO copied to local Repository.
INFO 2008-11-22 20:55:31
Function module RFC_SYSTEM_INFO set successfully.
INFO 2008-11-22 20:55:31
Executing function call RFC_SYSTEM_INFO.
INFO 2008-11-22 20:55:31
Function call was successful.
INFO 2008-11-22 20:55:31
Version 700 of remote SAP System SOL accepted.
INFO 2008-11-22 20:55:31
Setting new application function RFC_ABAP_INSTALL_AND_RUN.
INFO 2008-11-22 20:55:31
Generating interface for remote function.
INFO 2008-11-22 20:55:32
Function call was successful.
INFO 2008-11-22 20:55:32
Function interface generated successfully.
INFO 2008-11-22 20:55:32
Technical properties of function set successfully.
INFO 2008-11-22 20:55:32
Information for application function RFC_ABAP_INSTALL_AND_RUN copied to local Repository.
INFO 2008-11-22 20:55:32
Function module RFC_ABAP_INSTALL_AND_RUN set successfully.
INFO 2008-11-22 20:55:32
Executing function call RFC_ABAP_INSTALL_AND_RUN.
INFO 2008-11-22 20:55:37
Function call was successful.
INFO 2008-11-22 20:55:40
Function module RFC_ABAP_INSTALL_AND_RUN set successfully.
INFO 2008-11-22 20:55:40
Executing function call RFC_ABAP_INSTALL_AND_RUN.
INFO 2008-11-22 20:55:41
Function call was successful.
INFO 2008-11-22 20:55:46
Function module RFC_ABAP_INSTALL_AND_RUN set successfully.
INFO 2008-11-22 20:55:46
Executing function call RFC_ABAP_INSTALL_AND_RUN.
INFO 2008-11-22 20:55:46
Function call was successful.
INFO 2008-11-22 20:55:54
Function module RFC_ABAP_INSTALL_AND_RUN set successfully.
INFO 2008-11-22 20:55:54
Executing function call RFC_ABAP_INSTALL_AND_RUN.
INFO 2008-11-22 20:55:54
Function call was successful.
INFO 2008-11-22 20:56:03
Connect to message server (SOLMAN/3901) succeeded.
INFO 2008-11-22 20:56:03
Disconnect from message server (SOLMAN/3901) succeeded.
INFO 2008-11-22 20:56:03
Connect to message server (SOLMAN/3901) succeeded.
INFO 2008-11-22 20:56:03
Disconnect from message server (SOLMAN/3901) succeeded.
INFO 2008-11-22 20:56:21
Connect to message server (SOLMAN/3901) succeeded.
INFO 2008-11-22 20:56:21
Disconnect from message server (SOLMAN/3901) succeeded.
INFO 2008-11-22 20:56:21
Connect to message server (SOLMAN/3901) succeeded.
INFO 2008-11-22 20:56:21
Disconnect from message server (SOLMAN/3901) succeeded.
INFO 2008-11-22 20:56:45
Function module RFC_ABAP_INSTALL_AND_RUN set successfully.
INFO 2008-11-22 20:56:45
Executing function call RFC_ABAP_INSTALL_AND_RUN.
INFO 2008-11-22 20:56:45
Function call was successful.
INFO 2008-11-22 20:56:48
Function module RFC_ABAP_INSTALL_AND_RUN set successfully.
INFO 2008-11-22 20:56:48
Executing function call RFC_ABAP_INSTALL_AND_RUN.
INFO 2008-11-22 20:56:48
Function call was successful.
INFO 2008-11-22 20:56:48
Connect to message server (SOLMAN/3901) succeeded.
INFO 2008-11-22 20:56:48
Disconnect from message server (SOLMAN/3901) succeeded.
INFO 2008-11-22 20:56:48
Connect to message server (SOLMAN/3901) succeeded.
INFO 2008-11-22 20:56:48
Disconnect from message server (SOLMAN/3901) succeeded.
INFO 2008-11-22 20:56:58
Connect to message server (SOLMAN/3900) succeeded.
INFO 2008-11-22 20:56:58
Disconnect from message server (SOLMAN/3900) succeeded.
INFO 2008-11-22 20:56:58
Connect to message server (SOLMAN/3900) succeeded.
INFO 2008-11-22 20:56:58
Disconnect from message server (SOLMAN/3900) succeeded.
INFO 2008-11-22 20:57:07
State of instance SOL/DVEBMGS00 changed from ABAP: UNKNOWN, Java: UNKNOWN to ABAP: UNKNOWN, Java: UNKNOWN.
INFO 2008-11-22 20:57:29
Connect to message server (SOLMAN/3901) succeeded.
INFO 2008-11-22 20:57:29
Disconnect from message server (SOLMAN/3901) succeeded.
INFO 2008-11-22 20:57:29
Connect to message server (SOLMAN/3901) succeeded.
INFO 2008-11-22 20:57:29
Disconnect from message server (SOLMAN/3901) succeeded.
INFO 2008-11-22 20:57:42
Connect to message server (SOLMAN/3900) succeeded.
INFO 2008-11-22 20:57:42
Disconnect from message server (SOLMAN/3900) succeeded.
INFO 2008-11-22 20:57:42
Connect to message server (SOLMAN/3900) succeeded.
INFO 2008-11-22 20:57:42
Disconnect from message server (SOLMAN/3900) succeeded.
INFO 2008-11-22 20:58:13
Connect to message server (SOLMAN/3901) succeeded.
INFO 2008-11-22 20:58:13
Disconnect from message server (SOLMAN/3901) succeeded.
INFO 2008-11-22 20:58:13
Connect to message server (SOLMAN/3901) succeeded.
INFO 2008-11-22 20:58:13
Disconnect from message server (SOLMAN/3901) succeeded.
INFO 2008-11-22 20:58:22
Connect to message server (SOLMAN/3900) succeeded.
INFO 2008-11-22 20:58:22
Disconnect from message server (SOLMAN/3900) succeeded.
INFO 2008-11-22 20:58:22
Connect to message server (SOLMAN/3900) succeeded.
INFO 2008-11-22 20:58:22
Disconnect from message server (SOLMAN/3900) succeeded.
INFO 2008-11-22 20:58:53
Connect to message server (SOLMAN/3901) succeeded.
INFO 2008-11-22 20:58:53
Disconnect from message server (SOLMAN/3901) succeeded.
INFO 2008-11-22 20:58:53
Connect to message server (SOLMAN/3901) succeeded.
INFO 2008-11-22 20:58:53
Disconnect from message server (SOLMAN/3901) succeeded.
INFO 2008-11-22 20:59:29
Connect to message server (SOLMAN/3901) succeeded.
INFO 2008-11-22 20:59:29
Disconnect from message server (SOLMAN/3901) succeeded.
INFO 2008-11-22 20:59:29
Connect to message server (SOLMAN/3901) succeeded.
INFO 2008-11-22 20:59:29
Disconnect from message server (SOLMAN/3901) succeeded.
INFO 2008-11-22 20:59:30
Connect to message server (SOLMAN/3900) succeeded.
INFO 2008-11-22 20:59:30
Disconnect from message server (SOLMAN/3900) succeeded.
INFO 2008-11-22 20:59:30
Connect to message server (SOLMAN/3900) succeeded.
INFO 2008-11-22 20:59:30
Disconnect from message server (SOLMAN/3900) succeeded.
INFO 2008-11-22 20:59:55
State of instance SOL/DVEBMGS00 changed from ABAP: ACTIVE, Java: UNKNOWN to ABAP: ACTIVE, Java: UNKNOWN.
INFO 2008-11-22 21:00:13
Connect to message server (SOLMAN/3901) succeeded.
INFO 2008-11-22 21:00:13
Disconnect from message server (SOLMAN/3901) succeeded.
INFO 2008-11-22 21:00:13
Connect to message server (SOLMAN/3901) succeeded.
INFO 2008-11-22 21:00:13
Disconnect from message server (SOLMAN/3901) succeeded.
INFO 2008-11-22 21:00:28
Connect to message server (SOLMAN/3901) succeeded.
INFO 2008-11-22 21:00:28
Disconnect from message server (SOLMAN/3901) succeeded.
INFO 2008-11-22 21:00:28
Connect to message server (SOLMAN/3901) succeeded.
INFO 2008-11-22 21:00:28
Disconnect from message server (SOLMAN/3901) succeeded.
INFO 2008-11-22 21:00:29
Connect to message server (SOLMAN/3900) succeeded.
INFO 2008-11-22 21:00:29
Disconnect from message server (SOLMAN/3900) succeeded.
INFO 2008-11-22 21:00:29
Connect to message server (SOLMAN/3900) succeeded.
INFO 2008-11-22 21:00:29
Disconnect from message server (SOLMAN/3900) succeeded.
INFO 2008-11-22 21:00:39
State of instance SOL/DVEBMGS00 changed from ABAP: ACTIVE, Java: (dispatcher: STARTING, server0: UNKNOWN) to ABAP: ACTIVE, Java: (dispatcher: STARTING, server0: UNKNOWN).
INFO 2008-11-22 21:01:06
Connect to message server (SOLMAN/3901) succeeded.
INFO 2008-11-22 21:01:06
Disconnect from message server (SOLMAN/3901) succeeded.
INFO 2008-11-22 21:01:06
Connect to message server (SOLMAN/3901) succeeded.
INFO 2008-11-22 21:01:06
Disconnect from message server (SOLMAN/3901) succeeded.
INFO 2008-11-22 21:01:50
Connect to message server (SOLMAN/3901) succeeded.
INFO 2008-11-22 21:01:50
Disconnect from message server (SOLMAN/3901) succeeded.
INFO 2008-11-22 21:01:50
Connect to message server (SOLMAN/3901) succeeded.
INFO 2008-11-22 21:01:50
Disconnect from message server (SOLMAN/3901) succeeded.
INFO 2008-11-22 21:01:50
Connect to message server (SOLMAN/3900) succeeded.
INFO 2008-11-22 21:01:50
Disconnect from message server (SOLMAN/3900) succeeded.
INFO 2008-11-22 21:01:50
Connect to message server (SOLMAN/3900) succeeded.
INFO 2008-11-22 21:01:50
Disconnect from message server (SOLMAN/3900) succeeded.
ERROR 2008-11-22 21:01:57
CJS-30151 Java process server0 of instance SOL/DVEBMGS00 [ABAP: ACTIVE, Java: (dispatcher: RUNNING, server0: UNKNOWN)] did not start after 4:00 minutes. Giving up.
ERROR 2008-11-22 21:01:57
FCO-00011 The step startJava with step key |NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CI_Instance|ind|ind|ind|ind|11|0|NW_CI_Instance_StartJava|ind|ind|ind|ind|5|0|startJava was executed with status ERROR .
INFO 2008-11-22 21:02:06
An error occured and the user decided to retry the current step: "|NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CI_Instance|ind|ind|ind|ind|11|0|NW_CI_Instance_StartJava|ind|ind|ind|ind|5|0|startJava".
INFO 2008-11-22 21:02:07
Connect to message server (SOLMAN/3901) succeeded.
INFO 2008-11-22 21:02:07
Disconnect from message server (SOLMAN/3901) succeeded.
INFO 2008-11-22 21:02:07
Connect to message server (SOLMAN/3901) succeeded.
INFO 2008-11-22 21:02:07
Disconnect from message server (SOLMAN/3901) succeeded.
INFO 2008-11-22 21:02:34
Connect to message server (SOLMAN/3900) succeeded.
INFO 2008-11-22 21:02:34
Disconnect from message server (SOLMAN/3900) succeeded.
INFO 2008-11-22 21:02:34
Connect to message server (SOLMAN/3900) succeeded.
INFO 2008-11-22 21:02:34
Disconnect from message server (SOLMAN/3900) succeeded.
INFO 2008-11-22 21:02:54
Connect to message server (SOLMAN/3901) succeeded.
INFO 2008-11-22 21:02:54
Disconnect from message server (SOLMAN/3901) succeeded.
INFO 2008-11-22 21:02:54
Connect to message server (SOLMAN/3901) succeeded.
INFO 2008-11-22 21:02:54
Disconnect from message server (SOLMAN/3901) succeeded.
INFO 2008-11-22 21:03:18
Connect to message server (SOLMAN/3900) succeeded.
INFO 2008-11-22 21:03:18
Disconnect from message server (SOLMAN/3900) succeeded.
INFO 2008-11-22 21:03:18
Connect to message server (SOLMAN/3900) succeeded.
INFO 2008-11-22 21:03:18
Disconnect from message server (SOLMAN/3900) succeeded.
INFO 2008-11-22 21:03:29
Function module RFC_ABAP_INSTALL_AND_RUN set successfully.
INFO 2008-11-22 21:03:29
Executing function call RFC_ABAP_INSTALL_AND_RUN.
INFO 2008-11-22 21:03:30
Function call was successful.
INFO 2008-11-22 21:03:43
Function module RFC_ABAP_INSTALL_AND_RUN set successfully.
INFO 2008-11-22 21:03:43
Executing function call RFC_ABAP_INSTALL_AND_RUN.
INFO 2008-11-22 21:03:43
Function call was successful.
INFO 2008-11-22 21:03:56
Function module RFC_ABAP_INSTALL_AND_RUN set successfully.
INFO 2008-11-22 21:03:56
Executing function call RFC_ABAP_INSTALL_AND_RUN.
INFO 2008-11-22 21:03:56
Function call was successful.
INFO 2008-11-22 21:04:14
Function module RFC_ABAP_INSTALL_AND_RUN set successfully.
INFO 2008-11-22 21:04:15
Executing function call RFC_ABAP_INSTALL_AND_RUN.
INFO 2008-11-22 21:04:15
Function call was successful.
INFO 2008-11-22 21:04:40
Connect to message server (SOLMAN/3901) succeeded.
INFO 2008-11-22 21:04:40
Disconnect from message server (SOLMAN/3901) succeeded.
INFO 2008-11-22 21:04:40
Connect to message server (SOLMAN/3901) succeeded.
INFO 2008-11-22 21:04:40
Disconnect from message server (SOLMAN/3901) succeeded.
INFO 2008-11-22 21:04:52
Function module RFC_ABAP_INSTALL_AND_RUN set successfully.
INFO 2008-11-22 21:04:52
Executing function call RFC_ABAP_INSTALL_AND_RUN.
INFO 2008-11-22 21:04:52
Function call was successful.
INFO 2008-11-22 21:05:06
Function module RFC_ABAP_INSTALL_AND_RUN set successfully.
INFO 2008-11-22 21:05:06
Executing function call RFC_ABAP_INSTALL_AND_RUN.
INFO 2008-11-22 21:05:07
Function call was successful.
INFO 2008-11-22 21:05:07
Connect to message server (SOLMAN/3901) succeeded.
INFO 2008-11-22 21:05:07
Disconnect from message server (SOLMAN/3901) succeeded.
INFO 2008-11-22 21:05:07
Connect to message server (SOLMAN/3901) succeeded.
INFO 2008-11-22 21:05:07
Disconnect from message server (SOLMAN/3901) succeeded.
INFO 2008-11-22 21:05:21
Connect to message server (SOLMAN/3900) succeeded.
INFO 2008-11-22 21:05:21
Disconnect from message server (SOLMAN/3900) succeeded.
INFO 2008-11-22 21:05:21
Connect to message server (SOLMAN/3900) succeeded.
INFO 2008-11-22 21:05:21
Disconnect from message server (SOLMAN/3900) succeeded.
INFO 2008-11-22 21:05:42
State of instance SOL/DVEBMGS00 changed from ABAP: UNKNOWN, Java: UNKNOWN to ABAP: UNKNOWN, Java: UNKNOWN.
INFO 2008-11-22 21:05:55
Connect to message server (SOLMAN/3901) succeeded.
INFO 2008-11-22 21:05:55
Disconnect from message server (SOLMAN/3901) succeeded.
INFO 2008-11-22 21:05:55
Connect to message server (SOLMAN/3901) succeeded.
INFO 2008-11-22 21:05:55
Disconnect from message server (SOLMAN/3901) succeeded.
INFO 2008-11-22 21:06:21
Connect to message server (SOLMAN/3900) succeeded.
INFO 2008-11-22 21:06:21
Disconnect from message server (SOLMAN/3900) succeeded.
INFO 2008-11-22 21:06:21
Connect to message server (SOLMAN/3900) succeeded.
INFO 2008-11-22 21:06:21
Disconnect from message server (SOLMAN/3900) succeeded.
INFO 2008-11-22 21:06:57
Connect to message server (SOLMAN/3901) succeeded.
INFO 2008-11-22 21:06:57
Disconnect from message server (SOLMAN/3901) succeeded.
INFO 2008-11-22 21:06:57
Connect to message server (SOLMAN/3901) succeeded.
INFO 2008-11-22 21:06:57
Disconnect from message server (SOLMAN/3901) succeeded.
INFO 2008-11-22 21:07:24
Connect to message server (SOLMAN/3901) succeeded.
INFO 2008-11-22 21:07:24
Disconnect from message server (SOLMAN/3901) succeeded.
INFO 2008-11-22 21:07:24
Connect to message server (SOLMAN/3901) succeeded.
INFO 2008-11-22 21:07:24
Disconnect from message server (SOLMAN/3901) succeeded.
INFO 2008-11-22 21:07:24
Connect to message server (SOLMAN/3900) succeeded.
INFO 2008-11-22 21:07:24
Disconnect from message server (SOLMAN/3900) succeeded.
INFO 2008-11-22 21:07:24
Connect to message server (SOLMAN/3900) succeeded.
INFO 2008-11-22 21:07:24
Disconnect from message server (SOLMAN/3900) succeeded.
INFO 2008-11-22 21:07:48
State of instance SOL/DVEBMGS00 changed from ABAP: ACTIVE, Java: UNKNOWN to ABAP: ACTIVE, Java: UNKNOWN.
INFO 2008-11-22 21:08:11
Connect to message server (SOLMAN/3901) succeeded.
INFO 2008-11-22 21:08:11
Disconnect from message server (SOLMAN/3901) succeeded.
INFO 2008-11-22 21:08:11
Connect to message server (SOLMAN/3901) succeeded.
INFO 2008-11-22 21:08:11
Disconnect from message server (SOLMAN/3901) succeeded.
INFO 2008-11-22 21:08:50
Connect to message server (SOLMAN/3901) succeeded.
INFO 2008-11-22 21:08:50
Disconnect from message server (SOLMAN/3901) succeeded.
INFO 2008-11-22 21:08:50
Connect to message server (SOLMAN/3901) succeeded.
INFO 2008-11-22 21:08:50
Disconnect from message server (SOLMAN/3901) succeeded.
INFO 2008-11-22 21:08:50
Connect to message server (SOLMAN/3900) succeeded.
INFO 2008-11-22 21:08:50
Disconnect from message server (SOLMAN/3900) succeeded.
INFO 2008-11-22 21:08:50
Connect to message server (SOLMAN/3900) succeeded.
INFO 2008-11-22 21:08:50
Disconnect from message server (SOLMAN/3900) succeeded.
INFO 2008-11-22 21:08:55
State of instance SOL/DVEBMGS00 changed from ABAP: ACTIVE, Java: (dispatcher: STARTING, server0: UNKNOWN) to ABAP: ACTIVE, Java: (dispatcher: STARTING, server0: UNKNOWN).
INFO 2008-11-22 21:09:03
Connect to message server (SOLMAN/3901) succeeded.
INFO 2008-11-22 21:09:03
Disconnect from message server (SOLMAN/3901) succeeded.
INFO 2008-11-22 21:09:03
Connect to message server (SOLMAN/3901) succeeded.
INFO 2008-11-22 21:09:03
Disconnect from message server (SOLMAN/3901) succeeded.
INFO 2008-11-22 21:09:48
Connect to message server (SOLMAN/3901) succeeded.
INFO 2008-11-22 21:09:48
Disconnect from message server (SOLMAN/3901) succeeded.
INFO 2008-11-22 21:09:48
Connect to message server (SOLMAN/3901) succeeded.
INFO 2008-11-22 21:09:48
Disconnect from message server (SOLMAN/3901) succeeded.
INFO 2008-11-22 21:09:49
Connect to message server (SOLMAN/3900) succeeded.
INFO 2008-11-22 21:09:49
Disconnect from message server (SOLMAN/3900) succeeded.
INFO 2008-11-22 21:09:49
Connect to message server (SOLMAN/3900) succeeded.
INFO 2008-11-22 21:09:49
Disconnect from message server (SOLMAN/3900) succeeded.
ERROR 2008-11-22 21:10:08
CJS-30151 Java process server0 of instance SOL/DVEBMGS00 [ABAP: ACTIVE, Java: (dispatcher: RUNNING, server0: UNKNOWN)] did not start after 4:00 minutes. Giving up.
ERROR 2008-11-22 21:10:08
FCO-00011 The step startJava with step key |NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CI_Instance|ind|ind|ind|ind|11|0|NW_CI_Instance_StartJava|ind|ind|ind|ind|5|0|startJava was executed with status ERROR .
sapinst_dev.log
TRACE [iaxxejsexp.cpp:199]
 EJS_Installer::writeTraceToLogBook()
2008-11-22 21:10:08.531 NWDIState._assertJavaProcessStateProgress() done
TRACE [iaxxejsexp.cpp:199]
 EJS_Installer::writeTraceToLogBook()
2008-11-22 21:10:08.546 NWDIState._assertJavaProcessStatesProgress() done
TRACE [iaxxejsexp.cpp:199]
 EJS_Installer::writeTraceToLogBook()
2008-11-22 21:10:08.546 NWDIState.unbalancedStates()
TRACE [iaxxejsexp.cpp:199]
 EJS_Installer::writeTraceToLogBook()
2008-11-22 21:10:08.546 NWInstState.getElapsedString()
TRACE [iaxxejsexp.cpp:199]
 EJS_Installer::writeTraceToLogBook()
2008-11-22 21:10:08.546 NWInstState.getElapsedString() done: 4:00
TRACE [iaxxejsexp.cpp:199]
 EJS_Installer::writeTraceToLogBook()
2008-11-22 21:10:08.546 NWDIState.unbalancedStates() done: nw.progress.waitingForStartJavaFailed2SOLDVEBMGS00ABAP: ACTIVE, Java: (dispatcher: RUNNING, server0: UNKNOWN)4:00server0
TRACE [iaxxejsexp.cpp:199]
 EJS_Installer::writeTraceToLogBook()
2008-11-22 21:10:08.546 NWDIState.unbalancedStates()
TRACE [iaxxejsexp.cpp:199]
 EJS_Installer::writeTraceToLogBook()
2008-11-22 21:10:08.546 NWInstState.getElapsedString()
TRACE [iaxxejsexp.cpp:199]
 EJS_Installer::writeTraceToLogBook()
2008-11-22 21:10:08.562 NWInstState.getElapsedString() done: 3:00
TRACE [iaxxejsexp.cpp:199]
 EJS_Installer::writeTraceToLogBook()
2008-11-22 21:10:08.562 NWDIState.unbalancedStates() done: nw.progress.waitingForStartJavaFailed2SOLDVEBMGS00ABAP: ACTIVE, Java: (dispatcher: RUNNING, server0: UNKNOWN)3:00server0
TRACE [iaxxejsexp.cpp:199]
 EJS_Installer::writeTraceToLogBook()
NWException thrown: nw.progress.waitingForStartJavaFailed2:
Java process server0 of instance SOL/DVEBMGS00 [ABAP: ACTIVE, Java: (dispatcher: RUNNING, server0: UNKNOWN)] did not start after 4:00 minutes. Giving up.
ERROR 2008-11-22 21:10:08
 CJSlibModule::writeError_impl()
CJS-30151 Java process server0 of instance SOL/DVEBMGS00 [ABAP: ACTIVE, Java: (dispatcher: RUNNING, server0: UNKNOWN)] did not start after 4:00 minutes. Giving up.
TRACE [iaxxejsbas.hpp:460]
 EJS_Base::dispatchFunctionCall()
JS Callback has thrown unknown exception. Rethrowing.
ERROR 2008-11-22 21:10:08 [iaxxgenimp.cpp:731]
 showDialog()
FCO-00011 The step startJava with step key |NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CI_Instance|ind|ind|ind|ind|11|0|NW_CI_Instance_StartJava|ind|ind|ind|ind|5|0|startJava was executed with status ERROR .
TRACE [iaxxgenimp.cpp:719]
 showDialog()
<html><head></head><body>An error occurred while processing service SAP Solution Manager 4.0 Support Release 2 > SAP Systems > MaxDB > Central System > Central System Installation. You may now<ul> <li>press Retry to repeat the current step.</li> <li>press the View Log button to get more information about the error.</li> <li>stop the task and continue with it later.</li></ul>Log files are written to C:\Program Files/sapinst_instdir/SOLMAN/SYSTEM/ADA/CENTRAL/AS.</body></html>
TRACE [iaxxgenimp.cpp:1155]
 showDialog()
waiting for an answer from gui
INFO 2008-11-22 23:01:26 [iaxxgenimp.cpp:782]
 showDialog()
An error occured and the user decide to stop.\n Current step "|NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CI_Instance|ind|ind|ind|ind|11|0|NW_CI_Instance_StartJava|ind|ind|ind|ind|5|0|startJava".
start_SOL_DVEMGS00.log
STARTSAP failed
Details are written to C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\ADA\CENTRAL\AS\startSOL.log
startSOL.log
running C:\usr\sap\SOL\SYS\exe\uc\NTI386\sapstart.exe name=SOL nr=00 SAPDIAHOST=SOLMAN -wait
SAPSTART finished successfully on SOLMAN_SOL_00, but at least one process doesn't run correctly:
C:\usr\sap\SOL\SYS\exe\uc\NTI386\sapstart.exe=>sapparam(1c): No Profile used.
somebody can helpme??
thanks

I had overcome the problem with the version of java, but now when we reach the phase 40
drops the installation and try to resume, presents the following problem:
sapint.15.log
INFO 2008-12-04 16:42:17
Function interface generated successfully.
INFO 2008-12-04 16:42:17
Technical properties of function set successfully.
INFO 2008-12-04 16:42:17
Information for application function BAPI_SLD_SUPPLIER_CONFIG_SET copied to local Repository.
INFO 2008-12-04 16:42:17
Function module BAPI_SLD_SUPPLIER_CONFIG_SET set successfully.
INFO 2008-12-04 16:42:17
Executing function call BAPI_SLD_SUPPLIER_CONFIG_SET.
INFO 2008-12-04 16:42:28
Function call was successful.
INFO 2008-12-04 16:42:28
RFC connection closed.
ERROR 2008-12-04 16:42:29
FKD-00070 Error when opening table container file C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS\keydb.xml for writing. Possible reason: "read-only"
sapinst.log
ERROR 2008-12-05 11:35:20
FKD-00049 XML - Parser error: error: no DTD specified, can't validate in line 1, 1
in file C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS\keydb.xml
sapinst_dev.log
TRACE
Running with toplevel file C:\Program Files/sapinst_instdir/SOLMAN/SYSTEM/MSS/CENTRAL/AS/toplevel.xml
TRACE
Running with dialog file C:\Program Files/sapinst_instdir/SOLMAN/SYSTEM/MSS/CENTRAL/AS/dialog.xml
TRACE
Running with keydb file C:\Program Files/sapinst_instdir/SOLMAN/SYSTEM/MSS/CENTRAL/AS/keydb.xml
ERROR 2008-12-05 11:35:20 [kdxxctaco.cpp:872]
 CKdbTableContainerImpl::buildUpKeydbFromXmlFile(iastring,PKdbNameSpaceManager,iXMLDocument&)
FKD-00049 XML - Parser error: error: no DTD specified, can't validate in line 1, 1
in file C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS\keydb.xml

Error when opening table container file keydb read only

Hi Guys,
We are installing solution manager 4.0 on windows/sql but we are getting following error and couldnt continue the installation
FKD-00070 Error when opening table container file C:\PROGRA1\SAPINS1\SOLMAN\SYSTEM\MSS\CENTRAL\AS\keydb.xml for writing. Possible reason: "read-only"
ERROR 2008-06-04 20:10:56.843
FKD-00049 XML - Parser error: error: no DTD specified, can't validate in line 1, 1
in file C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS\keydb.xml.
Please help
Regards,
Santosh

Further info
keydb.xml is empty and the directory has got write access for everyone
regards
Edited by: Santosh Keerti on Jun 4, 2008 1:29 PM

ECC 6.0 Installation error not starting "Continue old option"

Hi Gurus,
I am instating ecc 6 in my system it is giving a error like.. bellow...
INFO       2012-08-18 19:44:01.640 [synxcfile.cpp:493]
           CSyFileImpl::copy(const CSyPath & C:/Program Files/sapinst_instdir/ERP/SYSTEM/MSS/CENTRAL/AS/statistic.47.xml, ISyNode::CopyMoveMode_t 0x3, ISyProgressObserver*) const
Copied file 'C:/Program Files/sapinst_instdir/ERP/SYSTEM/MSS/CENTRAL/AS/statistic.xml' to 'C:/Program Files/sapinst_instdir/ERP/SYSTEM/MSS/CENTRAL/AS/statistic.47.xml'.
ERROR      2012-08-18 19:44:05.125 [kdxxctaco.cpp:891]
           lib=iakdblib
FKD-00049 XML parser error: error: no DTD specified, can't validate in line 2, 2
in file C:/Program Files/sapinst_instdir/ERP/SYSTEM/MSS/CENTRAL/AS/statistic.xml.
please help me out
Regards
Krishna

Read,
regarding FKD-0049 XML Parser Error
That should solve the problem
Regards
Juan

ANN: XML Parser for Java v2.0.2.6

The v2.0.2.6 of the XML Parser for Java is now available for download. The following features and bug fixes are included:
Changes:
Conformance to the XSLT/XPATH October REC.
New API in XSLStylesheet class:
removeParam(String param)
resetParams()
Bug fixes:
Bug #1111423: OutOfMemory exception, if multiple calls made to document()
Bug #1101028: Unexpected character error in DTD parsing document using Docbook DTD
Bug #1101021: #default not supported in exclude-result-prefixes
Bug #1099830: Extra characters inserted into output using the XML Parser
Bug #1099663: HTML output does not allow only doctype-public to be specified
Bug #1099536: HTML output does not disable escaping for script, style unless lowercase
Bug #1098738: ArrayOutOfBoundsException xsl:if test="not(@a)'"
Bug #1095047: XSLProcessor NPE'S on named templates with non-empty namespaces
Bug #1094971: XSLStylesheet needs methods for removing parameters
Bug #1092351: Using valueof() shuffles order of elements in my source document
Bug #1086663: xsl:sort data-type attribute can now be a namespace-prefixed name
Bug #1086661: xsl:version attribute now required on literal result element
Bug #1064692: Default xml-serialization should use empty-element syntax
Bug #1064689: Current() function doesn't work correctly
This is the sixth production patch release for v2.
Oracle XML Team http://technet.oracle.com
Oracle Technology Network
null

The link has been fixed. You will go to the v2 download page
now. Sorry for the inconvience.
Oracle XML Team
http://technet.oracle.com
Oracle Technology Network
Renilton Oliveira (guest) wrote:
: I didn't find the file for version 2.0.0.0 as well.
: Renilton
: Andrei Filimonov (guest) wrote:
: : I tried to download XML Parser for Java v2 it seems that
only
: v
: : 1.0.1.4 is available. Could you please give an exact URL for
: v2
: : download?
: : Andrei Filimonov
: : Oracle XML Team wrote:
: : : The Oracle XML v2 parser is now available for download
here
: as
: : : an early beta release and is written in Java. It features
: an
: : : improved architecture over the Oracle XML v1 parser and
has
: : : shown better performance on small to large XML documents.
: It
: : : will also be able to format the XML document according to
a
: : : stylesheet, having integrated an XSLT processor.
: : : Version 2 of the XML Parser for Java, besides
incorporating
: an
: : : XSLT processor, has been re-architected from version 1.
This
: : has
: : : resulted in a number of changes to the class names
: especially
: : : those that support Namespaces. See v2changes.txt and
: the .diff
: : : difference files in the sample directory.
: : : Oracle XML Team
: : : http://technet.oracle.com
: : : Oracle Technology Network
null

Problem Installing Sol Man 4.0 /Windows/SQL Server 2000

Hi,
Ran into the following problem when installing, any ideas:
SAPinst is getting started.
Please be patient ...
starting gui server process:
sapinstport: 21200
guiport    : 21212
guistart   : true
command    : "C:\Program Files\Java\jre1.5.0_06/bin\javaw.exe" -cp "C:/DOCUME1/ADMINI1/LOCALS1/Temp/2/sapinst_exe.4268.1158783242\jar\instgui.jar;C:/DOCUME1/ADMINI1/LOCALS1/Temp/2/sapinst_exe.4268.1158783242\jar\inqmyxml.jar" -Xmx256M -Dsun.java2d.noddraw=true SDTServer config=jar:sdtserver.xml guiport=21212 sapinsthost=localhost sapinstport=21200 guistart=true
load resource pool J:\IM_WINDOWS_I386\resourcepool.xml
guiengine: no GUI connected; waiting for a connection on host SCLO027, port 21200 to continue with the installation
guiengine: login in process.
IRunModeReceiver CChoiceDialogModifier::continuePreviousRun()
ERROR      2006-09-20 13:14:44 [kdxxctaco.cpp:872]
           CKdbTableContainerImpl::buildUpKeydbFromXmlFile(iastring,PKdbNameSpaceManager,iXMLDocument&)
FKD-00049 XML - Parser error: error: no DTD specified, can't validate in line 1, 1
in file C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS\keydb.xml
Exit status of child: 1
Thanks,
Bob

I have solved this problem :
1. Rename the keydb.xml. For exmaple rename to keydb.xml_bak.
2. You can see the keydb.1.xml, keydb.2.xml, keydb.3.xml, keydb.4.xml, etc. in the same folder.
3. You choose the biggest or latest .xml file. For example, you choose the keydb.3.xml.
4. The choosen file, keydb.3.xml, rename keydb.xml
5. You can reinstall.
Take care of yourself.
Se Hoon, Jin
Seoul, Korea

Use of Filter by in P6.2 Web Causes Auto Logoff

When I select any of the filter by icons the filter window opens but never populates with the filter selections. Then when I close the window and try to select the filter again, the application performs an automatic logout and returns me to the signin screen. I am currently running Java 6 Update 15 and I found the following in the Java log:
Reading certificates from 11 http://pmwebaccess.rmtc.fedex.com:8001/primaveraweb/applets/prm-common.jar | C:\Documents and Settings\116242\Application Data\Sun\Java\Deployment\cache\6.0\47\7986022f-6ea630c4.idx
[Fatal Error] loose.dtd:31:3: The declaration for the entity "HTML.Version" must end with '>'.
The declaration for the entity "HTML.Version" must end with '>'.
org.xml.sax.SAXParseException: The declaration for the entity "HTML.Version" must end with '>'.
     at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(Unknown Source)
     at com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source)
     at com.primavera.pvapplets.tree.JTreeXMLInputOutput.xmlParser(Unknown Source)
     at com.primavera.pvapplets.tree.JTreeControl.makeRequest(Unknown Source)
     at com.primavera.pvapplets.tree.JTreeControl.getNodesAndInsert(Unknown Source)
     at com.primavera.pvapplets.tree.JTreeControl.a(Unknown Source)
     at com.primavera.pvapplets.tree.JTreeControl$InsertThread.run(Unknown Source)
     at java.awt.event.InvocationEvent.dispatch(Unknown Source)
     at java.awt.EventQueue.dispatchEvent(Unknown Source)
     at java.awt.EventDispatchThread.pumpOneEventForFilters(Unknown Source)
     at java.awt.EventDispatchThread.pumpEventsForFilter(Unknown Source)
     at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source)
     at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
     at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
     at java.awt.EventDispatchThread.run(Unknown Source)
Any suggestions?

This has been fixed. I updated to the latest version of Java (Version 6 Update 17 (build 1.6.0_17-b04)) & cleared my browser history (temporary files, history, cookies, saved passwords and web form information). I did not have to reboot. Apparently, Java version 6 update 15 had some sort of conflict with P6 Web.

Regex: qualifying by not matching a pattern

I have this pattern:
(.[^(?<=d)(?=d)t].*error.*|.{0,2}error.*)and these Strings to match:
1 "dtd validation error"
2 "dtd error"
3 "error"
4 "foobar error"
5 "dt derror"The pattern fails to match #1 and #2, which is good. It succeeds in matching #3 and #4, which is also good. However, it fails to match #5, which is not what I expected.
According to me, the second half of the pattern means find 0, 1 or 2 chars of any type, followed by the word 'error', followed by 0 or more chars of any type. I don't expect #5 to be matched by this one, so that's okay.
However, the first half of the pattern seems to say find one char of any type, followed by a char that is not 't' if prefixed and suffixed with 'd', followed by 0 or more chars of any type, followed by the word 'error', followed by 0 or more chars of any type.
The 't' in #5 is prefixed with a 'd' alright, but it obviously isn't suffixed with a 'd' (as I see it, it's suffixed with a whitespace). How come that the first half of the pattern seems to recognize that it is? Or is there another problem with my expression?

Why not create the opposite pattern? It's easier..
 String pattern = ".*dtd.*error.*";
 String t1 = "dtd validation error";
 String t2 = "dtd error";
 String t3 = "error";
 String t4 = "foobar error";
 String t5 = "dt derror";
 System.out.println(!Pattern.matches(pattern, t1));
 System.out.println(!Pattern.matches(pattern, t2));
 System.out.println(!Pattern.matches(pattern, t3));
 System.out.println(!Pattern.matches(pattern, t4));
 System.out.println(!Pattern.matches(pattern, t5));/Kaj

Multiline Data needs to show in seperate records

Dear Friend
I have a data which is stored in a field of a table. That data is multilined data.
I want to use a select statement, which will return all the data in seperate records.
because I may use any individual record from that Multilined data.
Can anyone help me fetch in my required way..................
in the below in bold i am sending the sample data of Multilined data
rgds
Mithun
V.0.1 * 28.01.1999 * PS * init
V.0.2 * 04.02.2000 * PS * changes: follow suggestions made by GL,JR,MSK
V.1.0 * 08.02.2000 * PS * correct some errors, checked DTD with produced output
                    from AE2XML
V.1.1 * 10.02.2000 * PS * Tracking events
V.1.2 * 01.03.2000 * PS * Added Sea, Dgs, Eqd
V.1.3 * 22.09.2000 * PS * added freight on shipment level; added optional internal RSI fields
* for carrier: ShortName, Prefix, IsMemberOfIata
V.1.3.1 * 26.09.2000 * PS * added SendersRole (export,import,agent,...)
V.1.3.2 * 26.09.2000 * PS * TDT: Air/Sea optional e.g. for bookings

SQL> drop table t;
Table dropped.
SQL> create table t
2 (txt varchar2(4000));
Table created.
SQL> insert into t
2 values('V.0.1 * 28.01.1999 * PS * init)
3 V.0.2 * 04.02.2000 * PS * changes: follow suggestions made by GL,JR,MSK
4 V.1.0 * 08.02.2000 * PS * correct some errors, checked DTD with produced output
5 from AE2XML
6 V.1.1 * 10.02.2000 * PS * Tracking events
7 V.1.2 * 01.03.2000 * PS * Added Sea, Dgs, Eqd
8 V.1.3 * 22.09.2000 * PS * added freight on shipment level; added optional internal RSI fields
9 * for carrier: ShortName, Prefix, IsMemberOfIata
10 V.1.3.1 * 26.09.2000 * PS * added SendersRole (export,import,agent,...)
11 V.1.3.2 * 26.09.2000 * PS * TDT: Air/Sea optional e.g. for bookings
12 ');
1 row created.
SQL> commit;
Commit complete.
SQL> create or replace type TStrings as table of varchar2(4000);
2 /
Type created.
SQL> create or replace function SamplePipe return TStrings pipelined is
2
3   vc1 varchar2(4000);
4   n number;
5 begin
6    for rec in (select txt from t) loop
7     n := length(rec.txt)-length(replace(rec.txt,chr(10)));
8     for i in 1..n loop
9      pipe row(substr(rec.txt||chr(10),instr(rec.txt||chr(10),chr(10),1,i),
10             instr(rec.txt||chr(10),chr(10),1,i+1)-instr(rec.txt||chr(10),chr(10),1,i)));
11     end loop;
12   end loop;
13   return;
14 end;
15 /
Function created.
SQL> show errors
No errors.
SQL> select * from table(samplepipe);
COLUMN_VALUE
V.0.2 * 04.02.2000 * PS * changes: follow suggestions made by GL,JR,MSK
V.1.0 * 08.02.2000 * PS * correct some errors, checked DTD with produced output
from AE2XML
V.1.1 * 10.02.2000 * PS * Tracking events
COLUMN_VALUE
V.1.2 * 01.03.2000 * PS * Added Sea, Dgs, Eqd
V.1.3 * 22.09.2000 * PS * added freight on shipment level; added optional intern
al RSI fields
* for carrier: ShortName, Prefix, IsMemberOfIata
COLUMN_VALUE
V.1.3.1 * 26.09.2000 * PS * added SendersRole (export,import,agent,...)
V.1.3.2 * 26.09.2000 * PS * TDT: Air/Sea optional e.g. for bookings
10 rows selected.
Message was edited by:
        jeneesh
If this give you any idea, thanks to Billy...

Dtd-is-prohibited-error-when-accessing-sharepoint-2013-office365-list-but-not

I need to update some items in a list and previously done it through a console app and using the sharepoint.client.dll but for some reason it no longer works.
When I call the clientContext.ExecuteQuery() it throws this error:-
"For security reasons DTD is prohibited in this XML document. To enable DTD processing set the DtdProcessing property on XmlReaderSettings to Parse and pass the settings into XmlReader.Create method."
I have googled this and seen others have had similar problems but changing DNS has not resolved this which did in their case.
I can probably create a sharepoint-hosted app to do it but just takes longer for such a simple update.
I have checked fiddler and can see it is requesting the FPUrl.xml and returning a 302 response.
GET http://msoid.thesportsoffice.com/FPUrl.xml HTTP/1.1
Host: msoid.thesportsoffice.com
HTTP/1.1 302 Found
Cache-Control: private
Content-Type: text/html; charset=utf-8
Location: /
Server: Microsoft-IIS/8.5
X-AspNetMvc-Version: 4.0
X-AspNet-Version: 4.0.30319
X-Powered-By: ASP.NET
Date: Fri, 26 Sep 2014 14:43:36 GMT
Content-Length: 118
Any ideas why this is starting to happen?
Karl Diggle

Hi D00gle,
DTD means document type declaration. Using DTD entity expansion, it is easy to make a very small XML data stream fully expand into a very large document.
It will run parser without source limit, so the system will tell you the data has a security issue.
To fix the issue, you can set like below in your code:
XmlReaderSettings settings = new XmlReaderSettings();
settings.ProhibitDtd = false;
Here is a thread about this issue for your reference:
http://stackoverflow.com/questions/13854068/dtd-prohibited-in-xml-document-exception
Feel free to reply if you still have any questions about this.
Best Regards
TechNet Community Support
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact
[email protected]
Zhengyu Guo
TechNet Community Support

"DTD is prohibited" error when accessing sharepoint 2013/office365 list (but not openly aware of using XML)

I've been getting a list of folders and files from Sharepoint (on Office 365) by using the following C# code...
var folders = ListFolders(libraryName, clientContext, web);
public List<Folder> ListFolders(string libraryName, ClientContext clientContext, Web web)
var list = GetDocumentLibrary(libraryName, clientContext, web);
var folders = list.RootFolder.Folders;
clientContext.Load(folders);
clientContext.ExecuteQuery();
return folders.ToList();
public List GetDocumentLibrary(string libraryName, ClientContext clientContext, Web web)
var query = clientContext.LoadQuery(web.Lists.Where(p => p.Title == libraryName));
clientContext.ExecuteQuery();
return query.FirstOrDefault();
It was working fine until I rebooted my computer (it installed a Windows Update), I strongly suspect, based on some testing I've done, it is caused by http://support.microsoft.com/kb/2964358
When the *clientContext.ExecuteQuery()* statement is reached in *GetDocumentLibrary()*, the
following exception is thrown.
*An unhandled exception of type 'System.Xml.XmlException' occurred in System.Xml.dll
Additional information: For security reasons DTD is prohibited in this XML document. To enable DTD processing set the DtdProcessing property on XmlReaderSettings to Parse and pass the settings into XmlReader.Create method.*
I'm wondering how I can work around this, as I'm not consciously using System.XML, it's a background function or process when the ExecuteQuery runs.
Can I pass some additional XMLReader info to this or clientContext (I'm assuming not), so I'm not sure how to execute this query to prevent the DTD error. I have also tried accessing the list in a different manner, by using this code... (from Microsoft's MSDN
pages)
List list = clientContext.Web.Lists.GetByTitle(libraryName);CamlQuery camlQuery = new CamlQuery(); camlQuery.ViewXml = "<View/>";ListItemCollection listItems = list.GetItems(camlQuery);clientContext.Load(list); clientContext.Load(listItems);clientContext.ExecuteQuery();
This works on a computer without the KB above, however on my PC it doesn't (I get the same exception as my other code) , obviously uninstalling the KB will make things work in the short term, but its no good in the longer term. Any advice on how to avoid
this error would be greatly appreciated. I can only assume there will be a "preferred" way from Microsoft for accessing lists now this KB is implemented, but I'm clueless as to what it is.
Thanks
Dougie

I've found that the issue is related to certain ISP's providing a "search assistance" page when a request returns an error due to no DNS entry matching that URL. For example, if you use Verizon in the USA, and go to www.somenonexistanturl.com, it will
"helpfully" respond to you with a search results page of possible options to match the URL you requested.
Because this is not the expected XML that the SP Client Context library was looking for (i.e., it does not have the DTD that it validates), the exception is thrown. The offending request that I have seen in my case is to the following URL: http://msoid.[my
office 365 acct name].onmicrosoft.com/FPUrl.xml
A simple resolution is to change your network connection adapter settings to use a DNS server IP other than the one auto-retrieved from your ISP, such as Google's (8.8.8.8 and 8.8.4.4). It's not a long term fix, since you'd breaking the ability to resolve
internal resources from a private or corporate network (unless the private network is also setup with Google's IP for the DNS gateway).
While you may have not changed any of your code, I would bet that you changed how/where you access the internet from when it was working to when it stopped working.
What I am not entirely sure of is why did this start happening all of a sudden - was it a change from MSFT that broke the URL, or did the ISP(s) decide to become extra helpful with bad URLs?
HTH
--Thiago
--Thiago

XML parsing error: web-jsptaglibrary_1_1.dtd not found

I'm getting the following Exception while Tomcat is parsing my welcome jsp page:
exception
org.apache.jasper.JasperException: XML parsing error on file /WEB-INF/struts-template.tld: Internal Error: File /javax/servlet/jsp/resources/web-jsptaglibrary_1_1.dtd not found
 at org.apache.jasper.parser.ParserUtils.parseXMLDocument(ParserUtils.java:227)
 at org.apache.jasper.compiler.TagLibraryInfoImpl.parseTLD(TagLibraryInfoImpl.java:283)
 at org.apache.jasper.compiler.TagLibraryInfoImpl.(TagLibraryInfoImpl.java:219)
 at org.apache.jasper.compiler.TagLibraryInfoImpl.(TagLibraryInfoImpl.java:174)
 at org.apache.jasper.compiler.JspParseEventListener.processTaglibDirective(JspParseEventListener.java:1170)
 at org.apache.jasper.compiler.JspParseEventListener.handleDirective(JspParseEventListener.java:765)
 at org.apache.jasper.compiler.DelegatingListener.handleDirective(DelegatingListener.java:125)
 at org.apache.jasper.compiler.Parser$Directive.accept(Parser.java:255)
 at org.apache.jasper.compiler.Parser.parse(Parser.java:1145)
 at org.apache.jasper.compiler.Parser.parse(Parser.java:1103)
 at org.apache.jasper.compiler.Parser.parse(Parser.java:1099)
 at org.apache.jasper.compiler.ParserController.parse(ParserController.java:214)
 at org.apache.jasper.compiler.Compiler.compile(Compiler.java:210)
 at org.apache.jasper.servlet.JspServlet.loadJSP(JspServlet.java:548)
 at org.apache.jasper.servlet.JspServlet$JspServletWrapper.loadIfNecessary(JspServlet.java:176)
 at org.apache.jasper.servlet.JspServlet$JspServletWrapper.service(JspServlet.java:188)
 at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:381)
 at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:473)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
 at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:247)
 at org.apache.catalina.core.ApplicationFilterChain.access$000(ApplicationFilterChain.java:98)
 at org.apache.catalina.core.ApplicationFilterChain$1.run(ApplicationFilterChain.java:176)
 at java.security.AccessController.doPrivileged(Native Method)
 at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:172)
 at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:243)
 at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566)
 at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472)
 at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)
 at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:190)
 at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566)
 at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:475)
 at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:564)
 at org.apache.catalina.valves.CertificatesValve.invoke(CertificatesValve.java:246)
 at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:564)
 at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472)
 at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)
 at org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2347)
 at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:180)
 at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566)
 at org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve.java:170)
 at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:564)
 at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:170)
 at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:564)
 at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472)
 at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)
 at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:174)
 at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566)
 at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472)
 at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)
 at org.apache.ajp.tomcat4.Ajp13Processor.process(Ajp13Processor.java:458)
 at org.apache.ajp.tomcat4.Ajp13Processor.run(Ajp13Processor.java:551)
 at java.lang.Thread.run(Thread.java:534)
This is the reference to the dtd its not finding from the tld
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE taglib PUBLIC "-//Sun Microsystems, Inc.//DTD JSP Tag Library 1.1//EN" "http://java.sun.com/j2ee/dtds/web-jsptaglibrary_1_1.dtd">
Do you think this is a bug with the parser itself or an incompatablilty between it and the tag library?
Or am I missing something?
Thanks for any help..... Andy

Store the web-jsptaglibrary_1_1.dtd to a directory and specify the file url.
<!DOCTYPE taglib SYSTEM "file://C:/dtds/web-jsptaglibrary_1_1.dtd">

Error while running forge - Could not open DTD file

Hi,
I have a simple application created in Endeca,facing below error when I run baseline_update.sh
FATAL 09/04/13 22:26:42.491 UTC (1378333602491) FORGE {baseline}: Error in file 'file:///../../endeca/apps/Sample/data/processing/Sample.analytics_config.xml' (line 2, char 58): An exception occurred! Type:RuntimeException, Message:Could not open DTD file 'file:///../../endeca/apps/Sample/data/processing/analytics_config.dtd'.
Initially Forge was running error free, only changes we made were :
1. Ingesting multiple XML files.
2. Changed match mode of dimensions to Autogen
Forge is unable to open any of the DTD files, for testing removed DTD reference line from Sample.analytics_config.xml.
Forge fails again " FORGE {baseline}: Error in file 'file:///../../endeca/apps/Sample/data/processing/Sample.cral_profile.xml...................................."
Regards,
Shruthi

I've seen this type of error before when Forge is configured to read multiple files with spec *.xml. Is that how you've configured your record adapter? This configuration then collides with Forge XML config files merged into the same data/processing directory.
From memory there's a couple of solutions for this - one might be to give the files a common name prefix if that's feasible, e.g. _data*.xml. You could use a sub-directory to separate the files, but you'd need to modify your copy scripts.

Error in DTD

Similar Messages

Maybe you are looking for