cancel
Showing results for 
Search instead for 
Did you mean: 

Solution Manager 4.0SR3 installation problem

Former Member
0 Kudos

Hi Experts

I am installing Solution Manager 4.0 sr 3 in a windows 2003 platform and sql 2000 sp4 latest hofix, right at the last processing phases I first received following and sapinst just exited:

INFO 2007-12-21 12:53:16.234

Execution of the command "C:\j2sdk1.4.2_12\bin\java.exe -classpath C:/usr/sap/SLM/DVEBMGS00/j2ee/cluster/server0/apps/sap.com/tclmctcutilbasic_ear/servlet_jsp/ctc/root/WEB-INF/classes/ com.sap.ctc.util.ConfigMainExt XXXXXX ZAJNBSVSM:50000 J2EE_ADMIN XXXXXX" finished with return code 0. Output:

ConfigMainExt state200

TYPE=S<BR>STATE=<BR>INFO_SHORT=<BR>CONFIGURATION=

INFO 2007-12-21 12:53:17.234

Execute step configSLDMainLocalConfigure of component |NW_Onehost|ind|ind|ind|ind|0|0|SAP_Software_Features_Configuration|ind|ind|ind|ind|5|0|NW_Usage_Types_Configuration_AS|ind|ind|ind|ind|0|0|NW_CONFIG_SLD|ind|ind|ind|ind|0|0.

INFO 2007-12-21 12:53:18.172

Creating file C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS\java.exe.log.

INFO 2007-12-21 12:53:18.172

Output of C:\j2sdk1.4.2_12\bin\java.exe -classpath C:/usr/sap/SLM/DVEBMGS00/j2ee/cluster/server0/apps/sap.com/tclmctcutilbasic_ear/servlet_jsp/ctc/root/WEB-INF/classes/ com.sap.ctc.util.ConfigMainExt XXXXXX ZAJNBSVSM:50000 J2EE_ADMIN XXXXXX is written to the logfile java.exe.log.

INFO 2007-12-21 12:54:04.147

Execution of the command "C:\j2sdk1.4.2_12\bin\java.exe -classpath C:/usr/sap/SLM/DVEBMGS00/j2ee/cluster/server0/apps/sap.com/tclmctcutilbasic_ear/servlet_jsp/ctc/root/WEB-INF/classes/ com.sap.ctc.util.ConfigMainExt XXXXXX ZAJNBSVSM:50000 J2EE_ADMIN XXXXXX" finished with return code 0. Output:

ConfigMainExt state200

TYPE=S<BR>STATE=<BR>INFO_SHORT= => Stopping SLD ...

... Ready

+ Object Server stopped.

=> Setting Object Server Name to: ZAJNBSVSM ...

... Ready

+ Object Server configured.

=> Starting SLD ...

... Ready

+ Object Server started.

<BR>CONFIGURATION=

ERROR 2007-12-21 12:54:05.132

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"

Then when trying to restart sapinst the following:

TRACE 2007-12-21 13:52:29.815

Running with toplevel file C:\Program Files/sapinst_instdir/SOLMAN/SYSTEM/MSS/CENTRAL/AS/toplevel.xml

TRACE 2007-12-21 13:52:29.909

Running with dialog file C:\Program Files/sapinst_instdir/SOLMAN/SYSTEM/MSS/CENTRAL/AS/dialog.xml

TRACE 2007-12-21 13:52:30.770

Running with keydb file C:\Program Files/sapinst_instdir/SOLMAN/SYSTEM/MSS/CENTRAL/AS/keydb.xml

ERROR 2007-12-21 13:52:30.801 [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.

Any Ideas?

Regards

Pieter

Accepted Solutions (0)

Answers (5)

Answers (5)

Former Member
0 Kudos

My issue was resolved and the installation completed successfully when i increased my memory resources. Mine would fail when the virtual memory got too low. I changed the setting to allow it to grow when needed and all went well.

hamendra_patel
Explorer
0 Kudos

Hi bob ,

Did you found solution of your problem ,since ia m facing similar issue while installing CRM . Here is my error similar to yours

ERROR 2008-01-22 12:42:10.32

FKD-00049 XML parser error: error: no DTD specified, can't validate in line 1, 1

in file ORADBSIZE.XML.

ERROR 2008-01-22 12:42:10.34

MUT-03025 Caught EKdException in Modulecall: error: no DTD specified, can't validate in line 1, 1

.

ERROR 2008-01-22 12:42:10.35

FCO-00011 The step importRow_Tsp with step key |NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0|NW_CreateDB|ind|ind|ind|ind|0|0|NW_OraDBCheck|ind|ind|ind|ind|0|0|NW_OraDBMain|ind|ind|ind|ind|0|0|importRow_Tsp was executed with status ERROR .

Let me know if you found work around to this issue

Thaks

Hamendra

Former Member
0 Kudos

Pieter,

I am also installing Solution Manager 4.0 sr 3 in a windows 2003 platform and right at the last processing phases I get the same 2 errors as you listed below.

First the: 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" (which is not read only, i checked)

And when I tried to restart I get - ERROR 2008-01-12 11:54:03.755 [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.

I am actively installing right now and am stuck. Have you gotten past this message. If so, how did you get there.

Regards,

Bob

Matt_Fraser
Active Contributor
0 Kudos

Instead of 'read-only,' could it be that the installation user account doesn't have full access to the keydb.xml file or the folders it's in?

Former Member
0 Kudos

Hi Pieter,

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"

Have you unticked the read-only option for keydb.xml?

Former Member
0 Kudos

Hi Pieter,

It looks like you are having some problems with keydb.xml and it might be corrupted. Check it or unpack fresh one and restart your installation. Also check if there any viruses on you WIN server, I recently had similar strange problem with control.xml and it turned out it was a hidden virus work.

Hope it will help!

Reward points if useful please

Best regards, Elena