Reproducing SAP GUI exception using Application Verifier

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

Related:

  1. Expected release dates for SAP GUI for Windows & ITS PatchesSymptom You need information on the expected release dates of...
  2. SAP GUI for the Java environment (Platform Independent GUI)Symptom This note relates to support for front-end platforms. Other...
  3. SAP GUI for HTML: Autocompletion on the logon pageSymptom On the logon page of the external ITS, there...
  4. Download and start of SAP Shortcut from URL failsSymptom When trying to download and start an SAP Shortcut...
  5. Supported SAP GUI platformsSymptom Preface This note contains information on platforms supported by...
  6. Maintenance strategy / deadlines ‘SAP GUI’Symptom This note explains the maintenance strategy for SAP GUI...
  7. Unicode: Text with question marks in window title and MsgBoxSymptom Text in window title or standard windows message boxes...
  8. Wide lists displayed with more than 255 columnsSymptom You created a list with more than 255 columns...

Symptom

In the call stack, an exception in the SAP GUI for Windows leads to a termination in a “malloc” command. This is probably a memory overwrite.
Other terms

SAP GUI, exception, AppVerifier, PDB
Reason and Prerequisites

In the case of a SAP GUI exception, SAP Support asks you to reproduce the termination using the Microsoft Application Verifier tool (freeware). You can use this tool to determine the software that overwrites the memory.
Solution

As a prerequisite, follow the instructions of Note 520688. In addition, activate the complete exception tracing as described in Note 559285.
Then install the Microsoft Application Verifier tool (ApplicationVerifier.x86.msi):
http://www.microsoft.com/downloads/details.aspx?FamilyID=bd02c19c-1250-433c-8c1b-2619bd93b3a2&DisplayLang=en#filelist
Exit SAP Logon (and all open SAP GUI screens) and start the installed Application Verifier. Choose FILE -> ADD APPLICATION to select the saplogon.exe and sapgui.exe files (Image Name), and select HEAPS (under the BASICS tree) as the only test. Then choose SAVE. (Confirm the “Debugger Required” dialog box with OK. In this special case you DO NOT require a debugger.)
Start SAP Logon as normal and reproduce the exception. Attach the generate exception file (see Note 520688) to the message to be sent to SA Support.
Finally, deactivate the HEAP test in the Application Verifier and choose SAVE (this step should remove the saplogon.exe file from the “Image Name” window).

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

Leave a Comment