Ranorex Forum

We recently upgraded to Office 365 and as part of that we now have Excel 2013. We find since we've installed it that if we try and change an excel connector or try and add one to a new project that the connector won't work. Ranorex will hang for a while and then give an error. I've attached a screen shot of that error to this message. The projects where we've not looked at their connectors are working just fine.

We will also receive the message that excel must be installed on our machine occasionally. We definitely have Excel installed.

We're running Ranorex version 4.0.30319.296 on a machine with windows 7 service pack 1. Have an intel core I7 processor 3.4 ghz and 8 gb of ram.

Thanks for your help

Hello,

It looks like a security issue with Office 2013.
Could you please try to set the 'Identity' of 'Microsoft Excel Application' to 'This user' (providing login data) in the 'Component Services'?
Please enter 'dcomcnfg' in the 'Search bar' in Windows and go to 'Microsoft Excel Application' in 'DCOM Config' (Component Services > Computers > My Computer > DCOM Config).

Please let me know if this setting solves your issue.
Thank you in advance.

Regards,
Markus (T)

That was the first thing we considered. Unfortunately Excel is not listed as one of the items, nor is it's address that it has in the registry so we are unable to adjust it's settings in dcom. Do you have any other suggestions?

Hello,

That's a bit strange that this item is not shown in the DCOM.
It seems that something went wrong during the installation of Office 2013.
This TechNet blog describes such an issue.

Could you please try to re-install Office 2013 with all features?

Regards,
Markus (T)

Somehow installing/uninstalling office 2007 and 2013 resulted in a missing registry key ( HKEY_CLASSES_ROOT\AppID\{00020812-0000-0000-C000-000000000046} )which I discovered while reviewing this site:
http://blogs.technet.com/b/the_microsof ... ap-in.aspx

The missing key caused Excel to not be available in DCOMCNFG. After importing the key and confirming the permissions (in regedit and DCOM), everything is working again.

Thanks for your help

Hello,

You are welcome

Regards,
Markus (T)