Diagnostic Tools and Technical Support
On this page
Alloy Navigator includes a set of Windows administrative tools for creating, upgrading, backing up, and restoring the database, importing data, and running and checking the Automation Server and its jobs. The installation also has a set of fixed and changeable operational limits, and support needs a defined set of evidence before an issue is escalated.
The administrative tool set
| Tool | What it is | Use it when |
|---|---|---|
Database Management (DbWizard.exe) |
A wizard for creating or upgrading a database and managing its Database Access Key. | A database must be created, upgraded, or its access key reissued. |
Database Backup/Restore (DbBackup.exe) |
A wizard that either backs up or restores one database. | A full backup or a restore is needed and no separate database-administration process exists. |
Import (ImportWizard.exe) |
45 per-class import forms over CSV and Excel sources, with reusable import profiles (.ipf files). |
Bulk data must be loaded, or an import profile replayed. |
Active Directory Import (ImportContacts.exe) |
The Active Directory import job executable; you can also run it by hand. | An Active Directory sync must be reproduced outside its schedule. |
Automation Server Manager (AServerMngr.exe) |
A control-panel applet for the Automation Server service, with Start, Stop, Restart, Resume, Change Account, Import Access Key, and Test Connection, and the startup account and connection the service uses. | The service does not start, or its database connection or startup identity must be checked. |
Web Configuration (WebCfgMngr.exe) |
Turns an installed web package template into an IIS application, and saves and restores that configuration across upgrades. | A web application must be created, repaired, or its settings recovered after an upgrade. |
| Connection Manager | Not a separate program: a dialog shared by the Settings App and the Import tool that holds named connections, each pairing an access key with a server, database, and technician identity. | A tool must be pointed at a different database, or a stored connection is wrong. |
Scheduled Task Agent (ScheduledTasks.exe) |
The job executable behind the Scheduled Tasks job. | A scheduled task must be run or reproduced outside its schedule. |
The Database Backup/Restore wizard connects to the master database of a named SQL Server with sysadmin credentials. It has no scheduling, no verification step, no retention, and no differential or log backups. It has no Start-menu shortcut and no entry in the Alloy Control Panel or the Settings App: start DbBackup.exe from the Bin folder under the installation folder. Starting it a second time on the same computer brings the open window to the front.
The web application setup runs Web Configuration with command-line verbs that each name the web application by its identifier: install:, uninstall:, save_settings:, and restore_settings:. Web Configuration also accepts check_uninstall: and config:, configures only the Web App, the Self Service Portal, and the API, and opens its window when it is started with install: or with invalid arguments.
The installer adds four shortcuts to the Start menu folder Alloy Software > Alloy Navigator 2026 > Tools: Automation Server, Database Management, Settings, and Import. The Import tool is installed as ImportWizard.exe in the same Bin folder, which on a default installation is C:\Program Files\Alloy Software\Alloy Navigator\Bin. The Alloy Control Panel also lists Settings, Database Management, Import, the Automation Server manager, and Web Configuration when their files are present; see Alloy Control Panel.
Under a Cloud license, the installer that the database distributes and the automatic upgrade use is the Administrative Tools package, which installs five tools: the Settings App, Import, Active Directory Import, the Scheduled Task Agent, and the Alloy Control Panel; see The Administrative Tools package.
The Knowledge Base Import Utility (KB importer) is not part of the product and is not installed with it.
Started with the F1 command-line parameter, the Settings App, the Import tool, the Automation Server Manager, the Database Management wizard, and the Database Backup/Restore wizard show each help link in a window captioned Open Help Topic before opening it. The window holds the link in an editable box: OK opens what the box then says, and Cancel opens nothing. How help links are built, and which tools follow the online help address, is described in System Performance, Attachments and Help.
Starting the Import tool, the Administrator right it checks when you sign in interactively, and its unattended command-line run are administrator tasks of the Import Wizard; see Import Data.
Run a job executable from the command line
Every job executable accepts the same command-line options, written as /NAME or /NAME=value:
/RUNID=names the job to run./ACCESSKEY=with the name of a stored access key supplies the credentials./SERVER=,/DATABASE=(legacy/DB=),/TESTCONNECTIONONLY, and/Log=are also accepted. A/TESTCONNECTIONONLYrun that succeeds leaves no log entry./LOGLEVEL=NORMALor/LOGLEVEL=DETAILED;DETAILEDturns on the verbose log.
/WINAUTH, /USER=, and /PASSWORD= are not read by any job executable: the credentials always come from the access key.
A job executable's exit code is one of a fixed set:
| Exit code | Meaning |
|---|---|
2 |
Failed to create the log |
3 |
Failed to connect to the database |
4 |
Failed to read the external source |
5 |
Processing error |
6 |
The logging engine is not installed |
11, 12, 13 |
Windows sign-in failure: logon failure, privilege not held, or logon type not granted |
101 |
The Automation Server force-terminated the process |
102 |
The Automation Server terminated the process on the hang timeout |
Exit code 1 is not one of the product's codes; Windows returns it when the process is ended from Task Manager.
Before a tool writes its command line to the log header, it removes the credentials from it, so the header shows the invocation and the tool's version and build without a credential. The Outgoing Notifications log has no such header.
History and audit rows that a tool writes name a fixed service identity, not a technician: Automation Server, Mail Connector, Alloy Discovery Integration, Active Directory Integration, Archiving, Scheduled Reports, Self Service Portal, Import Wizard, Alloy Navigator API, Scheduled Task Agent, or AlloyScan.
Operational limits
For the operational limits of Alloy Navigator and the attachment size limit, see System Performance, Attachments and Help.
Database maintenance
The database schema includes Ola Hallengren's IndexOptimize procedure for index and statistics maintenance.
In a new 2026.1 database created with the Default Workflow (see Default Workflow Configuration), the scheduled task Integrity Check, and Index and Statistics Maintenance calls that procedure three ways: it reorganizes indexes above 15 percent fragmentation, updates all statistics with a 100 percent sample for modified objects only, and runs an offline rebuild pass. The task is disabled in the supplied configuration, with a weekly schedule at 01:00, so no index maintenance runs until it is enabled; see Scheduled Tasks. Two further supplied tasks, Maintenance: Delete 'x' Year Old Attachments and Maintenance: Delete 'x' Year Old History, control the growth of attachments and object history. An upgraded database need not have these tasks, and an administrator may have changed them.
SQL Server error messages
In the Settings App, the Database Management wizard, the Import tool, the Database Backup/Restore wizard, and the Automation Server Manager, an error that SQL Server raises is shown as "SQL Server replied:" with SQL Server's own message under it. The text after this prefix is SQL Server's answer, not a message of Alloy Navigator. When the error comes with the statement that failed, it opens in an extended window that shows the SQL text under Details.
Some places word the prefix differently: the Automation Server in a job's report, License Management in the Settings App, and the Import tool in its log write "SQL Server reply:", and the Database Management and Database Backup/Restore wizards write "SQL server reply:".
A few errors are reported in a message of their own, without the prefix:
- An object that other database objects refer to cannot be deleted or changed: the message reads "Unable to delete/modify object because it is referenced by other database object(s). …", with SQL Server's text under Details.
- The OLE DB provider is missing.
- The connection fails while a Database Access Key is in use.
In the Settings App, when SQL Server refuses to delete a classification category, for example one that still has subcategories, SQL Server's message is shown alone, without the prefix.
Two examples of SQL Server messages that can follow the prefix:
- A message about the current security context: the SQL Server account that the tool connects with has no access to the database.
- "Invalid column name": the statement names a column that the database does not have, for example a user-defined field that has been deleted.
In the Admin Center, the prefix appears only on an error that a database trigger raises, and the trigger's message follows it.
When you report such an error, include the full text of the message, including its Details, together with the evidence listed in Before you escalate to support.
Before you escalate to support
Collect the following, in this order, before you open a support case:
- The edition, licensed modules, deployment, and seat model, from General > License Management in the Admin Center.
- The build of every application involved (Web App, Self Service Portal, API, Settings App, Automation Server), for example from the API default page or from the tool log header of a recent job run.
- The database's schema version, from the
VersionDBandProductrows of the database'scfgInfotable. - System Log rows for the incident window, with their occurrence counts and first and last occurrence, from the System Log under All Errors in the Settings App or the Admin Center. The System Log merges events with the same message text into one row, so one row can stand for many events.
- The failing job's tool-log session rows (
cfgToolLogs) and its job history rows (cfgJobHistory), queried from the database and not only read in the job history dialog. The dialog shows only finished runs and hides runs left awaiting or executing, and job history can be empty on any system, so an empty result does not prove that nothing ran. - The full content of the tool log for the failing run, from the tool's Logs node or the tool log details in the Admin Center. It contains the invocation, the build, and the run's own errors.
- A re-run of the job executable by hand with
/LOGLEVEL=DETAILED, and its exit code. Detailed logging is off by default, and the exit code names the failure class. - Workflow log rows for the affected object, with their operation and e-mail child rows, from the workflow log. By default this log keeps 7 days and records only errors, so this evidence expires first.
- The retention setting in effect for every log you cite, to establish whether missing evidence was purged or never written. See Logs.
- Whether the Automation Server was running throughout the window, from the state of the service and from gaps in job history. While it is stopped, jobs do not run and no log is purged.
- The Administrative Dashboard's issue items, in the Admin Center or the Settings App; see Administrative Dashboard. In a new 2026.1 database created with the Default Workflow, these items bring the backup gap, failed jobs, license expiry, and a workflow-logging warning together in one place. The warning reads "Logging all workflow events may slow you down" and appears when the workflow log is set to record every execution, not only failed ones.
- The date and outcome of the last full database backup, from the SQL Server backup history (
msdb.dbo.backupset), which determines whether a restore-based recovery is available. In a new 2026.1 database created with the Default Workflow (see Default Workflow Configuration), an Administrative Dashboard item also reports this gap with "You have not backed up the database for %s days" once the last full backup is more than 30 days old. When no full backup was ever taken, it counts from the date the database was created, so it stays silent for the database's first 30 days. An upgraded database need not have this item, and an administrator may have changed or removed it. - For a data-loss report, the Deleted Objects log rows for the window. This log keeps 999 days by default, so unless its retention has been shortened the evidence is usually still present.
- For an archiving report, the archiving job's options and the archive database's name and version, from the
cfgArchivingJobOptionsandcfgArchiveDatabasestables, to tell an archived object from one that was removed without archiving. - Any customization of the items above, from an export of the workflow configuration. Dashboard items and maintenance tasks are supplied content and may have been edited or removed.
Do not include credentials, access-key data, or license serial numbers in a support case. A database backup does not belong in a support case either, because it carries the whole customer dataset.