> For the complete documentation index, see [llms.txt](https://docs.sealights.io/knowledgebase/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sealights.io/knowledgebase/setup-and-configuration/sealights-agents-and-plugins/abap-agent/command-line-interface/validate-your-setup.md). # Validate Your Setup 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 {% tabs %} {% tab title="Command Prompt" %} {% code title="Command" overflow="wrap" %} ```batch slabapcli.exe setup status ``` {% endcode %} {% endtab %} {% tab title="PowerShell" %} {% code title="Command" overflow="wrap" %} ```powershell .\slabapcli.exe setup status ``` {% endcode %} {% endtab %} {% endtabs %} This 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. | Check | What it verifies | | ------------------------ | ---------------------------------------------------------------------------------------------------------------------------- | | 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: ``` Agent token is valid. Sealights connectivity check succeeded. ``` 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: | Sub-check | What it verifies | | --------------------- | ----------------------------------------------------------------------------------------------------------------------------------- | | 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 {% code title="Successful run (abbreviated)" overflow="wrap" %} ``` == Agent == Agent version: 2026.1.0 Detected Windows version: Windows Server 2019 Install directory access: OK - current operator and NETWORK SERVICE can read+execute C:\Program Files\Tricentis\SeaLights\ABAP Agent\bin Executable directory: OK - config install matches current executable directory C:\Program Files\Tricentis\SeaLights\ABAP Agent\bin Required executables: OK - watcher.exe and purgeLogs.exe exist in C:\Program Files\Tricentis\SeaLights\ABAP Agent\bin ProgramData config access: OK - current operator and NETWORK SERVICE can read+write C:\ProgramData\Tricentis\SeaLights\ABAP Agent\config public userdata access: OK - current operator and NETWORK SERVICE can read+write C:\ProgramData\Tricentis\SeaLights\ABAP Agent\public private userdata access: OK - current operator and NETWORK SERVICE can read+write C:\ProgramData\Tricentis\SeaLights\ABAP Agent\private watcher logs access: OK - current operator and NETWORK SERVICE can read+write C:\ProgramData\Tricentis\SeaLights\ABAP Agent\public\Logs\watcher Custom userdata access: default / n/a - configured userdata is under ProgramData sapnwrfc.dll: OK - detected x64, version 7530.0.67.0 at C:\Program Files\Tricentis\SeaLights\ABAP Agent\bin\sapnwrfc.dll Task Scheduler: OK - service is reachable Agent checks succeeded. == Sealights == Agent token is valid. Sealights connectivity check succeeded. == RFC destinations == ---------- RFC destination: QAS Connected System info: RFCDBHOST: sapqas01 RFCSYSID: S21 RFCIPADDR: 10.0.1.50 RFCKERNRL: 753 RFCSAPRL: 750 SeaLights ABAP add-on: Installed SeaLights ABAP add-on version: Installed version: RELEASE=2025_01 EXTRELEASE=0012 (minimum supported RELEASE=2024_01 EXTRELEASE=0001) Time synchronization: K_DateTime: 2026-05-07 20:00:00 L_DateTime: 2026-05-07 20:00:00 Average delay of RFC connection: 00:00:00.035 RFC K_Datetime: 2026-05-07 20:00:00. UTC offset: 02:00:00 RFC UTC datetime: 2026-05-07 18:00:00 (Local UTC datetime - RFC UTC datetime) difference: 00:00:00.002 Agent UTC sent to SeaLights : 2026-05-07 18:00:00.123 SeaLights server UTC : 2026-05-07 18:00:00.125 SeaLights - agent offset : 00:00:00.002 RFC function modules: All required RFC function modules callable Tables: All required tables readable SCMON Configuration: DEACTIVATE_ON: 20270101 SCMON is running and configured to stay active until 2027-01-01 SCMON_COLLECT callability: SCMON_COLLECT call succeeded ``` {% endcode %} ## Resolving Failures {% hint style="info" %} Each failure message includes guidance on what to fix. For detailed troubleshooting, see [Troubleshooting the ABAP Agent](/knowledgebase/setup-and-configuration/sealights-agents-and-plugins/abap-agent/troubleshooting-the-abap-agent.md). {% endhint %} Common failure scenarios: | Failure | Likely cause | Resolution | | ------------------------------------ | ----------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | 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](/knowledgebase/setup-and-configuration/sealights-agents-and-plugins/abap-agent/install-the-abap-agent/install-watcher-and-slabapcli.md). | | SeaLights ABAP add-on: Not installed | Add-on transport not imported | Import the SeaLights ABAP add-on transport. See [Install the ABAP addon](/knowledgebase/setup-and-configuration/sealights-agents-and-plugins/abap-agent/install-the-abap-agent/install-the-abap-addon.md). | | RFC function modules not callable | Missing S\_RFC authorizations | Regenerate the SeaLights authorization profile. See [Generate Authorization Profiles](/knowledgebase/setup-and-configuration/sealights-agents-and-plugins/abap-agent/install-the-abap-agent/generate-authorization-profiles.md). | | 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](/knowledgebase/setup-and-configuration/sealights-agents-and-plugins/abap-agent/install-the-abap-agent/configure-your-qas-systems-to-collect-scmon-data.md). | | Install directory access: ERROR | Permissions issue | Re-run the installer or manually grant NETWORK SERVICE read+execute on the install directory. | --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.sealights.io/knowledgebase/setup-and-configuration/sealights-agents-and-plugins/abap-agent/command-line-interface/validate-your-setup.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.