The usual symptom for the 0x800401F3 DCOM error is an inability for an OPC Client to establish an initial connection with the OPC Server. Read the full article to troubleshoot and repair this DCOM error.
0x80040202 error appears in the OPC Client application when it fails to receive a callback from the OPC Server. Read the full article to troubleshoot and repair this DCOM error.
0x80070002 or 80070002 File not found DCOM Error occurs when DCOM is unable to find the OPC Server file. The most common cause is...
0x80070003 Directory not found. This DCOM error occurs when users attempt to connect to the OPC Server, but DCOM uses the wrong name for the OPC Server folder (directory). This typically happens when...
DCOM Error 0x80070005 appears in the OPC Client application when it succeeds in launching an OPC Server or OpcEnum, but fails to receive a reply from either of the applications. This error could be caused under several conditions. Read the full article to troubleshoot and repair this DCOM error.
0x80070422 (-2147023838) DCOM error appears in the OPC Client application when it fails to start (launch) an OPC server. Read the full article to troubleshoot and repair this DCOM error. Microsoft describes this error as ERROR_SERVICE_DISABLED.
The 0x800706BA DCOM error appears in an OPC client application when it is unable to connect to the OPC server, or loses an existing connection. This can happen under several conditions. Read the full article to troubleshoot and repair this DCOM error.
0x800706D9 OPC DCOM error 2147944153 appears on computers with an improper DCOM configuration. Read the full article to troubleshoot and repair this DCOM error.
The results of technology such as our OPC servers have been a lifesaver in terms of efficiency, but getting there can be complex in some older plants where we are dealing with some legacy equipment. Simple things like naming conventions require a standard practice to prevent having a collision when multiple plants tie together...
Engineering and IT (Information Technology) evaluate and respond to computer system issues in ways that are repeatedly at odds. Nowhere is this more evident and disruptive than in plant Process Control and Automation...
This error appears in the OPC Client application when it fails to find the OPC Server. The two most common causes are: a. Failure to find the OPC server in the Windows Registry and b. Failure to connect to OPCENUM.EXE. For the complete solution, download this whitepaper.
Confused about selecting the right OPC Driver from the right vendor? This article outlines a number of things integrators need to consider when selecting a driver. Emphasis is also placed on the consequence of not selecting the proper driver. Download the article for complete details.
As this case study points out, the intentional cyber threat from outside plants is obscuring the need for integration and training to prevent the danger of unintentional cyber security violations from inside.
Today, process data is readily available at many levels, from instrumentation to higher-level data historians and OPC servers. Choosing the right platform can be key to successfully implementing robust and maintainable process calculations at your company.
This paper is intended to show how .NET applications can access OPC servers. It explains the current transition from the classic DCOM OPC to web services based OPC specifications.
Manufacturing companies have invested billions of dollars in industrial automation infrastructures, but many have not yet realized the full value from their investments as many remain islands of automation, disconnected from other systems—including essential business systems.
Integration Objects' OPC tunneling software provides a solution to this vital issue, addressing both COM/DCOM challenges and important cyber security requirements.
NERC standards for Critical Infrastructure Protection (CIP) apply to various critical assets, and this paper aims to show how Change Control principles can help protect: SCADA and control systems. Click to Download
Find out how to diagnose and repair common OPC communication problems. This whitepaper takes readers through a structured approach to troubleshooting OPC connectivity issues between clients and servers on local and remote connections.
Whitepaper covering five steps to a simple and effective strategy to establish reliable DCOM communication. Find out how to setup DCOM in only 5 steps. The focus of this whitepaper is Windows 8, Windows 8.1, Windows 10, Windows 2012, Windows 2012R2, and Windows Server 2016. Refer to our other whitepapers for other Windows versions.
Whitepaper covering five steps to a simple and effective strategy to establish reliable DCOM communication. Find out how to setup DCOM in only 5 steps. The focus of this whitepaper is Windows 7, Windows Vista, Windows 2008, and Windows 2008R2. Refer to our other whitepapers for other Windows versions.
Whitepaper covering five steps to a simple and effective strategy to establish reliable DCOM communication. Setup DCOM in only 5 steps. Whitepaper focuses on Windows XP, Windows Server 2003, Windows Server 2003R2, and Windows XP 64-bit edition. Refer to our other whitepapers for other Windows versions.
Standards are intrinsically difficult to implement and adopt. In the industrial automation business, OPC is a unifying standard that allows true interoperability. It needs more end-user support and involvement.
OPC .NET (previously OPC Xi) is the newest OPC specification from the OPC Foundation. This article is written by Tom Burke (OPC Foundation), Lee Neitzel (Emerson) and Randy Kondor (OPCTI) briefly compares OPC Xi with Classic OPC and OPC UA, and provides an overview of OPC .NET.
OPC .NET (previously OPC Xi) is the newest OPC specification from the OPC Foundation. The specification is available for download here. The new OPC .NET specification defines a .NET interface that eliminates the need for DCOM and .NET wrappers.
Whitepaper provides an overview of OPC .NET (previously OPC Xi), OPC Client and Server development, and the transition from Classic OPC (based on DCOM) to OPC Xi (based on WCF).
The OPC .NET (previously OPC Xi) specification defines a .NET interface for the data exchange between local and remote automation systems and uses Microsoft WCF (Windows Communication Foundation) for the communication. This whitepaper by Advosol gives an overview of the design concept and available features and restrictions related to certain configuration options.
This whitepaper discusses how to use OPC technology to connect one industrial automation system with another so data can be shared between the two systems.
Fielding Chemical Technologies is using OPC DataHub to provide real-time data across a network of small plants connected via a data link to reduce costs of chemical recycling at its Pervap project. The Pervap project requires data to be collected from various locations and displayed live in web browsers running in workstations in the central office and off-site. The data must also be stored in a SQL Server database for archival and analytical use...
OPC Security White Paper 1 is the first of the three and explains what OPC is and describes the results of a survey of OPC end-users on how OPC is actually used in the field. Download the whitepaper.
The white paper is the second of the three. In it we detail the vulnerabilities typically found in OPC hosts, based on OPC’s current architecture (such as the use of DCOM) and the typical underlying operating system.
The white paper is the last of the three. In it we detail the vulnerabilities typically found in OPC hosts, based on OPC’s current architecture (such as the use of DCOM) and the typical underlying operating system.
OPC provides organizations with a standards-based communication infrastructure that enables them to increase production efficiency, reduce costs, and decrease environmental impact. Upstream Oil and Gas companies have been using OPC for over 10 years and have seen many successful implementations that have helped them overcome specific industry challenges. OPC improves system interoperability over previous proprietary solutions, and, as new OPC specifications come online, we will see more companies adopt OPC in more places in the next five years than ever before.
OPC Unified Architecture (OPC UA) is an important building block that enables users to build the next generation of software automation solutions. With complete backward compatibility ensured, vendors will have much to gain – and nothing to lose – by adopting the new OPC Unified Architecture. Download this whitepaper and learn more.
OPC UA (Unified Architecture) represents the OPC Foundation’s most recent set of specifications for Process Control and Automation system interconnectivity. This paper explains OPC UA from the perspective of the organization that will benefit from the connectivity, in other words: the End User.
A new generation of OPC, known as OPC-UA, is upon us, unifying the multiple specifications of the past and redefining the acronym of OPC, formerly OLE for Process Control, to OPC-UA (OPen Connectivity-Unified Architecture). As often happens the second time around, this latest generation of OPC-UA delivers solutions to problems of the past, adds significant new capabilities, and provides a foundation for future developments.
Integration between process control, plant-level and enterprise systems is no longer an option for industrial companies if they want to remain competitive, especially considering the current global context. Convergence of the IT world with automation and process controls greatly helps in this effort by providing economically and technically competitive solutions. There are different options available and it is important for companies to thoroughly understand their needs and objectives before making decisions.
OPC middleware products are designed to enhance any OPC-based application.
PROFIBUS, the world’s most popular fieldbus has more than 24,000 000 installed devices making it the most successful fieldbus in history. Its comprehensive coverage of automation domains across factory, discrete and process applications makes it ideal for use in all industries. PROFINET, the open and all-encompassing Industrial Ethernet solution, has many features in common with PROFIBUS, including shared profiles, engineering and support. Its innovative IO solution makes it perfect for modern real-time applications - including advanced Motion Control - while its ability to integrate with higher level networks is ideal for bringing the plant floor into harmony with enterprise-wide IT systems.
Both Process and Discrete Manufacturing enterprises have to stay competitive in today’s global marketplace. That means automating as many production processes as possible, and linking them effectively to IT management systems so that timely and useful data reaches the right places fast, letting managers make the decisions that lead to ‘results’. Since 1989, PI (PROFIBUS & PROFINET International) has been supporting that vision with the best automation technology available.
Although the concept of redundancy is straightforward, implementing it in an OPC-based system requires a good understanding of what's at stake. A poorly implemented solution can mean delays, data loss, and overuse of system resources. Whether someone is currently using a redundant system, planning to implement one, or simply wants to broaden their understanding, this white paper provides useful information, such as definitions of basic redundancy concepts like cold, warm, and hot standby, seamless and smart switchovers, fallbacks, and object and link monitoring. It also points out common design problems like the timer pitfall and forced switching, and gives useful advice on how to get the best value in a redundancy manager.
Discover how Saudi Aramco's Abqaiq Plant, the company's largest oil processing facility and the largest crude stabilization plant in the world, used OPC standards and custom-designed system integration to bring its process, data and alarm management technologies and plant systems to the forefront of the oil industry and optimize their day-to-day operations.
In a recent data integration project, Siemens engineers in Copenhagen, Denmark were able to connect equipment and instrumentation running in a high-security facility to a remote monitoring location, using the OPC DataHub. The goal was to allow...
There are critical capabilities that manufacturers need to consider that position plant-wide historians as a better option for leveraging raw data from sensors and other real-time systems to improve production for operations.
Automation users worldwide are driven to minimize energy consumption, to cut costs and comply with increasingly stringent "green" obligations. PROFIenergy enables the deployment of smart energy management strategies over PROFINET.
The design of Process Historian databases must include considerations for performance. Failure to do so could result in a poorly performing database or even data loss. This article provides 10 tips that can help speed up the performance of your SQL database.
The OPC Training Institute has compiled, and answered, 45 of the most popular OPC integration questions. If you’re responsible for integrating OPC technology or troubleshooting OPC, you want to pass up the chance to find out what you don’t know. If you’re struggling with a current project, chances are we have the answer.
.NET is the choice platform for most client applications and it’s also a good choice for the development of OPC servers. This whitepaper covers the different components of .NET OPC servers.
Visualizing your DCOM based OPC client and server connections is not always easy. This paper describes how to do this across your Windows Domain using OPCNetView.
The performance of wireless networks can change over time due to increased performance demands, changes in the radio frequency (RF) environment and changes in the physical environment. This article will explore the use of a wireless diagnostic OLE for Process Control (OPC) server technology to embed diagnostic information in human machine interfaces (HMIs), thus optimizing industrial wireless network performance.
Windows reports error 0x80040155 as: Interface not registered. Programmers know this error as REGDB_E_IIDNOTREG...
The .NET platform required for XML DA is now widely used and OPC server and client applications are being developed on the .NET platform. However, still most applications are built as DCOM based OPC DA server/clients, using .NET wrappers. Despite the many difficulties with DCOM configuration the transition to web services based designs is slow.