Automation error Library not registered.

RE: Automation error Library not registered.

Aparna M — Wed, 09 Aug 2017 12:37:27 GMT

Having multiple versions of office is not a typical or common scenario. Most of the machines have a single version of office. All our machines here have only one office version installed (my case it is office 365 64 bit).

RE: Automation error Library not registered.

Emmanouil Zervas — Wed, 09 Aug 2017 09:15:45 GMT

Thank you for your response!

Apparently after some triaI and error tests I found that the export can happen normally to a computer with only one office version installed. I am not sure if this is the real reason but the export worked in another computer where this was the case.

So, I am ok for now but it might be useful to investigate this issue, so that import/exports can work flawlessly. If you could do some research and let me know if the conflict is really due to existence of multiple office versions, or, if not, the real root cause of this issue, that would be nice.

Thank you in advance!

RE: Automation error Library not registered.

Aparna M — Tue, 08 Aug 2017 17:53:45 GMT

Hello Emmanouil,

After performing the same steps by step procedure you have explained, the excel export was successful. This was done in latest version of gINT 10.00.00.50

- created a new blank gpj using gINT std ags 4_0.gdt (used gINT std ags 4_0.glb)

- File>Import Export>Export to Excel.

- Selected excel file, all tables. Toggled structure only and captions.

I can try the same with your set of files. If so please email the files to aparna.matange@bentley.com