Skip to Content
avatar image
Former Member

HTTP

Hello SAP Document Management Experts,

I am unable to open any old documents using GOS (Generic Object Services) in our SAP system.

Once I open the billing document in VF03 transaction, I get the error as below.

########################

HTTP error: 404 Not Found

Message No. CMS025

Diagnosis

Error in accessing via HTTP

404 Not Found

###############

I have checked this page and none of the sap notes helped.

ArchiveLink BC-SRV-ARL - Application Server Infrastructure - SCN Wiki

And particularly this note does not applies to my scenario.

1846469 - HTTP 401 error message, login pop-up displayed for ArchiveLink System database

please provide your suggestion or solution. Thank you.

Regards,

Eswaran

Add comment
10|10000 characters needed characters exceeded

  • Follow
  • Get RSS Feed

1 Answer

  • Best Answer
    Aug 25, 2016 at 10:08 PM

    Hi Eswaran,

    This is a fairly common error and it might have multiple reasons. I presume here your documents are ArchiveLink based and reside in an external content repository, either SAP Content Server or any 3rd party repository such as OpenText.

    First I would try transaction OAC0 and locate the corresponding content repository. Validate the settings, especially the HTTP server name and make sure the server is there and is accessible from SAP. You may get this error if you have security enabled on this content repository (look for a check box "No signature") in OAC0 under full administration and there is a security certificate mismatch, in which case you might need to re-send the certificate from OAC0 or even generate one in STRUST.

    Good Luck,

    //Peter

    Add comment
    10|10000 characters needed characters exceeded

    • Hi Eswaran,

      Happy when I can help.

      At least that explains the issue. You don't necessarily want to copy your production content repository to QA - doesn't make much sense and this could also be a confidentiality issue. What most clients do they scrub the TOA* tables completely after the system copy. Also make sure you point to your QA / Dev system to the appropriate server in OAC0.

      Cheers,

      //Peter