Hello.
The example is in .NET, but the principles explained in the article relate to all environments.

Following I am proposing the steps to take in PHP. I have not verified them, but they should work. If you run into problems, let me know.

1. Determine the name and location of the executable that runs your PHP scripts. Depending on your solution, the name might be e.g. php-win.exe, php-cgi.exe, php.exe, or something else. Aldo, figure out where it is running from (the directory on the disk).

2. Download the attached MyApplication.Config.xml file.



3. Place this file to the directory where your PHP executable is, and rename it to the name (without extension) of your PHP runner, plus ".Config.xml". For example, if you were using php-win.exe, rename the configuration file to php-win.Config.xml.

4. Edit the configuration file as needed. In your case, locate the MaxStringLength element, and increase it to make it cope with the length of strings coming from the server.

5. Add following at the beginning of your PHP program:Best regards

Hello.

Look at this:

- opclabs.doc-that.com/files/onlinedocs/OPCLabs-OpcStudio/Late...plication%20Configuration.html

You need to include the XML file properly with your app. In case it is not clear from the comments in the examples source code: In the C# examples solution installed with QuickOPC, there is UANetSdkConfiguration project which shows it in full.

There is <MaxStringLength> setting in the example's XML file, and you can change it to a value that suits you well.

Best regards

Hello.

The BadEncodingLimitsExceeded can be returned for various reasons, such as:

- MaxMessageSize exceeded
- MaxStringLength exceeded
- MaxByteStringLength exceeded
- Maximum nesting level of InnerDiagnosticInfo exceeded
- MaxArrayLength exceeded
- general value nesting level exceeded

It is likely that the server is returning something large that it was not returning before.
In order to troubleshoot this, can you please:

1. Explain why you think this problem may have to do with insufficient stack.

2. Obtain the full .Message text of the exception (the […] indicates that there is more to it; you are showing what the default formatting gives, which is .ErrorMessageBried).

3. Obtain the exception call stack (.StackTrace).

4. Obtain the .InnerException (if not null), its .Message and its .StackTrace, and do that recursively for more inner exception if they are there.

Best regards