Avatar

Please consider registering
guest

sp_LogInOut Log In sp_Registration Register

Register | Lost password?
Advanced Search

— Forum Scope —




— Match —





— Forum Options —





Minimum search word length is 3 characters - maximum search word length is 84 characters

sp_Feed Topic RSS sp_TopicIcon
Prosys OPC Client to Prosys OPC server connection issue.
January 9, 2018
22:35, EET
Avatar
rdc1997
Member
Members
Forum Posts: 6
Member Since:
January 9, 2018
sp_UserOfflineSmall Offline

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.

January 10, 2018
14:03, EET
Avatar
Jouni Aro
Moderator
Moderators
Forum Posts: 963
Member Since:
December 21, 2011
sp_UserOfflineSmall Offline

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?

January 24, 2018
21:54, EET
Avatar
rdc1997
Member
Members
Forum Posts: 6
Member Since:
January 9, 2018
sp_UserOfflineSmall Offline

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.

January 26, 2018
17:02, EET
Avatar
Heikki Tahvanainen
Moderator
Members

Moderators
Forum Posts: 402
Member Since:
April 17, 2013
sp_UserOfflineSmall Offline

Hi,

We can reproduce the same issue on a Windows 10 machine, but haven’t found a solution yet. We’ll post an update when the solution is found.

January 28, 2018
16:12, EET
Avatar
rdc1997
Member
Members
Forum Posts: 6
Member Since:
January 9, 2018
sp_UserOfflineSmall Offline

Thank You!

My machine isn’t critical but I have a customer who will need a fix within a few weeks if at all possible.

February 1, 2018
19:38, EET
Avatar
rdc1997
Member
Members
Forum Posts: 6
Member Since:
January 9, 2018
sp_UserOfflineSmall Offline

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.

February 2, 2018
16:29, EET
Avatar
Heikki Tahvanainen
Moderator
Members

Moderators
Forum Posts: 402
Member Since:
April 17, 2013
sp_UserOfflineSmall Offline

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?

February 2, 2018
17:08, EET
Avatar
rdc1997
Member
Members
Forum Posts: 6
Member Since:
January 9, 2018
sp_UserOfflineSmall Offline

Good day.

The server I created with SK Sentrol is NOT running as a service but exhibits the problem. Perhaps I have something else going on but it exhibits the same symptoms as the ProSys sample server running as a service.

I am using Delphi 10.1 Berlin Update 1 and Sentrol672B662DC10_1Pro.

February 23, 2018
16:58, EET
Avatar
Heikki Tahvanainen
Moderator
Members

Moderators
Forum Posts: 402
Member Since:
April 17, 2013
sp_UserOfflineSmall Offline

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?

March 1, 2018
22:32, EET
Avatar
rdc1997
Member
Members
Forum Posts: 6
Member Since:
January 9, 2018
sp_UserOfflineSmall Offline

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.

Forum Timezone: Europe/Helsinki

Most Users Ever Online: 518

Currently Online:
9 Guest(s)

Currently Browsing this Page:
1 Guest(s)

Top Posters:

hbrackel: 124

pramanj: 86

ibrahim: 74

rocket science: 65

kapsl: 57

Sabari: 51

gjevremovic: 49

Xavier: 43

fred: 41

TimK: 41

Member Stats:

Guest Posters: 0

Members: 684

Moderators: 15

Admins: 1

Forum Stats:

Groups: 3

Forums: 15

Topics: 1335

Posts: 5711

Newest Members:

daniel.boada@soprasteria.com, Ratheesh, Dustingen, janessawhittell, ravi_prabhakar, dustyy137676428, Douglasabibe, DonaldWibip, kennithmazza4, Heiko Geissler

Moderators: Jouni Aro: 963, Otso Palonen: 32, Tuomas Hiltunen: 5, Pyry: 1, Petri: 0, Bjarne Boström: 877, Heikki Tahvanainen: 402, Jukka Asikainen: 1, moldzh08: 0, Jimmy Ni: 25, Teppo Uimonen: 21, Markus Johansson: 42, Niklas Nurminen: 0, Matti Siponen: 230, Lusetti: 0

Administrators: admin: 1