XamlParseException After upgrading from v4 to v6
Posted: Mon Jan 23, 2017 2:24 pm
Hi,
I am just starting the process of upgrading all of our Ranorex projects from v4.2 to v6.2.1.
The first issue I have encountered is with WPF where when searching for an object I get the following error -
System.Windows.Markup.XamlParseException: Creating an instance of the COM component with CLSID {7AB36653-1796-484B-BDFA-E74F1DB7C1DC} from the IClassFactory failed due to the following error: 80070005 Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED)). ---> System.UnauthorizedAccessException: Creating an instance of the COM component with CLSID {7AB36653-1796-484B-BDFA-E74F1DB7C1DC} from the IClassFactory failed due to the following error: 80070005 Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED)).
This works with no issue in v4 so must be a v6 specific issue or an upgrade issue.
I would appreciate any help in resolving this as we will not be able to upgrade to v6 until it is sorted out.
Even if you suggest reviewing our code, we still need to know where to start reviewing given that this isn't an issue using v4 of Ranorex.
Thanks
I am just starting the process of upgrading all of our Ranorex projects from v4.2 to v6.2.1.
The first issue I have encountered is with WPF where when searching for an object I get the following error -
System.Windows.Markup.XamlParseException: Creating an instance of the COM component with CLSID {7AB36653-1796-484B-BDFA-E74F1DB7C1DC} from the IClassFactory failed due to the following error: 80070005 Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED)). ---> System.UnauthorizedAccessException: Creating an instance of the COM component with CLSID {7AB36653-1796-484B-BDFA-E74F1DB7C1DC} from the IClassFactory failed due to the following error: 80070005 Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED)).
This works with no issue in v4 so must be a v6 specific issue or an upgrade issue.
I would appreciate any help in resolving this as we will not be able to upgrade to v6 until it is sorted out.
Even if you suggest reviewing our code, we still need to know where to start reviewing given that this isn't an issue using v4 of Ranorex.
Thanks