If you encounter an issue when publishing an Automation script or when attempting to run a published script on the Toad Intelligence Central (TIC) server, review the following to help diagnose and resolve the issue.
For issues related to the default user account used to execute scripts on Intelligence Central, see Default Account for Script Execution.
Note: This feature is available in the Toad Data Point Professional edition only and requires access to a Toad Intelligence Central server.
If you encounter an error message after you click Publish in the Wizard bar (Automation window), review the following table to find a description of your issue and a solution.
| Message | Issue Description and Solution |
|---|---|
| "This automation script contains one or more connections that are not supported by Intelligence Central. Please modify or remove the following connections before publishing: <connection name>" |
Toad cannot publish a script containing one of the following connections to a local data source:
Solution: Modify or remove the connection before publishing the script. For example, consider moving the data source to a network location. A network connection to an Access database or Excel file is allowed. |
| "A published Automation script cannot refresh a snapshot in Local Storage. Your script cannot be published because it contains the following activities that refresh a snapshot: <activity name>" |
The script contains an activity that refreshes a snapshot in your Local Storage database. A published script cannot support a connection to a local data source such as your Local Storage database, so Toad cannot publish the script. Solution: Please remove or modify the activities that refresh a Local Storage snapshot before publishing. |
| "We do not currently support publishing automation scripts that utilize Toad Views. Please replace the following Toad View with its SQL before publishing: <Toad View name>" |
You cannot publish a script that includes a Toad View. Solution: Please replace the Toad View in the SQL statement or script with its corresponding SQL before publishing. |
| When attempting to publish or run a script, it fails to run and you encounter a "endpoint listening" error |
If Intelligence Central is running in a Windows 7 or Windows Server 2008 environment, you might need to activate Windows Communication Foundation (WCF). Solution: Turn on Windows Communication Foundation through the Control Panel. In Windows 7: Go to Control Panel | Programs and Features | Turn Windows features on or off | Microsoft .NET Framework. Then select both checkboxes to enable Windows Communication Foundation. In Windows Server 2008: Go to Control Panel | Administrative Tools | Server Manager | Features | Add Features. On the Select Features page, expand .NET Framework features. Select WCF Activation to enable Windows Communication Foundation. After enabling Windows Communication Foundation, make sure ports 8066 and 8067 are open. |
| "The Automation script cannot be published because it uses one or more macro-enabled Excel files (.xlsm) that are stored locally." | You cannot publish a script that uses a macro-enabled Excel file (.xlsm) that is stored locally. Move the file to a network location and modify the script to include the network file path. |
It is recommended that you instruct Toad to test run your script during the publishing process to uncover any issues such as missing input files or connections that are not properly set up on the TIC server.
To instruct Toad to test run your script during publishing
You can use the messages found in the Automation script execution log (and Toad error messages) to troubleshoot issues that arise during the script publishing process or during subsequent script executions.
To view script logs for scripts executed in Intelligence Central, open the Script Manager, select the script, and then select the Log tab.
A connection error message begins with the following:
"During publishing, the following connections in the Automation script failed (use the error message to troubleshoot the issue):"
The remainder of the message includes the error message which will help you pinpoint the issue. Review the following for additional information:
| Error Message | Issue Description and Solution |
|---|---|
| "Can not obtain Oracle client information from registry. Make sure that Oracle Client software is installed, or use Direct mode of connecting to server." |
Toad cannot find the Oracle Client. Solution: Make sure that an Oracle Client software is installed on the TIC server. |
| "Server did not respond within the specified timeout interval." |
Oracle connection: If the error involves an Oracle connection, ensure that an entry for this connection exists in the TNSnames.ora file. |
| "Data source name not found and no default driver specified." | For ODBC connections, verify that the system DSN name also exists on the TIC server and that it matches the system DSN name you have defined on your local computer. |
| "The alias name of this database was not found in the database directory." | DB2 connection. Ensure that an entry for the DB2 connection exists in the DB2 catalog on the TIC server. |
|
A log on error, for example: "ORA-01017: invalid username/password; logon denied" |
You might encounter this error message with an Oracle connection, or a similar message for another connection type, if the password for the connection changed. To learn how to update the password for a connection in a script running on Intelligence Central, see Change Passwords for Intelligence Central Objects. |
| Message | Issue Description and Solution |
|---|---|
| "The file was not available at run time. The location and user authentication may be different at run time." |
One or both of the following might be true:
Solution:
|
| "The original Excel file <filename.xlsm> does not exist." |
If your script uses a macro-enabled Excel file (.xlsm), ensure the file exists in the location specified in the script. Toad cannot create a missing macro-enabled Excel file. An Excel file containing macros must be created by the user. A macro-enabled Excel file used by a script must be stored in a network location, not locally. |
| Message | Issue Description |
|---|---|
| "Exit code was inaccessible" |
Toad was unable to retrieve the exit code. This error does not involve script execution and most likely occurs after script execution. Review the Log tab for details about the run, or re-run the script. |
| "Toad could not load or compile the script" | The script might not be compatible with the version of Toad used to run the script on Intelligence Central. An exit code of 222 is returned. |
| "The user account specified to run this script on a server is not configured to execute macros in Excel." | The script executes a macro-enabled Excel file and the account used to run the script is not configured to run macros on the server. See Using Macro-Enabled Excel Files for steps to resolve server-side Excel automation issues. |
If you encounter an issue with the execution of a scheduled Automation script in Intelligence Central, the issue might involve scheduling. Use the following information to help troubleshoot the issue.
| Issue | Issue Description and Solution |
|---|---|
| Toad Data Point Trial license key expires in TIC environment |
When Toad Data Point is installed with Intelligence Central, Toad uses a Trial license key. If this key expires and no other license is active, scheduled scripts fail to run on TIC. Troubleshoot: Determine the return code for script execution:
Solution:
|
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. Feedback Terms of Use Privacy Cookie Preference Center
