Error : Express document "Update was terminated" received from author in MM01

[former_member684999]

Hi All,

I checked in TCode SM13 for the error mentioned in question, below was the error details :

In FM : MATERIAL_UPDATE_DB

A database error occured. The error message in the database was: "authentication failed".

How do i know which authentication is failing, as nothing is captured in SU53.

[former_member684999]

**Error : Express document "Update was CANCELED" received from author in MM01

[former_member684999 · Accepted solution]

verify the password of user LCADB is maintained correctly in the T-code DBCO.

You may need to reset the password and refresh the connection again.

[Lakshmipathi]

If CO is implemented in your system, then, it could be due to missing number range which you can verify in tcode KANK
It could also be due to liveCache function not activated which you can check with your Basis team

[former_member684999]

Hi lakshmipathi.ganesan ,

Number ranges are correct in KANK. Nothing is missing.

LiveCache function is activated - implemented note - 2909571

[DominikTylczyn]

Hello apurvaj

The fact that the short dump is not save is most probably due to SNAP table being full. You need to reorganize short dumps (delete the old ones) as described in note 2496091 - How to deal with SNAP_NO_NEW_ENTRY However I don't think that's not the root cause of the problem with MM01.

Do you experience similar problems in other transactions as you do in MM01?

Best regards

Dominik Tylczynski

[former_member684999]

Hi 3a9e4ce873a94034b33dc62b0ce600ee ,

Yes, i have reorganised my ST22 as given in note 2496091.

The same error comes for MM02.

[DominikTylczyn]

Hello apurvaj

When the error is risen in MM02, do you get short dump know?

Do you experience similar problems in other transactions as you do in MM02?

BR, Dominik

[former_member684999]

Hi 3a9e4ce873a94034b33dc62b0ce600ee

Yes, short dumps comes in MM02 as well.

This issue is seen in MM01 and MM02 transactions.

It seems a database inconsistency, but how do we resolve it ?

[DominikTylczyn]

Hello apurvaj

The message you are seeing indicates problems with database connection. You should be able to find more details in ABAP short dump generated when update failed. Check out transaction ST22.

In the mean time see the following notes, assuming you are on HANA database

2399990 - How-To: Analyzing ABAP Short Dumps in SAP HANA Environments

2159014 - FAQ: SAP HANA Security

If the problem is only with MM01 transaction and not with any others, investigate any custom enhancements around MM01 that might cause the error.

Best regards

Dominik Tylczynski

[former_member684999]

Hi dominik.tylczynski ,

There aren't any custom enhancements around MM01.

The error also occurs for MM02.

Also, nothing is captured in ST22. If i execute error row in SM13 as below :

Error :

Category ABAP programming error Runtime Errors SNAP_NO_NEW_ENTRY ABAP Program Application Component Not assigned Date and Time 00.00.0000 12:03:20 (UTC)

for the 'SNAP_NO_NEW_ENTRY', i checked below note .

2496091 :

• database error :

Program: dbds

Line: 1138

Message: 10

Message: CON

How do I rectify this error ?

• Reorganize the table via Transaction ST22->Go to->Reorganize. --- Done

[Abinathsiva]

Hi,

Maintain defaults-spool control tab-output device-LOCL.(your spool) in SU01 for the that user.

[former_member684999]

Hi abishankar ,

LOCL in SU01 is already maintained.