Hi,
We recently updated our product from version 5.34 to 5.54 of QuickUAOpcClient. In the first installation for one of our customers, we observe the following strange behavior:
- When our program starts the first time, everything is working fine
- When we restart the program, the method BrowseDataNodes uses more than the 20 seconds we have allocated for this task. For this reason, the program fails to connect to the OPC Server. There are no exceptions, the program just 'hangs' on the call to BrowseDataNodes. In the initial start of the program, this call takes about 3 seconds.
The program is connecting to a local opc-server (phoenixcontacts). I am not able to reproduce this behavior on my machine where I currently use a Kepware OPC server. We did manage to reproduce it on a test-machine with the same setup as our customer. But after playing around with old and new versions, we were suddenly not able to reproduce the error anymore. Except for running both the old and new version, we did not do any changes.
My question is: What can the reasons be that makes 'BrowseDataNodes' take so long time on some machines (and even when it do happens, it does not happen every time we run the program)? It would seem like the OPC server does not respond in a timely manner, but there are no indications that it is in a bad state.
In some of the attempts we have seen an exception which basically says that it fails to create a file named bxsdk32.dll in C:\Windows. This exception does not come every time so I am not sure if this is related.
I will test with a version where I allocate more than 20 seconds to see if BrowseDataNodes is timing out or throwing an exception. But apart from this I am running out of ideas of what I can try. Any input is most welcome.
/Tor
We recently updated our product from version 5.34 to 5.54 of QuickUAOpcClient. In the first installation for one of our customers, we observe the following strange behavior:
- When our program starts the first time, everything is working fine
- When we restart the program, the method BrowseDataNodes uses more than the 20 seconds we have allocated for this task. For this reason, the program fails to connect to the OPC Server. There are no exceptions, the program just 'hangs' on the call to BrowseDataNodes. In the initial start of the program, this call takes about 3 seconds.
The program is connecting to a local opc-server (phoenixcontacts). I am not able to reproduce this behavior on my machine where I currently use a Kepware OPC server. We did manage to reproduce it on a test-machine with the same setup as our customer. But after playing around with old and new versions, we were suddenly not able to reproduce the error anymore. Except for running both the old and new version, we did not do any changes.
My question is: What can the reasons be that makes 'BrowseDataNodes' take so long time on some machines (and even when it do happens, it does not happen every time we run the program)? It would seem like the OPC server does not respond in a timely manner, but there are no indications that it is in a bad state.
In some of the attempts we have seen an exception which basically says that it fails to create a file named bxsdk32.dll in C:\Windows. This exception does not come every time so I am not sure if this is related.
I will test with a version where I allocate more than 20 seconds to see if BrowseDataNodes is timing out or throwing an exception. But apart from this I am running out of ideas of what I can try. Any input is most welcome.
/Tor
