ExcelDataConnector stopped working

Ask general questions here.
Posts: 1
Joined: Mon Apr 29, 2013 8:00 pm

ExcelDataConnector stopped working

Post by callisl » Mon Apr 29, 2013 9:13 pm

UPDATE: I found the fix!!
See http://social.msdn.microsoft.com/Forums ... 4fd9c6b9fc
The registry was corrupted by the Office 2013 uninstall.
Workaround: Never uninstall Microsoft software, even if you don't like it :)
OS: Windows 7, 64bit
Ranorex Version:
ExcelDataConnectorPlugin listed in About
Excel 2013, 64 bit originally installed and used to create the current dataconnectors.

1) ExcelDataConnectors were originally working, connections were created and used
2) Excel 2013 has a different interface than required (need to use Excel 2007, 32 bit).
3) Office 2013 was uninstalled.
4) Office 2007 was installed successfully, updated and patched via windows update.
5) When starting Ranorex and attempt to create a new data connector, navigating to a 2007 excel file results in it not being recognized (worksheet list not displayed, worksheet and range grayed out/disabled).
6) Click OK results in the message "Excel is not installed. ExcelDataConnector requires Excel to be installed"
7) Selecting an existing ExcelDataConnector results in the Name and File Name to be correctly displayed but grayed out/disabled and results in the following error message:

"Unable to cast COM object of type 'Excel.ApplicationClass' to interface type 'Excel._Application'. This operation failed because the QueryInterface call on the COM component for the interface with IID '{xxxxxx,etc}' failed due to the following error: Library not registered. ..., etc. Exception (TYPE_E_LIBNOTREGISTERED).

It appears that the registry is still pointing to 64 bit (no library there now) and not to the 32 bit interface.

I'm totally dead in the water now..
Any help would be greatly appreciated.

User avatar
Support Team
Site Admin
Site Admin
Posts: 12145
Joined: Fri Jul 07, 2006 4:30 pm
Location: Houston, Texas, USA

Re: ExcelDataConnector stopped working

Post by Support Team » Fri May 03, 2013 1:59 pm


You solved this issue by deleting the Excel 2013 entry in the registry as written in your last email.

The registry was corrupted when Office 2013 was removed and 2007 installed.
Ranorex was using the 2013 entry instead of 2007.

Thank you for providing your solution.

Markus (T)