Troubleshooting Automation Script Failures on Toad Intelligence Central (TIC) (4382722)

After publishing an Automation script to Toad Intelligence Central, the script fails to run or completes with errors such as:

• Script succeeds locally but fails when run on TIC
• Automation stops at a specific step without clear messaging
• Exit code 555 returned during execution
• File read/write failures
• Database connection errors despite working locally

These issues typically surface after scheduling or executing the script from the TIC Script Manager. [support.quest.com], [support.quest.com]

Automation scripts run in the TIC server context, not the local user environment. Differences that commonly cause failures include:

• Missing ODBC drivers on the TIC server
• Use of User DSNs instead of System DSNs
• File paths pointing to local drives (C:) rather than network-accessible locations
• The TIC execution account lacking permission to databases, network shares, or FTP locations
• Expired trial or invalid Toad license (return code 555)
• Scripts referencing local storage snapshots or unsupported local resources

Quest confirms that automation execution requires the TIC server to have the same connectivity stack and access as the publishing workstation. [support.quest.com], [support.quest.com]

1. Check Script Logs

1. Open Toad Data Point
2. Navigate to View ▸ Script Manager
3. Select the published script
4. Open the Log tab
5. Identify the exact activity or step where the failure occurs

The Script Manager provides execution status, exit codes, timestamps, and detailed error messages for each run. [support.quest.com]

2. Enable Verbose Logging

• Edit the automation script in Toad Data Point
• Open Script Settings
• Change Log Level to Verbose
• Re-publish and re-run the script

Verbose logging provides deeper detail on connection attempts, file access, and execution context. [support.quest.com]

3. Verify Database and FTP Connections

• In Script Manager, open the Connections tab
• Confirm all connections:
  • Are valid
  • Use System DSNs, not User DSNs
  • Exist on the TIC server

The Deployment Guide explicitly states that ODBC drivers and DSNs must be installed and configured on the TIC host for automation execution. [support.quest.com]

4. Confirm ODBC Drivers Are Installed

Ensure the TIC server has the same ODBC drivers as the publishing machine.

When Toad Data Point is used to publish automation scripts, the Intelligence Central server must have the applicable database clients and ODBC drivers installed to execute them successfully. [support.quest.com]

5. Validate Execution Credentials

• Open Alter Schedule ▸ Run Details
• Verify the account used to run the script
• Ensure the account has:
  • Database access
  • Network share permissions
  • FTP/email permissions if used

Scripts often fail when executed under the default Local System account due to limited access rights. [quest.com]

6. Check File Paths

• Replace all local file paths (e.g., C:\Users\...) with UNC network paths
  • Example: \\FileServer\SharedFolder\output.xlsx
• Ensure the TIC execution account has read/write access

Quest documentation confirms that published scripts cannot reliably access local client file paths. [support.quest.com]

7. Verify License Status

• An exit code 555 indicates an expired trial license
• Apply a valid Toad license key to the TIC-installed Toad Data Point instance

Licensing is required even when Toad Data Point is installed automatically as part of the TIC deployment. [support.quest.com]

Common Issues & Solutions

Additional Notes

• Test automation scripts locally before publishing
• Ensure Toad Data Point is installed on the TIC server
• Confirm SMTP, Excel, and proxy requirements if used in the script

These are formal prerequisites documented in the TIC Deployment Guides for 2025 R2 and 2026 R1. [support.quest.com], [support.quest.com]