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 UA using PHP
This is a bug on our side. It comes, however, from an OPC Foundation code. In some cases, it attempts to strip off last 4 characters of the command-line argument zero, without considering all the possible cases. We will fix it in the upcoming QuickOPC version (2017.2). For now, there are workarounds:
1a. Use PHP.EXE to start the program, and not just PHP (in this case you do not have to put in the full path)
1b. Use the full path to start the program.
2. Add following at the beginning of your program:
I apologize for the inconvenience - and thank you once again for your help in finding the root cause.
Best regards
Please Log in or Create an account to join the conversation.
2. Start from CMD directly using just PHP (not php.exe).
Is this normal behavior? Hard links to these commands are impractical.
Please Log in or Create an account to join the conversation.
1) Are you trying to make some configuration using the .config (XML) file?
2) how are you starting the PHP? From the CMD, or some other way? If from CMD, how precisely? - Specifically, do you have just PHP at the end, or PHP.EXE?
Thank you
Please Log in or Create an account to join the conversation.
Please Log in or Create an account to join the conversation.
1) when the exception is thrown, you may get a little popup titled "Exception Thrown", and in it, there is a link that says "Copy Details". Click on it, and then send us the content of the clipboard.
2) In the Quick Watch window you have, select the "StackTrace" row, and then click the drop-down button at the right of it, and select "Text Visualizer". Then, send us the resulting text from the visualizer window.
3) When the exception occurs, Debug -> Windows -> Call Stack from the VS menu. Then, right-click inside the Call Stack window, select "Select All", and send us the content of the clipboard.
Thank you in advance, and best regards
Please Log in or Create an account to join the conversation.
We had selected 'System.ArgumentException' as instructed, but it is not breaking into a debugger (see this image link . I went ahead and added checkmarks next to the two exception types that we are seeing: 'System.ArgumentOutOfRangeException' and 'System.Reflection.TargetInvocationException'. With these checked, Visual Studio kicked into Break Mode with the following additional details:
- Imgur Link : System.ArgumentOutOfRangeException
- Imgur Link : System.Reflection.TargetInvocationException
Please Log in or Create an account to join the conversation.
The exception type seems to be slightly different from what I expected, although it is still a subtype of 'System.ArgumentAxception'. It is 'System.ArgumentOutOfRangeException' instead. Can you please make sure that this type is also explicitly checked in the Exception settings (Step 2 in the original instructions)?
Best regards
Please Log in or Create an account to join the conversation.
Please Log in or Create an account to join the conversation.
And, can you please disable "Just My Code": In Debug -> Options, General: uncheck the corresponding setting. It may also be worth enabling the "Use Manage Compatibility Mode"
Regards
Please Log in or Create an account to join the conversation.
Please Log in or Create an account to join the conversation.