Developer traces analysis in MMC Snap-In is incorrect

[] [] [] [] [] [] [] [] [] [] [] []

  1. RFC traces appear on desktop or other directorySymptom RFC trace files are written on the desktop or into another directory but not the SapWorkDir. Other terms SAP GUI, SAPGUI, RFC, trace, desktop Reason and Prerequisites The librfc32.dll did not...
  2. Incorrect matches when using find_next( )Symptom If you use anchor characters, the methods find_next( ) and replace_next( ) of class cl_abap_matcher find additional, incorrect matches. Other terms Regular expressions, beginning of line, cl_abap_regex, match, regex, regexp Reason...
  3. Where-used list incorrect for includesSymptom The where-used list for includes does not find all usage locations. Other terms WBCROSSI, SE38, where-used list Reason and Prerequisites This problem is caused by a program error. Solution Implement the...
  4. NR: Number from incorrect year is usedSymptom You create an interval in a year-dependent number range, and an interval for a later year already existed before. For the interval that already existed before, a buffer was created in...
  5. Where-used list incorrect after renaming methodsSymptom The navigation index is incorrect after you rename methods. The system does not find the new method in the where-used list. Other terms Where-used list, renaming methods, refactoring Reason and Prerequisites...
  6. Incorrect format when printing listsSymptom The system uses an incorrect format when printing ABAP lists: In the print dialog, the system proposes a format for an output device, which is not defined for the relevant device...
  7. OS07: Display incorrect OS log after refreshSymptom When you display the operating system log via transaction OS07, the incorrect OS log is displayed after you refresh the display. The error only occurs if a server is selected in...
  8. Job refers to incorrect spool requestSymptom You want to display the spool request for a job step in transaction SM37. However, the system displays a spool request that does not seem to correspond to the relevant job....

Symptom

For “All Tasks -> Analyse Developer traces…”, SAP MMC Snap-In terminates at system node level or returns incorrect results.
Other terms

Microsoft Management Console, MMC, SAP Developer Network, SDN
Reason and Prerequisites

This is due to a program error in the SAP MMC Snap-In.
Solution

The error in the SAP MMC Snap-In is corrected as of Release 7.11 patch level 44 change list 1072620. Install the relevant version using the SAP MMC MSI installation package (also see the SAP MMC SDN home page https://www.sdn.sap.com/irj/sdn/index?rid=/webcontent/uuid/f056bfb7-94e0-2b10-978a-c4783aae3e9e).

[Slashdot] [Digg] [Reddit] [del.icio.us] [Facebook] [Technorati] [Google] [StumbleUpon]

Leave a Comment