Skip to content

DB Integrator Operations

The DB Integrator is the on-prem component that processes integrations (including incoming mail) against the Halo database. It runs on the Application Server, usually on a schedule through Windows Task Scheduler. This page covers the two operational tasks that come up most: confirming its version and troubleshooting failed runs.

Canonical reference

The HaloITSM vendor guides (usehalo.com/haloitsm/guides) are the canonical reference for DB Integrator behavior -- see "DB Integrator - Troubleshooting" and "Checking your DB Integrator Version". This page summarizes the operational essentials for GRC-ITSM on-prem deployments.

Checking the DB Integrator version

The integrator executable is bundled with the Halo app upgrader files, but it is not automatically updated if the executable has been moved from its default location. After any Halo upgrade, confirm the integrator matches the WebApp and database version:

  1. Open Task Scheduler and locate the task(s) that run the integrator -- Task Scheduler is the authoritative pointer to where the executable actually lives.
  2. Open the task's Actions tab to find the executable's folder.
  3. Navigate to that folder and run the integrator; the version is displayed in the application.

A version mismatch between the integrator, WebApp, and database is a common cause of post-upgrade errors referencing database tables or columns.

Troubleshooting failed runs

First checks

  • Credentials: are the credentials in the DB Integrator correct, and do they survive a save-close-reopen cycle? Can you validate the connection from within the integrator?
  • Version: is the integrator on the same version as the database and WebApp (see above)?

Running the integrator manually

Two ways to force a run when diagnosing:

  • Via the application: DB Integrator > Processing tab > select All or a specific integration (incoming mail is the usual suspect) > Start.
  • Via Task Scheduler: Task Scheduler Library > select the integrator task > Run.

If manual runs succeed but scheduled runs fail, check which account the scheduled task runs as -- this is typically a Windows permissions issue on the task's user account.

Email module not processing

If the incoming-mail integration is selected but nothing processes, confirm the email module is enabled for the integrator (Config > Advanced in the agent application). On the database side you can verify with:

select mshalointegratorenabled from modulesetup where msid=5

If it returns false, enable it and refresh the cache from the agent application:

update modulesetup set mshalointegratorenabled=1 where msid=5

Connection error: TdsParser type initializer exception

The error "The type initializer for 'Microsoft.Data.SqlClient.TdsParser' threw an exception" (inner exception referencing SNILoadHandle) is usually an incomplete SQL client installation on the server. Resolve by placing Microsoft.Data.SqlClient.SNI.dll in the integrator's folder:

  1. Download the microsoft.data.sqlclient.sni package from nuget.org.
  2. Rename the .nupkg to .zip and extract Microsoft.Data.SqlClient.SNI.x64.dll from build\net462.
  3. Place it in the integrator folder and rename it to Microsoft.Data.SqlClient.SNI.dll (dropping the .x64).

Decryption check failed

The "Decryption check failed" condition relates to the API certificate and integrator availability -- see the guidance in Upgrading the Host OS, which covers when the integrator can safely be stopped.