Rank: Newbie
Joined: 3/12/2017(UTC)
Posts: 2
|
Hai All, i am trying to communicate with Octiris OPC server with Invensys FBM233 module. The Octiris OPC server is installed in Windows 2012,64 bit. While trying to connect, the following error is generating in OPCdiagbox: "02/28/2017 13:23:22 AddGroup[GMC] failed to connect: hr=0x80070005
02/28/2017 13:23:23 Connect Group - GMC FAILED
02/28/2017 13:23:23 Error returned is 0x80070005 - WIN32: Access is denied."02/28/2017 13:26:38 **** Server proAsset.Octiris.11.1.1 Disconnected ****
02/28/2017 13:26:39 ***** Connect success: proAsset.Octiris.11.1.1 at station 192.168.10.141 *****
02/28/2017 13:27:21 **** Server proAsset.Octiris.11.1.1 Disconnected ****
02/28/2017 13:27:21 ***** Connect success: proAsset.Octiris.11.1.1 at station 192.168.10.141 ***** If anybody have DCOM settings for this OPC server and DCOM Settings for Windows 2012, please send it to me. Thanks in advance. Regard's, Sathesh 00965 60386385 Edited by user Sunday, March 12, 2017 1:08:55 AM(UTC)
| Reason: phone number updated
|
|
|
|
|
|
Rank: Advanced Member
Joined: 10/21/2014(UTC)
Posts: 93
Was thanked: 11 time(s) in 11 post(s)
|
Can you please confirm the following: 1) What is the OPC Client you are using? 2) Is the OPC Client and OPC Server on the same machine? 3) I presume that the Octiris OPC Server is meant to talk to the FBM233 module and expose the data as OPC? 4) Have you tried to connect to the OPC Server with a test client like MatrikonOPC Explorer? What was the result/error seen? Based on what you have provided, it looks like a DCOM issue between the OPC Client and OPC Server. Given that Access is denied is received after the AddGroup call, this could mean a couple of things. If the communication type is Asynchronous Subscription (Report by exception), the OPC Client side access limits may not be set to accept the user that the OPC Server is running as (call back denied). If the communication type is Synchronous, the OPC Server does not have the user that the OPC Client is running as in its DCOM access permissions list. Without knowing anything more about your situation, the best suggestion I can make at this point is to ensure that both the OPC Client and OPC Server are running as the same user. If they are on separate machines, this means ensuring that both machines have the same username and password configured in Windows, remember to make the user an administrator also. Here is an article that may help. It is based on WS2008 but many of the settings will be common to WS2012: http://www.matrikonopc.c...8/whitepapers/index.aspx
|
|
|
|
|
|
Rank: Newbie
Joined: 3/12/2017(UTC)
Posts: 2
|
Dear Roger,
Thanks for your reply.
Actually FBM233 is a hardware module mke by Invensys Automation.
I have checked with Matrikon Explorer , its working fine.
But while communicate with FBM233 module, i am getting the error.
In the same location, i have done the communication with bently nevada system using FBM233 , its working fine. But Bently nevada software installed in windows2008.
Octiris installed in Windows 2012.
Is there any extra DCOM settings required for Windows2012?
Regard's,
Sathesh
|
|
|
|
|
|
Rank: Advanced Member
Joined: 10/21/2014(UTC)
Posts: 93
Was thanked: 11 time(s) in 11 post(s)
|
Not that I am aware of. The usual applies:
*Both OPC Client and OPC Server PCs must have the same user name or password present (or be both on the same domain, using a domain user)
*The user must be an administrator
*Both machines must be on the same domain or workgroup
*No firewalls between
*DCOM properly configured
You may have to set the OPC Server and OPC Client to run as the common user.
What does the FBM233 do? Is it a device card that has an OPC Server on board?
|
|
|
|
|
|
Forum Jump
You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.
