E26 253 Error while checking in and storing: \\sapserver\file.tif

[Former Member]

Hi Experts,

I have now been fighting with this problem for a couple of weeks, and not been able to solve the issue.

My problem is to upload/check-in documents from the application serve in background.

I have a program to create DIF and attach files using BAPI_DOCUMENT_CREATE2.

When I'm running the program in foreground there is no problem.

When I run it in background I get the error message E26 254 Error while checking in and storing:
sapserver\file.tif

I have checked that the background process can see the document on the server and that is OK, so the problem must be within the actual storing of the document in DMS in the BAPI.

Any input to how I can solve this issue is appreciated.

Thanks in advance,

Thomas

[Former Member]

Hi Folks,

We will try to look into these suggestions.

However I think we have tried these example codes from the note at that returns the same error message.

But I will come back when we have investigated this more.

/Thomas

[Former Member]

Hi All,

We have now done some testing.

We got it to work on one of our systems but not on the other

I ran report RSCMST on both systems with the same backend directory. (A directory on the application server of the one that fails).

Running this report I get this result on the system that does not work.

HTTP interface test using function group SCMS_HTTP

21.06.2010 14:39:01

serverInfo:

contRep ZEBAN

contRepDescription PR Attachments

serverStatus running

serverVendor Copyright SAP AG, All rights reserved 1998, 2001

serverVersion 6300

serverBuild 193

serverTime 123902

serverDate 21.06.2010

serverStatusDescription

pVersion 0046

contRepStatus data(89%) log(1%)

contRepStatusDescription

ok 58.848

create(1): new doc (frontend) ok 445.211

create(2): new doc (back end)

check_subrc: subrc 2 instead 0

check_subrc: HTTP error: 400 Bad Request

create(2): new doc (back end) error

docGet/create(1): copy document ok 105.684

info(1): existing doc ok 26.881

update(1): new comp ok 47.050

info(2): after update ok 30.458

delete(1): unknown doc ok 33.061

delete(2): unknown comp ok 31.669

delete(3): existing doc ok 53.330

delete(4): deleted doc ok 34.781

delete(5): existing doc ok 31.088

putCert: ok 35.785

1 errors

Any ideas to what could be wrong?

Thanks in advance.

[christoph_hopf]

Hi Thomas,

please note that DMS BAPIs require always a SAPGUI channel or open RFC connection to start the SAPHTTP/SAPFTP program that is used to up- or download files to the client. If the BAPI ist executed in background mode, the system doesn't know from where to get the original file.

Please do not use BAPIs in background mode, use APIs instead. They are more flexible regarding RFC calls (background processing). Read through SAP note 504692, which contains sample programs for special checkin/checkout cases. Please read this note and use the sample programs as a basis for your own coding. Further please see also note

796709 which also might contain useful information for such cases.

Addtionally the SAP notes 1094459 which could also be useful to avoid such problems in the future.

Best regards,

Christoph

[Former Member]

Thomas,

I have dealt with same problem. Your approach of using server and giving hte path is correct. but the problem is here you cannot use the standard BAPI_DOCUMENT_CREATE2. This BAPI utilizes the SAP GUI as the front end to check in the document. I have to dig in a bit to find the precise BAPI we have used. Will get back to you.

regards

C

[Former Member]

Hi C,

Thanks a lot so far.

I know for sure that I can see the file because I have put these few lines of code in the program:

OPEN DATASET ls_draw-filep FOR INPUT IN TEXT MODE ENCODING DEFAULT.

IF NOT sy-subrc IS INITIAL.

CLOSE DATASET ls_draw-filep.

MESSAGE e500(26) WITH ls_draw-filep 'not found'.

ELSE.

CLOSE DATASET ls_draw-filep.

MESSAGE i500(26) WITH ls_draw-filep 'Found'.

ENDIF.

and I get a SUBRC of 0.

I hope you find the code ASAP since I need this urgently

Thanks in advance,

Thomas

[Former Member]

Thomas,

Did you check the file format? It wasn't the code, the file was being copied to R/3 directory but the data format was no longer holding good, so I believe there was some string / binary conversion involved. Please verify this too and hope this helps.

[Former Member]

Any luck so far?