Skip to Content
author's profile photo Former Member
Former Member

Documents stuck in transport dir


Im setting up a SAP content server on Windows Server 2003. On development, its installed on the same server the SAP (microsoft SQL) database resides. Production has a different server. In R/3, I've setup an archive link to the content server. Everything seems to work fine, but the documents never reach the database. They appear in the transport directory that is setup in the repository link. The logfiles of IIS stay empty, it looks like the system is configured not to use it. I've followed all the guides and now I'm running out of options.

Also, in CSADMIN, the repository keeps going from running (if I start it manually) to defined with a red light after a while.

Additional information: also if the repository is started the database is not reachable. In the logfiles it shows 'Content Repository Reports Error', although it runs fine and the IIS log files show some activity.

Anyone has any ideas?

Edited by: Martin Loohuizen on Dec 16, 2008 2:40 PM

Add a comment
10|10000 characters needed characters exceeded

Related questions

2 Answers

  • author's profile photo Former Member
    Former Member
    Posted on Dec 18, 2008 at 01:47 PM

    Well, weve narrowed it down to a webservice that doesn t respond. In SICF, the contentserver service is enabled, but unlike most other services, if I right click it and choose test, it responds with 'the page cannot be found'.

    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member


      You need not go to SICF for content server testing.

      Verify the below URL after CS installation but before creating repositories,

      http://<hostname>:<portno.>/ContentServer/ContentServer.dll?serverInfo is working fine and all installation is done by using domain administrator user rights.

      The commonly used port is 1090.


      Martin - Pls award if useful

  • author's profile photo Former Member
    Former Member
    Posted on Dec 22, 2008 at 10:44 AM

    For the record, it turned out that one, but probably two issues were relevant; the most important was that the RFC SAPHTTPA which is used by contentserver refers to just the exe SAPHTTP.exe. However, the path statement in Windows didnt point to the exe dir.

    Also the server was under some heavy load, it looked like the SAPHTTPA RFC didn't have enough at 20 seconds timeout. It looks fine now..

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.