SAP Knowledge Base Article - Preview

3286949 - How to perform clean installation and reinstallation of SAP GUI for Windows?

Symptom

Some SAP GUI functionalities are being affected after SAP GUI upgrading, and it can present the following symptoms (but not limited to): From errors in the Installation Check, Windows logs (Event Viewer app), SAP GUI automation and session traces.

Most of the errors detailed here can be caused by things other than a faulty installation, therefore to verify if an issue qualifies as an installation error, it is important to perform an Installation Check and verify if there are installation errors.

Examples:

  • Unresolved module dependencies/ unresolved exports of some GUI controls (some runtime errors: MESSAGE_TYPE_X and RAISE_EXCEPTION dump on program CL_GUI_PICTURE================CP dumps can occur);
  • WinAPI::searchPath() failed;
  • WinAPI::searchPath() failed. - xxxx.dll: Error message: The system cannot find the file specified. Error code 0x00000002 (2).
  • Automation(Error);
  • Automation(Error):Exception fire by :SAP Frontend Server
  • Automation(Error):Exception info: Cannot create control
  • Sometimes an automation error occurs due to an inconsistency caused by a mismatch between GUI controls from different SAP GUI releases coexisting on a workstation (faulty installation):

Automation(Error):    SAPGUI.APPLICATION     |Sapgui Application     |CreateControl |Cannot create control |Version info not found |7500.2.4.1141 |"C:\Program Files\SAP\FrontEnd\SAPGUI\saplogon.exe".

For instance, in the above sample automation trace record, the GUI control version refers to SAP GUI 750 but the current SAP GUI release installed is higher (e.g, SAP GUI for Windows 800);

  • Automation(Error):Exception code:65523
  • Faulting application name: saplogon.exe (SAP GUI crashes);
  • SAP GUI crashes with following message on exception trace: ExceptionCode: c0000005 (Access violation);
  • Return-Code: 129 (Reboot is recommended) and  "1W  Registration with 'sapregsv.exe' failed" in the NwSapSetup.log can appear.

The errors may occur regardless of the application, randomly, and it is generally workstation-specific, affecting only a few users.


Read more...

Environment

SAP GUI for Windows

Product

ABAP platform all versions

Keywords

Installation error, SAP GUI, NwSapSetup.log, WinAPI::searchPath() failed, Automation(Error), crash, dump, ST22, MESSAGE_TYPE_X, Unresolved module dependencies, unresolved exports, 1E, 1W  Registration with 'sapregsv.exe' failed, WinAPI::searchPath() failed, Access Violation, Exception Code 5, Exception Code c0000005, Exception Code, c0000005, Exception fire by, SAP Frontend Server, Cannot create control, Exception code, 65523, RAISE_EXCEPTION, CL_GUI_PICTURE================CP, CL_GUI_PICTURE. , KBA , BC-FES-INS , Frontend Installation , BC-FES-GUI , SAP GUI for Windows , BC-FES-CTL , SAP GUI for Windows Controls , How To

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.