VBA Script Error creating TD object displayed in Excel.

Question ID: 109751
1
1

Hello. Some users are getting an error when attempting to execute a VBA script that was written to produce a Dashboard report. The following error is being thrown by Microsoft Excel: “Error creating TD object. Exiting”.  We tried removing the ALM client and reloading it fresh, but the error still occurs. Other users can run the script successfully. We ar currently using ALM v12.55 with a 64-Bit version of MS Office 365. I appreciate any information that you can provide.

Error that displays: Microsoft Excel – Error:Error creating TD object. Exiting

Marked as spam
Posted by (Questions: 216, Answers: 20)
Asked on July 31, 2020 12:06 pm
3 views
Answers (1)
1
Private answer

Hello. I would like for you to try the following on the affected machine. Open a 32-bit version of IE as an administrator. From the qcbin page, click on the 'Tools' link. On the 'Tools' page, you will need to click the 'ALM Connectivity' link, which will take you to the 'ALM Connectivity Tool' page, where you will need to click the 'Download ALM Connectivity' link. You will be prompted to either run the executable or save it to the desired location (Feel free to do either). After you have installed the 'ALM Connectivity Tool', you will then need to go back to the qcbin page, where you will click the 'Tools' link once again. On the 'Tools' page, you will now click the 'ALM Client Registration' link, which will take you to the 'ALM Client Registration' page. There you will need to scroll to the bottom of the page and click both the 'Register ALM' and 'Register ALM Site Administration' links.

Although Micro Focus lists MS Office 365 as being supported by v12.55, it does not specify 32 or 64-Bit. If the first suggestion does not resolve the issue, then I would then like for you to try changing your version of MS Office 365 to 32-Bit, and retest to see if the issue still occurs.

Marked as spam
Posted by (Questions: 2, Answers: 277)
Answered on July 31, 2020 12:19 pm
Thank you! We were able to resolve the error by changing our Office 365 install to the 32-bit version.
( at July 31, 2020 12:20 pm)