Toad World® Forums

Macros not firing up from scripts published on TIC working fine with TDP

Hi,

I have a script that has an export activity followed with a macro, when I run this script from TDP , macro fire up. But when I run the same script after publishing from TIC, it ignores the macro and only export happens. I am using TDP 4.2 and TIC 3.3.

Hello vbvgpt,

What indicates to you that the macro was ignored? Is there some log entry missing after execution?

Could you please ensure that you have verbose logging enabled and then republish the script and get the execution log? (Automation script > Settings activity > Logging level dropdown > Verbose)

Martin

Hi,

Previously verbose logging was not enabled, I have enabled it now and have got some extra log entries, it says could not load excel assemblies, is it an issue with excel or Toad Data point.

  • 6/14/2017 3:41:00 AM: test.log: 3:40:58 AM Thread (18) Excel version = 12
    – 6/14/2017 3:41:00 AM: test.log: 3:40:58 AM Thread (19) DoneReadTreadWriter
    – 6/14/2017 3:41:00 AM: test.log: 3:40:58 AM Thread (19) Writing rows 0 - 15
    – 6/14/2017 3:41:00 AM: test.log: 3:40:58 AM Thread (19) Writing rows Finalize
    – 6/14/2017 3:41:00 AM: test.log: 3:40:58 AM Thread (19) Executing macros from Excel.
    – 6/14/2017 3:41:00 AM: test.log: 3:40:58 AM Thread (19) Loading Excel Assemblies
    – 6/14/2017 3:41:00 AM: test.log: 3:40:58 AM Thread (19) Trying Excel 2013
    – 6/14/2017 3:41:00 AM: test.log: 3:40:58 AM Thread (19) Could not load Excel 2013 assemblies, Could not load file or assembly ‘Microsoft.Office.Interop.Excel, Version=15.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c’ or one of its dependencies. The system cannot find the file specified.
    – 6/14/2017 3:41:00 AM: test.log: 3:40:58 AM Thread (19) Trying Excel 2010
    – 6/14/2017 3:41:00 AM: test.log: 3:40:58 AM Thread (19) Could not load Excel 2010 assemblies, Could not load file or assembly ‘Microsoft.Office.Interop.Excel, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c’ or one of its dependencies. The system cannot find the file specified.
    – 6/14/2017 3:41:00 AM: test.log: 3:40:58 AM Thread (19) Trying Excel 2007
    – 6/14/2017 3:41:00 AM: test.log: 3:40:58 AM Thread (19) Could not load Excel 2007 assemblies, Could not load file or assembly ‘Microsoft.Office.Interop.Excel, Version=12.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c’ or one of its dependencies. The system cannot find the file specified.
    – 6/14/2017 3:41:00 AM: test.log: 3:40:58 AM Thread (19) Trying Excel 2003
    – 6/14/2017 3:41:00 AM: test.log: 3:40:58 AM Thread (19) Could not load Excel 2003 assemblies, Could not load file or assembly ‘Microsoft.Office.Interop.Excel, Version=11.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c’ or one of its dependencies. The system cannot find the file specified.
    – 6/14/2017 3:41:00 AM: test.log: 3:40:58 AM Thread (19) Trying Excel 2002
    – 6/14/2017 3:41:00 AM: test.log: 3:40:58 AM Thread (19) Could not load Excel 2002 assemblies, Could not load file or assembly ‘Microsoft.Office.Interop.Excel, Version=10.0.4504.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35’ or one of its dependencies. The system cannot find the file specified.
    – 6/14/2017 3:41:00 AM: test.log: 3:40:58 AM Thread (19) DoneReadThreadWriter finally - adapter.RowsRead 15
    – 6/14/2017 3:41:00 AM: test.log: 3:40:58 AM Thread (4) END Query :
    – 6/14/2017 3:41:00 AM: test.log: 3:40:58 AM Thread (4) Object SQL Query finished.
    – 6/14/2017 3:41:00 AM: test.log: 3:40:58 AM Thread (4) Export Finished [6/14/2017 3:40:58 AM]
    – 6/14/2017 3:41:00 AM: test.log: 3:40:58 AM Thread (4) Export time = 00:00:00.6562255

Thanks for the log.

It seems that the server where TIC is installed does not have ms office installed - this is essential for macros to be executed and the ms office installation is not part of the TDP/TIC installation files. And i believe it’s a bug that there is no error message about this scenario however there is nothing to fix in terms of “missing office interop assemblies”

So the solution is to install ms office on the server.

Hope this helps,

Martin

thanks, that’s exactly what the issue was