cancel
Showing results for 
Search instead for 
Did you mean: 

Archiving write job got failed

Former Member
0 Kudos

Hi,

Archive write job got failed

Log:

Name for new archive file: BC_IDOC_20111018_205051_0.ARCHIVE

Name for new archive file: BC_IDOC_20111018_205215_0.ARCHIVE

Name for new archive file: BC_IDOC_20111018_205337_0.ARCHIVE

Name for new archive file: BC_IDOC_20111018_205504_0.ARCHIVE

Name for new archive file: BC_IDOC_20111018_205746_0.ARCHIVE

Input or output error in archive file /interfaces/archive/FCP/IDOC/BC_IDOC_20111018_2057

Job cancelled after system exception ERROR_MESSAGE

Diagnosis

An error has occurred when wirting the archive file /interfaces/archive/FCP/IDOC/BC_IDOC_20111018_2057 in the file system. This can occur, for example, as the result of temporary network

problems or of a lack of space in the fileing system.

Pls suggest how to shortout the issue

Tks,

Raju

Accepted Solutions (0)

Answers (3)

Answers (3)

Former Member
0 Kudos

Hi,

I am experiencing the same problem.  The job logs do not indicate other possible causes.  The OS and system logs don't have either.  I am archiving CO_COSTCTR and during test mode it runs for almost 8 hours.  The error happens during production mode where the system is generating archive files.  The weird thing, I do not have this issue with our Test system (db copy from our Prod).  It only happens in our Prod server.  I am thinking of some system or OS related parameter that is unique or different from our Test server.  This parameter could affect long running background job such as this.  We're running SAP R3 4.7 by the way.

Anyone has encountered this before and was able to resolve it?

Tony

JPReyes
Active Contributor
0 Kudos

I believe the message is self-explanatory???...

Former Member
0 Kudos

Hello,

Please verify if /interfaces/archives directory is accessible and has enough space at OS level.

Thanks

Former Member
0 Kudos

Hi ,

Thanks for your advice.

our file system have more sufficent space and permission .

we are not able to get exact erroe in sap system.

Tks,

Raju

Former Member
0 Kudos

the issue not fixed