How To Fix COM_PRODUCT_ARCHIVE034 - Archiving terminated: PME server not active

SAP Error Message - Details

• Message type: E = Error

• Message class: COM_PRODUCT_ARCHIVE - Messages for Archiving and Deletion of Products

• Message number: 034

• Message text: Archiving terminated: PME server not active

What causes this issue?

One or more products have multi-value attributes and the status 'Can Be
Archived'. The PME Server must be activated in Customizing in order to
be able to archive products with multi-value attributes, so that the
system can access multi-value attribute information using the PME
interface during program runtime.

System Response

The program ends the process and product archiving does not take place.

How to fix this error?

Check the PME interface Customizing for the system.
If you have any doubts contact SAP Support or create a message for the
problem.

Procedure for System Administrators

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message COM_PRODUCT_ARCHIVE034 - Archiving terminated: PME server not active ?

  The SAP error message COM_PRODUCT_ARCHIVE034 indicates that the archiving process has been terminated because the PME (Product Master Data Management) server is not active. This error typically occurs when attempting to archive product data in SAP, and it suggests that the necessary services or components required for the archiving process are not running.
  Cause:
  
  PME Server Not Running: The PME server, which is responsible for handling product master data, may not be started or is down.
  Configuration Issues: There may be configuration issues in the system that prevent the PME server from starting or functioning correctly.
  Network Issues: There could be network connectivity problems that prevent the archiving process from communicating with the PME server.
  System Maintenance: The PME server might be undergoing maintenance or updates, making it temporarily unavailable.
  
  Solution:
  
  
  Check PME Server Status:
  
  Verify if the PME server is running. You can do this by checking the server status in the SAP system or using transaction codes like SM51 to view active application servers.
  If the PME server is not active, start it using the appropriate method (e.g., through the SAP Management Console or relevant transaction).
  
  
  
  Review Configuration:
  
  Check the configuration settings for the PME server in the SAP system. Ensure that all necessary parameters are correctly set.
  Look for any recent changes in configuration that might have affected the PME server's operation.
  
  
  
  Check Logs:
  
  Review the system logs (transaction SM21) and application logs (transaction SLG1) for any related error messages that could provide more context about why the PME server is not active.
  
  
  
  Network Connectivity:
  
  Ensure that there are no network issues preventing communication between the archiving process and the PME server. Check firewall settings, network configurations, and connectivity.
  
  
  
  Consult Documentation:
  
  Refer to SAP documentation or notes related to the PME server and archiving processes for any specific troubleshooting steps or known issues.
  
  
  
  Contact Support:
  
  If the issue persists after checking the above points, consider reaching out to SAP support for further assistance. Provide them with detailed information about the error and the steps you have already taken.
  
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as SM37 (to check job status), SM21 (system log), and SLG1 (application log).
  SAP Notes: Search for SAP Notes related to the PME server and archiving processes for any patches or updates that may resolve the issue.
  System Documentation: Review the system documentation for your specific SAP version, as there may be version-specific considerations or configurations.
  
  By following these steps, you should be able to identify the cause of the error and take appropriate action to resolve it.