How To Fix FG918 - Phase 6/6: Writing archive

FG918 - Overview

• Message type: E = Error

• Message class: FG - Program Error Messages

• Message number: 918

• Message text: Phase 6/6: Writing archive

Self-Explanatory Message

Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of messages in the SAP system have a message text, however this is frequently insufficient to comprehend or resolve the problem.

To make things easier, more detailed information is frequently added to describe the issue, how to fix it, and the necessary steps or configuration modifications.

Unfortunately, there isn't any extra information in this error notice.

What else can you do?

First, use our AnswerBot below to get a possible cause and solution (requires a premium subscription).

Also, review the in-depth Common Questions & Answers listed below; you could discover a solution there or be able to connect with others who have faced similar challenges.

You can also try searching the SAP support portal (support.sap.com) but you need a special user ID to access it. It is possible that an SAP support note exists that provides additional details about the mistake or even steps for fixing it.

Smart SAP Assistant

• What is the cause and solution for SAP error message FG918 - Phase 6/6: Writing archive ?

  The SAP error message FG918, which occurs during the archiving process, specifically during Phase 6/6 (Writing archive), typically indicates that there is an issue with the archiving process, which can be caused by various factors. Here’s a breakdown of potential causes, solutions, and related information:
  Causes:
  
  File System Issues: The target directory for the archive files may not have sufficient space, or there may be permission issues preventing the writing of files.
  Configuration Errors: Incorrect configuration settings in the archiving object or the archiving process can lead to this error.
  Database Issues: Problems with the database, such as locks or connectivity issues, can interrupt the archiving process.
  Transport Issues: If the archiving process is being executed in a transport environment, there may be issues related to transport settings or missing transport requests.
  Background Job Failures: If the archiving job is running in the background, it may fail due to timeouts or resource limitations.
  
  Solutions:
  
  Check Disk Space: Ensure