Problems and Solutions
Error 2 from fio file data_field: No such file or directory
Error of type COR_SC_ERR:source 130 code 2 COR_logstatus FATAL error resulting in exit
Solution Do the following:
1. Open the project's Workbench. 2. Click Tools on the menu bar. 3. Select Command prompt…
Problem Starting the Datamerge without running the project.
Symptoms …
CIpcPortShm::Register m_ConnOut.Attach Err:2 …
Solution Do the following: 1. Start the project.
2. Open the project's Workbench. 3. Click Tools on the menu bar. 4. Select Command prompt…
Type datamerge.exe in the Command Prompt window. Problem Using CIMPLICITY Point Logging (datasource) or
CIMPLICITY Alarm Logging for the secondary(slave) server, without proper mapping on the primary (master) server. Symptoms Entry in the db_merge.log stating that there is no data to be
merged. This in itself does not indicate an error. However, if you know you have data to merge, it might be one.
Solution See "Redundancy Configuration Procedures–Configuring for Database Redundancy" in this manual.
Problem Using data source with the same names on the primary and secondary servers that are pointing to different databases. Symptoms Entry in the db_merge.log stating that there is no data to be
merged. This in itself does not indicate an error. However, if you know you have data to merge, it might be one.
Solution See "Redundancy Configuration Procedures–Configuring for Database Redundancy" in this manual.
Problem Rerunning the DataMerge. Symptoms No ptlr[date].log file found.
Solution Rename the last modified file ptlr[date].sav to ptlr[date].log.
Problem Rerunning the DataMerge for data that has already been processed.
Symptoms Error message telling you that insertion violates the primary key.
Index
A
About
Computer Cabling Redundancy 6-1
Supported communication interfaces for Server redundancy A-1
2-13
Alarm Management
Operation during failover 5-5 Redundant system behavior 2-14 Allen-Bradley Communications
Redundant configuration A-4 Allen-Bradley Data Highway Plus
Redundant configuration A-5
Scripting requirements for server redundancy 2-4 Applications
Database logging requirements for server redundancy 2-4
Network configuration requirements for server redundancy 2-5
Primary and secondary computer requirements for server redundancy 2-4
Time synchronization requirements for server redundancy 2-5
APPLICOM
Redundant configuration A-5 Automatic Redundancy
Introduction 2-6
Recover from process failure 5-10
B
Base System
Order of configuration 3-1 Boot
Configuring the project to start at 5-4
C
Cabling Redundancy 1-3 Cause
Detecting for primary server failure 5-6 CCM2
Redundant configuration A-3 cimhosts.txt
Computer cabling redundancy 6-4 IP addresses 6-4
Cimhosts.txt DEBUG flag 6-5 Number_of_ports 6-6 Start_port_range 6-6
Redundant system behavior 2-14 CloseSocketChange 7-4
Computer
Requirements for server redundancy 2-2 Computer cabling redundancy
Error messages and missed communications C-2 Monitoring API 7-1
Computer Cabling Redundancy About 6-1
Configuration 6-4
Definition for CIMPLICITY HMI 1-5 Diagnostic output 6-5
Error messages and connection failures C-2 Error messages and socket failures C-2 Failover rate configuration 6-5 Failure recovery limitations 6-2 Functionality Limitations 6-2 Hardware requriements 6-3 IP status API 7-2
Rules of operation 6-2 Socket status API 7-6
Supported network configurations 6-4 TCP/IP port use 6-6
Computer Network Redundancy 1-4 Computers
In server redundancy 2-6 Configuration
Computer cabling redundancy 6-4 Database logging 3-6
Order of in base system 3-1 Server redundancy procedures 3-1 Connect_Timeout 6-5
Connection Failures
D
Data Collection
Redundant system behavior 2-9 Database Logging
Configuration 3-6
Requirements for server redundancy 2-4 Resynchronizing files in server redundancy 5-8 Datamerge.exe 5-9
DDE Client
Redundant configuration A-5 Definition
Primary server 2-6 Secondary Server 2-6 Detect
Cause for primary server failure 5-6 Devcom Configuration
Server redundancy 3-5 Device Communications
Operation during failover 5-5 Diagnostic Output
Computer cabling redundancy 6-5
E
Error Messages
Computer cabling redundancy and Binding failures C-1
Computer cabling redundancy and connection failures C-2
Computer cabling redundancy and missed communications C-2
Computer cabling redundancy, Socket failures C-2
F
Failover
Alarm management operation during 5-5 Automatic-overview 2-7
Device communications operation during 5-5 Point management operation during 5-5 Runtime interfaces during 5-6
2-14
Server Redundancy 2-14 System operation during 5-5 User logons operation during 5-6 Failover Rate Configuration
Computer cabling redundancy 6-5 Server redundancy B-1
Failure
Detecting cause on primary server 5-6 Network failure exceptions 5-11 Process failure exceptions 5-10
Failure Exceptions Server redundancy 5-10
2-9
Failure recovery Limitations Server redundancy 2-9 Failure Recovery Limitations
Computer cabling redundancy 6-2 FindCloseSocket 7-10 FindCloseSocketChangeNotification 7-9 FindFirstSocket 7-9 FindFirstSocketChangeNotification 7-8 FindNextSocket 7-10 FindNextSocketChangeNotification 7-8 Functionality Limitations
Computer cabling redundancy 6-2 Server redundancy 2-8
Functions
IP status API 7-3 Socket status API 7-8
G
Genius
Redundant Configuration A-3 GetNextSocketChange 7-5 Global Point
Server redundancy configuration 3-5
H
Hardware
Computer requirements for server redundancy 2-2 Network requirements for server redundancy 2-2 Hardware requirements
Server redundancy 2-1 Hardware Requirements
Computer cabling redundancy 6-3
I
InitSocketChange 7-3 Integration Redundant features 2-6 Introduction Server redundancy 2-6 IP Addresses cimhosts.txt 6-4 IP Status API 7-1, 7-2 CloseSocketChange 7-4 Functions 7-3 GetNextSocketChange 7-5 InitSocketChange 7-3 WaitSocketChange 7-3L
Limitations
Circumvent in automatic redundancy 5-10 Computer cabling redundancy functionality 6-2 Limitations Failure Recovery
Computer cabling redundancy 6-2
M
Manual Redundancy Introduction 2-6 Map Drive
Requirement for redundancy 2-4 Missed Communications
Error messages and computer cabling redundancy C-2 Modbus RTU
Redundant configuration A-7 Modbus TCP/IP
Redundant configuration A-8 Modubs Plus
Redundant configuration A-6 Monitoring API
Computer cabling redundancy 7-1
N
Network
Configuration requirements for server redundancy 2-5 Requirements for server redundancy 2-2
Server redundancy failures 5-11 Network Configuration
Server redundancy 3-3 Normal operating procedures
Server redundancy 5-1
Normal Operating Procedures Startup and Shutdown Server redundancy 5-1
Number_of_Ports 6-6
O
Overview
Before you start 2-1
P
Ping_Count 6-5 Ping_Interval 6-5 PLC Redundancy 1-3 Point Bridge
Redundant configuration A-8 Point Management
Operation during failover 5-5
Primary
Sysnchronize databases on the primary and secondary nodes 5-9
Primary and Secondary Computers Requirements for server redundancy 2-4 Primary Computer
Mapped drive requirement in redundancy 2-4 Primary Server
Automatic failover overview 2-7 Definition 2-6
Failover return overview 2-7
Reset after recovery, Server redundancy 5-7 Privileges
Required for mapping a slave drive 2-7 Problems Database merging D-1 Procedures Server redundancy 3-1 Process Failures Server redundancy 5-10 Project
Configuration in server redundancy 3-2 Configure project to start at boot 5-4 Start a redundant project 5-2 Start from a secondary server 5-3 Stop a redundant project 5-3 Project Failover Automatic-overview 2-7
R
REDUND_LINK_SLEEP B-2 REDUND_PROBE_DELAY B-1 REDUND_PROBE_INTERVAL B-1 Redundancy Cabling 1-3 General definition 1-2 Host Computer network 1-4 PLC 1-3Server 1-4
Redundant configuration
Allen-Bradley communications A-4 Allen-Bradley Data Highway Plus A-5
Redundant Configuration APPLICOM A-5 CCM2 A-3 DDE client A-5 Genius A-3 Modbus Plus A-6 Modbus RTU A-7 Modbus TCP/IP A-8 Point bridge A-8 Series 90 TCP/IP A-2
Series 90 TCP/IP redundancy A-2 SNPX A-4
Redundant System Behavior Alarm management 2-14 CimView 2-14
Data collection 2-9 Setpoints 2-12 Requirement
Mapped drive in redundancy 2-4 Requirements
User privileges for mapping a drive 2-7 Requirements for Server Redundancy
Application 2-4 Computer 2-2 Database logging 2-4 Network 2-2 Network configuration 2-5 Scripting 2-4 Time synchronization 2-5
Use of primary/secondary computers 2-4 Reset
After automatic failover 2-7 Primary server after recovery 5-7 Re-synchronize
Database logging files 5-8 Rules of Operation
Computer cabling redundancy 6-2 Runtime Interfaces
Operation during failover 5-6
S
Scripting
Requirements for server redundancy 2-4 Secondary
Synchronzie databases on the primary and secondary nodes 5-9
Secondary Computer
Mapped drive requirement in redundancy 2-4 Secondary Server
Automatic failover overview 2-7 Definition 2-6
Failover return overview 2-7 Starting a project from 5-3 Series 90 TCP/IP
Redundant configuration A-2 Series 90 TCP/IP redundancy
Redundant configuration A-2 Server redundancy
Hardware requirements 2-1 Server Redundancy 1-4
Allen-Bradley communications A-4 Allen-Bradley Data Highway Plus A-5 APPLICOM A-5
CCM2 A-3
Configuration procedures 3-1 DDE client A-5
Definition for CIMPLICITY HMI 1-5 Devcom configuration 3-5
Failover 2-14
Failover rate configuration B-1 Failure Recover Limitations 2-9 Functionality limitations 2-8 Genius A-3
Global point configuration 3-5 Modbus Plus A-6
Modbus RTU A-7 Modbus TCP/IP A-8 Network configuration 3-3 Network failures 5-11
Normal operating procedures 5-1 Point bridge A-8
Process failures 5-10
Resetting primary server after recovery 5-7 Resynchronizing database logging files 5-8 Series 90 TCP/IP A-2
Series 90 TCP/IP redundancy A-2 Slave startup timeout B-2
SNPX A-4
Supported communication interfaces, About A-1 User registration synchronization B-2
Server Redundancy Failure Exceptions 5-10 Server Redundancy System Operation During
Failover 5-5
Server RedundancyNormal startup and shutdown 5-1 Redundant system behavior 2-12
Slave Startup Timeout Server redundancy B-2
SLAVE_STARTUP_TIMEOUT B-2 SNPX
Redundant configuration A-4 Socket failures
Socket Status API 7-1, 7-6 FindCloseSocket 7-10 FindCloseSocketChangeNotification 7-9 FindFirstSocket 7-9 FindFirstSocketChangeNotification 7-8 FindNextSocket 7-10 FindNextSocketChangeNotification 7-8 Functions 7-8 Solutions Database merging D-1 Start
A project from a secondary server 5-3 Redundant project 5-2
Start_Port_Range 6-6 Stop
A redundant project 5-3
Supported Network Configurations Computer cabling redundancy 6-4 System Operation During Failover
Server redundancy 5-5
T
TCP/IP Port Use
Computer cabling redundancy 6-6 Time Synchronization
Requirements for server redundancy 2-5
U
User
Requirements for mapping a drive 2-7 User Logons
Operation during failover 5-6
Redundant system behavior 2-14 2-14
User Registration Synchronization Server redundancy B-2