Skip to content
English
  • There are no suggestions because the search field is empty.

Understanding the SDL AutoUpdater for SDL Desktop

Learn how the SDL AutoUpdater keeps your GeoClient software and department modules up to date without manual effort.

What is SDL AutoUpdater?

SDL AutoUpdater (SDL_AutoUpdater.exe) is a background utility that keeps your SDL GeoClient installation up to date. It connects to the SDL portal, checks whether any modules installed on your machine are out of date, and downloads the latest installers automatically — without requiring manual action from the user.


When does it run?

The AutoUpdater is launched automatically by GeoClient during startup. It runs silently in the background and does not require user interaction under normal circumstances.


What does it update?

The AutoUpdater checks and can update all installed SDL GeoClient modules, including:

  • GeoClient (core application)

  • Assessor

  • Clerk

  • Code Enforcement

  • Commerce

  • Construction

  • Engineering

  • Finance

  • Fire

  • Fire Prevention

  • Health

  • HealthPro

  • Historical Commission

  • Kiosk

  • Land Use

  • NFIRS

  • Parks & Recreation

  • Pet Licensing

  • Police

  • Public Works

  • Sewer Utility

  • Township Manager

  • Water Utility

Only modules that are actually installed on the machine will be evaluated.


How does it work?

  1. GeoClient calls the SDLUpdateService on local users machine on start-up.

  2. The AutoUpdater runs nightly at around 21:00 on clients server, contacts the SDL Portal to retrieve current version list.

  3. It compares the available versions we publish, against what is installed locally.

  4. If a newer version is found for any module, it downloads the corresponding installer.

  5. The updated installer is staged locally, ready to be applied.


Log file

The AutoUpdater writes a log file named AutoUpdate_SDL.log in the same folder where the application is installed. If something goes wrong during an update check, this file is the first place to look. Old log files are automatically cleaned up after 45 days.


Common issues

The update check did not run
The AutoUpdater requires a connection to the SDL portal. If the machine is offline or the portal is unreachable, the check will be skipped silently. No update will be applied, and GeoClient will continue to load normally.

A module did not update
If a specific module fails to update, GeoClient will still load. The AutoUpdater logs the outcome for each module — check AutoUpdate_SDL.log for details.

"Connection to the database has failed" message
If this dialog appears, it means the AutoUpdater could not connect to the local SDL database. Restart GeoClient. If the problem persists, contact SDL technical support or your IT department.


Force re-download

In some support scenarios, SDL technical staff may instruct you to force a full re-download of module installers. This is typically done by passing a specific flag when launching the updater and is not something end users need to do on their own.


Key Summary Points:

  • Purpose: The SDL_AutoUpdater.exe ensures your department stays compliant and secure by automatically delivering the latest features and bug fixes without requiring IT intervention.

  • How it works: Launches at startup, compares local versions to the SDL portal, and downloads updates automatically.

  • Scope: Updates core GeoClient and all installed modules (e.g., Construction, Pet Licensing, Police).

  • Troubleshooting: Maintains a 45-day log file (AutoUpdate_SDL.log) to track errors or connection issues.


For additional assistance, contact SDL technical support.