Validate Your Setup
Run a comprehensive health check of your ABAP agent setup in one command.
The setup status command runs a comprehensive health check of the entire ABAP agent installation. It verifies SeaLights connectivity, RFC connections, SAP authorizations, SCMON configuration, and local agent prerequisites — all in one report.
Use it:
After initial setup to confirm everything is configured correctly
After upgrading to a new agent version
When troubleshooting — before investigating individual components
Command Syntax
slabapcli.exe setup status.\slabapcli.exe setup statusThis command takes no parameters.
Report Sections
The report runs the following checks in order:
Agent Prerequisites
Checks local prerequisites on the machine where the agent is installed.
Agent version
Displays the installed agent version.
Windows version
Confirms the OS version is supported.
Install directory access
Current operator and NETWORK SERVICE have read+execute on the install directory.
Executable directory
Config install path matches the current executable location; required binaries (watcher.exe, purgeLogs.exe) are present.
ProgramData access
Read+write access for operator and NETWORK SERVICE on config, userdata, and logs directories.
Custom userdata access
If a custom userdata path is configured, verifies NETWORK SERVICE has read+write access.
sapnwrfc.dll
SAP NW RFC SDK library is present, x64, and meets the minimum version requirement.
Task Scheduler
Windows Task Scheduler service is reachable.
SeaLights Connectivity
Validates the agent token by calling the SeaLights API. Equivalent to running slabapcli sealights test.
On success, you see:
On failure, the report shows the HTTP status and a link to the troubleshooting page.
RFC Destinations
For each [[rfc]] entry in config.toml, runs the following sub-checks:
Connectivity
RFC connection succeeds. Distinguishes communication failures (unreachable host) from logon failures (bad credentials).
System info
Prints RFC system info fields (SysID, hostname, kernel, etc.).
SeaLights ABAP add-on
The /TRICE/RFC_GET_TABLE_DATA function module exists — meaning the SeaLights ABAP add-on is installed.
Add-on version
Reads the add-on version from the CVERS table and compares it to the minimum supported version.
Time synchronization
SAP system clock, RFC round-trip delay, and SeaLights clock sync offset.
RFC function modules
Probes all RFC function modules the agent uses at runtime. Lists any that are not callable by the configured SAP user.
Tables
Probes all SAP tables the agent reads. Lists any that are not readable by the configured user.
SCMON configuration
Reads SCMON_CONFIG entries. Reports whether SCMON is active, its deactivation date, and whether the agent can call SCMON_COLLECT.
Reading the Output
Each check line uses a status indicator:
OK (green) — check passed
ERROR (red) — check failed; action required
INFO — informational note (e.g., leftover permissions from an older install)
The command exits with code 0 if all checks pass, or 1 if any check fails.
Example Output
Resolving Failures
Each failure message includes guidance on what to fix. For detailed troubleshooting, see Troubleshooting the ABAP Agent.
Common failure scenarios:
sapnwrfc.dll: ERROR - missing
SAP NW RFC SDK not installed
Re-run the installer and point it to the SAP NW RFC SDK DLL. See Install WATCHER and SLABAPCLI.
SeaLights ABAP add-on: Not installed
Add-on transport not imported
Import the SeaLights ABAP add-on transport. See Install the ABAP addon.
RFC function modules not callable
Missing S_RFC authorizations
Regenerate the SeaLights authorization profile. See Generate Authorization Profiles.
Tables not readable
Missing S_TABU_DIS authorizations
Same as above — regenerate the authorization profile.
SCMON not active
SCMON not enabled on QAS
Activate SCMON. See Configure your QAS systems to collect SCMON data.
Install directory access: ERROR
Permissions issue
Re-run the installer or manually grant NETWORK SERVICE read+execute on the install directory.
Last updated
Was this helpful?

