The Open Systems Event
Replicator Error Message format is:
The
Message ID below is composed of the Error Code, Error Class, Error Action
and Error State.
General Messages
|
|
WARNINGS
|
|
Message
ID
|
Explanation
|
Resolution
|
|
1001
|
W
|
L
|
N
|
Application initialized.
|
Informational.
|
|
1002
|
W
|
L
|
S
|
Application shutting down.
|
Informational.
|
|
1300
|
W
|
L
|
N
|
Application state has changed
to: (ACTIVE).
|
Server has entered an active
state.
|
|
1301
|
W
|
L
|
C
|
Application state has changed
to: (CONFIGURE).
|
Server is processing a CDD
for deployment.
|
|
1302
|
W
|
L
|
D
|
Application state has changed
to: (DISABLED).
|
Server has entered an inactive
state. May indicate an error has occurred. Check log for more
information.
|
|
1303
|
W
|
L
|
S
|
Application state has changed
to: (SHUTDOWN).
|
Server has entered a shutdown
state due to normal process control.
|
|
1304
|
W
|
L
|
N
|
Application
is attempting to switch identity: (<old
identity>)-->({<new
identity>).
|
No
action required.
|
|
ERRORS
|
|
Message ID
|
Explanation
|
Resolution
|
|
1501
|
E
|
X
|
U
|
Unable to initialize application
state.
|
Error occurred while reading
internal configuration files. Please contact technical support.
|
|
1502
|
E
|
X
|
D
|
Unable to write to system
log: (<path to log file>).
|
Error occurred while writing
to log file. Verify log file directory is writable and user ID
has appropriate permissions.
|
|
1503
|
E
|
X
|
D
|
Unable to execute user notification.
Return code from OS Command (<error code>)
|
Verify that the notification
command can be executed. Refer to User Guide.
|
|
1504
|
E
|
L/N3
|
D
|
Unable to allocate dynamic
memory.
|
Check system resources.
|
|
1505
|
E
|
L/N3
|
D
|
System call failure (<system
call>): (<OS specific error>).
|
Contact technical support.
|
|
1506
|
E
|
L/N3
|
S
|
The process configuration
path length exceeds the maximum allowed.
|
Reinstall to allocation with
a shorter install path length. See your OS documentation for path
length limits.
|
|
1507
|
E
|
L/N3
|
S
|
Unable to create a data directory
(<directory name>): (<OS specific error msg>).
|
See OS error message and
correct as appropriate.
|
|
1508
|
E
|
X
|
S
|
Unable to initialize the
Exec sub-system.
|
Contact technical support.
|
|
1509
|
E
|
X
|
S
|
The CONNX registry cannot
be read or does not contain a value for: (CONNX.REPLICATION.INSTALLPATH).
|
Windows: Verify that the
INSTALLPATH value is correct in the CONNX Configuration Manager
(CONNX\Replication).
Unix/Linux: Use the SqlRegistry tool to verify
the INSTALLPATH value is correct.
|
|
1510
|
E
|
L/N3
|
S
|
Event Replicator message
API version mismatch.
|
Verify all Event Replicator
components are upgraded to a compatible version.
|
|
1511
|
E
|
L/N3
|
D
|
Unable to resolve host (<host>).
|
DNS name did not resolve.
Specify dot notation addresses.
|
|
1512
|
E
|
L
|
N
|
Bad multi-packet message.
Fragment sequence out of order.
|
Message queue internal error.
Contact technical support.
|
|
1800
|
E
|
X
|
U
|
The process configuration
path is either blank or the length exceeds the maximum allowed.
|
Reinstall to allocation with
a shorter install path length. See your OS documentation for path
length limits.
|
|
1801
|
E
|
X
|
U
|
The process name is either
blank or the length exceeds the maximum allowed.
|
Internal error. Contact technical
support.
|
|
1802
|
E
|
X
|
U
|
The specified configuration
directory does not exist.
|
Windows: Verify that the
INSTALLPATH value is correct in the CONNX Configuration Manager
(CONNX\Replication)
Unix/Linux: Use the SqlRegistry tool to verify
the INSTALLPATH value is correct
|
|
1803
|
E
|
X
|
U
|
Unable to create a log file
directory.
|
Verify installation directory
is writable and user ID has appropriate permissions.
|
|
1804
|
E
|
X
|
U
|
Unable to initialize process
log (<logfile>)
|
Verify installation directory
is writable and user ID has appropriate permissions.
|
|
1805
|
E
|
X
|
U
|
Unable to install signal
handler: (<OS-specific error message>).
|
See OS error message and
correct as appropriate.
|
|
1806
|
E
|
X
|
U
|
Application is attempting
to switch identity: (<Engine
ID>)-->(<Engine
ID>).
|
Error notification is enabled
and the notification command is either blank or the length exceeds
the maximum allowed.
|
|
1807
|
E
|
X
|
U
|
The
process version is either blank or the length exceeds the maximum
allowed.
|
Contact
technical support.
|
Admin
|
|
WARNINGS
|
|
Message ID
|
Explanation
|
Resolution
|
|
2001
|
W
|
L
|
N
|
Deployment message queued.
|
Deployment message was sent
to the controller's message queue. No action required.
|
|
2002
|
W
|
L
|
N
|
Preparing to queue Deployment
message.
|
No action required.
|
|
2003
|
W
|
L
|
N
|
Deployment CDD Initialized.
|
No action required.
|
|
ERRORS
|
|
Message ID
|
Explanation
|
Resolution
|
|
2501
|
E
|
L
|
N
|
Invalid configuration path.
|
Path does not exist.
Windows: Verify that the INSTALLPATH value
is correct in the CONNX Configuration Manager (CONNX\Replication).
Unix/Linux: Use the SqlRegistry tool to verify
the INSTALLPATH value is correct.
|
|
2502
|
E
|
L
|
N
|
Unable to open master configuration
file: API Error (<OS-specific error>).
|
Verify installation directory
is writable to the Admin process.
|
|
2503
|
E
|
L
|
N
|
Unable to initialize replications.
|
Contact technical support.
|
|
2504
|
E
|
L
|
N
|
Unsupported source database
type.
|
An internal error has occurred
in the deployed CDD. Contact technical support.
|
|
2505
|
E
|
L
|
N
|
Replication configuration
contains no active replications.
|
Deploy replications.
|
|
2506
|
E
|
L
|
N
|
System call failure (<system
call>): (<OS specific error>).
|
See OS error message and
correct as appropriate.
|
|
2507
|
E
|
L
|
N
|
Unable to open master configuration
file: IO Error (<OS specific error>).
|
Ensure the install directory
is writable and user ID has appropriate permissions. See OS error
message and correct as appropriate.
|
|
2508
|
E
|
L
|
N
|
Unable to connect to Replicator
queue service on (<queue
server host>):(<server port>): (<queue
sub-system error>).
|
Ensure that the message queue
has been started and initialized correctly, the port number in
the Replication Administrator matches the port number in the Registry,
and the message queue directory is writable to the current process.
See the User Guide for more information.
|
|
2509
|
E
|
L
|
N
|
Unable to open Replicator
work queue: (<queue subsystem error>).
|
Ensure that the message queue
has been started and initialized correctly, the port number in
the Replication Administrator matches the port number in the Registry,
and the message queue directory is writable to the current process.
See the User Guide for more information.
|
|
2510
|
E
|
L
|
N
|
Unable to enqueue work message:
(<queue subsystem error>).
|
Ensure that the message queue
has been started and initialized correctly, the port number in
the Replication Administrator matches the port number in the Registry,
and the message queue directory is writable to the current process.
See the User Guide for more information.
|
|
2511
|
E
|
L
|
N
|
Unable to retrieve Support
DLL instance.
|
Contact technical support.
|
|
2512
|
E
|
L
|
N
|
Unable to initialize Support
DLL.
|
Contact technical support.
|
|
2513
|
E
|
L
|
N
|
Unable to find CDD Object
(<CDD object>).
|
Contact technical support.
|
|
2514
|
E
|
L
|
N
|
Unable to update CDD Object
(<CDD object>).
|
Contact technical support.
|
|
2515
|
E
|
L
|
N
|
Unable to find Replication
server information.
|
Contact technical support.
|
|
2516
|
E
|
L
|
N
|
Unable to open Replication
Work Queue (<queue
subsystem error>). Queue does not exist.
|
Ensure that the message queue
has been started and initialized correctly, the port number in
the Replication Administrator matches the port number in the Registry,
and the message queue directory is writable to the current process.
See the User Guide for more information.
|
|
2517
|
E
|
L
|
N
|
Unable to initialize Replication
Server Map.
|
Contact technical support.
|
|
2518
|
E
|
L
|
N
|
Bad Reply from Status Message.
|
Contact technical support.
|
|
2519
|
E
|
L
|
N
|
Replication Server Map not
found.
|
CDD not deployed properly.
Re-deploy CDD.
|
|
2520
|
E
|
L
|
N
|
Failed to retrieve Server
Status.
|
Refresh Server Status. If
the problem persists, contact technical support.
|
|
2521
|
E
|
L
|
N
|
Failed to write Server Status.
|
Ensure that install directory
is writable to the current process.
|
|
2522
|
E
|
L
|
N
|
Invalid Server Status path:
(<server status database path>).
|
Ensure that INSTALLPATH is
set correctly.
|
|
2523
|
E
|
L
|
N
|
Invalid replication server
ID: (<replication server ID>).
|
Contact technical support.
|
|
2524
|
E
|
L
|
N
|
Invalid replication server
name: (<replication server name>).
|
Validate the server name
on the Configure Servers dialog in the Replication Administrator.
If the server name is correct, ensure that the server is connected
to the network and is operating correctly.
|
|
2525
|
E
|
L
|
N
|
Invalid server state request:
(<server state>).
|
Contact technical support.
|
|
2526
|
E
|
L
|
N
|
Unable to delete status queue
(<queue name>): (<queue subsystem error>).
|
Non-fatal error; if problem
persists, start and stop the CONNX message queue service (Windows)
or Daemon (Unix/Linux).
|
|
2527
|
E
|
L
|
N
|
Invalid target table ID:
(<table ID>).
|
Contact technical support.
|
|
2528
|
E
|
L
|
N
|
Configuration API error:
(<API error>).
|
Contact technical support.
|
|
2529
|
E
|
L
|
N
|
Failed to purge existing
Server Status.
|
Ensure that the install directory
is writable to the Replication Administrator and retry Server
Status. If problem persists, contact technical support.
|
|
2530
|
E
|
L
|
N
|
Failed to dequeue Server
Status: (<queue subsystem error>).
|
Ensure that the message queue
has been started and initialized correctly, the port number in
the Replication Administrator matches the port number in the Registry,
and the message queue directory is writable to the current process.
See the User Guide for more information.
|
|
2531
|
E
|
L
|
N
|
Incompatible API version
in ADM message reply.
|
One or more components are
at a different version level than the Administrator. Ensure that
all components of the Replication Server have the same build number
and version.
|
|
2532
|
E
|
L
|
N
|
Unable to allocate dynamic memory.
|
Check system resources for
available memory.
|
|
2533
|
E
|
L
|
N
|
Unable to initialize status queue. Unable to
report status.
|
Ensure that the CONNX message
queue service is running.
|
|
2534
|
E
|
L
|
N
|
Unable to gain exclusive access to deployment
CDD.
|
Ensure that the CDD is not
open by another Event Replication Administrator or the CONNX Data
Dictionary Manager.
|
|
2535
|
E
|
L
|
N
|
Unable to purge the Controller work queue (<queue
name>): (<queue subsystem error>).
|
Ensure that the message queue
has been started and initialized correctly, the port number in
the Replication Administrator matches the port number in the Registry,
and the message queue directory is writable to the current process.
See the User Guide for more information.
|
Controller
|
|
WARNINGS
|
|
Message ID
|
Explanation
|
Resolution
|
|
3001
|
W
|
L
|
N
|
De-initializing driver support
failed.
|
Non-fatal warning. No action
necessary.
|
|
3002
|
W
|
L
|
N
|
Recovering from an unclean
shutdown.
|
Previous shutdown was not
executed via normal process mechanism. No action necessary.
|
|
3003
|
W
|
L
|
N
|
Engine unreachable: PID:(<process
ID>). Attempting to re-spawn: (<engine ID>).
|
Controller lost TCP/IP connection
to Replication Engine and is attempting to restart Engine.
|
|
3004
|
W
|
L
|
S
|
Stop service request received.
|
No action necessary.
|
|
3005
|
W
|
L
|
N
|
Monitor accept for unknown
engine: (<engine ID>).
|
No action necessary.
|
|
3006
|
W
|
L
|
N
|
Master configuration contains
invalid engine count. Defaulting to 1.
|
No action necessary.
|
|
3007
|
W
|
L
|
N
|
Engine spawned: PID:(<process
ID>). ID:(<engine ID>).
|
Engine has been started successfully.
No action necessary.
|
|
3008
|
W
|
L
|
N
|
Engine initialization complete:
PID:(<process ID>) ID:(<engine ID>).
|
No action necessary.
|
|
3009
|
W
|
L
|
N
|
Event producer initialization
complete. ID:(<engine ID>).
|
No action necessary.
|
|
3010
|
W
|
L
|
N
|
Deploy succeeded.
|
No action necessary.
|
|
3011
|
W
|
L
|
N
|
Deploy failed.
|
Check the Controller log
file for the preceding messages containing additional error information
and take action based on those messages.
|
|
ERRORS
|
|
Message
ID
|
Explanation
|
Resolution
|
|
4001
|
E
|
L/N1
|
N
|
Unable to connect to local
queue service: (<queue subsystem error>).
|
Ensure that the message queue
has been started and initialized correctly, the port number in
the Replication Administrator matches the port number in the Registry,
and the message queue directory is writable to the current process.
See the User Guide for more information.
|
|
4002
|
E
|
L/N1
|
N
|
Unable to open controller
work queue: (<queue subsystem error>).
|
Ensure that the message queue
has been started and initialized correctly, the port number in
the Replication Administrator matches the port number in the Registry,
and the message queue directory is writable to the current process.
See the User Guide for more information.
|
|
4003
|
E
|
L/N2
|
N
|
Unable to dequeue work message:
(<queue subsystem error>).
|
Ensure that the message queue
has been started and initialized correctly, the port number in
the Replication Administrator matches the port number in the Registry,
and the message queue directory is writable to the current process.
See the User Guide for more information.
|
|
4004
|
E
|
L/N3
|
N
|
Unable to open master configuration
file: IO Error: (<OS
specific error>).
|
See OS error message and
correct as appropriate.
|
|
4005
|
E
|
L/N1
|
N
|
Unable to open EP Identity
queue: (<queue subsystem error>).
|
Ensure that the message queue
has been started and initialized correctly, the port number in
the Replication Administrator matches the port number in the Registry,
and the message queue directory is writable to the current process.
See the User Guide for more information.
|
|
4006
|
E
|
L/N3
|
N
|
Unable to spawn engine: (<OS specific error>).
|
See OS error message and
correct as appropriate.
|
|
4007
|
E
|
L/N1
|
N
|
Unable to connect to EP queue
service: (<queue subsystem error>).
|
Ensure that the message queue
has been started and initialized correctly, the port number in
the Replication Administrator matches the port number in the Registry,
and the message queue directory is writable to the current process.
See the User Guide for more information.
|
|
4008
|
E
|
L/N1
|
N
|
Unable to open EP work queue:
(<queue subsystem error>).
|
Ensure that the message queue
has been started and initialized correctly, the port number in
the Replication Administrator matches the port number in the Registry,
and the message queue directory is writable to the current process.
See the User Guide for more information.
|
|
4009
|
E
|
L/N1
|
N
|
Unable to open EP target
queue (<queue name>): (<queue subsystem error>).
|
Ensure that the message queue
has been started and initialized correctly, the port number in
the Replication Administrator matches the port number in the Registry,
and the message queue directory is writable to the current process.
See the User Guide for more information.
|
|
4010
|
E
|
L/N2
|
N
|
Unable to enqueue EP work
message: (<queue subsystem error>).
|
Ensure that the message queue
has been started and initialized correctly, the port number in
the Replication Administrator matches the port number in the Registry,
and the message queue directory is writable to the current process.
See the User Guide for more information.
|
|
4011
|
E
|
L/N2
|
N
|
Unable to enqueue Engine
work message: (<queue subsystem error>).
|
Ensure that the message queue
has been started and initialized correctly, the port number in
the Replication Administrator matches the port number in the Registry,
and the message queue directory is writable to the current process.
See the User Guide for more information.
|
|
4012
|
E
|
L/N3
|
N
|
Unable to open master configuration
file: (<OS specific
error>).
|
See OS error message and
correct as appropriate.
|
|
4013
|
E
|
L/N3
|
N
|
Unable to initialize replications:
(<API error message>).
|
Contact technical support.
|
|
4014
|
E
|
L/N3
|
N
|
Unsupported backend for replication
source.
|
Configuration files may have
been modified outside Event Replication. Re-deploy replications.
|
|
4015
|
E
|
L/N1
|
N
|
Invalid target table id for
replication
|
Configuration files may have
been modified outside Event Replication. Re-deploy replications.
|
|
4016
|
E
|
L/N1
|
N
|
Replication configuration
contains no active replications.
|
Configuration files may have
been modified outside Event Replication. Re-deploy replications.
|
|
4017
|
E
|
L/N3
|
N
|
Unable to write master configuration
file: IO Error: (<OS
specific error>).
|
Verify install directory
is writable and user ID has appropriate permissions.
|
|
4018
|
E
|
L/N3
|
S
|
Unable to open replication
license file: (<API error message>).
|
Ensure that a valid Event
Replication license is installed and registered.
|
|
4019
|
E
|
L/N3
|
S
|
Unable to lock replication
license file: (<API error message>).
|
User license count has been
exceeded. Ensure that a valid Event Replication license is installed
and registered.
|
|
4020
|
E
|
L/N3
|
S
|
Driver support initialization
failed: (<API error message>).
|
Windows: DLL was not registered.
Ensure that the system was rebooted after installation.
Unix/Linux: Shared library could not be located
or loaded. Check dependencies.
|
|
4021
|
E
|
L
|
N
|
Unable to delete failed configuration:
(<config file name>): (<OS
specific error>).
|
Ensure that the install directory
is writable to the Controller user/process. See OS error
message and correct as appropriate.
|
|
4022
|
E
|
L
|
N
|
Bad work message. Unexpected
message fragment type: (<embedded message type>).
|
Contact technical support.
|
|
4023
|
E
|
L
|
N
|
Unable to flush configuration
to disk: (<OS specific
error>).
|
See OS error message and
correct as appropriate.
|
|
4024
|
E
|
L
|
N
|
Unable to open existing config
(<config file name>): (<OS
specific error>) Starting over.
|
See OS error message and
correct as appropriate.
|
|
4025
|
E
|
L
|
N
|
Unable to map existing config
(<config file name>): (<OS
specific error>). Starting over.
|
See OS error message and
correct as appropriate.
|
|
4026
|
E
|
L
|
N
|
Configuration mapped to NULL.
Starting over.
|
Out of resources. Check disk
space and available memory.
|
|
4027
|
E
|
L
|
N
|
Unable to create new configuration
(<config file name>): (<OS
specific error>).
|
Out of resources. Check disk
space and available memory.
|
|
4028
|
E
|
L
|
N
|
Unable to map new configuration
(<config file name>): (<OS
specific error>).
|
Out of resources. Check disk
space and available memory.
|
|
4029
|
E
|
L
|
N
|
New configuration mapped
to NULL.
|
Out of resources. Check disk
space and available memory.
|
|
4030
|
E
|
L/N1
|
N
|
Unable to initialize target
queues. Exceeded maximum attempts to connect to queue service.
|
Ensure that the CONNX message
queue service is running.
|
|
4031
|
E
|
L/N1
|
N
|
Invalid replication server
ID. Unable to process configuration.
|
Configuration files may have
been modified outside Event Replication. Re-deploy replications.
|
|
4032
|
E
|
L/N1
|
N
|
Cannot retrieve object from
master configuration: (<configuration object>).
|
Contact technical support.
|
|
4033
|
E
|
L/N1
|
N
|
Invalid source table id for
replication: (<table ID>).
|
Contact technical support.
|
|
4035
|
E
|
L/N1
|
C
|
Socket error sending status
change to producer
|
This error indicates a problem
with the communication between the controller and the producer.
Ensure that the source nucleus is running and the nucleus
log indicates that replication was successfully initialized. Also
ensure that there are no firewalls present between the controller
and the producer that would prevent communication. If the
producer is running and there are no network issues, contact technical
support.
|
|
4036
|
E
|
L/N1
|
N
|
Unable to create control
reply queue: (<queue subsystem error>).
|
Ensure that the message queue
has been started and initialized correctly, the port number in
the Replication Administrator matches the port number in the Registry,
and the message queue directory is writable to the current process.
See the User Guide for more information.
|
|
4037
|
E
|
L/N1
|
S
|
Configuration reset. Stopping
all servers and shutting down.
|
Invalid license or all active
replications removed from this CDD. Either correct the license
file,
|
|
4038
|
E
|
L/N3
|
S
|
Unable to accept connections
on port (<port number>).
|
Attempted to accept connections
on the first available port. No ports were available. Ensure that
there is a range of ports available. If configured to a specific
port, ensure that port is available.
|
|
4039
|
E
|
L
|
N
|
Monitor request timed out.
|
Attempted to communicate
with the Replication Engine but did not receive a timely reply.
Check the Event Consumer log files.
|
|
4040
|
E
|
L
|
N
|
Unable to send engine monitor
request: (<socket error>).
|
TCP/IP error. Check the Event
Consumer log files.
|
|
4041
|
E
|
L
|
N
|
Monitor accept for active
or deactivated engine.
|
Sequence error detected and
corrected. No action necessary.
|
|
4042
|
E
|
L
|
N
|
Monitor unable to retrieve
configuration for re-spawned engine.
|
Controller is in an invalid
state. Contact technical support.
|
|
4043
|
E
|
L
|
N
|
Monitor timed out sending
configuration to re-spawned engine.
|
Communication with engine
lost; system will attempt to reconnect. No action necessary.
|
|
4044
|
E
|
L
|
N
|
Monitor error sending configuration
to re-spawned engine: (<socket error>).
|
TCP/IP error. Check the Event
Consumer log files.
|
|
4045
|
E
|
L
|
N
|
Monitor request reply timed
out.
|
Engine failed to respond
in a timely manner. Check the Event Consumer log files.
|
|
4046
|
E
|
L
|
N
|
Unable to receive engine
monitor request reply: (<socket error>).
|
TCP/IP error. Check the Event
Consumer log files.
|
|
4047
|
E
|
L/N3
|
S
|
Unable to restart acceptor
for connections on port (<port number>).
|
Controller was configured
to accept on a specific port and port is no longer available.
Specify an available port.
or
Controller was configured to accept on a range
of ports and no ports in the range were available. Ensure that
there are available ports.
|
|
4048
|
E
|
L/N3
|
S
|
Monitor accept for an engine
with a mis-matched process ID (<engine
ID>_<engine ID>):
(<current process ID>)
!= (<incoming process ID>).
|
Contact technical support.
|
|
4049
|
E
|
L
|
N
|
Database specific configuration
missing table descriptors.
|
Contact technical support.
|
|
4050
|
E
|
L
|
N
|
Invalid user/pass length
in master configuration. Please re-configure and re-deploy.
|
Contact technical support.
|
|
4051
|
E
|
L/N1
|
N
|
Invalid source database id
for replication: (<database ID>).
|
Contact technical support.
|
|
4052
|
E
|
L
|
N
|
Connection timed out sending
configuration to engine.
|
Non-fatal error; engine will
re-attempt connection. No action necessary.
|
|
4053
|
E
|
L
|
N
|
Connection error sending
configuration to engine: (<socket error>).
|
TCP/IP error. Check the Event
Consumer log files.
|
|
4054
|
E
|
L
|
N
|
Unknown engine dereferenced:
(<engine ID>).
|
Contact technical support.
|
|
4055
|
E
|
L
|
N
|
Unable to connect to Admin
queue service: (<queue subsystem error>).
|
Ensure that the message queue
has been started and initialized correctly, the port number in
the Replication Administrator matches the port number in the Registry,
and the message queue directory is writable to the current process.
See the User Guide for more information.
|
|
4056
|
E
|
L
|
N
|
Unable to open Admin status
queue: (<queue subsystem error>).
|
Ensure that the message queue
has been started and initialized correctly, the port number in
the Replication Administrator matches the port number in the Registry,
and the message queue directory is writable to the current process.
See the User Guide for more information.
|
|
4057
|
E
|
L
|
N
|
Unable to enqueue message
on Admin status queue: (<queue subsystem error>).
|
Ensure that the message queue
has been started and initialized correctly, the port number in
the Replication Administrator matches the port number in the Registry,
and the message queue directory is writable to the current process.
See the User Guide for more information.
|
|
4058
|
E
|
L/N1
|
N
|
Master configuration file
does not exist: (<config file name>). Unable to process.
|
Configuration files may have
been deleted outside Event Replication. Redeploy replication CDD.
|
|
4059
|
E
|
L/N1
|
N
|
Unable to load replication
columns from master configuration for ID: (<table ID>).
Error: (<API error>).
|
Contact technical support.
|
|
4060
|
E
|
L
|
N
|
Unable to remove old configuration:
(<config file name>) Error: (<OS
specific error>).
|
See OS error message and
correct as appropriate.
|
|
4061
|
E
|
L
|
N
|
Unable to initialize engine:
PID: (<process ID>) ID: (<engine ID>).
|
Contact technical support.
|
|
4062
|
E
|
L
|
N
|
Unable to initialize event
producer.
|
Contact technical support.
|
|
4063
|
E
|
L
|
N
|
Monitor accept for disabled
engine.
|
Sequence error detected and
corrected. No action necessary.
|
|
4064
|
E
|
L/N3
|
N
|
Engine request for respawn
denied. Engine disabled: PID: (<process ID>) ID:
(<engine ID>). Please contact technical support.
|
Contact technical support.
|
|
4065
|
E
|
L
|
N
|
Version mismatch for engine:
ID: (<engine ID>).
|
One or more components are
at a different version level than the Controller. Ensure that
all components of the Replication Server have the same build number
and version.
|
|
4066
|
E
|
L
|
N
|
Engine configuration status
check send timed out. ID: (<engine ID>).
|
Ensure that the system has
sufficient resources and that the install directory is readable
and writable. Check the Engine logs.
|
|
4067
|
E
|
L
|
N
|
Engine configuration status
check send error: ID: (<engine ID> ) Error: (<socket
error>).
|
Ensure that the system has
sufficient resources and that the install directory is readable
and writable. Check the Engine logs.
|
|
4068
|
E
|
L
|
N
|
Engine configuration status
check reply error: ID:(<engine ID>) Error: (Status
not NORMAL)
|
Check the Engine logs.
|
|
4069
|
E
|
L
|
N
|
Engine configuration status
check reply timed out. ID: (<engine ID>).
|
Ensure that the system has
sufficient resources and that the install directory is readable
and writable. Check the Engine logs.
|
|
4070
|
E
|
L
|
N
|
Engine configuration status
check reply error: ID: (<engine ID>) Error: (<socket
error>).
|
Ensure that the system has
sufficient resources and that the install directory is readable
and writable. Check the Engine logs.
|
|
4071
|
E
|
L
|
N
|
Unable to create Controller
to EP status queue: (<API
error>).
|
Ensure that the system has
sufficient resources and that the install directory is readable
and writable.
|
|
4072
|
E
|
L
|
N
|
The Controller to EP status
queue has been deleted: (<queue
name>).
|
Contact technical support.
|
|
4073
|
E
|
L
|
N
|
Unable to open Controller
to EP status queue (<queue
name>):
(<queue API error>).
|
Ensure that the system has
sufficient resources and that the install directory is readable
and writable.
|
|
4074
|
E
|
L
|
N
|
Controller to EP status queue
message version mismatch detected.
|
Ensure that the latest version
of the Event Replicator is installed on all machines.
|
|
4075
|
E
|
L
|
N
|
Unknown message type encountered
on Controller to EP status queue: (<internal
message type>).
|
Contact technical support.
|
|
4076
|
E
|
L
|
N
|
The EP has reported a failed
deploy.
|
Consult the appropriate EP
log and correct environment. Re-deploy.
|
|
4077
|
E
|
L
|
N
|
Unknown EP encountered in
post-deploy enquiry: (<EP
id>).
|
Contact technical support.
|
|
4078
|
E
|
L
|
N
|
Error in message dequeue
on Controller to EP status queue (<queue
name>): (<queue API error>).
|
Ensure that the CONNX message
queue is active on all machines involved in replication, the queue
directory is readable and writable, and that the system has sufficient
resources.
|
|
4079
|
E
|
L
|
N
|
Duplicate source column detected:
TBL: (<table
name>) COL: (<column
name>).
|
Contact technical support.
|
|
4080
|
E
|
L
|
N
|
Unable to resolve target
table column: TBL: (<table
name>) COL: (<column
name>).
|
Contact technical support.
|
|
4081
|
E
|
L
|
N
|
Non-unique table column ordinal
detected: (<table name>).
|
Contact technical support.
|
|
4082
|
E
|
L
|
N
|
Fatal error. Unable to configure
producer identities.
|
Contact technical support.
|
|
4083
|
E
|
L
|
N
|
Post-deploy EP status check
exceeded maximum time limit.
|
Ensure that the Adabas nucleus
has been started and has been correctly configured for replication.
|
|
4084
|
E
|
L
|
N
|
Source table has no index
defined: (<table name>).
|
Replications must be configured
with at least one primary index.
|
|
4085
|
E
|
L
|
N
|
Target table has no index
defined: (<table name>).
|
Replications must be configured
with at least one primary index.
|
|
4086
|
E
|
L/N1
|
N
|
Unable to open license for
database involved in replication (<DB
name>): (<API error message>)
|
Each database involved in
replication must have a corresponding license file. Ensure that
your license server is properly configured and running.
|
|
4087
|
E
|
L/N1
|
N
|
Unable to lock license for
database involved in replication (<DB
name>): (<API error message>)
|
Each database involved in
replication must have a corresponding license file. Ensure that
your license server is properly configured and running.
|
|
4200
|
E
|
L
|
N
|
Unrecognized ADABAS table
name format: (<Adabas table name>). Table: (<table
name>).
|
Contact technical support.
|
|
4201
|
E
|
L
|
N
|
Invalid column name exceeds
maximum length. Column: (<column name>). Table: (<table
name>).
|
Contact technical support.
|
|
4202
|
E
|
L
|
N
|
Invalid virtual column type
in configuration. Column: (<column name>). Table:
(<table name>).
|
Contact technical support.
|
|
4203
|
E
|
L
|
N
|
Invalid index column type
in configuration. Column: (<column name>). Table:
(<table name>).
|
Contact technical support.
|
|
4204
|
E
|
L
|
N
|
Duplicate table encountered
in ADABAS cluster definition: Table: (<table name>):
({int}).
|
Contact technical support.
|
|
4205
|
E
|
L
|
N
|
Non-MU/PE column encountered
in rotated table descriptors (<column name>): (<table
name>).
|
Contact technical support.
|
|
4206
|
E
|
L
|
N
|
MU/PE column encountered
in table index descriptors (<column name>): (<table
name>).
|
Contact technical support.
|
|
4207
|
E
|
L
|
N
|
Unrecognized physical DB
Name format for ADABAS: (<internal
DB name>).
|
Contact technical support.
|
|
4208
|
E
|
L
|
N
|
Unable to create queue name.
Max queue name exceeded (<max
value>): (<supplied
value>).
|
Contact technical support.
|
|
4209
|
E
|
L
|
N
|
No ADABAS cluster definitions
match the requested source information.
|
Contact technical support.
|
|
4303
|
E
|
L/N1
|
N
|
Unable to perform Adabas
to Adabas Initial State
|
The Adabas to Adabas initial state process
uses the Adabas utility ADABCK to do a DUMP of the source files
and an OVERLAY on the target. Error 4303 indicates that
there was an error in either the source or target ADABCK process.
Please check the ADABCK log files for information about
the error. These log files are located in the replicator's
log directory (connx32\replication\log on Windows and connx/replicator/log
on Unix/Linux) in a subdirectory named DBxxx where xxx is the
3 digit number of the database ID. Please check the logs
for both the source and target. Note, if an error on the
source prevented any processing, there my not be an ADABCK log
on the target.
|
Event Consumer
|
|
WARNINGS
|
|
Message ID
|
Explanation
|
Resolution
|
|
5001
|
W
|
L
|
C
|
Loading new EC configuration.
|
Informational.
|
|
5002
|
W
|
L
|
D
|
Request to DISABLE PROCESS
received.
|
Informational. A Stop Target
was issued from the Administrator.
|
|
5003
|
W
|
L
|
N
|
Request to initial state
source.
|
Informational.
|
|
5004
|
W
|
L
|
U
|
EC Configuration locked by
another process: (<Configuration
Path>). Exiting.
|
Duplicate engine respawned
due to temporary communication failure. No action required.
|
|
5005
|
W
|
L
|
N
|
Configuration is dirty: recovering
from bad shutdown.
|
Informational
|
|
5006
|
W
|
L
|
N
|
Engine active: Source: (<DB name>):(<internal
DB ID>) --> Target: (<DB
name>):(<internal
DB ID>).
|
Informational
|
|
5201, 5202
|
W
|
L
|
N
|
Record information pertaining
to a 5203 informational message
|
Informational
|
|
5203
|
W
|
L
|
N
|
Engine encountered an SQL
error. The operation will be retried. The SQL error
can be found in the body of the error message. This message
is issued for SQL errors that are transient. They normally
succeed on a retry. If they do not succeed after 3 retries,
error 5702 will be issued.
|
Informational
|
|
5301
|
W
|
L
|
S
|
Shut down occurring before
enqueue of Initial State end card. Initial state will be replayed.
|
Informational.
|
|
5302
|
W
|
L
|
S
|
Shut down occurring before
dequeue of Initial State. Initial State will be replayed.
|
Informational.
|
|
5303
|
W
|
L
|
S
|
Shut down occurring before
dequeue of transaction.
|
Informational.
|
|
ERRORS
|
|
Message ID
|
Explanation
|
Resolution
|
|
5501
|
E
|
L/N2
|
N
|
Unable to connect to EP queue
service: (<queue subsystem error>).
|
Ensure that the message queue
has been started and initialized correctly, the port number in
the Replication Administrator matches the port number in the Registry,
and the message queue directory is writable to the current process.
See the User Guide for more information.
|
|
5502
|
E
|
L/N2
|
N
|
Unable to open cursor for
EP transaction queue: (<queue subsystem error>).
|
Ensure that the message queue
has been started and initialized correctly, the port number in
the Replication Administrator matches the port number in the Registry,
and the message queue directory is writable to the current process.
See the User Guide for more information.
|
|
5503
|
E
|
L/N2
|
N
|
Unable to get message from
EP transaction queue: (<queue subsystem error>).
|
Ensure that the message queue
has been started and initialized correctly, the port number in
the Replication Administrator matches the port number in the Registry,
and the message queue directory is writable to the current process.
See the User Guide for more information.
|
|
5504
|
E
|
L/N1
|
N
|
Unable to dequeue message
from EC work queue: (<queue subsystem error>).
|
Ensure that the message queue
has been started and initialized correctly, the port number in
the Replication Administrator matches the port number in the Registry,
and the message queue directory is writable to the current process.
See the User Guide for more information...
|
|
5505
|
E
|
L/N1
|
N
|
Unable to connect to local
queue service: (<queue subsystem error>).
|
Ensure that the message queue
has been started and initialized correctly, the port number in
the Replication Administrator matches the port number in the Registry,
and the message queue directory is writable to the current process.
See the User Guide for more information.
|
|
5506
|
E
|
L/N1
|
N
|
Unable to open EC work queue:
(<queue subsystem error>).
|
Ensure that the message queue
has been started and initialized correctly, the port number in
the Replication Administrator matches the port number in the Registry,
and the message queue directory is writable to the current process.
See the User Guide for more information.
|
|
5507
|
E
|
L/N3
|
N
|
Unable to create new replication.
|
Check system resources for
available memory.
|
|
5508
|
E
|
X
|
U
|
Unable to initialize the
process name.
|
Non-fatal error. No action
necessary.
|
|
5509
|
E
|
L
|
N
|
Unable to open connection
to status queue service on (<queue service host>):
(<port>): (<queue subsystem error>).
|
Ensure that the message queue
has been started and initialized correctly, the port number in
the Replication Administrator matches the port number in the Registry,
and the message queue directory is writable to the current process.
See the User Guide for more information.
|
|
5510
|
E
|
L
|
N
|
Unable to open status queue
(<queue name>): (<queue subsystem error>).
|
Ensure that the message queue
has been started and initialized correctly, the port number in
the Replication Administrator matches the port number in the Registry,
and the message queue directory is writable to the current process.
See the User Guide for more information.
|
|
5511
|
E
|
L/N3
|
D
|
Unable
to set the process name. Unable to initialize logfile. Deploy
failed.
|
Contact
technical support.
|
|
5512
|
E
|
L/N3
|
D
|
Null record loader returned.
Unable to continue processing.
|
Check system resources for
available memory.
|
|
5513
|
E
|
L/N3
|
D
|
Duplicate initial state end
received.
|
Contact technical support.
|
|
5514
|
E
|
L/N3
|
D
|
Unexpected message in queue.
|
Contact technical support.
|
|
5515
|
E
|
L
|
N
|
Unable to open existing config
(<config file name>): (<OS
specific error>). Starting over.
|
Non-fatal error. System will
recover automatically.
|
|
5516
|
E
|
L
|
N
|
Unable to map existing config
(<config file name>): (<OS
specific error>). Starting over.
|
Non-fatal error. System will
recover automatically.
|
|
5517
|
E
|
L
|
N
|
Configuration mapped to NULL.
Starting over.
|
Out of resources. Check disk
space and available memory.
|
|
5518
|
E
|
L
|
N
|
Configuration file does not
belong to this engine: Expected: (<engine ID>) Mapped:
(<engine ID>). Starting over.
|
Non-fatal error. System will
recover automatically.
|
|
5519
|
E
|
L/N3
|
S
|
Unable to create new configuration
(<config file name>): (<OS
specific error>).
|
Out of resources. Check disk
space and available memory.
See OS error message and correct as appropriate.
|
|
5520
|
E
|
L/N3
|
S
|
Unable to map new configuration
(<config file name>): (<OS
specific error>).
|
Out of resources. Check disk
space and available memory.
See OS error message and correct as appropriate.
|
|
5521
|
E
|
L/N3
|
S
|
New configuration mapped
to NULL.
|
Out of resources. Check disk
space and available memory.
|
|
5522
|
E
|
L
|
N
|
Configuration is dirty: recovering
from bad shutdown.
|
Non-fatal error. No action
necessary.
|
|
5523
|
E
|
L/N3
|
S
|
Unable to flush configuration
to disk: (<OS specific
error>).
|
See OS error message and
correct as appropriate.
|
|
5524
|
E
|
L/N3
|
S
|
Unexpected message state
initializing queue.
|
Contact technical support.
|
|
5525
|
E
|
L/N3
|
S
|
Duplicate initial state found
while initializing queue.
|
Contact technical support.
|
|
5526
|
E
|
L
|
N
|
Unable to enqueue status
message on queue (<queue name>): (<queue subsystem
error>).
|
Ensure that the message queue
has been started and initialized correctly, the port number in
the Replication Administrator matches the port number in the Registry,
and the message queue directory is writable to the current process.
See the User Guide for more information.
|
|
5527
|
E
|
L
|
N
|
Unable to set SQL statement
for replicating: Length is zero.
|
Contact technical support.
|
|
5528
|
E
|
L
|
N
|
Unable to enqueue init marker:
(<queue interface error>).
|
Ensure that the CONNX message
queue service is running.
|
|
5531
|
E
|
L/N3
|
D
|
Unable to restart engine.
Queue initialization failure.
|
Contact technical support.
|
|
5532
|
E
|
L/N3
|
S
|
Control host address has
an invalid length: (<host address>).
|
Contact technical support.
|
|
5533
|
E
|
L/N3
|
S
|
Unable to connect to Controller
service: (<socket error>).
|
Check controller log.
|
|
5534
|
E
|
L
|
S
|
Timeout waiting for initial
configuration. Exiting.
|
System unable to process
all replications. Check for resource availability.
|
|
5535
|
E
|
L
|
S
|
Connection to Controller
service lost: (<socket error>). Exiting.
|
Check controller log.
|
|
5536
|
E
|
L/N3
|
D
|
Corrupt
queue. Partial message detected.
|
Contact technical support.
|
|
5537
|
E
|
L/N3
|
D
|
Corrupt queue. Message sequence
out of order.
|
Contact technical support.
|
|
5538
|
E
|
L/N3
|
D
|
Corrupt queue. Message sequence
out of order.
|
Contact technical support.
|
|
5539
|
E
|
L/N3
|
D
|
Corrupt queue. Message sequence
out of order.
|
Contact technical support.
|
|
5540
|
E
|
L/N3
|
D
|
Corrupt queue. Message sequence
out of order.
|
Contact technical support.
|
|
5541
|
E
|
L/N3
|
D
|
Corrupt queue. Message sequence
out of order.
|
Contact technical support.
|
|
5700
|
E
|
L/N2
|
D
|
Unable to connect to Target
DB: (<SQL error>).
|
Check API error and correct
problem. When problem has been corrected, restart servers from
the Status Tab in the Replication Administrator.
|
|
5701
|
E
|
L/N2
|
D
|
End Transaction error: (<SQL
error>).
|
Check SQL error and correct
problem. When problem has been corrected, restart servers from
the Status Tab in the Replication Administrator.
|
|
5702
|
E
|
L/N2
|
N
|
SQL
error (<SQL error type>): (<SQL error>). Final
try, giving up. Process will disable.
|
Target
table may have been modified externally. Check SQL error and correct
problem. When problem has been corrected, restart servers from
the Status Tab in the Replication Administrator. An initial state
may be required.
|
|
5703
|
E
|
L/N2
|
N
|
SQL
action affected 0 records: (<SQL error>).
|
Target
table may have been modified externally. An initial state may
be required.
|
|
5704
|
E
|
L
|
N
|
Unable to set connection
information: Logical DB name length exceeds maximum: (<logical
DB name>).
|
Contact technical support.
|
|
5705
|
E
|
L
|
N
|
Unable to set connection
information: Connection string length exceeds maximum: (<connection
string>).
|
Contact technical support.
|
|
5706
|
E
|
L/N3
|
D
|
Unable to set connection
attributes: (<SQL error>).
|
Contact technical support.
|
|
5707
|
E
|
L/N2
|
D
|
Current transaction rolled
back.
|
Application state is disabled.
Check Event Consumer logs, fix problems and re-deploy.
|
|
5708
|
E
|
L/N2
|
D
|
Begin transaction failed:
(<SQL error>).
|
Application state is disabled.
Check Event Consumer logs, fix problems and re-deploy.
|
|
5709
|
E
|
L/N2
|
D
|
Invalid transaction. NULL
source map.
|
Contact technical support.
|
|
5710
|
E
|
L
|
N
|
SQL error: (<SQL error>).
|
Transaction event has failed.
Event Consumer will re-connect and retry the transaction.
|
|
5711
|
E
|
L
|
N
|
Current transaction rolled
back.
|
No action required.
|
|
5712
|
E
|
L/N2
|
D
|
Application
has entered an exception state. Current transaction rolled back
|
No
action required.
|
|
5713
|
E
|
L/N3
|
D
|
An error occurred during
initial state processing.
|
Compound error state within
the engine is preventing clean error handling. Prior error messages
contain additional information.
Contact technical support.
|
|
5800
|
E
|
L/N2
|
N
|
Unable to connect to EP queue
service: (<queue subsystem error>).
|
Ensure that the message queue
has been started and initialized correctly, the port number in
the Replication Administrator matches the port number in the Registry,
and the message queue directory is writable to the current process.
See the User Guide for more information.
|
|
5801
|
E
|
L/N2
|
N
|
Unable to open EP transaction
queue (<queue name>): (<queue subsystem error>).
|
Ensure that the message queue
has been started and initialized correctly, the port number in
the Replication Administrator matches the port number in the Registry,
and the message queue directory is writable to the current process.
See the User Guide for more information.
|
|
5802
|
E
|
L/N2
|
N
|
Unable to enqueue message
on EP transaction queue (<queue name>): (<queue
subsystem error>).
|
Ensure that the message queue
has been started and initialized correctly, the port number in
the Replication Administrator matches the port number in the Registry,
and the message queue directory is writable to the current process.
See the User Guide for more information.
|
|
5803
|
E
|
L/N2
|
N
|
Unable to dequeue message
from EP transaction queue (<queue name>): (<queue
subsystem error>).
|
Ensure that the message queue
has been started and initialized correctly, the port number in
the Replication Administrator matches the port number in the Registry,
and the message queue directory is writable to the current process.
See the User Guide for more information.
|
|
5804
|
E
|
L/N2
|
S
|
Error
in COMMIT. Transaction not committable due to application exception
state.
|
Compound
error state within the engine is preventing clean error handling.
Prior error messages contain additional information.
Contact technical support.
|
|
5805
|
E
|
L/N2
|
S
|
Unexpected
end of queue. Transaction manager out of sync with event consumer.
QUEUE:(<queue name>).
|
Contact
technical support.
|
Event Producer
|
|
WARNINGS
|
|
Message ID
|
Explanation
|
Resolution
|
|
6001
|
W
|
L
|
U
|
No existing configuration
found. Creating new configuration.
|
Informational.
|
|
6002
|
W
|
L
|
U
|
Event producer: Identity
configured.
|
Informational.
|
|
6003
|
W
|
L
|
N
|
The transaction cache is
not empty at shutdown.
|
Informational.
|
|
6004
|
W
|
L
|
N
|
The transaction queue is
not empty at shutdown.
|
Informational.
|
|
6005
|
W
|
L
|
N
|
Processing empty transaction.
|
Informational.
|
|
6006
|
W
|
L
|
D
|
Resetting the Event Producer.
Deleting current configuration.
|
Informational. Response to
a request to remove all replications.
|
|
6007
|
W
|
L
|
U
|
Recovering from dirty shutdown.
|
Informational.
|
|
6008
|
W
|
L
|
C
|
Processing existing configuration.
|
Informational.
|
|
6009
|
W
|
L
|
N
|
Existing configuration loaded.
|
Informational.
|
|
6010
|
W
|
L
|
C
|
Processing new configuration.
|
Informational.
|
|
6011
|
W
|
L
|
N
|
Dynamic configuration loaded.
|
Informational.
|
|
6012
|
W
|
L
|
N
|
Process configuration unloaded
successfully
|
Informational.
|
|
6200
|
W
|
L
|
N
|
Spawned ep_config: PORT:(<port number>).
|
Informational.
|
|
6250
|
W
|
L
|
S
|
Listener exiting main control
loop.
|
Informational.
|
|
ERRORS
|
|
Message ID
|
Explanation
|
Resolution
|
|
7001
|
E
|
L/N2
|
N
|
Unable to connect to local
queue service: (<queue subsystem error>).
|
Ensure that the message queue
has been started and initialized correctly, the port number in
the Replication Administrator matches the port number in the Registry,
and the message queue directory is writable to the current process.
See the User Guide for more information.
|
|
7002
|
E
|
L/N2
|
N
|
Unable to open target queue
(<queue name>): (<queue subsystem error>).
|
Ensure that the message queue
has been started and initialized correctly, the port number in
the Replication Administrator matches the port number in the Registry,
and the message queue directory is writable to the current process.
See the User Guide for more information.
|
|
7003
|
E
|
L/N2
|
N
|
Unable to enqueue on target
queue (<queue name>): (<queue subsystem error>).
|
Ensure that the message queue
has been started and initialized correctly, the port number in
the Replication Administrator matches the port number in the Registry,
and the message queue directory is writable to the current process.
See the User Guide for more information.
|
|
7004
|
E
|
L/N2
|
N
|
Unable to open EP work queue:
(<queue subsystem error>).
|
Ensure that the message queue
has been started and initialized correctly, the port number in
the Replication Administrator matches the port number in the Registry,
and the message queue directory is writable to the current process.
See the User Guide for more information.
|
|
7005
|
E
|
L
|
N
|
Unable
to delete unused record caches: DIR:(<queue
directory) ERR:(<queue
subsystem error>).
|
Ensure
that the message queue has been started and initialized correctly,
the port number in the Replication Administrator matches the port
number in the Registry, and the message queue directory is writable
to the current process. See the User Guide for more information.
|
|
7006
|
E
|
L/N2
|
N
|
Unable to dequeue EP work
queue: (<queue subsystem error>).
|
Ensure that the message queue
has been started and initialized correctly, the port number in
the Replication Administrator matches the port number in the Registry,
and the message queue directory is writable to the current process.
See the User Guide for more information.
|
|
7007
|
E
|
L
|
S
|
Queue
unreachable and shutdown called during transaction queue processing:
TXID:(<internal transaction
ID>).
|
Ensure
that the CONNX message queue is the last process to stop when
stopping all Event Replicator services.
|
|
7008
|
E
|
L
|
S
|
Queue
unreachable and shutdown called during initial state queue processing:
TXID: (<queue subsystem error>).
|
Ensure
that the CONNX message queue is the last process to stop when
stopping all Event Replicator services.
|
|
7009
|
E
|
L
|
N
|
Unable
to purge target queue (<queue
name>): (<queue
subsystem error>).
|
Ensure
that the CONNX message queue is the last process to stop when
stopping all Event Replicator services.
|
|
7010
|
E
|
L/N2
|
N
|
EP configuration error: duplicate
source.
|
Contact technical support.
|
|
7011
|
E
|
L/N2
|
N
|
Unable to open EP control
queue: (<queue subsystem error>).
|
Ensure that the message queue
has been started and initialized correctly, the port number in
the Replication Administrator matches the port number in the Registry,
and the message queue directory is writable to the current process.
See the User Guide for more information.
|
|
7012
|
E
|
L/N2
|
N
|
Unable to peek EP control
queue: (<queue subsystem error>).
|
Ensure that the message queue
has been started and initialized correctly, the port number in
the Replication Administrator matches the port number in the Registry,
and the message queue directory is writable to the current process.
See the User Guide for more information.
|
|
7013
|
E
|
L
|
U
|
Unable to open configuration
cache for EP (<config file name>): IO Error: (<OS specific error>).
|
Verify installation directory
is readable and user ID has appropriate permissions. See OS error
message and correct as appropriate.
|
|
7014
|
E
|
L
|
U
|
Unable to read cached configuration
for EP (<config file name>): IO Error: (<OS
specific error>)
|
Verify installation directory
is readable and user ID has appropriate permissions. See OS error
message and correct as appropriate.
|
|
7015
|
E
|
L
|
U
|
Unable to create configuration
cache for EP (<config file name>): IO Error: (<OS specific error>)
|
Verify installation directory
is writable and user ID has appropriate permissions. See OS error
message and correct as appropriate.
|
|
7016
|
E
|
L
|
U
|
Unable to cache configuration
for EP (<config file name>): IO Error: (<OS
specific error>).
|
Verify installation directory
is writable and user ID has appropriate permissions. See OS error
message and correct as appropriate.
|
|
7017
|
E
|
L/N1
|
U
|
Unable to open existing configuration
(<config file name>): (<OS
specific error>). Initial state required.
|
Verify installation directory
is writable and user ID has appropriate permissions. See OS error
message and correct as appropriate.
|
|
7018
|
E
|
L/N1
|
U
|
Unable to map existing configuration
(<config file name>): (<OS
specific error>).
|
Out of resources. Check disk
space and available memory.
|
|
7019
|
E
|
L/N1
|
U
|
Pointer to existing configuration
is NULL: (<OS specific
error>).
|
Out of resources. Check disk
space and available memory.
|
|
7020
|
E
|
L/N3
|
U
|
Unable to initialize mapped
allocator: (<API error>).
|
Contact technical support.
|
|
7021
|
E
|
L/N3
|
U
|
Unable to initialize transaction
data.
|
Contact technical support.
|
|
7022
|
E
|
L/N3
|
U
|
Unable to initialize record
data.
|
Contact technical support.
|
|
7023
|
E
|
X
|
S
|
The CONNX registry cannot
be read or does not contain a value for: (CONNX.REPLICATION.INSTALLPATH).
|
Adabas nucleus was terminated
unexpectedly. Initial state required to regain data integrity.
|
|
7024
|
E
|
L
|
U
|
Unable to delete dirty configuration
(<config file name>): (<OS
specific error>).
|
Verify installation directory
is writable and user ID has appropriate permissions. See OS error
message and correct as appropriate.
|
|
7025
|
E
|
L/N3
|
D
|
Unable to create new configuration
(<config file name>): (<OS
specific error>).
|
Verify installation directory
is writable and user ID has appropriate permissions. See OS error
message and correct as appropriate.
|
|
7026
|
E
|
L/N3
|
D
|
Unable to map new configuration
(<config file name>): (<OS
specific error>).
|
Out of resources. Check disk
space and available memory.
|
|
7027
|
E
|
L/N3
|
D
|
Pointer to new configuration
is NULL: (<OS specific
error>).
|
Out of resources. Check disk
space and available memory.
|
|
7028
|
E
|
L/N3
|
D
|
Unable to construct new mapped
allocator: (<API error>).
|
Contact technical support.
|
|
7029
|
E
|
L/N3
|
D
|
Unable to construct new transaction
data.
|
Contact technical support.
|
|
7030
|
E
|
L/N3
|
D
|
Unable to construct new record
data.
|
Contact technical support.
|
|
7031
|
E
|
L/N3
|
D
|
Unable to flush the configuration
to disk: (<OS specific
error>).
|
Verify installation directory
is writable and user ID has appropriate permissions. See OS error
message and correct as appropriate.
|
|
7032
|
E
|
L
|
N
|
Unable to connect to status
queue.
|
Ensure that the message queue
has been started and initialized correctly, the port number in
the Replication Administrator matches the port number in the Registry,
and the message queue directory is writable to the current process.
See the User Guide for more information.
|
|
7033
|
E
|
L
|
N
|
Unable to open status queue.
|
Ensure that the message queue
has been started and initialized correctly, the port number in
the Replication Administrator matches the port number in the Registry,
and the message queue directory is writable to the current process.
See the User Guide for more information.
|
|
7034
|
E
|
L
|
N
|
Unable to enqueue status
message.
|
Ensure that the message queue
has been started and initialized correctly, the port number in
the Replication Administrator matches the port number in the Registry,
and the message queue directory is writable to the current process.
See the User Guide for more information.
|
|
7035
|
E
|
L
|
N
|
Unable to delete cache map
(<queue name>): (<queue subsystem error>).
|
Ensure that the message queue
has been started and initialized correctly, the port number in
the Replication Administrator matches the port number in the Registry,
and the message queue directory is writable to the current process.
See the User Guide for more information.
|
|
7036
|
E
|
LN/3
|
U
|
Unable to load cached configuration.
Deployment required.
|
Ensure that the install directory
is writable to the Event Producer user/process and re-deploy.
|
|
7037
|
E
|
L
|
S
|
Unable to reset the Event
Producer. Forcing internal replication processes to shutdown.
|
Contact technical support.
|
|
7038
|
E
|
L/N3
|
D
|
Duplicate transaction requested.
|
Contact technical support.
|
|
7039
|
E
|
L/N3
|
D
|
Unable to retrieve pointer
to mapped memory: (<API
error>).
|
Contact technical support.
|
|
7040
|
E
|
L/N3
|
D
|
Unable to free pointer to
mapped memory: (<API
error>).
|
Contact technical support.
|
|
7041
|
E
|
L/N3
|
D
|
Unable to cache record. Invalid
transaction ID.
|
Contact technical support.
|
|
7042
|
E
|
L/N1
|
D
|
Unable to retrieve transaction
data alloc info.
|
Contact technical support.
|
|
7043
|
E
|
L/N1
|
D
|
Unable to retrieve record
data alloc info.
|
Contact technical support.
|
|
7044
|
E
|
L
|
N
|
Initial state request received
when no configuration exists.
|
Non-fatal error. No action
necessary.
|
|
7045
|
E
|
L
|
N
|
Delete config request received
when no configuration exists.
|
Non-fatal error. No action
necessary.
|
|
7046
|
E
|
L/N2
|
N
|
EP configuration error: Duplicate
source.
|
Contact technical support.
|
|
7047
|
E
|
L/N3
|
S
|
Unable to initialize the
Event Producer. Forcing internal replication processes to shutdown.
|
Contact technical support.
|
|
7048
|
E
|
LN/3
|
D
|
Unable to cache configuration.
|
Ensure that the install directory
is writable to the Event Producer user/process and then re-deploy.
|
|
7049
|
E
|
LN/3
|
S
|
Number of cached transactions
is non-zero and the configuration is new.
|
Contact technical support.
|
|
7050
|
E
|
LN/3
|
S
|
Number of cached transactions
does not match the saved configuration.
|
Contact technical support.
|
|
7051
|
E
|
LN/3
|
S
|
Number of cached transactions
does not match the number of restored transactions.
|
Contact technical support.
|
|
7052
|
E
|
LN/3
|
S
|
Unable to reconstitute record
data: (<API error>)
|
Contact technical support.
|
|
7053
|
E
|
LN/3
|
S
|
Number of cached transactions
is zero and the number of cached records is non-zero.
|
Contact technical support.
|
|
7071
|
E
|
LN/3
|
N
|
Adabas to Adabas Deploy Failed.
|
Check previous error messages
in the EP log. Check Nucleus log.
|
|
7072
|
E
|
LN/3
|
N
|
Call to Adabas nucleus to
change replication status failed.
|
Check previous messages in
the EP log for more detail. Check Nucleus log. Possible
causes of this error are adding a file to the replication list
that has a referential integrity dependency on another file that
was not added or attempting to do an initial state on a file that
has a referential integrity dependency on another file that was
not part of the initial state process - most likely because it
was not added to the replication list.
|
|
7200
|
E
|
L/N3
|
D
|
Internal API call failed.
Nucleus Response: (<nucleus
response code>).
|
Contact technical support.
|
|
7201
|
E
|
L/N3
|
D
|
Unable to retrieve Primary
Key data.
|
Contact technical support.
|
|
7202
|
E
|
L/N3
|
D
|
Internal call failed. Nucleus
Response: (<nucleus response
code>).
|
Contact technical support.
|
|
7203
|
E
|
L/N
|
D
|
Unable to resolve sub tables:
(<API error>).
|
Contact technical support.
|
|
7204
|
E
|
L/N3
|
|
Event handler termination
called with non-zero reference count.
|
Adabas has terminated abnormally.
Contact technical support.
|
|
7205
|
E
|
L/N3
|
|
FATAL ERROR: Unable to initialize
producer.
|
Contact technical support.
|
|
7206
|
E
|
L
|
|
FATAL ERROR: Unable to initialize
producer global status framework.
|
Contact technical support.
|
|
7207
|
E
|
L/N3
|
|
FATAL ERROR: Unable to initialize
ep_config.
|
Contact technical support.
|
|
7208
|
E
|
L/N3
|
|
FATAL ERROR: Unable to create
handler.
|
Contact technical support.
|
|
7210
|
E
|
L
|
|
Unable to send message to
ep_config: (<socket error>).
|
System will try to restart
CNXEPCFG automatically. If it doesn't, contact technical support.
|
|
7211
|
E
|
L/N3
|
|
Unable to send message to
ep_config: (<socket error>).
|
System will try to restart
CNXEPCFG automatically. If it doesn't, contact technical support.
|
|
7212
|
E
|
L/N3
|
|
Failed to retrieve reply
message to ep_config: (<socket error>).
|
System will try to restart
CNXEPCFG automatically. If it doesn't, contact technical support.
|
|
7213
|
E
|
L/N3
|
|
Unable to spawn ep_config:
(<OS specific error>).
|
See OS error message and
correct as appropriate.
|
|
7215
|
E
|
L/N3
|
|
Unable to open connection
to ep_config: PORT:(<port
number>) ERR:(<socket
error>).
|
Contact technical support.
|
|
7250
|
E
|
L
|
|
Unable to initialize socket
acceptor on port (<port number>) (<socket error>).
|
See OS error message and
correct as appropriate.
|
|
7251
|
E
|
L
|
|
Unable to accept incoming
socket: (<socket error>). Will attempt to re-initialize
acceptor.
|
Non-fatal error.
|
|
7252
|
E
|
L
|
|
Unable to re-initialize socket
acceptor on port (<port number>) (<socket error>).
|
See OS error message and
correct as appropriate.
|
|
7254
|
E
|
L
|
|
Receive failed for incoming
request: (<host>)(<port
number>): (<socket
error>).
|
Ensure that the Adabas nucleus
has been started and has been correctly configured for replication.
|
|
7255
|
E
|
L
|
|
Invalid message type received:
(<host>)(<port
number>): (<socket
error>).
|
Contact technical support.
|
|
7256
|
E
|
L
|
|
Timeout sending response
to client: (<host>)(<port
number>).
|
Ensure that the Adabas nucleus
has been started and has been correctly configured for replication.
|
|
7257
|
E
|
L
|
|
Unable to send response to
client: (<host>)(<port
number>): (<socket
error>).
|
Ensure that the Adabas nucleus
has been started and has been correctly configured for replication.
|
Debug
|
|
WARNINGS
|
|
Message ID
|
Explanation
|
Resolution
|
|
99801
|
W
|
L
|
U
|
EXEC:
{ {string} }.
|
Internal use only. For debug
level 2.
|
|
99802
|
W
|
L
|
U
|
ADM: { {string} }.
|
Internal use only. For debug
level 2.
|
|
99803
|
W
|
L
|
U
|
CTRL: { {string}
}.
|
Internal use only. For debug
level 2.
|
|
99804
|
W
|
L
|
U
|
EC: { {string} }.
|
Internal use only. For debug
level 2.
|
|
99805
|
W
|
L
|
U
|
RL: { {string} }.
|
Internal use only. For debug
level 2.
|
|
99806
|
W
|
L
|
U
|
RL Pool: { {string}
}.
|
Internal use only. For debug
level 2.
|
|
99807
|
W
|
L
|
U
|
TX: { {string} }.
|
Internal use only. For debug
level 2.
|
|
99808
|
W
|
L
|
U
|
EP: { {string} }.
|
Internal use only. For debug
level 2.
|
|
99809
|
W
|
L
|
U
|
CTRL (ADABAS): { {string}
}.
|
Internal use only. For debug
level 2.
|
|
99810
|
W
|
L
|
U
|
EP (ADABAS): { {string}
}.
|
Internal use only. For debug
level 2.
|
