OPC General

Are Softing OPC Servers 64-bit applications or can they be used on 64-bit systems?

Softing OPC Servers are 32-bit applications that can be used on 64-bit systems in 32-bit mode without any limitations or performance reduction.

Background information from the German Wikipedia entry (translated excerpt):
The advantages of 64-bit CPUs include an easier calculation of large integer values. This offers benefits, for example, for encryption algorithms, graphical calculations (e.g. fixed point arithmetic for computer games), 64-bit file systems, or multimedia formats (MPEG2, MP3).

Another advantage over 32-bit architecture is that 64-bit systems can directly address more than four GB RAM. This is useful for applications with large memory requirements, such as video processing applications and database systems, provided they have been programmed for a 64-bit system. In most other applications – in particular, office applications – there is no subjectively noticeable speed advantage.

How can I find the version number of my installed OPC product?

OPC Server: 
Softing OPC Servers provide an integrated web server interface where you can access the exact version information of an OPC server. To start the OPC server's web interface, open the context menu of the Tray Application and click “Show Web Pages.” The “Information” area can be accessed by all users
without any user login.

Note:
You can only access the web pages of the OPC server when the server is running!

Some of the tray applications also display the exact version information.

OPC Toolbox: 
In the OPC Toolbox, the exact version information is contained in the “SOVersion.h” file. The version number can also be determined from the version of the “OTB.dll” file. You can find these files in the following directories:

  • "C:\Program Files\Softing\OPCToolkit\V44x\Windows\core\common" and
  • "C:\Program Files\Softing\OPCToolkit\V44x\Windows\bin"



OPC ActiveX Controls:
 
You can determine the version number from the file version of “C:\Program Files\Softing\OPCActiveX\bin\soaxcmn32.ocx.”

The attempt to establish a connection to an OPC-Server which is running as a service fails.

The attempt to establish a connection to an OPC-Server which is running as a service fails.

Is it necessary to install the OPC Core Components on my computer before using any OPC Client or OPC Server?

The OPC Foundation provides the binaries needed to run DCOM OPC server and OPC client application as Windows Installer packages. 
It is necessary to install the "OPC Core Components" on each machine where an OPC server or an OPC client is installed. 
The latest version of the OPC Core Components Redistributables can be downloaded from the OPC Foundation web pages.

Is it possible to start the Softing OPC Demo Client with a specific configuration file?

Yes this is possible. First, create the desired configuration file (.soc) with the OPC Demo Client. You can then access the OPC Demo Client with this configuration by specifying the  parameter load.

SOClient /load filename.soc

This parameter can be passed either in the command line or in the desktop from the context menu "Properties".

Starting an OPC Server / Easy Connect with limited access rights

If the OPC Server / Easy Connect is configured as a Service then a user with limited access rights cannot start or stop this

Softing Traceoutput

Description of the Softing Traceoutput

Error messages beginning with 0x8

Generally the error codes beginning with 0x8 are operating system specific error messages. You can find a short description to such kind of error codes in the Microsoft Visual Studio Error Lookup Tool or in Internet.

Error message: Access denied (0x80070005)

The error 0x80070005 (Access denied) indicates a DCOM problem.

The problem often lies in the user context used by COM/DCOM to launch the OPC Server (Microsoft DCOM Identity Setting).  

The Identity setting (dcomcnfg) also plays an important role by a local connection and even with our OPC Tunnel! In order to handle the underlying OPC Server in the OPC Tunnel correctly, the identity should be set to "Interactive User".

This identity setting is applicable only when running in Application Mode and not as “Service”. Please configure the OPC Server/Client as “Application” in the OPC Tray (Running Mode) and change the identity in the DCOM configuration (dcomcnfg).  

In the most cases this DCOM setting is helpful. Otherwise, please configure a user with administrator privileges and password and start the application under this user (on client and server sides).

The DCOM settings are however not part of our scope since the DCOM is a service of the Microsoft Windows operating system. For further information about it please visit the Microsoft Websites.

Error message: RPC server is not available (0x800706BA)

When an OPC Client reports this DCOM error (0x800706BA) then the OPC Client is unable to connect to an OPC Server or loses an existing connection. The OPC Client doesn’t detect the loss of connection. The OPC Client can’t access data from the OPC Server. The callbacks for data exchange don’t get through from the Server to the Client.

This might have different reasons:

  • The OPC Server is not responding to a DCOM call due to deadlock / crash
  • The OPC Server is not responding to a DCOM call due to a bad DCOM configuration.
  • The Firewall is on
  • The OPC Server is not available due to network interruption.


The problem often lies in the user context under which the Server is running (DCOM Identity Setting). Therefore please configure a user with administrator privileges and password and start the application under this user. In the most cases this DCOM setting is helpful.

The DCOM settings are however not part of our scope since the DCOM is a service of the Microsoft Windows operating system. For further information about it please visit the Microsoft Websites.