We have a Windows service application using QuickOPC v5.63.162 and are trying to connect to a remote OPC DA server which is the ArchestrA FSGateway product with its ProgID=ArchestrA.FSGateway.2 and CLSID={19d98a61-b3ca-4143-0088-35464d714ea0}. Our app supports the Intrinsic Component config within QuickOpc so below is our INI file showing the permutations of configuration changes attempted:
Along with manipulating the settings above, we have also tried giving QuickOpc the server descriptor which includes the ProgID only, CLSID only, and both the ProgID and CLSID of the OPC server. All of these attempts have resulted in us seeing the error "No method available to convert ProgID to CLSID (E_FAIL.0xC0049039)" in the data change event handler following the initial subscription attempt. When we set BrowseViaCategories=false and used the CLSID only I would have expected a different error since OPCEnum should not be used in this scenario; instead forcing a registry search for the CLSID we provided. This was not the case, and we received the same error in the subject of this post. Another interesting thing about the host machine our application lives on, is that the OPCEnum Windows service is in Manual mode but not running. Since we are connecting to a remote OPC server here, should we care at all about the state of the OPCEnum Windows service on the local machine?
Weirdly enough, there are two OPC clients (OPC Expert and the other from Integration Objects) on the same machine as our application, both "run as" the same account as our Windows service application which are able to connect and subscribe to items on the remote OPC DA server. Not sure where to go next since two unrelated OPC clients are working leading me to believe firewall, DCOM, and associated permissions are all correct.
Along with manipulating the settings above, we have also tried giving QuickOpc the server descriptor which includes the ProgID only, CLSID only, and both the ProgID and CLSID of the OPC server. All of these attempts have resulted in us seeing the error "No method available to convert ProgID to CLSID (E_FAIL.0xC0049039)" in the data change event handler following the initial subscription attempt. When we set BrowseViaCategories=false and used the CLSID only I would have expected a different error since OPCEnum should not be used in this scenario; instead forcing a registry search for the CLSID we provided. This was not the case, and we received the same error in the subject of this post. Another interesting thing about the host machine our application lives on, is that the OPCEnum Windows service is in Manual mode but not running. Since we are connecting to a remote OPC server here, should we care at all about the state of the OPCEnum Windows service on the local machine?
Weirdly enough, there are two OPC clients (OPC Expert and the other from Integration Objects) on the same machine as our application, both "run as" the same account as our Windows service application which are able to connect and subscribe to items on the remote OPC DA server. Not sure where to go next since two unrelated OPC clients are working leading me to believe firewall, DCOM, and associated permissions are all correct.