Log In
Register
Forum
Topic RSS
13:18, EET
March 11, 2013
Offline
Good afternoon!
Whether the license trial for sentrol OPC SDK supports remote connection from the client to the server. It is impossible to adjust the PsOPCServer component. In attempt to change ServerName property there is a message “Could not connect to OPCEnum service at ‘192.168.1.84’: Range check error” (192.168.1.84 – IP address of remote OPC server). Despite it, other product “OPC client “Prosys OPC Client” is connected normally. In what there can be a reason?
Help please!
14:12, EET
December 21, 2011
Offline
Please, make sure that OpcEnum service is running in the remote computer. You also need to enable anonymous DCOM access for that computer so that the TPsOPCServer component can connect to the remote service.
If you know the server ProgID or CLSID, you can type that into the ServerName field and try to connect without using the OpcEnum service.
The Prosys OPC Client should also help you to diagnose the connection problems.
6:15, EET
March 11, 2013
Offline
Thanks!
But it is unclear why the “Prosys OPC Client” application is connected without problems, and PsOPCServer can’t connected even by means of CLSID. OPC client of other producer which we checked, also had no connection problems. In what feature of PsOPCServer?
8:03, EET
December 21, 2011
Offline
Do you get other errors as well, in addition to the OpcEnum error? That one is specific to the ServerName editor, which is using the TPsOPCServerList object internally.
Prosys OPC Client is using the same TPsOPCServer, so it should work identically, in principle.
9:32, EET
March 11, 2013
Offline
Yes, after the record CLSID in the field of PsOPCServer.ServerName and attempt to establish connection there is a mistake: “Cannot connect to OPC Server\\192.168.1.84\{0233D094-F7AE-48FE-9334-6691E9D22042}: Range check error”.
CLSID looked on “Prosys OPC Client”.
13:43, EET
December 21, 2011
Offline
OK, I will need to check if I can reproduce the problem. I suppose it is related to the failing connection to OpcEnum. If you manage to get a connection to that it will probably work better.
This can be a version specific problem, if Prosys OPC Client(compiled with a certain Sentrol version) is not suffering from the same problem.
Most Users Ever Online: 518
Currently Online:
39 Guest(s)
Currently Browsing this Page:
1 Guest(s)
Top Posters:
hbrackel: 135
pramanj: 86
Francesco Zambon: 81
rocket science: 77
Ibrahim: 76
Sabari: 62
kapsl: 57
gjevremovic: 49
Xavier: 43
fred: 41
Member Stats:
Guest Posters: 0
Members: 681
Moderators: 16
Admins: 1
Forum Stats:
Groups: 3
Forums: 15
Topics: 1467
Posts: 6261
Newest Members:
graciela2073, sagarchau, elviralangwell4, Donnavek, Eddiefauth, DonaldPooma, fidelduke938316, Jan-Pfizer, DavidROunc, fen.pang@woodside.comModerators: Jouni Aro: 1010, Otso Palonen: 32, Tuomas Hiltunen: 5, Pyry: 1, Petri: 0, Bjarne Boström: 983, Heikki Tahvanainen: 402, Jukka Asikainen: 1, moldzh08: 0, Jimmy Ni: 26, Teppo Uimonen: 21, Markus Johansson: 42, Niklas Nurminen: 0, Matti Siponen: 321, Lusetti: 0, Ari-Pekka Soikkeli: 5
Administrators: admin: 1
