Test an ODBC connection in the product context#

When to use this procedure#

Use for ODBC actions and database-monitor events.

Applies to#

This procedure applies to EventReporter.

Prerequisites#

  • Use an account that can read the product configuration and Windows diagnostic state.

  • Replace angle-bracket placeholders with values from the affected system.

Safety#

  • Do not place passwords in command history, logs, or support archives.

  • Use a read-only query until connectivity is proven.

Configuration path#

Configuration Client > the service, rule, or action named on the Event ID page.

Procedure#

  1. Record provider/DSN, server, database, authentication mode, service account, and redacted connection fields.

    Expected result: The affected object and its effective settings are identified.

    If it fails: Return to the complete Event Log detail and configuration export before changing settings.

  2. Run the native Windows checks below from the affected product host.

    Get-OdbcDsn -Name '<DSN_NAME>' | Format-List Name,DsnType,Platform,DriverName

    Expected result: The provider exists in the correct bitness and a redacted test connection opens successfully.

    If it fails: Use the provider error to correct driver, DNS, port, database, TLS, credentials, or permissions.

  3. Perform one uniquely identifiable product test through the same service, rule, or action.

    Expected result: The intended destination records the test exactly once.

    If it fails: Collect the first new product event and bounded debug output; do not change unrelated settings.

Verify the result#

Repeat the affected operation, confirm its positive output, and verify that queues, collection positions, or remote delivery continue normally.

Evidence to collect#

  • The complete Event Log entry and neighboring product events with timestamps.

  • The command output, relevant configuration export, and bounded debug log from the same interval.