Technology Blogs by SAP
Learn how to extend and personalize SAP applications. Follow the SAP technology blog for insights into SAP BTP, ABAP, SAP Analytics Cloud, SAP HANA, and more.
Showing results for 
Search instead for 
Did you mean: 
Product and Topic Expert
Product and Topic Expert

The SAPonWin Check Tool (SCT) collects configuration and logging data from a Windows Server host. Based on the collected information, the SAPonWin Check Tool validates your configuration and checks for common misconfigurations, for example:

  • Operating System: Operating System Version, Windows Service Start-up types, Permissions for file System objects and network shares, etc.
  • Network configuration: Forward/Backward Name Resolution of IP Addresses and Hostnames

Disclaimer: This tool is not part of the SAP Products and thus not officially supported by SAP. It was designed to help our customers and supporters to identify potential misconfigurations. Use it at your own risk.


Download the SAPonWin Check Tool (SCT)

You can find the latest version of the SCT attached to SAP Note 3273783 - How to use SAPonWin Check Tool?.

The version history of the SCT can be found at the end of this blog post.

Advance information

For more details about how to upgrade the .NET Framework and the WMF, see:

System Requirements

To run the SCT, the system must fulfil the following requirements

  • Windows Server 2012 or later with .NET Framework 4.5.2
  • Windows Management Framework 5.1 (including PowerShell 5.1) or later. You can get the Windows Management Framework 5.1 from Microsoft:
  • Disk space: The required disk space (on the drive where SAPonWinCheckTool.exe is located) mainly depends on the size of the collected data. Especially the size of the Windows event logs and the SAP work and log folders can sum up to several Gigabytes.
  • The user used to run the SCT must be at least a member of the local Administrators group. It can be either a local user account or a domain user account.

Running SCT

Extract the archive to a local directory on the system you want to check, for example C:\SCT.

You can run the SCT by running SAPonWinCheckTool.exe via Windows Explorer:

  • Navigate to C:\SCT
  • Run SAPonWinCheckTool.exe

or from an administrative (= run as Administrator) command prompt or PowerShell:

cd C:\SCT

Wait until SCT has collected all required information from your local system. This may take some minutes depending on the performance of your local system and the amount of data being collected.

After the SCT completed its work successfully, the generated report is opened with the default web browser. You will also find a SCTReport-<Date>-<Timestamp>.zip archive in the same directory where SAPonWinCheckTool.exe is located (C:\SCT in this example). This ZIP archive contains all data that was collected by the SCT:

  • Network:
    Network related configuration data like IP configuration, IP to Hostname resolution, configured SMB shares, etc.
  • OperatingSystem
    • EventLogs: Export of the event logs Application and System.
    • Configuration data like user rights Assignment, environment variables, list of active filter drivers,
  • SAP
    • Profile\<SID>: Profile files for all detected SAP Systems, grouped by the <SID>
    • Work\<SID>: Work folders of all local SAP Systems, grouped by the <SID> This directory contains one subdirectory <SID> for each detected SAP System storing the collected data
  • WMI:
    Several XML files that contain WMI/CIM data that was exported by SCT
  • SCTReport.html
    The generated report

Attach this archive file to a SAP incident to provide SAP support additional information about the affected Windows host and SAP system.


Method Invocation failed because [[...]] does not contain a method named 'new'.

The SAPonWin Check Tool fails immediately after starting with an error message like the following:

Method Invocation failed because [[ ... ]] does not contain a method named 'new'.

This error message was observed on Windows Server 2012 R2 and below if the system does not fulfill the .NET Framework- and PowerShell/WMF requirements. Please check if the required .NET Framework and PowerShell-versions are installed. Do not forget to reboot the system after you have installed the new .NET Framework and PowerShell/WMF version.

To prevent this error message, SCT version later run some basic prerequisite checks for the installed .NET Framework and PowerShell version.

Version History

The latest version is

Version (January 26th, 2024)

  • Added SAPOSCol counters
  • Updated URL of Cluster Check Tool Blog Post after SAP Community upgrade

Version (November 24th, 2023)

  • Added support for 16 Byte Mitigation Options data
  • Added query of file version information for SAP related Windows Service executables.

Version (November 10th, 2023)

  • Added export of Image File Execution Options
  • Added export of Local Dumps configurations

Version (August 7th, 2023)

  • Added extended data collection mode (parameter "-extended")
  • Added check for NetBIOS over TCP/IP setting
  • Added detection of Windows Defender EDR + EDR Block Mode
  • Fixed check for Memory Compression
  • Query all PnP-Devices

Version (April 5th, 2023)

  • Added parsing of exploit protection settings
  • Added export of running processes and Windows Firewall Profiles

Version (March 8th, 2023)

  • Added processor info and BIOS info to report file
  • Fixed handling of invalid characters (ASCII char 0x0) in registry values

Version (February 13th, 2023)

  • Fixed handling of invalid characters (for example ASCII characters 0x0 and 0x4) in WMI data
  • Fixed crash if SCT is running on Windows Server 2012 R2
  • Added export of Windows Event Logs Microsoft-Windows-SMBClient/* and Microsoft-Windows-SMBServer/*
  • More detailed error message if execution of the collector script fails.

Version (January 11th, 2023)

  • Added evaluation of security setting 'RestrictRemoteSAM'

Version (November 25th, 2022)

  • First Release