You are instructed to use the provided newer version and the traces it generates. We will not look at anything else.

Hi,Support:

There is another issue, I am not quite sure about the differences between the two versions.
 I directly used the current on-site version(QuickOpc 5.83.1043.1) and also enabled the interception log function(system.diagnostics). 
It seems that the internal interception logs are also very rich, 
and I did not find any special differences from the logs of the (OpcLabs. QuickOpc 5.85.0-rev0003) test version;

Simon.Yu
vskysoft.com
2026.5.29 11:33

Hello.

Ad 1) We will send you an evaluation license key, valid for 60 days (which can be renewed should the need arise), to the email address you used to register with the Online Forums. This will overcome the 30-minute runtime limit. Warning: Make sure to observe its end day, because at that date it will stop working.

Ad 2) Good.
Ad 3) OK.

Ad 4) Whatever happened with earlier version isn't of much use now, because of missing tracing.

Ad 5) Good.

Regards
 

Hi,Support:

After on-site release, several issues were identified and summarized as follows:
(1) After startup, it was found that there was a prompt for the demo version on the console, so it could only be a temporary test for a short period of time. Considering that the project needs to run stably, it is uncertain whether there is a problem of stopping the collection (demo version, which stopped collecting after using for 30 minutes before)
(2) According to the prompt you provided, trace logs have been enabled, and you can indeed see detailed logs in the trace directory with a lot of information content (enabled: system. diagnostics)
(3) The on-site testing time is relatively short, and there are currently no logs of large batches of rapid, continuous, and high-frequency disconnections as before
(4) Abnormalities that have been present for the past 1-2 weeks:
In multiple point subscriptions in an OpcServer, there are a few points where the signal is lost and the subscription cannot be made (value changes can be continuously subscribed through third-party tools). There are a few logs of disconnection reported in ServerConditionChange, but another event still receives value changes (easyUAClient. DataChangeNotification). However, other points in the same OpcServer server receive value change notifications normally;
(4.1) No special logs were found in the EasyUAClient. LogEntry event
(4.2) No relevant logs were seen for the HasBadStatus status change log of the monitoring target location
(4.3) The program on the customer's site has been rolled back to the previous version: 5.83. Temporary application layer logic monitoring has been added to determine the (3) problem and force the re creation of EasyUaClient isolated object instances for different IPs, and force re subscription to solve it;
(5) I plan to continue conducting in-depth testing in the early stages of another new project, and if there are significant findings, I will report them promptly

Simon.Yu
vSkysoft.com
2026.5.26 18:25

 

Hi ,Support:
I am glad to receive this letter,  I will put myself into testing first, and regardless of the results, I will provide timely feedback

Simon.Yu
vskysoft.com
2026.5.26 

Hello.We have implemented additional tracing into a pre-release version, available as OpcLabs.QuickOpc 5.85.0-rev0003 on nuget.org. For troubleshooting your issues, please rebuild with this version, and retest.In order to enable the tracing, you need to make some changes to you project. This can be seen in the example (Client-Instrumentation1), attached in zipped form to this form post. You need to: 

1. Make sure that configuration file, named <yourProgramName>.dll.config, is placed alongside the executable of your program (i.e. in the same directory). In the example project, this file is contained in the project itself, and configured with "Copy to output directory".
2. The contents of the file should be the same as it is in the example. The file essentially enables various tracing sources and options, and adds a Serilog trace listener.
3. Your project should contain initialization of the Serilog logger, as in the Program.cs. If the program is long running, make sure you configure a rolling interval, so that a new file is generated from tim to time (e.g. daily). We need the MinimumLevel to be Verbose, and the output template should be as in the example.
4. For the production run, make sure there is enough disk space - the trace files can be huge. Files are written to the "trace" subdirectory.

Regards

Hello.

This is to let you know that the version with enhanced tracing is in works, but it is not available yet. It will might be ready next week.

Regards
 

Hello,

it is of course unfortunate that new issues have emerged. We will proceed by extending the tracing/logging as planned, now also with extra focus put on the areas that can be related to these new issues. Please allow some days before we give you the new version and instructions.

Regards
 

Additional notes：

After switching to version 5.84, four machines were unable to subscribe normally, while the others were functioning normally;
```
opc.tcp://10.10.100.121:4840
opc.tcp://10.10.100.120:4840
opc.tcp://10.10.100.113:4840
opc.tcp://10.10.100.112:4840   
```
After rolling back to version 5.83, all machines can subscribe normally

Simon.Yu 
vskysoft.com
2026.5.12 17:29

Hi ,support:

today deploy and found Problem :
(1) use ver 5.84.192(2026.1) ,cann't subscrible tags,but OPC_Srv_ConditionChanged.log display "connected" ;
(2) use ver 5.83 ,can subscrible tags and received valueChanged;（But sometimes the machine fails to reconnect)

**Attachment document ： Bug.zip ** include log files

Simon.Yu
vskysoft.com
2026.5.12 17:24