cancel
Showing results for 
Search instead for 
Did you mean: 

CIM_ERR_FAILED: HTTP response code: 404 Not found

mart_mattikas
Explorer
0 Kudos

Hello!

We are installing NW7.0 PI with local SLD as HA system with virtual name and after patching it up to SPS17 we started Configuration wizard

PI_00_This wizard will execute Postinstall steps of technical configuration for the PI Usage

and on step 33/142 Configure the Integration server for sld we got an error:

CIM_ERR_FAILED: HTTP response code: 404 Not found

and from log:

InvokeService:Configure the integration server for sld

Library: sap.com/tclmctctemplateslevel1_4_tcc

SourcePath ./PIPostInstallProcess/configureIntegrationServer8

Time 2009/05/07 at 10:45:31

WSDL /content/NetWeaver/PI/service/SLDConfig_configureIntegrationServer_configureIntegrationServer.wsdl

Execute Java Service

Library:sap.com/tclmctcutilbasic_ear

Class:com.sap.ctc.util.SLDConfig

Method:void com.sap.ctc.util.SLDConfig.configureIntegrationServer(java.lang.String, java.lang.String, java.lang.String, java.lang.String, java.lang.String, java.lang.String)

Arguments

SID : XRQ

CLIENT : 001

HOST : capitate

PORT : 8032

SLDUSER : PISUPER

SLDPASSWORD : % secure content %

InvokeService- Result: Failed

Exception Message:CIM_ERR_FAILED: HTTP response code: 404 Not found

Exception Class:com.sap.sld.api.wbem.exception.CIMCommunicationException

Stacktrace

com.sap.sld.api.wbem.client.WBEMHttpRequestSender.newCommunicationException(WBEMHttpRequestSender.java:414)

com.sap.sld.api.wbem.client.WBEMHttpRequestSender.processResponse(WBEMHttpRequestSender.java:323)

com.sap.sld.api.wbem.client.WBEMHttpRequestSender.send(WBEMHttpRequestSender.java:142)

This error would be normal with Central SLD but we have local SLD. Is there any parameters for systems with virtual name which is not configured?

Regards,

Mart

Accepted Solutions (0)

Answers (5)

Answers (5)

mart_mattikas
Explorer
0 Kudos

Hello!

I configured this failed step manually as described on :

Link: http://help.sap.com/saphelp_nw70/helpdata/en/9b/da0f41026df223e10000000a155106/content.htm

and skiped that step on wizard. All other configuration steps were succesfully ended.

CPACache started work perfectly.

Regards,

Mart

mart_mattikas
Explorer
0 Kudos

Now SLD in updated to latest patches: cimsap41513_0 and CRDelta41513_0, but error is the same and CPACache refresh is unsuccessful too.

Regards,

Mart

mart_mattikas
Explorer
0 Kudos

All packages were installed with JSPM as stack and without errors.

Logon to the SLD is possible and it is up and running.

When we logon to the Exchange Profile with PISUPER and choose ' The new SAP Exchange Profil Page is available here' , it fails with error:

You do not have the neccessary authorisation.

But if I choose ' The previous SAP Exchange Profile UI is available here. ' profile works perfect.

Regards,

Mart

Former Member
0 Kudos

do you use the SLDDSUSER to logon at SLD?

do you have configured the sld connection in visual administrator (server->services->SLD Data Supplier) and this connection and cim client configuration works? (here you can check if the sld works fine)

is the cim client of sld at newest rel (cimsap41512_0)?

is the cr content delta CRDelta41512_0?

mart_mattikas
Explorer
0 Kudos

Thanks for answering.

Configuration is done by the Post-Installation Guide - SLD of SAP NetWeaver 7.0 , but there is still same error.

It seems, that point is in CPA Cache full refresh, because in SLD Java system on app.server still shows his patchlevel 9 not 17 .

CPA Cache refresh gives an error:

The XML page cannot be displayed

Cannot view XML input using style sheet. Please correct the error and then click the Refresh button, or try again later.

-


Invalid at the top level of the document. Error processing resource 'http://capitate:53200/CPACache/refresh?mode=full'. Li...

CPA cache refresh (mode=full) successfully executed in 703 milliseconds.

^

Regards,

Mart

Former Member
0 Kudos

app.server still shows his patchlevel 9 not 17

are the packages correct deployed in the SDM?

coul'd you logon to your local SLD? " http://<host>:5<instance>00/sld "

Former Member
0 Kudos

you have to configure your local SLD before.