Opc Core Components Redistributable (x64)

30 views

Skip to first unread message

Jason

unread,

Aug 3, 2024, 5:20:31 PM8/3/24

to mamiworti

I try to install the destributable components (opc-core-components-redistributable-x64-20150731.zip). It seems ok, no error,but when i look in the directory in which the components should be installt, it is empty. where are my files? where are the opc - dlls? I work with Win 8.1 and .net framework 4.6. can anybody helps me.

I have managed to get the 64-bit client working by copying the OPC dll's from SysWOW64 into the same folder where our 64-bit executable is located. I must say that I don't really understand why it works but I assume there's a valid reason. So far so good.

The OPCDA.NET DLLs are copied into the application folder by Visual Studio when the OPCDA.NET reference is added and are copied to the application output folder when the application is compiled. The OPCDA.NET DLLs need to be deployed with the other application components.

Test Clients
The test clients may optionally be deployed with the application if it could be necessary to test the server access in case of difficulties due to e.g. security permission settings.
The test clients are in the folder TOOLS in the OPCDA.NET product installation directory.

Simulation Server
The OPC DA V2/V3 simulation server DAESimServer.exe may optionally be deployed with the application if it could be necessary to test the server access in case of difficulties due to e.g. security permission settings. It is in the folder TOOLS in the OPCDA.NET product installation directory.

OPC Core Components
If the application is deployed to a computer without an installed OPC server then it may be necessary to install the OPC Core Components.
The OPC Core Components V 3.0.106 are provided in a 32bit and a 64bit version:
- OPC Core Components Redistributable (x86).msi
- OPC Core Components Redistributable (x64).msi

On 64bit systems the components install a new component called the Category Manager. This component makes x64 servers visible to x86 clients.
The x64 version of the Core Components Redistributables installs the 32bit versions so it is the only package that needs to be installed on x64 systems.
All .NET assemblies are placed in GAC.

Security Permission settings
Security Permission settings are the most likely cause for difficulties. If the application is deployed to an Windows XP SP2 system then the system has to be configured according the instructions in the document Using OPC via DCOM with XP SP2.pdf supplied in the folder OPC in the OPCDA.NET product installation directory.

Be aware that for callbacks from the server the roles of DCOM server/client are exchanged and the client application acts as the COM server for the callbacks. OPCDA.NET creates registry entries to allow everybody the right for callbacks. However in order to be able to do that the application needs the permission to write the registry key HKEY_Classes_Root\AppId
You may use the registry editor RegEdit to check if a key with the name of exe file was created.

I have installed OPC Core Components in One of my server where Ignition is running. [color=#FF0040]OPC connection is not established after restarted Ignition system itself[/color]. Is it necessary to install this OPC core component in existing Wincc system where ignition trying to connect.

Also, is your Ignition installation 32-bit or 64-bit? The OPC-COM module is known to have some problems in 64-bit JVMs, so if you are running 64-bit, you might try switching to 32, if nothing else, just to verify that it is the cause.

I have installed OPC Core Components in the remote server as well as ignition server. But there is no change yet. I am using Ignition installer 32 version 7.2.1. Can you please tell me what to do next solve the this error??

perhaps you could try and download the kepware opc-ua wrapper. you only get a 2 hour runtime on it but that may be enough to narrow down the problem to either opc-dcom or the ignition opc-da module. basically it connects to the opc-da server, converts it to opc-ua, then you connect ignition to kepware via opc-ua.

[color=#FF0000]WARNING:[/color] The OPC-COM module does not currently work correctly in 64-bit. By installing the core components, you'll be able to connect, but the system will be very unstable. The only work around is to run Ignition against a 32-bit JVM.

I did experience the issue as you said it would show. For a work around, if I install the 32bit version of ignition and 32bit java on the 64bit server 2008 installation should I then be able to use the opc-com?

By doing so, can I still utilize the additional ram of the server for the gateway or would I be restricted by the 32bit limit of 1536MB? Is the gateway max memory an ignition and java limitation or an OS only limitation?

PCo 2.0 requires the "OPC core components 1.0 redistributable (build 224 or later)" (Installation Guide, p. 9) to be able to create a source system of type OpcUaClient. Otherwise the creation fails, because the Opc.Ua.Core assembly could not be found.

The most official way to get the right dll's [Opc.Ua.Core.dll and Opc.Ua.Client.dll]would be to go to the www.opcfoundation.org -> Downloads -> SDK page, register and get the latest version of the "OPC UA Local Discovery Server 1.00". This package is available for non OPC members.

Kepware is about to release its OPC UA Server interface. This will be delivered in KEPServerEX version 5.2. We would like to work with you in validating our interface with PCo. For more information, please contact me at Kepware. Roy Kok, VP Sales and Marketing.

Kepware, Matrikon, and softing have no downloadable OPC UA demo servers yet. According to opcconnect.com there is only OPC UA demo server from Unified Automation. I installed it, but PCo still does not find the UA core components.

By the way, it is not a acceptable solution to install a demo UA Server on a production server, just to be able to connect to a remote UA Server. I just need the OPC UA core components like the ones for OPC DA.

For the real OPC UA specifications based server connection, PCo 2.1 has its all core components including OPC UA agents. But its still to be released. So we have nothing to do but waiting for PCo 2.1 to be out in market for dealing with OPC UA related stuffs.

OPC DA 2.0 was no problem for me either. No, I did not contact the OPC foundation yet. SAP PCo requires a 3rd party component which is not available (or just very hard to find!?!?), therefore at I ask SAP (or SAP developers) in this forum first.

To see command execution progress and return values, you must be the original administrator or use Run as administrator. For more information, see the Microsoft command documentation.

As a complement to using the installation commands directly, sample scripts are provided on the product ISO that install, upgrade, or remove VDAs on machines in Active Directory. For details, see Install VDAs using scripts.

If you attempt to install or upgrade on a Windows OS version that is not supported for this Citrix Virtual Apps and Desktops version, a message guides you to information about your options. See Earlier operating systems.

To install Secure Private Access: Run XenDesktopSPASetup.exe in the x64 > XenDesktop Setup folder on the installation media. Follow the guidance in Command-line options for installing a Secure Private Access.

Opens all ports in the Windows firewall used by the components being installed, if the Windows Firewall Service is running, even if the firewall is not enabled. If you are using a third-party firewall or no firewall, you must manually open the ports.

Valid only during Controller upgrade. Usually, any site test failures are ignored and the upgrade proceeds. If omitted (or set to false), any site test failure causes the installer to fail, without performing the upgrade. Default = false

By default, when a machine restart is needed during an installation, the installer resumes automatically after the restart completes. To override the default, specify /noresume. This can be helpful if you must remount the media or want to capture information during an automated installation.

Prevents the installation of Microsoft SQL Server Express on the server where you are installing the Controller. If this option is omitted, SQL Server Express is installed for use as the site database.

Automatically sends analytics collected during the installation, upgrade, or removal to Citrix. If this option is omitted (or /disableexperiencemetrics is specified), the analytics are collected locally, but not sent automatically.

Citrix account credentials are required to access the download site. You must either have elevated administrative privileges before starting the installation, or use Run as administrator.

To extract the files before installing them, use /extract with the absolute path, for example C:\YourExtractFolder\VDAWorkstationCoreSetup.exe /extract %temp%\CitrixVDAInstallMedia. The directory must exist. Otherwise, the extract fails. Then in a separate command, run the appropriate command, using the valid options listed in this article.

Opens ports in the Windows firewall required by the VDA and enabled features (except Windows Remote Assistance), if the Windows Firewall Service is detected, even if the firewall is not enabled. If you are using a different firewall or no firewall, you must configure the firewall manually. For port information, see Network ports.

Opens UDP ports in the Windows firewall that HDX adaptive transport uses, if the Windows Firewall Service is detected, even if the firewall is not enabled. If you are using a different firewall or no firewall, you must configure the firewall manually. For port information, see Network ports.

Enables or disables the use of UDP for audio packets (RealTime Audio Transport for audio). Enabling this feature can improve audio performance. Include the /enable_hdx_ports option if you want the UDP ports opened automatically when the Windows Firewall Service is detected.