We recently upgraded our Toad Data Point to version 4.3 (32 bit).
Following the upgrade of TDP 4.0 to TDP 4.3 (32 bit), I have encountered the following issue when running automations on my desktop.
The automation uses a single Export Wizard. The Export Wizard includes
- a query to extract data,
- the resulting data is sent to a .xlsm (macro enabled) excel spreadsheet,
- a single macro is kicked off in the spreadsheet.
When this automation is run on my desktop, it deletes the macro enabled spreadsheet. I then had this spreadsheet restored, and have tried to run the automation again with the same results (I now have a backup copy of my own so that I can test this automation). I have tried another automation with the same result. These automations worked fine prior to the upgrade to TDP 4.3.
The other puzzling thing is that when I remove the macro from the automation (the remaining operations include running a query and saving the data to the macro enabled spreadsheet), the automation runs normally and sends the data to the spreadsheet with no issues. Only when I include the instructions to kick off a macro within the automation, does the automation delete the excel spreadsheet. I have even revised the macro code within the spreadsheet to remove all vba functionality (only the macro begin and end statements remain), and the spreadsheet is still deleted.
This issue is of great concern as we cannot continue to allow the automation process to delete our spreadsheets.
The other extremely puzzling thing is that all of our automations that are published to run on TIC (version 4.3) have run normally with no issues. The issue only seems to occur when the automation is opened on my desktop and is run from my desktop.
The actual error message involves the file being used by another process, but results in the excel spreadsheet being deleted. The text of the automation notes are shown below:
– 2/7/2019 4:55:38 PM: Funding total today2.log: Setting up environment
– 2/7/2019 4:55:38 PM: Funding total today2.log: Script run by Toad Data Point 4.3.0.718 as jraguse on FFC-DESKTOP66
– 2/7/2019 4:55:38 PM: Funding total today2.log: Build started
– 2/7/2019 4:55:38 PM: Funding total today2.log: Compiling script
– 2/7/2019 4:55:38 PM: Funding total today2.log: Start CompileWorkflow
– 2/7/2019 4:55:38 PM: Funding total today2.log: Before Compile
– 2/7/2019 4:55:38 PM: Funding total today2.log: Return from CompileWorkflow
– 2/7/2019 4:55:38 PM: Funding total today2.log: Workflow Compiled without Errors
– 2/7/2019 4:55:38 PM: Funding total today2.log: Workflow Compiled has warnings
– 2/7/2019 4:55:38 PM: Funding total today2.log: Warning: No Exception Handler. To send an Email when there is an error, change the value of Email on Error to true and enter email values.
– 2/7/2019 4:55:38 PM: Funding total today2.log: Build completed
– 2/7/2019 4:55:38 PM: Funding total today2.log: Create Workflow instance
– 2/7/2019 4:55:38 PM: Funding total today2.log: Begin execution script activities
– 2/7/2019 4:55:38 PM: Funding total today2.log: Variable “ROOT_PATH” set to
– 2/7/2019 4:55:38 PM: Funding total today2.log: Started workflow instance
– 2/7/2019 4:55:38 PM: Funding total today2.log: Scanning the script for prompt bind variables
– 2/7/2019 4:55:38 PM: Funding total today2.log: Connection description = [connection info removed]
– 2/7/2019 4:55:38 PM: Funding total today2.log: Connection node found
– 2/7/2019 4:55:39 PM: Funding total today2.log: Connection to: [connection info removed]
– 2/7/2019 4:55:41 PM: Funding total today2.log: Running embedded export template
– 2/7/2019 4:55:41 PM: Funding total today2.log: Executing export using connection [connection info removed] is not XQuery Connection
– 2/7/2019 4:55:48 PM: Funding total today2.log: Export_1 - The process cannot access the file ‘S:\Automation\Daily Funding Total\Funding Totals.xlsm’ because it is being used by another process.
– 2/7/2019 4:55:49 PM: Funding total today2.log: Failed
Any ideas on how to resolve this?
Thanks. Jeff.