At this point, the OPC Client does not actually connect to the OPC Servers directly. This list includes the ProgID (human friendly name) and the CLSID (the numerical identification) of each OPC Server. When the OPC Client performs a Browse, it actually connects to a copy of OpcEnum, which resides on the remote PC, and retrieves the list of available OPC Servers (refer to Figure 1). This process is called Browsing, and is the process whereby the OPC Client application is able to view the OPC Servers that are installed on the remote PC. Most OPC Client applications attempt to display a list of available OPC Servers on the target PC. A CLSID is similar to your own government-issued identification, such as a Social Security Number (SSN) or Social Insurance Number (SIN), which identifies a specific person. The CLSID is a type of Globally Unique Identifier (GUID), which is a 128-bit number that identifies an application. Each OPC Server is identified by a Class Identification (CLSID). When an OPC Client application tries to connect to an OPC Server, the OPC Client application must be able to identify the exact application (OPC Server) to which it will connect. The inability to establish the first connection with an OPC Server is both the first and most common error that Integrators encounter when using OPC. O Unable to find any OpcEnum server on CLSID returns 800706BA
O Failed to obtain a valid CLSID for server O Unable to connect to the data source, COM error O Cannot browse for OPC Servers on remote PC Depending on the software product that you are using, this error may appear in various different formats as follows: When an OPC Client application is unable to find the OPC Server, users receive an error informing them that the OPC Client application could not obtain the CLSID of the OPC Server. Failure to find the OPC server in the Windows Registry
This error appears in the OPC Client application when it fails to find the OPC Server. THE FOLLOWING ARTICLE IS TAKEN FROM THE OPC RESOURCE SITE AT :
0 kommentar(er)
