Additional Blogs by Members
Showing results for 
Search instead for 
Did you mean: 
0 Kudos


After upgrading our SAP Solution Manager from version 7.0 EHP1 to 7.1 SP12, we still have to use

transaction CRM_DNO_MONITOR at least for some time. When you open it and list the

transactions, when you click the Refresh button the system hangs on program SAPLSENT and of course

after a while throws a Short Dump TIME_OUT.

Trying to solve the problem we implemented Notes:

1941803 - Application log is locked for a long time

and the connected 2069753 - Infinite wait in program SAPLSENA.

After that we started encountering error BL:264 in many transactions, including the web part of the system.

We checked note 2121466 but it is irrelevant.

It seems Implementing the above 2 notes was quite unnecessary.


The solution is quite simple. Use transaction SLG2 to run (or better schedule a monthly job Note 1911102) application log cleanup.

it seems the app log was full or corrupted.



Every time I write a blog, it takes some time and after I click Publish it gives me an Unexpected error.

Quite annoying! My advise is to write it in advance separately or click "Save and Continue" every once in a while

Top kudoed authors