Problem: Errors in Document Access 
Manifestation
The following problems indicate a document access error:
- Problems when accessing documents or report RSIRCCON
- Database error with <INSERT INTO KPRO>, error message number SO 013
- Database error with <GET DATA FROM KPRO>, error message number SO 013
- Error with data transfer, error message number 42 638
- Knowledge Provider transfer error, error message number SBDS 205
Explanation and Solution
The Knowledge Provider (KPro) has functions for storing and reading documents on external storage systems (content servers). The programs
saphttp, sapftp and sapkprotp are used for this. These programs are accessed via RFC. The program sapkprotp is usually only used on the application server or other selected servers, while sapftp and saphttp are also used on the front end. An RFC destination has to exist before programs can be used. The corresponding RFC destinations are as follows:
saphttp on the front-end workstation
SAPFTP: starts sapftp on the front-end workstation
SAPHTTPA: starts saphttp on the application server
SAPFTPA: starts sapftp on the application server
SAPKPROTP: starts sapkprotp on the application server
KPro automatically creates these RFC destinations when it is first used.
Manually Changing RFC Destinations
For testing and debugging purposes, you can change the destinations using transaction SM59. You can also change the flag for ‘trace’. This activates a special trace for the program in question, in addition to the RFC trace. Programs RSHTTP40 and RSFTP001 are used to display and delete the traces for saphttp and sapftp.
When using the trace, you must ensure that you switch it off afterwards. If you forget to do this, trace files of any size may be created.
- If the RFC destinations contain incorrect values (such as the wrong program, or the program is being started on the wrong machine), this can cause errors that are difficult to resolve.
- If problems occur in connection with HTTP access to the Content Server, or with transferring documents to and from the front end, you should check the destinations listed here.
If you are not sure that the destinations are in their original state, you can delete them. As explained earlier, this resets them to their initial state.
Related Notes
0093042, Problems with SAPFTP
0164203, Problems with SAPHTTP