How To Fix ILM_STOR_MBC035 - Notification version not found in initial MBC HTTP request

ILM_STOR_MBC035 - Overview

• Message type: E = Error

• Message class: ILM_STOR_MBC - ILM Store: MBC Message Class

• Message number: 035

• Message text: Notification version not found in initial MBC HTTP request

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.

ILM_STOR_MBC035 - Details

• The SAP error message ILM_STOR_MBC035 indicates that there is an issue with the notification version not being found in the initial MBC (Message-Based Communication) HTTP request. This error typically arises in the context of SAP Information Lifecycle Management (ILM) when dealing with archiving and data management processes.
  
  Cause:
  
  Version Mismatch: The error often occurs when the version of the notification being sent in the HTTP request does not match any of the versions that the system recognizes. This could be due to an outdated or incorrect version being referenced.
  
  Configuration Issues: There may be configuration issues in the ILM settings or the MBC setup that prevent the system from recognizing the notification version.
  Missing or Incorrect Data: The request may be missing required data or parameters that are necessary for the system to process the notification correctly.
  
  
  Solution:
  
  Check Notification Version: Verify that the version of the notification being sent in the HTTP request is correct