Toad World® Forums

TDA 3.1.0.638 Export Template Issue

I’m trying to create an export template to an Excel Macro-enabled worksheet - something that I’ve done several times before, all with the 3.1 beta because 3.0 wouldn’t work right.

All of a sudden, after I’ve selected the file that I wish to export to, and click save in the dialog box, TDA CPU usage jumps to 50% and the program locks up and doesn’t recover - the only way I can regain control is forcefully closing TDA from the Task Manager.

Any ideas? I really need to be able to do this - and I’ve tried it on three different PC’s with 3.1.0638 installed and they all have the same problem. I’ve successfully created and edited Export templates to Excel Macro-enabled workbooks before without any issue. I’ve restarted all PC’s involved and tried to see if that fixed the issue - no dice.

I’ve attached the two Excel templates that I was trying to use - I don’t see anything wrong with them.
01718 01723 09544 Daily DSR Sales - Pending & Completed.xlsm (46 KB)

Can you turn on verbose logging and reproduce the error? Then send the log files as well as the tas files? You can send directly to dpeabody@quest.com

Debbie

The issue is that TDA crashes/locks up before I even get a chance to finish creating the export template.

The issue happens as soon as I select the .xlsm file in the dialog box in the Export Wizard - I don’t get a chance to do anything else.

Debbie Peabody wrote:

Can you turn on verbose logging and reproduce the error? Then send the log files as well as the tas files? You can send directly to dpeabody@quest.com

Debbie

I see. I misunderstood you. Let me look into this.

Debbie

We’ve replicated the issue and have tracked the problem down to one of the 3rd party components we use to assist with reading and writing from certain Excel spreadsheets.

We’ve contacted them and have opened a support issue, as well as our own CR #98727 to track the issue and get it resolved.

Unfortunately, in the mean time this means you will have to go back to using TDA 3.0 in order to use those specific spreadsheets.

Please let us know if you have any other questions or concerns.

Thanks,
Mike Wilson
Quest Software

Unfortunately TDA 3.0 will not see the macros on an Excel spreadsheet - I went to using the 3.1 Beta for precisely that reason.

Also, I ended up opening a Support ticket (1024118) this morning and have been working with someone on it; they don’t seem to be aware that you’ve tracked this down.

I have found, oddly enough, that 3.1 will be fine if I’m trying to build a template to a sheet originally created in Excel 2007, but since modified in Excel 2010. The templates that it was crashing on originated in Excel 2010. Not sure if this is the source of the component issue or what.

Anyway, 3.0 won’t work for me as I could never, ever, get it to show me the Excel macros in a .xlsm file.

MikeWilson wrote:

We’ve replicated the issue and have tracked the problem down to one of the 3rd party components we use to assist with reading and writing from certain Excel spreadsheets.

We’ve contacted them and have opened a support issue, as well as our own CR #98727 to track the issue and get it resolved.

Unfortunately, in the mean time this means you will have to go back to using TDA 3.0 in order to use those specific spreadsheets.

Please let us know if you have any other questions or concerns.

Thanks,
Mike Wilson
Quest Software

I couldn’t ‘see’ the macros either. Installing the PIA file from Microsoft worked for me:

http://www.microsoft.com/download/en/details.aspx?id=3508

We’ve heard back from the developers of the component that is having the problem preventing you from loading the troubled spreadsheet in TDA 3.1. They are able to reproduce the issue and will get back to us shortly with an update on the situation.

For the TDA 3.0 issue, what version of Excel and Windows OS do you have on the machine you are running TDA from? I tested on a machine with Excel 2007 and TDA 3.0.1.1734 and I was able to ‘see’ the macros when attempting to export to one of your spreadsheets.

If you would like to go down the path of addressing the TDA 3.0 issue, please enable logging, perform an export (even without the macros being engaged) and send the logging output results to michael.wilson@quest.com. I suspect that this could be an environment issue with loading the office interop assemblies, so installing the Primary Interop Assemblies that planomax mentions might be a better first step (http://www.microsoft.com/download/en/details.aspx?id=3508). Keep in mind this is unrelated to the original issue of opening the spreadsheet.

–Mike

On a hunch, and after searching far and wide, I was able to confirm that this issue only appears to impact Excel Macro Workbooks originated in Excel 2010.

I tested the theory by re-creating from scratch the template files on a machine that had still had Excel 2007 (across the country too - remote desktop is slllooowww), and then trying to create the export template in 3.1 - and it worked just fine.

That said, I would greatly like to see 3.1 patched to fix this issue, as IT has told me that after next week, there will be no more Office or Excel 2007 installs, everyone will have moved to 2010.

MikeWilson wrote:

We’ve heard back from the developers of the component that is having the problem preventing you from loading the troubled spreadsheet in TDA 3.1. They are able to reproduce the issue and will get back to us shortly with an update on the situation.

For the TDA 3.0 issue, what version of Excel and Windows OS do you have on the machine you are running TDA from? I tested on a machine with Excel 2007 and TDA 3.0.1.1734 and I was able to ‘see’ the macros when attempting to export to one of your spreadsheets.

If you would like to go down the path of addressing the TDA 3.0 issue, please enable logging, perform an export (even without the macros being engaged) and send the logging output results to michael.wilson@quest.com. I suspect that this could be an environment issue with loading the office interop assemblies, so installing the Primary Interop Assemblies that planomax mentions might be a better first step (http://www.microsoft.com/download/en/details.aspx?id=3508). Keep in mind this is unrelated to the original issue of opening the spreadsheet.

–Mike

Thanks for the update, I’ve updated the CR with this information. Do you have Office 2010 installed on the machine you are using TDA 3.1 with? With Office 2010, if I open and save your original excel files, I’m able to open them with TDA, as long as I have Office 2010 installed. Not an ideal solution, but that might be worth experimenting with until we are able to resolve the issue.

We’re still waiting to hear back from the developers of the 3rd party tool we use for reading from Excel files regarding a fix or a workaround. Once we have that information, we’ll let you know the possibility of this issue getting patched.

–Mike

I do, but it still crashes for me, even with the InterOp assemblies installed. To be clear, TDA 3.1 crashes when trying to open an Excel Macro workbook created in Excel 2010 while attempting to create an export template.

I’ve now run into a separate issue with ghosting file locks that I’m not sure if it’s related or not, but it all ties back to these export templates and the automation script.

MikeWilson wrote:

Thanks for the update, I’ve updated the CR with this information. Do you have Office 2010 installed on the machine you are using TDA 3.1 with? With Office 2010, if I open and save your original excel files, I’m able to open them with TDA, as long as I have Office 2010 installed. Not an ideal solution, but that might be worth experimenting with until we are able to resolve the issue.

We’re still waiting to hear back from the developers of the 3rd party tool we use for reading from Excel files regarding a fix or a workaround. Once we have that information, we’ll let you know the possibility of this issue getting patched.

–Mike

Has there been any updates regarding getting the 3rd party component fixed?

My company has completed the removal of Office 2007, so I no longer have the ability to build compatible Excel macro workbooks.

We are hoping to have a fix for the 3rd party component by May 7, which should hopefully fix the issue. We’ll do our own internal testing, and at that point we will explore our options for what it would take to provide the fix for you.

Would you consider receiving a one-off build, which is a one-time build of TDA 3.1 with this included fix that has only been lightly tested by Quest?

–Mike

Yes, I’d be willing to accept it. I really just need it to be able to build the export templates (.txp files), that’s the only issue.

MikeWilson wrote:

We are hoping to have a fix for the 3rd party component by May 7, which should hopefully fix the issue. We’ll do our own internal testing, and at that point we will explore our options for what it would take to provide the fix for you.

Would you consider receiving a one-off build, which is a one-time build of TDA 3.1 with this included fix that has only been lightly tested by Quest?

–Mike

Have there been any more updates on this?

I’m needing to build a new report that uses an export template and do not have access to Excel 2007 any longer - and TDA still crashes on Excel 2010 macro-enabled workbooks.

We have received the fix and have created a one-off build which we are putting through a light QA test. We should have this finished in the next few days. Somebody from our support team should be reaching out to you shortly in order to further assist and coordinate getting this new build to you.

–Mike

I’m happy to report that the build appears to fix the issue with Export Template and Excel 2010 Macro workbooks.

I’ve got some additional testing to do, but I was able to successfully build an execute a template against an Excel 2010 macro workbook.

MikeWilson wrote:

We have received the fix and have created a one-off build which we are putting through a light QA test. We should have this finished in the next few days. Somebody from our support team should be reaching out to you shortly in order to further assist and coordinate getting this new build to you.

–Mike

Great news! We’re glad that the solution of providing a one-off build worked for you.

The issue will be fully resolved in TDA 3.5. If you, or others, run into similar issues prior to that release, including the up-coming release of TDA 3.2, please contact support so we can provide the fix.

Thanks,
Mike