Professional OPC
Development Tools

logos

No method available to convert ProgID to CLSID

More
02 Dec 2015 09:27 #3712 by saravana48
I have restarted the TOP Server located machine and the error gone away. Thanks for the response.

Please Log in or Create an account to join the conversation.

More
18 Nov 2015 12:49 #3690 by support
Please do so. For example, TOP Server installation contains a "Quick OPC client".

Please Log in or Create an account to join the conversation.

More
18 Nov 2015 12:39 - 18 Nov 2015 12:48 #3689 by saravana48
Another OPC client application running on the same machine as Top server located is also written using QuickOPC 5.31 and VB.NET, it uses ProgID (SWToolbox.TOPServer.V5) to connect to the Top server and it is working fine.

I haven't tried with any other OPC client Software other than QuickOPC 5.31.
Last edit: 18 Nov 2015 12:48 by saravana48.

Please Log in or Create an account to join the conversation.

More
18 Nov 2015 12:29 #3688 by support
Thanks for the info. This, I think, remained unanswered:

Have you tried some other OPC client from the machine where your QuickOPC app resides, and what were the results?

Please Log in or Create an account to join the conversation.

More
18 Nov 2015 08:54 - 18 Nov 2015 09:57 #3687 by saravana48
Thanks for response,

1) Run as 64 bit process
2) Desktop Windows Forms
3) Run under administrator account.

Is there any way to find what's wrong with OPCEnum service?
Last edit: 18 Nov 2015 09:57 by saravana48.

Please Log in or Create an account to join the conversation.

More
18 Nov 2015 07:42 #3686 by support
One possible reason could be that something is wrong with the OPCEnum service.

Does your application run in a 64-bit or 32-bit process?
What kind of app is that (desktop Windows Forms, Web app, Web service, Windows service, etc.?) Which use account it is running udner?


You say that other OPC clients running on the server machine can use the ProgID without problems. Have you, however, tried some other OPC client from the machine where your QuickOPC app resides, and what were the results?

As a final note, something must have changed in your system anyway, I think you understand that just by itself this error would not start appearing.

Please Log in or Create an account to join the conversation.

More
18 Nov 2015 06:30 - 18 Nov 2015 09:56 #3683 by saravana48
Hello,

I am using OPC Labs QuickOPC 5.31 in VB.NET application to read the OPC tags from the Top server. The application and the Top Server are located in different machine. DCOM is configured in both machine.

I have used the ProgID (SWToolbox.TOPServer.V5) to connect the Top server.
EasyDAClient.ReadItemValue("Machine-PC", "SWToolbox.TOPServer.V5", "TagName")
It was working fine for past 3 months, now the application throws the errror.

Error : No method available to convert ProgID to CLSID.
ErrorCode: -1073442759

If I change the ProgID(SWToolbox.TOPServer.V5) to ClassId ({680dfbf7-c92d-484d-84be-06dc3deccd68}) to connect the TOPserver, it works fine.
EasyDAClient.ReadItemValue("Machine-PC", "{680dfbf7-c92d-484d-84be-06dc3deccd68}", "TagName")
Another Quick OPC 5.31 client application running on the same machine as Top server located, it uses ProgID (SWToolbox.TOPServer.V5) to connect to the Top server, it also working fine.

The error is only from the remote Quick OPC 5.31 client applications which are using the ProgID to connect the TOPServer.

Let me know the reason for the error?
Last edit: 18 Nov 2015 09:56 by saravana48.

Please Log in or Create an account to join the conversation.

Moderators: support
Time to create page: 0.197 seconds

      

 Recommend this on Google