Opc Settings v1.6 en a4[1]

Configuration

of an

OPC-Connection

from

ibaPDA-V6

to an OPC-Server.

V 1.6 / ibaPDA V 6.3.0

12. February 2008

OPC Configuration Manual page 2

Table of Contents

1 INTRODUCTION...............................................................................................................4

1.1 General ....................................................................................................................................... 4 1.1.1 OPC ..................................................................................................................................... 4 1.1.2 OPC and iba Products.......................................................................................................... 4 1.1.3 DCOM................................................................................................................................. 5 1.1.4 Firewall................................................................................................................................ 5 1.1.5 Local Security Policy .......................................................................................................... 5

2 CONFIGURATIONS .........................................................................................................6

Part A: OPC Server with Windows XP or Win2003 Server ............................................................. 6 Step A1: Preparation ........................................................................................................................... 6 Step A2: Configuration of the Windows Firewall............................................................................... 7 Step A3: Configure Local Security Settings for Network Access....................................................... 8 Step A4: Set Security Settings for DCOM.......................................................................................... 9 Step A5: DCOM Configuration ........................................................................................................ 10 Step A6: DCOM Configuration for OPCEnum................................................................................. 11 Step A7: DCOM Configuration für OPC Data Access Server.......................................................... 12 Step A8: Reboot the OPC Server PC ................................................................................................ 12

Part B: OPC Client (ibaPda) with Windows XP or Win 2003 Server............................................ 13 Step B1: Configuration of Windows Firewall................................................................................... 13 Step B2: Set Local Security Settings for Network Access................................................................ 14 Step B3: Reboot the OPC-Client PC................................................................................................. 15 Step B4: User Accounts for OPC Connection................................................................................... 15 Step B5: Select OPC Server .............................................................................................................. 16 Step B6: Connect and add Signals .................................................................................................... 17

Part C: OPC Server (ibaLogic) with Windows 2000 ....................................................................... 18 Step C1: Prepartion ........................................................................................................................... 18 Step C2: Configuration of a Firewall ................................................................................................ 18 Step C3: Configure DCOM............................................................................................................... 19 Step C4: Configuration of DCOM for OPCEnum ............................................................................ 20 Step C5: DCOM Configuration for a OPC Data Access Server ....................................................... 21 Step C6: Reboot the OPC Server PC................................................................................................. 21

Part D: OPC Client (ibaPda) with Windows 2000 ........................................................................... 22 Step D1: Configure Firewall ............................................................................................................. 22 Step D2: User Account for OPC Connection .................................................................................... 23 Step D3: Select OPC Server.............................................................................................................. 24

3 SPECIAL OPC-SERVERS .............................................................................................25

3.1 DriveOPC (ABB) .................................................................................................................... 25

4 TROUBLESHOOTING....................................................................................................26

4.1 No OPC server found .............................................................................................................. 26

4.2 Error establishing connection ................................................................................................ 28

© iba AG 2006


4.3 Errors with the display of values ........................................................................................... 30

© iba AG 2006


1 Introduction

This document describes a few from many possible configurations that are necessary to establish a connection between OPC-client and OPC-server within a network. There are several ways to achieve this goal. The configurations described in this document were tested and lead to satisfying results. In case the settings in this document do not work as desired or if you find other set-tings that are more simple, please contact us. We are thankful for all hints considering errors in this document. contact: Dieter Kopp, iba-AG or Jan Goeman, iba-AG Email: [email protected] [email protected]

1.1 General

1.1.1 OPC OPC stands for OLE for Process Control. This is a standard software interface, which makes it possible that applications of different manufacturers exchange data with an-other. OPC is used wherever sensors, control systems and HMIs of different manu-facturers shall create a flexible network. For communication between the different applications the OPC uses Microsoft's DCOM technology. The transparent DCOM shows whether the data comes from own address space, another process or another computer connected by TCP/IP. OPC is based on the Client/Server-principle. The process data is generated on the server side (usually a control system) and is made available for the clients . More information about OPC is found under http://www.opcfoundation.org/, and in the manuals of ibaLogic and ibaPda(V6).

1.1.2 OPC and iba Products

The iba-applications ibaLogic-V3 and ibaPda-V6 have OPC-Interfaces. In ibaLogic there is an OPC-server (specification OPC Data Access 2.0) integrated, which is automatically installed and activated with the start of ibaLogic. In ibaPda there is an OPC-Client integrated which can establish a connection to an OPC-Server (of specification DA 1.0 und DA 2.0 ) . Note: The OPC-connection has a non-deterministic data transfer and is therefore not quali-fied for real-time measurement, although it can be used for slower processes (e.g.. temperature changes) or accompanied quality data (e.g. charge numbers, Technos-trings).

This document describes the connection between a ibaPDA OPC-Client and a iba-Logic OPC server, but most of these assertions apply to other OPC-connections as well.

© iba AG 2006

mailto:[email protected]

mailto:[email protected]

http://www.opcfoundation.org/


1.1.3 DCOM

DCOM (Distributed Component Object Model) is a protocol defined by Microsoft, for communication of program components within a network. The great potency of this functionality bears the problem – because DCOM is acti-vated as a part of the OS- that every internet user had the possibility of connecting to the server, which of course was a security hazard. A solution for this problem was the service pack 2 from XP. The Service Pack 2 im-proved the security and now the DCOM-interface requires access & launch permis-sions. To enable data transfer over OPC these permissions have to be specified exactly.

1.1.4 Firewall

XP service pack 2 also comes with a firewall which is activated by default, other fire-walls might be installed also on SP1 or Windows 2000 PCs. To enable the data transfer through the firewall we have to configure some excep-tions in the firewall.

1.1.5 Local Security Policy In the local security policy, of windows XP /2000, a few predefined options have to be adjusted.

© iba AG 2006


2 Configurations

First of all you need administrator rights on all PCs involved. Overview: Part A: OPC Server with Windows XP Part B: OPC Client with Windows XP Part C: OPC Server with Windows 2000 Part D: OPC Client with Windows 2000

Part A: OPC Server with Windows XP or Win2003 Server

Step A1: Preparation

Install the "OPC Core Components", necessary for using the OPC-browser service OpcEnum of .NET. These components are provided on the ibaPdaV6 –CD.

Note: Other OPC-Clients ( e.g.. the OPCTestClient from ExperTune or the OPCLink from Wondware) do not use this browse service. Therefore the Core components are not necessary for these and older OPC-Clients.

© iba AG 2006


Step A2: Configuration of the Windows Firewall

If the PC has no firewall active continue with step A3. Configuration of the Windows XP SP2 – Firewall :

Open firewall :

Control Panel security center Windows Firewall exceptions

Check if following entries are active : • File and printer sharing (TCP-Ports 139, 445, UDP-Ports 137, 138 ) • DCOM Port (TCP Port 135 ) • Management Console (...\Windows\System32\mmc.exe) • OpcEnum (...\Windows\System32\OpcEnum.exe) • "Opc Server" (...\iba\ibaLogic\ibaLogic.exe)

Add missing ports and programs.

If you have a different firewall installed, you have to make these entries there.

© iba AG 2006


Step A3: Configure Local Security Settings for Network Access

Open local security settings: Start control panel administrative tools local security policy

local policies Security Options

Look for security setting "Network access: Sharing and security model for local accounts..."

Set to

"Classic – local users authenticate as themselves".

© iba AG 2006


Step A4: Set Security Settings for DCOM

If the PC with the OPC-server has no SP2 continue with Step A5.

For Service Pack 2 go to local Security Settings

Select in local security settings the security Option " DCOM: Machine Access Restrictions in Security Descriptor Definition Language (SDDL) syntax."

Right mouse click select „ Properties „, click on "edit security", make follow-

ing settings:

Security Limits \ Group ANONYMOUS- Everyone Local access allow allow Remote access allow allow

Choose security Option

"DCOM: Machine Launch Restrictions in Security Descriptor Definition Language (SDDL) syntax "

Choose with right mouse click "Properties", click on "edit security", make fol-lowing settings:

Security Limits \ Group ANONYMOUS-. Everyone Local Launch allow allow Remote Launch allow allow Local Activation allow allow Remote Activation allow allow

© iba AG 2006


Note: If „ANONYMOUS LOGON“ and „ EVERYONE“ are not in the „Group or users names” field they have to be added with Button “Add”. Then you can add users by edit or with the button “advanced” and then “find”.

.

Step A5: DCOM Configuration

Start the configuration program Start Run…: dcomcnfg or Start Settings Control Panel Administrative Tools Component Services.

With double click on "Component Services", "Computers", "My Computer"

and "DCOM- Config" the DCOM objects are shown in the right column. with a right-click on the object you can open and edit the properties.

© iba AG 2006


Step A6: DCOM Configuration for OPCEnum

Select the object OpcEnum from the DCOM objects and choose properties with help of the right mouse button.

Set the following properties:

Tab "General": Authentication Level: none Tab "Location": Run Application on this computer Tab "Security": • Launch and Activation Permissions: Customize, Edit:


• Access Permission: Customize, Edit:


• Configuration Permission: default

Tab "Endpoints": no change Tab "Identity": The system account (services only)

Hint: If „ANONYMOUS LOGON“ and „ EVERYONE“ are not in the „Group or users names” field they have to be added with Button “Add”. Then you can add users by edit or with the button “Advanced” and then “Find” (see above).

© iba AG 2006


Step A7: DCOM Configuration für OPC Data Access Server

select object "OPC ibaLogic Data Access Server" (or any other OPC-Server) from the DCOM objects and open properties with a right mouse click.

Apply the following settings:

Tab "General": Authentication Level: none Tab "Location": Run Application on this computer Tab "Security": • Launch and Activation Permissions: Customize, Edit:


• Access Permission: Customize, Edit:


• Configuration Permission: default

Hint: If „ANONYMOUS LOGON“ and „ EVERYONE“ are not in the „Group or users names” field they have to be added with Button “Add" (see above ) Tab "Endpoints": no change Tab "Identity": The interactive user

Step A8: Reboot the OPC Server PC

© iba AG 2006


Part B: OPC Client (ibaPda) with Windows XP or Win 2003 Server

Step B1: Configuration of Windows Firewall

In case the OPC-Client PC has no firewall installed, continue Step B2

Usually the ibaPda installation program configures the Firewall automatically, so that you have to make no changes. To make sure you can check the firewall settings.

Open XP-Firewall : Settings Control Panel Windows Firewall Exceptions,

Following ports and programs must be active in the exception list:

• File and Printer sharing (TCP-Ports 139, 445, UDP-Ports 137, 138 ) • DCOM Port (TCP Port 135 ) • ibaPda-Client (...\iba\ibaPda\Client\ibaPda.exe) • ibaPda-Server (...\iba\ibaPda\Server\ibaPDAService.exe) • ibaPda-ServerStatus (...\iba\ibaPda\Server\ibaPDAServerStatus.exe) • Management Console (...\Windows\System32\mmc.exe)

Add missing ports and programs as needed.

© iba AG 2006


Step B2: Set Local Security Settings for Network Access

Navigate local security settings: Start Settings Control Panel Administrative Tools Local Security Policy Local Policies Security Options

Look for security option: " Network Access: Sharing and security model for local accounts"

Set to "Classic- local user authenticate as themselves".

© iba AG 2006


Step B3: Reboot the OPC-Client PC

Step B4: User Accounts for OPC Connection Case 1: Both PCs – OPC Server and OPC Client – are in the same domain:

All services and programs have to run with accounts registred in the domain. No further arrangements necessary.

Start the ibaPda Client, open the I/O Manager and create an OPC-Modul .

No need to declare account. case 2: Both are within the same workgroup:

Check if the OPC-Server PC and the OPC-Client are in the same workgroup. If not, change Network settings at the OPC-Client PC or the OPC-ServerPC. (My Computer Properties Computer Name change )

Check, if the OPC-Server PC and the OPC-Client PC run with the same user account and password. if not, you have to create a local user account on the OPC-Client PC ♦ With the same rights (Administrator !) ♦ With the same user name ♦ And with the same password , used in the OPC-Server PC. No empty

password allowed

Example: OPC-Server PC: PC-Name: ibaLogic-PC User: logic Password: logic1111

OPC-Client PC: PC-Name: ibaPDA-PC User: pda Password: pda2222

create on the OPC-Client PC an extra Administrator Account: User: logic Password: logic1111

It is not necessary to log in with this account, it only has to exist.

© iba AG 2006


Start the ibaPDA Client, open the I/O Manager, create a OPC-Module and enter Account data to the OPC-Connection of ibaPDA.

case 3: mixed mode:

As case 2: create a local user account on the OPC Client PC with the same rights, name and password as the user account of the OPC Server PC uses with XP (or domain).

Start the ibaPDA Client, open the I/O Manager, create an OPC Module and enter Account data to the OPC Connection of ibaPDA.

Step B5: Select OPC Server

Enter user account before selecting the Computer name. Then the Opc-Enum Service is started, with the correct access rights, on the target PC and you can select the OPC-server after you have entered the Computer name.

In case no OPC server is shown OPC-Server in this box and instead you see

the message "No OPC Server found", then you have a conflict with your se-curity policies. Read step B2.

© iba AG 2006


Step B6: Connect and add Signals

After Connect the OPC-Item browser is started by add signals and the OPC-Items are shown.

If you receive an "Error connecting to OPC-Server: .........." message, you

might have a problem with your Security Options. Read chapter : troubleshooting

© iba AG 2006


Part C: OPC Server (ibaLogic) with Windows 2000

Step C1: Prepartion

Install the "OPC Core Components", necessary for using the OPC-browser service OpcEnum of .NET. These components are provided on the ibaPdaV6 –CD.

Note: Other OPC-Clients ( e.g.. the OPCTestClient from ExperTune or the OPCLink from Wondware) do not use this browse service. Therefore the Core components are not necessary for these and older OPC-Clients.

Step C2: Configuration of a Firewall

If the PC has no firewall active continue with step C3. Configuration of a Firewall :

Check if following entries are active : • File and printer sharing (TCP-Ports 139, 445, UDP-Ports 137, 138 ) • DCOM Port (TCP Port 135 ) • Management Console (...\Windows\System32\mmc.exe) • OpcEnum (...\Windows\System32\OpcEnum.exe) • "Opc Server" (...\iba\ibaLogic\ibaLogic.exe)


© iba AG 2006


Step C3: Configure DCOM

Start configuration program: Start Run….: dcomcnfg

On Tab “Applications” select the desired DCOM object "OpcEnum" or "OPC... Data Access Server" and click on "Properties".

© iba AG 2006


Step C4: Configuration of DCOM for OPCEnum

Select object "OpcEnum" and click the button "Properties".

Tab "General": Authentication Level : none Tab "Location": Run Application on this computer Tab "Security":

• Use custom access permissions: edit:

user Type of Access Everyone Allow Access

• Use custom launch permissions : edit

user Type of Access Everyone Allow Launch

Note: If the name “Everyone“ does not appear you have to add it.

• Use default configuration permissions

Tab "Identity": The system Account (services only) Tab "Endpoints": do not change…. .default system protocols…

© iba AG 2006


Step C5: DCOM Configuration for a OPC Data Access Server

Select the desired OPC-Server from he DCOM applications and click on: Properties.

General: Authentication Level : none Location: Run Application on this computer Security:

• Use custom access permissions: edit:


• Use custom launch permissions: edit:


Note: If the name “Everyone“ does not appear you have to add it.

• Use default configuration permissions

Identity: The system Account (services only) Endpoints: do not change

Step C6: Reboot the OPC Server PC

© iba AG 2006


Part D: OPC Client (ibaPda) with Windows 2000

Step D1: Configure Firewall

If the PC has no firewall active continue with step D2. Configuration of a Firewall :

Check if following entries are active : • File and printer sharing (TCP-Ports 139, 445, UDP-Ports 137, 138 ) • DCOM Port (TCP Port 135 ) • ibaPda-Client (...\iba\ibaPda\Client\ibaPda.exe) • ibaPda-Server (...\iba\ibaPda\Server\ibaPDAService.exe) • ibaPda-ServerStatus (...\iba\ibaPda\Server\ibaPDAServerStatus.exe) • Management Console (...\Windows\System32\mmc.exe)


© iba AG 2006


Step D2: User Account for OPC Connection Case 1: Both PCs – OPC Server and OPC Client – are in the same domain:

All services and programs have to run with accounts registred in the domain. No further arrangements necessary.

Start the ibaPda Client, open the I/O Manager and create an OPC-Modul .

No need to declare account. case 2: Both are within the same workgroup:

Check if the OPC-Server PC and the OPC-Client are in the same workgroup. If not, change Network settings at the OPC-Client PC or the OPC-ServerPC. (My Computer Properties Computer Name change )

Check, if the OPC-Server PC and the OPC-Client PC run with the same user account and password. if not, you have to create a local user account on the OPC-Client PC ♦ With the same rights (Administrator !) ♦ With the same user name ♦ And with the same password , used in the OPC-Server PC. No empty

password allowed

Example: OPC-Server PC: PC-Name: ibaLogic-PC User: logic Password: logic1111

OPC-Client PC: PC-Name: ibaPDA-PC User: pda Password: pda2222

create on the OPC-Client PC an extra Administrator Account: User: logic Password: logic1111

It is not necessary to log in with this account, it only has to exist.

Start the ibaPDA Client, open the I/O Manager, create a OPC-Module and

enter Account data to the OPC-Connection of ibaPDA.

© iba AG 2006


Step D3: Select OPC Server

Enter user account before selecting the Computer name. Then the Op-cEnum-service is started, with the correct access rights, on the target PC and you can select the OPC-server after you have entered the Computer name.

In case no OPC server is shown OPC-Server in this box and instead you see

the message "No OPC Server found", then you have a conflict with your se-curity policies. Read chapter : troubleshooting.

After Connect the OPC-Item browser is started by add signals and the OPC-

Items are shown.

If you receive an "Error connecting to OPC-Server: .........." message, you might have a problem with your Security Options. Read chapter : trouble-shooting.

© iba AG 2006


© iba AG 2006

3 Special OPC-Servers

3.1 DriveOPC (ABB) From ibaPda Version 6.10.0 on, the ibaPda OPC-Client can connect and communicate with drive control DriveWindows (at Version V2.01) by the OPC-Server DriveOPC Version 2.02. With the standard installation of DriveWindows the OPC-Server is installed as "in-process server". The ibaPdaClient can not connect in this mode. You must Stopp the DriveOPC Server and reinstall as "local server". Do this the following way. 1. Stop In-process server:

The Server Dll "smp.dll" is normally located under "C:\Program Files\Common Files\DriveWare\DriveOPC".

Stop the server with this command: Regsvr32 -u "C:\Program Files\Common Files\DriveWare\DriveOPC\SMP.DLL"

2. start Local server:

The Server-exe "smp.exe" is normally located under "C:\Program Files\Common Files\DriveWare\DriveOPC".

Start the server with this command: "C:\Program Files\Common Files\DriveWare\DriveOPC\SMP.EXE" -RegServer

The Server is found in the DCOM Configuration under the name"DriveOPC" . You must select "ABB.SMP.1" in the ibaPDA browser.


4 Troubleshooting

4.1 No OPC server found No. Action Reaction ibaPda System Events Client PC System Events Server PC Reasons und remedy 1.1 DCOM 10000

A DCOM-Server could not be started: {13486D51-4821-11D2-A494-3CB306C10000}. Error: "The service cannot find the file specified" Caused by start of this command: "C:\WINDOWS\system32\OpcEnum.exe" –Embedding

1.2

DCOM 10006: DCOM got error "The service cannot find the file specified" from the com-puter "opc_server" when attempting to activate the server: {13486D51-4821-11D2-A494-3CB306C10000} DCOM 1005:

DCOM got error "The service cannot find the file specified" attempting to start the service OpcEnum with arguments "-Service" in order to run the server: {13486D51-4821-11D2-A494-3CB306C10000}

The Service OpcEnum is not installed on the OPC server PC. Install the "OPC Core Components" on the OPC server PC.

1.3 DCOM 10006: DCOM 10016 DCOM got error "General access denied error " from the computer Iba-fue-dev011 when attempting to acti-vate the server: {13486D51-4821-11D2-A494-3CB306C10000}

The application-specific permission set-tings do not grant Local Activation permis-sion for the COm server application with CLSID {CLSID} to the user {User} SID {SID}.

User names have to be the same see step B4 e.g.. D2. The user "user_2" has not activation rights to the service OpcEnum in the opc server PC. Make identical user accounts and pass-words on both PCs.

1.4

You start the OPC Browser by entering the PC name of the OPC Server. .

"No OPC Server found" In the server list

DCOM 10009: DCOM was unable to communicate with the computer "opc_server" using any of the configured protocols.

none 1. The computer "opc_server" is not reachable in the network. 2. Check the network connection. 3. Insure that the file and printer sharing is not blocked by the firewall in the OPC server PC. 4. User/Password do not match

© iba AG 2006


No. Action Reaction ibaPda System Events Client PC System Events Server PC Reasons und remedy 1.5 none none

Invalid user account. Enter a valid user account to the OPC connection.

1.6 none none With connections within the workgroup the network access is not enabled in the local security policy change local security policy see step A3, B2 In the local security policies the access network access sharing options are not correct.

1.7 none none On OPC-Serverside the OpcEnum.exe is blocked by a firewall. see steps A2, C2

1.8

You start the OPC Browser by entering the PC name of the OPC Server.

"No OPC Server found" in the server list

none DCOM 10024:The machine wide group policy <policy> Limits security descriptor is invalid....

Enable remote access in DCOM security policy see step A4

"No OPC Server found” in the server list

DCOM 1009: DCOM shows error " The RPC Ser-ver is Unavailable " {13486D51-4821-11D2-A494-3CB306C10000}

© iba AG 2006


4.2 Error establishing connection Nr. Action Reaction Pda System Events Client PC System Events Server PC Reasons und remedy 2.1 DCOM 10000

Unable to start a DCOM Server: {13486D51-4821-11D2-A494-3CB306C10000}. Error: The system can-not find the file specified. " appeared while starting: "C:\WINDOWS\system32\OpcEnum.exe" –Embedding

2.2

Message box "Errors occurred while connect-ing to "opc_server": System cannot find the file specified"

DCOM 10006: DCOM got an error "System cannot find the file specified" from the com-puter "opc_server", while trying to activate the following server: {13486D51-4821-11D2-A494-3CB306C10000}

DCOM 1005: “DCOM got error: “The system cannot find the file specified.” Attempting to start the service OPCEnum with arguments “-Service” in order to run the server {13486D51-4821-11D2-A494-3CB306C10000}

The service OPCEnum is not installed on the OPC-Server PC Install the OPC-Core-Components" on the OPC-Server PC.

2.3 Message box: "Error connecting to OPC-Server: access is de-nied"

none none Invalid user account. See step B4, D2

2.4 DCOM 10006DCOM got error "Server execution failed " from the computer

It is not allowed to start ibaLogic embed-ded, please start ibaLogic first

dieter_kopp_pc1 when attempting to activate the server: {4C68190E-91E0-11D3-8D47-0060084A056F}

DCOM 10010 The server {4C68190E-91E0-11D3-8D47-0060084A056F} did not register with DCOM within the required timeout.

2.5

connect

Message box: " Error connecting to OPC-Server: server execution failed"

DCOM 10010 The server {4C68190E-91E0-11D3-8D47-0060084A056F} did not regis-ter with DCOM within the required timeout.

none

The OPC-Server (e.g.. ibaLogic) is not running Start the OPC-Server, ( ibaLogic ) and start evaluation

© iba AG 2006


Nr. Action Reaction ibaPda System Events Client PC System Events Server PC Reasons und remedy 2.6 Message box: " Error

connecting to OPC-Server: Unknown Error"

DCOM 10006: DCOM got error "Server execution failed " from the computer PDA-NOTE1 when attempting to activate the server: {4C68190E-91E0-11D3-8D47-0060084A056F}

DCOM 10010: The server {4C68190E-91E0-11D3-8D47-0060084A056F} did not register with DCOM within the required timeout

The user account the OPC-server is using is different from the windows logon. Correct on the OPC-Server side the object property Identity: set it to „interactive user"

2.7 Message box: " Error connecting to OPC-Server : RPC server is not available "

DCOM 10006: -A494-3CB306C10000} DCOM got error "The RPC server is unavailable. " from the computer Pda-note1 when attempting to acti-vate the server: {2F5D6B10-9CA4-11D1-9FFD-00A024366A7A}

none The service OPCEnum.exe is blocked on the server side by a firewall. see step A2, C2

2.8 Error connecting to OPC Server: Specified cast is not valid

DCOM 10009: DCOM was unable to communicate with the computer opc_server using any of the configured protocols.

none The OPC-server can not be reached in the network. Check network and firewall settings

2.9 Error connecting to OPC Server: Access denied

DCOM 1006: DCOM got error "General access denied error " from the computer opc_server when attempting to activate the server: {4C68190E-91E0-11D3-8D47-0060084A056F}

none with W2000 : user accounts of ibaPDA-Services and OPC-Client-are different. see step D2

2.10 none none with W2000:different user accounts see step D2

2.11

connect

Error connecting to OPC Server: Specified cast is not valid

none DCOM 10024:The machine wide group policy <policy> Limits security descriptor is invalid. The security descriptor is defined as an invalid Security Descriptor Definitions Language (SDDL) string. The requested action was therefore not performed. Please contact your administrator to get the security de-scriptor corrected in the Group Policy set-tings.

Allow remote access, see step A4.

© iba AG 2006


4.3 Errors with the display of values Nr. Action Reaction Pda System Events Client PC Reaction from Server Reasons und remedy 3.1 Add OPC-Signals

the OPC-Items are shown but the values are not updated

none none

3.2 Start data acquisi-tion

Error at activating the callback of the OPC Server Iba.Logic.1 : Exception from HRESULT 0x80040202

none none

1.Network configuration workgroup: Network access is not enabled on the client PC. change local security policy see step A3/B2. 2. a user account does not have a pass-word.

add password to account. 3.3 Error at activating the

callback of the OPC server Iba.Logic.1 : The RPC server is unavail-able (Exception from HRESULT:0x800706BA)

none none 1. The service OPCEnum.exe is blocked on the server side by a firewall. 2. The ibaPdaServer.exe is blocked on the client side by a firewall. Enter application to exception list of fire-wall, see step A2

DCOM 1009: DCOM got error "The RPC server is unavailable. " from the computer Pda-note1 when at-tempting to activate the server: {13486D51-4821-11D2-A494-3CB306C10000}

Connection to OPC-server failed: System cannot find the file speci-fied.

DCOM 1000: DCOM got an error "System cannot find the file specified" from the com-puter "opc_server", while trying to activate the following server: {13486D51-4821-11D2-A494-…….

3.4 Start PDA-service none DCOM 10006: DCOM got error "Server execution failed " from the computer PDA-NOTE1 when attempting to activate the server: {4C68190E-91E0-11D3-8D47-0060084A056F}

It is not allowed to start ibaLogic embed-ded, please start ibaLogic first DCOM 10010: The server {3D14228D-FBE1-11D0-995D-00C04FD919C1} did not register with DCOM within the required timeout.

the OPC-Server (e.g.. ibaLogic) is not running . Start the OPC-Server, ( ibaLogic ) and start evaluation

3.5 Start Client PC none DCOM 10020: The machine wide Default Launch and Activation security descriptor is invalid. It contains Access Control Entries with permissions that are invalid. The requested action was therefore not performed. This secu-rity permission can be corrected using the Component Services administrative tool.

none Wrong default entries for DCOM : Change DCOM defaults

© iba AG 2006


© iba AG 2006

Documents

Opc Settings v1.6 en a4[1]