22:35, EET
January 9, 2018
Good day,
I’m currently using Prosys Sentrol 6.7.1.
A few years ago I wrote an OPC client and server using Sentrol SDK. Client and Server run locally on the same PC. Everything has worked fine.
Recently, on 2 systems, I have run into connection issues. The initial indication was that OpcEnum was not functioning properly although it was installed and shown as running. The OPC browser was not able to retrieve the installed OPC servers. I uninstalled all OPC related software and then reinstalled. The browser now shows installed servers but connection issues persist.
As part of the debug, I installed the Prosys test client and servers to observe how they would behave. What I found is that the Prosys Client (2.0.0.4) can connect to the Prosys Simulation server (Prosys.OPC.Simulation 1.7 Build21) but it cannot connect to the simulation server running as a service (Prosys.OPC.Service). The received error is “Cannot connect to OPC Server \\localhost\Prosys.OPC.Service: Interface IOPCServer not supported: Access is denied.” This is the same error I receive when attempting to connect my client to my server.
Oddly, I’ve found that a test client from Exele will connect to all servers without issue.
All suggestions for trouble shooting this are appreciated. I have a customer with a machine ready to ship once this is resolved.
Thank you.
14:03, EET
December 21, 2011
This sounds like a DCOM configuration issue (‘Access denied’ is a clear indicator). So, please, verify the DCOM settings, which may have changed in the Windows updates. Also, for the service version, check the properties of the service, especially the user account under which the service runs.
BTW: Which Windows version are you running at?
21:54, EET
January 9, 2018
Ok. I’ve seem to have exhausted my capabilities determining any issues with the DCOM settings and have not found anything. I also contracted OPC Training Institute to review the situation and they were not able to detect any DCOM configuration issues. They currently believe the issue possibly has something to do with an incorrect server installation procedure.
Since the issue presents itself when just using the ProSys client and the Prosys service server, I would like to focus on debugging that issue. This message is displayed by the Prosys Client when trying to browse for servers: “Could not connect to OPCEnum service at ‘localhost’: Interface IOPCServerList not supported: Access is denied.”
If I enable the Registry option of the client and refresh the server list, all installed servers are displayed. The client is able to connect to and display data from ProSys.OPC.Simulation. It cannot connect to ProSys.OPC.Service. When attempting to do so, this message is received: “Cannot connect to OPC Server \\localhost\Prosys.OPC.Service: Interface IOPCServer not supported: Access is denied.”.
An odd thing is that some clients seem to be able to connect and receive data from ProSys.OPC.Service and some cannot.
The service is running under the System account. The clients I am running are running under my local account which has Admin privileges.
The computer is Windows 10 Pro Version 1709.
How do you suggest I proceed to troubleshoot connection to the server? Thanks in advance.
17:02, EET
April 17, 2013
16:12, EET
January 9, 2018
19:38, EET
January 9, 2018
Thus far, it seems to me that this issue only applies to servers built with SDK Sentrol.. Is that the case?
I have numerous other projects coming on line that only require client side apps created with SDK Sentrol that will be interfacing with third party servers.
Is there an expected time frame for news on this issue?
Thanks.
16:29, EET
April 17, 2013
Unfortunately the issue still haven’t been solved.
Fortunately, you’re correct that the issue only affects servers made with Sentrol SDK. And furthermore, the issue happens only when these servers are run as a service.
So, if you’re only creating OPC client applications with Sentrol and you’re interfacing with other servers, you should be fine.
That being said, this is of course something that we’ll need to fix asap. We’ll keep you updated when we find a solution.
P.s. What Sentrol and Delphi version are you using?
17:08, EET
January 9, 2018
16:58, EET
April 17, 2013
Hello,
After some further investigations, it was found out that this issue is caused by a recent Windows update.
For the 1709 version, the breaking update is KB4056892. This issue is already fixed in newer updates, starting from KB4058258.
We also made a blog post about this so the information would be easier to find: https://prosysopc.com/blog/sentrol-sdk-dcom-issues/
Do you think this is the same issue that you were experiencing?
22:32, EET
January 9, 2018
Hi,
Thank you for finding the root cause of the issue. I have not been monitoring this for the last week or so as I’ve been implementing work arounds with customers until this was resolve.
What you found makes perfect sense. My system was working and then all of a sudden stopped. A few days ago, it started working again and I had no idea why. I’ve just checked my update level and it is KB4074588 and was just recently installed.
I also contacted one of my customers with the issue and found that they do indeed have update KB4056892, the offending update.
Thank you for your continued support.
Most Users Ever Online: 1919
Currently Online:
14 Guest(s)
Currently Browsing this Page:
1 Guest(s)
Top Posters:
Heikki Tahvanainen: 402
hbrackel: 144
pramanj: 86
rocket science: 86
Francesco Zambon: 83
Ibrahim: 78
Sabari: 62
kapsl: 57
gjevremovic: 49
Xavier: 43
Member Stats:
Guest Posters: 0
Members: 732
Moderators: 7
Admins: 1
Forum Stats:
Groups: 3
Forums: 15
Topics: 1508
Posts: 6396
Newest Members:
elainesever, powhephenry, mamiecaldwell5, Lamasom, scsneed, berrybulcock, icerdraizomma, athenasummy5, vtaletbhcx, HaroldaDobModerators: Jouni Aro: 1019, Pyry: 1, Petri: 0, Bjarne Boström: 1016, Jimmy Ni: 26, Matti Siponen: 340, Lusetti: 0
Administrators: admin: 1