Professional OPC
Development Tools

logos

Online Forums

Technical support is provided through Support Forums below. Anybody can view them; you need to Register/Login to our site (see links in upper right corner) in order to Post questions. You do not have to be a licensed user of our product.

Please read Rules for forum posts before reporting your issue or asking a question. OPC Labs team is actively monitoring the forums, and replies as soon as possible. Various technical information can also be found in our Knowledge Base. For your convenience, we have also assembled a Frequently Asked Questions page.

Do not use the Contact page for technical issues.

Connecting within SQL Server

More
10 Oct 2017 10:10 - 10 Oct 2017 10:11 #5585 by support
Here is the document (for users of QuickOPC 5.33+: OBSOLETE):


File Attachment:

File Name: QuickOPC-C...-COM.pdf
File Size:269 KB
Attachments:
Last edit: 10 Oct 2017 10:11 by support.

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

  • niels@opsdata.com
  • Visitor
  • Visitor
10 Oct 2017 10:06 #5584 by niels@opsdata.com
Replied by niels@opsdata.com on topic Connecting within SQL Server
I am using 5.31

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

More
10 Oct 2017 08:56 #5582 by support
The techniques described in the document you are asking no longer work with current QuickOPC version, and there is currently no replacement. So there is no need for that document any longer.

If you are on an old QuickOPC version, in this case 5.32 or earlier (I think it is unlikely), then you might have a reason to need this document, and in this case we can make it accessible to you.

Best regards

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

  • niels@opsdata.com
  • Visitor
  • Visitor
10 Oct 2017 07:15 #5581 by niels@opsdata.com
Replied by niels@opsdata.com on topic Connecting within SQL Server
Please advise where I can find the document "Accessing OPC from inside T-SQL (ODSOLE), using
QuickOPC-COM".

Thank you.

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

More
15 Aug 2014 11:31 #2162 by support
The example you are referring uses a COM component of the product (QuickOPC-COM). The default installation choice is for .NET development, so it likely that this was the reason.

Best regards

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

More
15 Aug 2014 10:52 #2161 by RickMerritt
I reinstalled the application using custom and selected virtually all the check boxes. It now functions without an error.

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

More
15 Aug 2014 10:08 #2160 by RickMerritt
I changed to 5.2 but it made no difference.

All I did yesterday was downloaded QuickOPC 5.31 from your site and ran the install
I added the OA procedures to SQL Server

Was there any additional steps required? I was able to run one of the .net examples and it worked correctly.

This is on a Windows Server 2008 R2 Enterprise computer

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

More
15 Aug 2014 07:57 #2159 by support
If you are using QuickOPC 5.2x or 5.3x (which is very likely), please change

'OPCLabs.EasyDAClient.5.1'

to

'OPCLabs.EasyDAClient.5.2'

This new ProgID of the component is documented in the manuals, but not all examples have been updated.

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

More
14 Aug 2014 21:02 #2158 by RickMerritt
I am using the information in the 'Accessing OPC from inside T-SQL (ODSOLE), using
QuickOPC-COM' document to try to get a stored procedure to access an OPC server.

I installed the OA Procedures as instructed. Whenever I try to execute this portion of the code:


EXEC @hr = sp_OACreate 'OPCLabs.EasyDAClient.5.1', @easyDAClient OUT, 4;

I get the error:
-2147221005
Msg 50000, Level 16, State 1, Line 13
Error Creating COM Component 0x800401f3, ODSOLE Extended Procedure, Invalid class string

Any idea on how to fix this??

Thanks

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

Moderators: support
Time to create page: 0.056 seconds