cancel
Showing results for 
Search instead for 
Did you mean: 

Content repository cannot be addressed from frontend

Former Member
0 Kudos

Hi all,

We have configured the sap content server 6.5 and trex7.1,

we have succesfully created content repository and test connection also passed.

we are creating a new document in cv01n tcode and uploading a document with that it is saving sucessfull, but after that i went to tcode slg1 there i find error as:

repository zcontentserver cannot be addressed from the frontend

mesaage number CMS066

Please suggest me with a helpfull information, if i am missing any configuration please let me know.

Thanks in advance.

Regards,

Praveen.

Accepted Solutions (0)

Answers (3)

Answers (3)

lmoc
Explorer
0 Kudos

Hi All,

Are there any updates how this was resolved? We are also experiencing this same error. I hope someone may shed some light to us. Thank you.

former_member204787
Contributor
0 Kudos

Hi Praveen,

Have you changed front end computer settings in DC20??

Reg,

Chandu

Former Member
0 Kudos

Hi Chandu,

Thanks for your reply. Yes, i have mauntained frontend computer settings in DC20 still it is same. Is there any other configuration issue for this error.

Regards,

Praveen.

markus_deuter
Active Participant
0 Kudos

Hi Praveen,

try to check the content server (CS) log by transaction SLG1. Do you use object SCMS and sub object HTTP ? Any further errors ?

Perhaps you have to define a full qualified HTTP server name  for CS ?

Example:

CS servers name = MYKPRO

Your domain = MYCOMPANY

so you should define MYKPRO@MYCOMPANY for http server address in OAC0.

If not, try to debug Include LSCMS_HTTPF01, Line 1393 ... this will give you the error CMS066 I suppose. Perhaps the repository ID is wrong ...

One last idea: if you have multiple application server, check your RFC destination and set correct gateway options to find the gateway.

Ok, really last idea: check if the frontend can use the CS port ... I suppose, it is port 1090 because of firewall settings.

Regards,

Markus    

former_member551676
Participant
0 Kudos

Hi Markus,

So the concept is

when you add an attachment,

SAPGUI on workstation will make a connection via HTTP( sm50 saphttp) directly to the content server( oac0 Z1's hostnameexample:1090 )

So if there is firewall blocking port 1090, this will end up in error like this

Connect Error: NiHostToAddr hostname.example.com error:NIECONN_REFUSED

Is my understanding correct ?

markus_deuter
Active Participant
0 Kudos

Hi Alex,

yes I would agree.

SAP application server generates a complete, valid URL including certificates for HTTP or HTTPS access and gives this back to SAPgui. Then the SAPgui clients triggers to SAP content server by this URL.

If not accessible/reachable multiple errors can happen as you describes depending on your scenario.

You can check this URL in detail if you use function module C_DESK_DOC_GET_URL

if you run test mode by entering a document info record. You will get all URLs to all files linked to the document record. Looks like this

Then you can check this URL by pasting it to your browser, too.

Hope this helps ...

Regards,

Markus

P.S. pls rate if this was helpful ...

Former Member
0 Kudos

Hi all,

Any update on above.

SSB
Advisor
Advisor
0 Kudos

Hello

Please check the SAPHTTP RFC destination. Also check the SLG Logs for more details on the issue.

Regards

S S B

Former Member
0 Kudos

Hi S S B,

I have checked the RFC it is connectiontest pass, and i have checked the SLG logs in there it is written as shown in the above:

repository zcontentserver cannot be addressed from the frontend


What will be cause for this error, please advice.


Regards,

Praveen.

benedikt_wagner_mdt
Active Participant


Hi Praveen,

as far as I understand it, SAP first tries to connect to archive server via frontend using RFC connection SAPHTTP. If that fails, then in a second try the communication is done via server using RFC connection SAPHTTPA. In this case the message CMS066 is written into the application log.

So all is o.k. but you are "informed" with this error message.

Regards,

Benedikt