Professional OPC
Development Tools

logos

lupa

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.

OPC XML-DA. Communication problem

More
26 Aug 2019 05:54 #7655 by support
Replied by support on topic OPC XML-DA. Communication problem
Hello,
some thoughts on this:

1. We do not support Microsoft Windows Server 2008 R2 Enterprise in QuickOPC 2018.3. I think it likely is not the cause of the problem, but you should be aware of it.
2. I believe that the server should never return text/html, for SOAP requests. If the server encounters an error, it should still return text/xml, with proper error indication as specified by OPC XML-DA.
3. The error seems to be related to the GetStatus method call. We are (periodically) calling the GetStatus method. It is possible that the dOPC Explorer does not do it (although a compliant OPC client is required to do so), and that the method is not implemented or has a bug on the server side. We have a setting that should disable the GetStatus method call. I will send the necessary instructions in next post here. It might help (or not...)

Best regards

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

More
23 Aug 2019 13:26 #7653 by Andriy
Replied by Andriy on topic OPC XML-DA. Communication problem
Hi,
BTW, dOPC Explorer connects to the server without any problem.
OPC server vendor: Enercon OPC XML DA

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

More
23 Aug 2019 13:19 #7652 by Andriy
Replied by Andriy on topic OPC XML-DA. Communication problem
Hi,
I'm sure that url is ok.
1. xxx.xx.xxx.xx:6010
2. the server is on private network
3. I'm not sure I can open connection for you. This requires permission from the customer.

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

More
23 Aug 2019 13:01 #7651 by support
Replied by support on topic OPC XML-DA. Communication problem
Hello.

1. Are you sure you are connecting to the right URL? What is the URL of the server you are using?
2. is the server on private network, or publicly available?
3. If on private network, can the endpoint be made available to us (open the firewall for a specified source IP address), so that we can connect from our side, and diagnose?

Thank you

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

More
23 Aug 2019 12:52 #7650 by Andriy
Replied by Andriy on topic OPC XML-DA. Communication problem
Hi,

1. I'm using Connectivity Explorer 2018.3 (5.54.1085.1)
2. OS Name Microsoft Windows Server 2008 R2 Enterprise
3. I don't know who is a opc server vendor

The exception is attached

File Attachment:

File Name: exception.txt
File Size:16 KB


Best regards

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

    More
    23 Aug 2019 12:33 #7649 by support
    Replied by support on topic OPC XML-DA. Communication problem
    Hello,
    can you please provide additional details?

    1. Which version and build of QuickOPC are you using?
    2. Is it under .NET Framework or .NET Core?
    3. Which operaring system and version are you running the client on?
    4. What is the target OPC server (vendor, type).

    Thank you

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

    More
    23 Aug 2019 11:58 #7648 by Andriy
    OPC XML-DA. Communication problem was created by Andriy
    Hi,

    I can't communicate with OPC XML server. Can you help?
    I receive next error:
    OpcLabs.EasyOpcClassic E_FAIL
    Client found response content type of 'text/html; charset=utf-8', but expected 'text/xml'.
    The request failed with the error message:
    --

    <html>
    <head id="Head1"><t-itle>
    Error
    </title></head>
    <body>
    <div>
    An error occurred while processing your request.
    </div>
    </body>
    </html>

    --.

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

    Moderators: support, vaclav.zaloudek
    Time to create page: 0.149 seconds