> 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-2.0/command-line-interface/validate-your-setup.md). # 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 {% hint style="warning" %} **New install?** `setup status` requires `config.toml` to already exist. If you see `Config file does not exist`, `slabapcli setup install` hasn't been run yet — complete [Set up the agent](/knowledgebase/setup-and-configuration/sealights-agents-and-plugins/abap-agent-2.0/command-line-interface/set-up-the-agent.md) first, then come back to validate your setup. {% endhint %} ## 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 executables | The required binaries (`watcher.exe`, `purger.exe`) are present in the executable directory. | | ProgramData access | Read+write access for operator and NETWORK SERVICE on the config, public userdata, private userdata, and watcher logs directories under `%ProgramData%\Tricentis\SeaLights\ABAP Agent`. Reported as "ProgramData config access", "Public userdata access", "Private userdata access", and "Watcher logs access". | | 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. The same checks run for every RFC Destination, including your Production system. | 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. | | Authorizations | Checks that the configured SAP user has the SAP authorizations the agent needs. Lists any that are missing. | | Required tables in DDIC | Checks that all SAP tables the agent reads exist in the ABAP Dictionary (DDIC). Lists any that are missing. | | 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 In the Agent section, each check line uses a status indicator: * **OK** (green), shown after the check name (for example, `Task Scheduler: OK - service is reachable`) — check passed * **Error:** (red), shown at the start of the line as `Error: - ` — check failed; action required * **INFO** — informational note (e.g., leftover permissions from an older install) In the RFC destinations section, passed checks are shown in green, a failed check starts with `Error:` (red), and a check that could not be completed starts with `Warning:` (yellow). The command exits with code `0` if all checks pass, or `1` if any check fails. {% hint style="info" %} **Production RFC Destinations:** If the SeaLights add-on is not used on Production (`useaddon = false`, the default), the add-on and SCMON checks fail on the Production RFC Destination. The failures are shown in red and `setup status` exits with code `1`. This is expected, and you can ignore those failures for the Production RFC Destination in that case. See [Production usage data source](/knowledgebase/setup-and-configuration/sealights-agents-and-plugins/abap-agent-2.0/configuration-settings.md#production-usage-data-source). {% endhint %} ## Example Output {% code title="Successful run (abbreviated)" overflow="wrap" %} ``` == Agent == Agent version: 2.1.2.175 Detected Windows version: Windows Server 2022 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 purger.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: S21 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 Authorizations: All required authorizations present Required tables in DDIC: All required tables present in DDIC 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-2.0/troubleshooting-the-abap-agent.md). {% endhint %} Common failure scenarios: | Failure | Likely cause | Resolution | | ------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Config file does not exist | `setup install` has not been run yet | Run `slabapcli setup install` to create `config.toml`. See [Set up the agent](/knowledgebase/setup-and-configuration/sealights-agents-and-plugins/abap-agent-2.0/command-line-interface/set-up-the-agent.md). | | Error: sapnwrfc.dll - missing at | SAP NW RFC SDK not installed | Re-run the installer and point it to the SAP NW RFC SDK DLL. See [Install WATCHER, SLABAPCLI and Server](/knowledgebase/setup-and-configuration/sealights-agents-and-plugins/abap-agent-2.0/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 add-on](/knowledgebase/setup-and-configuration/sealights-agents-and-plugins/abap-agent-2.0/install-the-abap-agent/install-the-abap-addon.md). Expected on a Production RFC Destination that does not use the add-on (`useaddon = false`); ignore it in that case. | | Authorizations: Missing authorizations | Missing SAP authorizations for the RFC user | Regenerate the SeaLights authorization profile. See [Generate Authorization Profiles](/knowledgebase/setup-and-configuration/sealights-agents-and-plugins/abap-agent-2.0/install-the-abap-agent/generate-authorization-profiles.md). | | Authorizations: Required authorization check could not be performed | The agent could not read the RFC user's authorization profiles (for example, no profile is assigned to the user, or reading the SAP authorization tables is denied) | Assign the SeaLights authorization profile to the RFC user, or regenerate it. See [Generate Authorization Profiles](/knowledgebase/setup-and-configuration/sealights-agents-and-plugins/abap-agent-2.0/install-the-abap-agent/generate-authorization-profiles.md). | | Required tables in DDIC: Tables not in DDIC | One or more SAP tables the agent needs were not found in the ABAP Dictionary of that system | Verify that the RFC Destination points to the intended SAP system. If the tables should exist there, contact SeaLights Support with the listed table names. | | 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-2.0/install-the-abap-agent/configure-your-qas-systems-to-collect-scmon-data.md). | | Error: Install directory access | Permissions issue | Re-run the installer or manually grant NETWORK SERVICE read+execute on the install directory. | | Error: Required executable | The agent installation is incomplete, or `slabapcli` runs from a folder other than the installation `bin` folder | Re-run the installer, or run `slabapcli` from the `bin` folder of the installation. | | Error: ProgramData config access (also Public userdata access, Private userdata access, Watcher logs access) | Permissions issue | Grant NETWORK SERVICE read+write access to `%ProgramData%\Tricentis\SeaLights\ABAP Agent`. | --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.sealights.io/knowledgebase/setup-and-configuration/sealights-agents-and-plugins/abap-agent-2.0/command-line-interface/validate-your-setup.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.