This description is only intended for the use of trained specialists in control and automation engineering who
are familiar with applicable national standards.
It is essential that the documentation and the following notes and explanations are followed when installing
and commissioning the components.
It is the duty of the technical personnel to use the documentation published at the respective time of each
installation and commissioning.
The responsible staff must ensure that the application or use of the products described satisfy all the
requirements for safety, including all the relevant laws, regulations, guidelines and standards.
Disclaimer
The documentation has been prepared with care. The products described are, however, constantly under
development.
We reserve the right to revise and change the documentation at any time and without prior announcement.
No claims for the modification of products that have already been supplied may be made on the basis of the
data, diagrams and descriptions in this documentation.
Trademarks
Beckhoff®, TwinCAT®, EtherCAT®, EtherCAT G®, EtherCAT G10®, EtherCAT P®, Safety over EtherCAT®,
TwinSAFE®, XFC®, XTS® and XPlanar® are registered trademarks of and licensed by Beckhoff Automation
GmbH.
Other designations used in this publication may be trademarks whose use by third parties for their own
purposes could violate the rights of the owners.
Patent Pending
The EtherCAT Technology is covered, including but not limited to the following patent applications and
patents:
EP1590927, EP1789857, EP1456722, EP2137893, DE102015105702
with corresponding applications or registrations in various other countries.
EtherCAT® is a registered trademark and patented technology, licensed by Beckhoff Automation GmbH,
Germany
Please note the following safety instructions and explanations!
Product-specific safety instructions can be found on following pages or in the areas mounting, wiring,
commissioning etc.
Exclusion of liability
All the components are supplied in particular hardware and software configurations appropriate for the
application. Modifications to hardware or software configurations other than those described in the
documentation are not permitted, and nullify the liability of Beckhoff Automation GmbH & Co. KG.
Personnel qualification
This description is only intended for trained specialists in control, automation and drive engineering who are
familiar with the applicable national standards.
Description of symbols
In this documentation the following symbols are used with an accompanying safety instruction or note. The
safety instructions must be read carefully and followed without fail!
DANGER
Serious risk of injury!
Failure to follow the safety instructions associated with this symbol directly endangers the life and health of
persons.
WARNING
Risk of injury!
Failure to follow the safety instructions associated with this symbol endangers the life and health of persons.
CAUTION
Personal injuries!
Failure to follow the safety instructions associated with this symbol can lead to injuries to persons.
NOTE
Damage to the environment or devices
Failure to follow the instructions associated with this symbol can lead to damage to the environment or
equipment.
Tip or pointer
This symbol indicates information that contributes to better understanding.
TF66106Version: 1.1
Overview
2Overview
The function blocks of the PLC library Tc2_S5S7Com can be used to realise data exchange between the
local TwinCAT PLC and a S5/S7 controller via an Ethernet LAN adapter from IBHsoftec.
The adapter is not part of the Beckhoff product and must be bought from IBHsoftec.
Product components
The function TF6610 | S5/S7 consists of the following components which are automatically installed during
setup:
• Functions: TF6310
• PLC library Tc2_S5S7Com (Tc2_TcpIp installed with TF6310)
• Background program:TwinCAT TCP/IP connection server (for communication, installed with
TF6310);.
System requirements
Supported adapters:
• IBH Link S5++ adapter from IBHsoftec (from firmware version 1.39; the firmware version can be
read via the configuration software provided).
Older adapters (without ++) are currently not supported.
• IBH Link S7++ adapter from IBHsoftec (from firmware version NL50MPI V02.004 05.06.09; the
firmware version can be read via the configuration software provided).
The following article describes the minimum requirements for the engineering or runtime system.
Development environment
A development environment describes a computer developing PLC program, but not running. On a
development computer, the following have to be installed:
• TwinCAT v3.1.4016.0 XAE (engineering) or higher;
• TwinCAT 3 Function TF6610 S5 / S7 Communication;
Run-time environment
A runtime environment describes a computer running PLC programs. On a runtime computer, the following
have to be installed:
• TwinCAT v3.1.4016.0 XAR (runtime) or higher;
• TwinCAT 3 Function TF6610 S5 / S7 Communication;
• Licenses for TC1200 PLC and TF6610;
Developer and run-time version on a computer
To run a runtime and development environment on a computer (for example, to test a PLC program before
loading it to the target computer), the following requirements must be fullfilled:
• TwinCAT v3.1.4016.0 XAE (Engineering) or higher;
• TwinCAT 3 function TF6610 S5 / S7 communication;
• Licenses for TC1200 PLC, TF6610;;
Please note: For test purposes a 7-day trial license can be generated, see licensing.
TF66107Version: 1.1
Installation
3Installation
The function TF6610 can be installed with the Operating System XP and CE.
3.1Installation
The following section describes how to install the TwinCAT3Function for Windows-based operating
systems.
ü The TwinCAT3Function setup file was downloaded from the Beckhoff website.
1. Run the setup file as administrator. To do this, select the command Run as administrator in the context
menu of the file.
ð The installation dialog opens.
2. Accept the end user licensing agreement and click Next.
TF66108Version: 1.1
3. Enter your user data.
Installation
4. If you want to install the full version of the TwinCAT3Function, select Complete as installation type. If
you want to install the TwinCAT3Function components separately, select Custom.
TF66109Version: 1.1
Installation
5. Select Next, then Install to start the installation.
ð A dialog box informs you that the TwinCAT system must be stopped to proceed with the installation.
6. Confirm the dialog with Yes.
TF661010Version: 1.1
7. Select Finish to exit the setup.
Installation
ð The TwinCAT3Function has been successfully installed and can be licensed (see Licensing [}13]).
3.2Installation WindowsCE
The following section describes how to install a TwinCAT3function (TFxxx) on a Beckhoff Embedded PC
with WindowsCE.
1. Download and install the setup file [}11]
2. Transfer the CAB file to the WindowsCE device [}12]
3. Run the CAB file on the WindowsCE device [}12]
If an older TFxxx version is already installed on the WindowsCE device, it can be updated:
• Software upgrade [}12]
Download and install the setup file
The CAB installation file for WindowsCE is part of the TFxxx setup. This is made available on the Beckhoff
website www.beckhoff.com and automatically contains all versions for Windows XP, Windows 7 and
Windows CE (x86 and ARM).
Download the TFxxx setup file and install the TwinCAT3function as described in the Installation [}8]
section.
After the installation, the installation folder contains three directories (one directory per hardware platform):
• CE-ARM: ARM-based Embedded PCs running WindowsCE, e.g. CX8090, CX9020
• CE-X86: X86-based Embedded PCs running WindowsCE, e.g. CX50xx, CX20x0
• Win32: Embedded PCs running WindowsXP, Windows7 or WindowsEmbeddedStandard
The CE-ARM and CE-X86 directories contain the CAB files of the TwinCAT3function for WindowsCE in
relation to the respective hardware platform of the WindowsCE device.
Example: "TF6310" installation folder
TF661011Version: 1.1
Installation
Transfer the CAB file to the WindowsCE device
Transfer the corresponding CAB file to the WindowsCE device.
There are various options for transferring the executable file:
• via network shares
• via the integrated FTP server
• via ActiveSync
• via CF/SD cards
Further information can be found in the Beckhoff Information System in the "Operating Systems"
documentation (EmbeddedPC>Operating Systems>CE).
Run the CAB file on the WindowsCE device
After transferring the CAB file to the WindowsCE device, double-click the file there. Confirm the installation
dialog with OK. Then restart the WindowsCE device.
After restarting the device, the files of the TwinCAT3function (TFxxxx) are automatically loaded in the
background and are then available.
The software is installed in the following directory on the WindowsCE device:
\Hard Disk\TwinCAT\Functions\TFxxxx
Software upgrade
If an older version of the TwinCAT3function is already installed on the WindowsCE device, carry out the
following steps on the WindowsCE device to upgrade to a new version:
1. Open the CE Explorer by clicking Start>Run and entering "Explorer".
2. Navigate to \Hard Disk\TwinCAT\Functions\TFxxx\xxxx.
3. Rename the file Tc*.exe to Tc*.old.
4. Restart the WindowsCE device.
5. Transfer the new CAB file to the WindowsCE device.
6. Run the CAB file on the WindowsCE device and install the new version.
7. Delete the file Tc*.old.
8. Restart the WindowsCE device.
ð The new version is active after the restart.
TF661012Version: 1.1
Installation
3.3Licensing
The TwinCAT3function can be activated as a full version or as a 7-day test version. Both license types can
be activated via the TwinCAT 3 development environment (XAE).
Licensing the full version of a TwinCAT3Function
A description of the procedure to license a full version can be found in the Beckhoff Information System in
the documentation "TwinCAT3Licensing".
Licensing the 7-day test version of a TwinCAT3Function
A 7-day test version cannot be enabled for a TwinCAT 3 license dongle.
1. Start the TwinCAT 3 development environment (XAE).
2. Open an existing TwinCAT 3 project or create a new project.
3. If you want to activate the license for a remote device, set the desired target system. To do this, select
the target system from the Choose Target System drop-down list in the toolbar.
ð The licensing settings always refer to the selected target system. When the project is activated on
the target system, the corresponding TwinCAT 3 licenses are automatically copied to this system.
4. In the Solution Explorer, double-click License in the SYSTEM subtree.
ð The TwinCAT 3 license manager opens.
TF661013Version: 1.1
Installation
5. Open the Manage Licenses tab. In the AddLicense column, check the check box for the license you
want to add to your project (e.g."TF6420:TC3DatabaseServer").
6. Open the Order Information (Runtime) tab.
ð In the tabular overview of licenses, the previously selected license is displayed with the status
“missing”.
7. Click7-DayTrialLicense... to activate the 7-day trial license.
ð A dialog box opens, prompting you to enter the security code displayed in the dialog.
8. Enter the code exactly as it is displayed and confirm the entry.
9. Confirm the subsequent dialog, which indicates the successful activation.
ð In the tabular overview of licenses, the license status now indicates the expiry date of the license.
10. Restart the TwinCAT system.
TF661014Version: 1.1
ð The 7-day trial version is enabled.
Installation
TF661015Version: 1.1
Configuration of an IBH Link S5/S7 ++ adapter
4Configuration of an IBH Link S5/S7 ++ adapter
The adapter configuration software is provided by the manufacturer of the adapter. It is not part of the
TwinCAT function. A detailed description of the module configuration can be found in the manufacturer
documentation.
Configuration of an IBH Link S5++ adapter
In the following example a fixed IP address 172.16.11.16 was set:
Configuration of an IBH Link S7++ adapter
In the following example a fixed IP address 172.16.11.17 was set:
TF661016Version: 1.1
Configuration of an IBH Link S5/S7 ++ adapter
TF661017Version: 1.1
Description of the PLC data area parameter values
5Description of the PLC data area parameter
values
The parameter values to be used for the write/read command differ depending on the type of external control
used, the adapter or the communication protocol. Some data areas may not be available, or the data have to
be read/written word by word instead of byte by byte. Further information can be found in the documentation
for the external control.
Data type
Read access to word variables in the S5/S7 controller returns data in Motorola format (Hi and Lo
bytes interchanged). For the evaluation the read data first have to be converted to the common Intel
format used in the TwinCAT system. Data to be written from the TwinCAT system to the S5/S7 controller must be converted to the Motorola format before the write access.
The BCD number system is used in the S5/S7 controller for representing the counter/timer variables. The
data may have to be converted, if necessary.
The TwinCAT PLC library: TcUtilities.Lib offers functions for conversion between Motorola and Intel format
(e.g. BE16_TO_host, host_TO_BE16...).
The following table provides an overview of the available communication routes:
Control LAN adapterTransport
protocol
S5IBH Link S5++TCP/IPIBH S5 LAN link protocol =
S7IBH Link S7++TCP/IPNetLink MPI protocol (NL-MPI)
IBH S5 LAN link protocol = FETCH/WRITE telegrams
• Currently this protocol can only be used with S5 controllers.
• The TCP/IP port number has the default value 2002;
• The parameter devAddr is not evaluated.
• The data block number (nDB) is only evaluated when the areas data blocks (DB) and extended data
blocks (DX) are accessed. Permitted range: 1..255;
• The areas P (periphery) and OS (operating state) are not supported.
Data area (eArea)Start address (nOffset)Permitted data length (cbBuffer)
DBData word offset: 0..2047read/write 1..2048 words
MFlag byte offset: 0..255read/write 1..256 bytes
IInput byte offset: 0..127read 1..128 bytes
QOutput byte offset: 0..127write 1..128 bytes
PI/O periphery byte offset: 0..127 (digital
I/Os), 128..255 (analog I/Os)
CCounter start offset: 0..255read/write 1 word
TTimer start offset: 0..255read/write 1 word
DXData word offset:read/write 1..2048 words
LAN adapter communication
protocol
FETCH/WRITE telegrams
from Hilscher
read/write 1..256 bytes
Notes
No connection parameterisation
required in the external controller.
No connection parameterisation
required in the external controller.
NetLink MPI protocol (NL-MPI) from Hilscher
• This protocol can only be used with S7 controllers.
• The TCP/IP port number has the default value 1099
• The MPI address (devAddr) has the default value 2. Permissible values: 1..126;
• The data block number (nDB) is only evaluated when the data blocks (DB) data area is accessed.
Permissible values: 0..65534;
TF661018Version: 1.1
Description of the PLC data area parameter values
• The areas P (periphery) and DX (extended data block) are not supported.
• The byte length has to be specified for the data length parameter (cbBuffer).
• The OS area (operating state) is only available for read access.
Data area (eArea)Start address (nOffset)Permitted data length (cbBuffer)
CCounter start offset: 0..65534Read: max. 111 word counters, write:
TTimer start offset: 0..65534Read: max. 111 word timers, write: max.
OSOperating state: Irrelevant1 word (0=STOP, 1=START, 2=RUN,
bytes
max. 108 counters
108 timers
3=UNKNOWN)
TF661019Version: 1.1
API
6API
6.1PLC Reference
6.1.1Function blocks
6.1.1.1FB_NLinkOpen
This function block (actively) establishes a network connection to the third-party system. If successful, the
internal parameters of the hLink variable are initialised. The same instance of the hLink variable must then
be transferred to the other instances of the communication blocks FB_NLinkFetch [}22], FB_NLinkWrite[}24] or FB_NLinkClose [}21]. In a PLC application one instance of this variables is required for each
network connection (TwinCAT system<->Ethernet LAN adapter<->external controller).
VAR_IN_OUT
VAR_IN_OUT
hLink : T_HNLINK;
END_VAR
hLink : Network connection handle ( Type:T_HNLINK [}29]). The instance of this variable is required by the
other communication blocks and is transferred to them via VAR_IN_OUT.
stSettings: Structure with configuration settings for the communication connection. The member variables of
this structure should contain parameters such as port number, host name, etc.
nOpt: Reserved for future applications.
bExecute: The block is activated by a rising edge at this input.
tTimeout: Specifies the timeout that must not be exceeded on receipt of the command.
bBusy: When the function block is activated this output is set. It remains set until a feedback is received.
While Busy = TRUE, no new command will be accepted at the inputs. Please note that it is not the command
execution but the receipt of the command that is monitored.
bError: In the event of an error during the command transfer, this output is set once the bBusy output has
been reset.
nErrID: Supplies the error number [}32] when the bError output is set.
Example:
See examples [}31].
Requirements
Development environmentTarget platformPLC libraries to include
TwinCAT V3.1.4016 or higherPC oder CX (x86, x64, ARM)Tc2_S5S7Com (Communication->TcpIp)
This function block closes the network connection to the third-party system.
VAR_IN_OUT
VAR_IN_OUT
hLink : T_HNLINK;
END_VAR
hLink : Network connection handle ( Type:T_HNLINK [}29]). This is where the instance of the variable used
for establishing the connection by the FB_NLinkOpen [}20] function block is transferred.
bExecute: The block is activated by a rising edge at this input.
tTimeout: Specifies the timeout that must not be exceeded on receipt of the command.
VAR_OUTPUT
VAR_OUTPUT
bBusy : BOOL;
bError : BOOL;
TF661021Version: 1.1
API
nErrID : UDINT;
END_VAR
bBusy: When the function block is activated this output is set. It remains set until a feedback is received.
While Busy = TRUE, no new command will be accepted at the inputs. Please note that it is not the command
execution but the receipt of the command that is monitored.
bError: In the event of an error during the command transfer, this output is set once the bBusy output has
been reset.
nErrID: Supplies the error number [}32] when the bError output is set.
Example:
See examples [}31].
Requirements
Development environmentTarget platformPLC libraries to include
TwinCAT V3.1.4016 or higherPC oder CX (x86, x64, ARM)Tc2_S5S7Com (Communication->TcpIp)
This function block reads data from the third-party system and writes them to the local TwinCAT system
(FETCH service).
VAR_IN_OUT
VAR_IN_OUT
hLink : T_HNLINK;
END_VAR
hLink : Network connection handle (Type:T_HNLINK [}29]). This is where the instance of the variable used
for establishing the connection by the FB_NLinkOpen [}20] function block is transferred.
devAddr: Device address, MPI address of the component on the third-party system.
eArea: PLC data area in the third-party system (inputs, outputs, data block etc.) from which data are to be
read (type:E_NLinkArea [}26]).
nDB: Data block number in the third-party system. Data are to be read from this data block (only relevant for
access to data blocks and extended data blocks).
nOffset: The start byte address or word address from which data are to be read in the third-party system.
Whether a byte or word address is to be specified depends on the type of external controller/protocol used
and the data area to be accessed. Further information can be found here: Description of the PLC data areaparameter values [}18].
cbBuffer: Maximum number of data bytes to be read. The byte length is specified even for access to word
addresses.
pBuffer: Pointer/address of the target data buffer in the TwinCAT system. The read data are written into this
buffer. The address can be determined with the ADR operator. The target data buffer must not be smaller
than the specified length of the data to be read.
nOpt: Reserved for future applications.
bExecute: The block is activated by a rising edge at this input.
tTimeout: Specifies the timeout that must not be exceeded on receipt of the command.
VAR_OUTPUT
VAR_OUTPUT
bBusy : BOOL;
bError : BOOL;
nErrID : UDINT;
cbRead : UDINT := 0; (* Number of recend realy returned data bytes *)
END_VAR
bBusy: When the function block is activated this output is set. It remains set until a feedback is received.
While Busy = TRUE, no new command will be accepted at the inputs. Please note that it is not the command
execution but the receipt of the command that is monitored.
bError: In the event of an error during the command transfer, this output is set once the bBusy output has
been reset.
nErrID: Supplies the error number [}32] when the bError output is set.
cbRead: Number of successfully read data bytes.
Example:
See examples [}31].
Requirements
Development environmentTarget platformPLC libraries to include
TwinCAT V3.1.4016 or higherPC oder CX (x86, x64, ARM)Tc2_S5S7Com (Communication->TcpIp)
This function block sends data from the local TwinCAT system to the third-party system (WRITE service).
VAR_IN_OUT
VAR_IN_OUT
hLink : T_HNLINK;
END_VAR
hLink : Network connection handle ( Type:T_HNLINK [}29]). This is where the instance of the variable used
for establishing the connection by the FB_NLinkOpen [}20] function block is transferred.
devAddr: Device address, MPI address of the component on the third-party system.
eArea: PLC data area in the third-party system (inputs, outputs, data block, etc.) to which data are to be
written (type:E_NLinkArea [}26])
nDB: Data block number in the third-party system. Block in which data are to be written (only relevant for
access to data blocks and extended data blocks).
nOffset: The start byte address or word address from which data are to be written to the third-party system.
Whether a byte or word address is to be specified depends on the type of external controller/protocol used
and the data area to be accessed. Further information can be found here: Description of the PLC data areaparameter values [}18].
cbBuffer: Maximum byte length of the data to be transferred from the source data buffer in the local
TwinCAT system to the third-party system. The byte length is specified even for access to word addresses.
pBuffer: Pointer/address for the source data buffer. Data from this buffer are transferred to the third-party
system. The address can be determined with the ADR operator. The source data buffer must not be smaller
than the specified length of the data to be sent.
nOpt: Reserved for future applications.
bExecute: The block is activated by a rising edge at this input.
tTimeout: Specifies the timeout that must not be exceeded on receipt of the command.
TF661024Version: 1.1
API
VAR_OUTPUT
VAR_OUTPUT
bBusy : BOOL;
bError : BOOL;
nErrID : UDINT;
cbWrite : UDINT := 0;(* Number of successfull written data bytes *)
END_VAR
bBusy: When the function block is activated this output is set. It remains set until a feedback is received.
While Busy = TRUE, no new command will be accepted at the inputs. Please note that it is not the command
execution but the receipt of the command that is monitored.
bError: In the event of an error during the command transfer, this output is set once the bBusy output has
been reset.
nErrID: Supplies the error number [}32] when the bError output is set.
cbWrite: In case of success: Number of successfully written data bytes.
Example:
See examples [}31].
Requirements
Development environmentTarget platformPLC libraries to include
TwinCAT V3.1.4016 or higherPC oder CX (x86, x64, ARM)Tc2_S5S7Com (Communication->TcpIp)
TYPEE_NLinkArea:
(
eNLinkArea_DB:=16#01,(* Source/dest. data from/to data block in main memory. *)
eNLinkArea_M:=16#02,(* Source/dest. data from/to flag area. *)
eNLinkArea_I:=16#03,(* Source/dest. data from/to process image of the inputs. *)
eNLinkArea_Q:=16#04,(* Source/dest. data from/to process image of the outputs. *)
eNLinkArea_P:=16#05,(* Source/dest. data from/to in I/O modules (S7 only PI, PQ). *)
eNLinkArea_C:=16#06,(* Source/dest. data from/to counter cells. *)
eNLinkArea_T:=16#07,(* Source/dest. data from/to timer cells. *)
eNLinkArea_DX:=16#0A,(* Source/dest. data from/to extended data block. *)
eNLinkArea_OS:=16#100(* Read PLC operational status information *)
);
END_TYPE
PLC data area (inputs, outputs, flag, data block etc.) to be accessed. The parameter values differ depending
on the type of external control used, the adapter or the communication protocol. Some data areas may not
be available, or the data have to be read/written word by word instead of byte by byte .
More detailed information on this topic can be found under: S5/S7 data area parameter values [}18].
Requirements
Development environmentTarget platformPLC libraries to include
TwinCAT V3.1.4016 or higherPC oder CX (x86, x64, ARM)Tc2_S5S7Com (Communication->TcpIp)
TYPE E_NLinkProtocol:
(
eNLinkProtocol_IBH_SX_PP := 0, (* IBH Link protocol (used by IBH Link S5++ adater) *)
eNLinkProtocol_MPI (* Hilscher NL-MPI protocol (used only by IBH Link S7++ adapter) *)
);
END_TYPE
Communication protocol (depends on the hardware used).
Requirements
Development environmentTarget platformPLC libraries to include
TwinCAT V3.1.4016 or higherPC oder CX (x86, x64, ARM)Tc2_S5S7Com (Communication->TcpIp)
Via these parameters the debug outputs can be activated/deactivated during troubleshooting (standard
setting: inactive)
The debug outputs are shown in the log view of the TwinCAT System Manager.
bServer: FALSE = client (active) connection. TRUE = server (passive) connection. Currently only client
connections are permitted.
bThrottle: If this parameter is set, the number of polling socket calls is reduced if no or few data are
received, i.e. the poll cycle is slowed down, thereby reducing the system load (default = FALSE).
Background information about the configuration of eProtocol- and eTransport parameter:
The IBHsoftec S7++ adapter is supporting more than one communication protocol (channel) to S7 controller.
• Using the Hilscher MPI-Protokoll + TCP/IP as transport protocol.
• Using the IBHsoftec S5++/S7++ protocol + RFC1006 as transport protocol.
The TwinCAT S5/S7 communication library is supporting only the first communication channel (using TCP/IP
transport protocol).
If you want to communicate with S7 controller then use this settings:
A variable of this type represents a network connection handle. The structural elements should not be written
to or modified directly. Variables of this type are used for internal data exchange.
One instance is required for each network connection (TwinCAT system<->Ethernet LAN adapter<->external
controller). The same instance is then transferred to other communication blocks as VAR_IN_OUT
parameter.
TYPE T_HNLINK :
STRUCT
END_STRUCT
END_TYPE
Requirements
Development environmentTarget platformPLC libraries to include
TwinCAT V3.1.4016 or higherPC oder CX (x86, x64, ARM)Tc2_S5S7Com (Communication->TcpIp)
All libraries have a specific version. This version is shown in the PLC library repository too.
A global constant contains the library version information:
stLibVersion_Tc2_S5S7Com: version information of Tc2_S5S7Com library (type: ST_LibVersion).To
compare the existing version to a required version the function F_CmpLibVersion (defined in Tc2_System
library) is offered.
Hint: All other possibilities known from TwinCAT2 libraries to query a library version are obsolete!
Requirements
Development environmentTarget platformPLC libraries to include
TwinCAT V3.1.4016 or higherPC oder CX (x86, x64, ARM)Tc2_S5S7Com (Communication->TcpIp)
• Write 1 word (2
bytes) from the
start address
(word offset): 9
• Read 10 words
(20 bytes) from
the start address
(word offset): 0
• Data area: DB
• Data block
number: 1
• Write 10 bytes
from the start
address (byte
offset): 0
• Read 10 bytes
from the start
address (byte
offset): 0
Description
The data in the
data block are
accessed word
by word.
The data in the
data block are
accessed byte
by byte. In
addition to the
selected data
area the
operating status
of the controller
is read (STOP,
RUN, START...).
0x0000853034096NLINK_COMMERR_MPI_TOTimeout, the request message was
0x0000853934105NLINK_COMMERR_MPI_SESequence fault, internal state machine
0x0000858534181NLINK_COMMERR_MPI_REJ_IVSpecified offset address out of limits or
0x0000858634182NLINK_COMMERR_MPI_REJ_PDUWrong PDU coding in the MPI response
0x0000858734183NLINK_COMMERR_MPI_REJ_OPSpecified length to write or to read results
0x0000858834184NLINK_COMMERR_MPI_REJ_OPSpecified address not defined in the
0x0000858934185NLINK_COMMERR_MPI_REJ_OPMPI remote station not in the right
Code
(dec)
Symbolic constantDescription
General error codesOffset 0x8300 + error code
available or not sifficient. HOST too many
messages. no more segments in DEVICE
free
invalid HOST check the limit of 222 bytes
(read) respectively 216 bytes (write) in
msg.data_cnt
accepted but no indication is sent back by
the remote station remote station MPI
protocol error, or station not presentor
error. Remote station does not react like
awaited or a reconnection was retried
while connection is already open or
device has no SAPs left to open
connection channel
not known in the remote station HOST
please check msg.data_adr if present or
offset parameter in request message
of the remote station DEVICE contact
hotline
in an access outside the limits HOST
please check msg.data_cnt length in
request message
remote station, please check
msg.data_adr in the request message
0x100F 41110x9811 100FRTERR_EXTIRQINSTALLFAILEDApplication of the external synchronization interrupt
0x1010 41120x9811 1010RTERR_IRQLNOTLESSOREQUALCall of a service function in the wrong context
0x1017 41190x9811 1017RTERR_VMXNOTSUPPORTEDIntel VT-x extension is not supported.
0x1018 41200x9811 1018RTERR_VMXDISABLEDIntel VT-x extension is not enabled in the BIOS.
0x1019 41210x9811 1019RTERR_VMXCONTROLSMISSINGMissing function in Intel VT-x extension.
0x101A 41220x9811 101ARTERR_VMXENABLEFAILSActivation of Intel VT-x fails.
maximum number of TCBs is 64.
ber of semaphores is 64.
number of positions in the queue is 64.
plied.
has failed.
TCP Winsock error codes
HexDecNameDescription
0x274C 10060 WSAETIMEDOUTA connection timeout has occurred - error while establishing the connection, because
0x274D 10061 WSAECONNREFUSEDConnection refused - no connection could be established because the target computer
0x2751 10065 WSAEHOSTUNREACHNo route to host - a socket operation referred to an unavailable host.
the remote terminal did not respond properly after a certain period of time, or the established connection could not be maintained because the connected host did not respond.
has explicitly rejected it. This error usually results from an attempt to connect to a service that is inactive on the external host, that is, a service for which no server application is running.
More Winsock error codes: Win32 error codes [}40]
TF661039Version: 1.1
Appendix
8.4Win32 Error Codes
The following table provides a list of Win32 error codes.
10010x000003E9ERROR_STACK_OVERFLOWRecursion too deep; the stack overflowed.
10020x000003EAERROR_INVALID_MESSAGEThe window cannot act on the sent message.
10030x000003EBERROR_CAN_NOT_COMPLETECannot complete this function.
10040x000003ECERROR_INVALID_FLAGSInvalid flags.
10050x000003EDERROR_UNRECOGNIZED_VOLUMEThe volume does not contain a recognized file
10060x000003EEERROR_FILE_INVALIDThe volume for a file has been externally altered
10070x000003EFERROR_FULLSCREEN_MODEThe requested operation cannot be performed in
10080x000003F0ERROR_NO_TOKENAn attempt was made to reference a token that
10090x000003F1ERROR_BADDBThe configuration registry database is corrupt.
10100x000003F2ERROR_BADKEYThe configuration registry key is invalid.
10110x000003F3ERROR_CANTOPENThe configuration registry key could not be
10120x000003F4ERROR_CANTREADThe configuration registry key could not be read.
10130x000003F5ERROR_CANTWRITEThe configuration registry key could not be writ-
10140x000003F6ERROR_REGISTRY_RECOVEREDOne of the files in the registry database had to be
10150x000003F7ERROR_REGISTRY_CORRUPTThe registry is corrupted. The structure of one of
10160x000003F8ERROR_REGISTRY_IO_FAILEDAn I/O operation initiated by the registry failed un-
10170x000003F9ERROR_NOT_REGISTRY_FILEThe system has attempted to load or restore a file
10180x000003FAERROR_KEY_DELETEDIllegal operation attempted on a registry key that
10190x000003FBERROR_NO_LOG_SPACESystem could not allocate the required space in a
10200x000003FCERROR_KEY_HAS_CHILDRENCannot create a symbolic link in a registry key
10210x000003FDERROR_CHILD_MUST_BE_VOLATILECannot create a stable subkey under a volatile
10220x000003FEERROR_NOTIFY_ENUM_DIRA notify change request is being completed and
10510x0000041BERROR_DEPENDENT_SERVICES_RUNNINGA stop control has been sent to a service that
10520x0000041CERROR_INVALID_SERVICE_CONTROLThe requested control is not valid for this service.
10530x0000041DERROR_SERVICE_REQUEST_TIMEOUTThe service did not respond to the start or control
10540x0000041EERROR_SERVICE_NO_THREADA thread could not be created for the service.
10550x0000041FERROR_SERVICE_DATABASE_LOCKEDThe service database is locked.
10560x00000420ERROR_SERVICE_ALREADY_RUNNINGAn instance of the service is already running.
10570x00000421ERROR_INVALID_SERVICE_ACCOUNTThe account name is invalid or does not exist, or
10580x00000422ERROR_SERVICE_DISABLEDThe service cannot be started, either because it is
10590x00000423ERROR_CIRCULAR_DEPENDENCYCircular service dependency was specified.
10600x00000424ERROR_SERVICE_DOES_NOT_EXISTThe specified service does not exist as an in-
system. Please make sure that all required file
system drivers are loaded and that the volume is
not corrupted.
so that the opened file is no longer valid.
full-screen mode.
does not exist.
opened.
ten.
recovered by use of a log or alternate copy. The
recovery was successful.
the files containing registry data is corrupted, or
the system's memory image of the file is corrupted, or the file could not be recovered because
the alternate copy or log was absent or corrupted.
recoverably. The registry could not read in, or
write out, or flush, one of the files that contain the
system's image of the registry.
into the registry, but the specified file is not in a
registry file format.
has been marked for deletion.
registry log.
that already has subkeys or values.
parent key.
the information is not being returned in the caller's
buffer. The caller now needs to enumerate the
files to find the changes.
other running services are dependent on.
request in a timely fashion.
the password is invalid for the account name
specified.
disabled or because it has no enabled devices associated with it.
stalled service.
TF661047Version: 1.1
Appendix
ErrorDescription
decimalHexadecimalName
10610x00000425ERROR_SERVICE_CANNOT_ACCEPT_CTRLThe service cannot accept control messages at
10620x00000426ERROR_SERVICE_NOT_ACTIVEThe service has not been started.
13600x00000550ERROR_GENERIC_NOT_MAPPEDGeneric access types were contained in an ac-
13610x00000551ERROR_BAD_DESCRIPTOR_FORMATA security descriptor is not in the right format (ab-
13620x00000552ERROR_NOT_LOGON_PROCESSThe requested action is restricted for use by logon
13630x00000553ERROR_LOGON_SESSION_EXISTSCannot start a new logon session with an ID that
13640x00000554ERROR_NO_SUCH_PACKAGEA specified authentication package is unknown.
13650x00000555ERROR_BAD_LOGON_SESSION_STATEThe logon session is not in a state that is consis-
13660x00000556ERROR_LOGON_SESSION_COLLISIONThe logon session ID is already in use.
13670x00000557ERROR_INVALID_LOGON_TYPEA logon request contained an invalid logon type
13680x00000558ERROR_CANNOT_IMPERSONATEUnable to impersonate using a named pipe until
13690x00000559ERROR_RXACT_INVALID_STATEThe transaction state of a registry subtree is in-
13700x0000055AERROR_RXACT_COMMIT_FAILUREAn internal security database corruption has been
13710x0000055BERROR_SPECIAL_ACCOUNTCannot perform this operation on built-in ac-
13720x0000055CERROR_SPECIAL_GROUPCannot perform this operation on this built-in spe-
13730x0000055DERROR_SPECIAL_USERCannot perform this operation on this built-in spe-
13740x0000055EERROR_MEMBERS_PRIMARY_GROUPThe user cannot be removed from a group be-
13750x0000055FERROR_TOKEN_ALREADY_IN_USEThe token is already in use as a primary token.
13760x00000560ERROR_NO_SUCH_ALIASThe specified local group does not exist.
ble with the attributes for the group as a whole.
vided, or the provided impersonation level is invalid.
valid.
tempted use.
ject that has no associated security.
the domain controller, either because the machine
is unavailable, or access has been denied.
curity authority (LSA) server was in the wrong
state to perform the security operation.
security operation.
main Controller of the domain.
could not be contacted.
number of domains per server.
cause of either a catastrophic media failure or a
data structure corruption on the disk.
cess mask which should already be mapped to
nongeneric types.
solute or self-relative).
processes only. The calling process has not registered as a logon process.
is already in use.
tent with the requested operation.
value.
data has been read from that pipe.
compatible with the requested operation.
encountered.
counts.
cial group.
cial user.
cause the group is currently the user's primary
group.
TF661054Version: 1.1
Appendix
ErrorDescription
decimalHexadecimalName
13770x00000561ERROR_MEMBER_NOT_IN_ALIASThe specified account name is not a member of
13780x00000562ERROR_MEMBER_IN_ALIASThe specified account name is already a member
13790x00000563ERROR_ALIAS_EXISTSThe specified local group already exists.
13800x00000564ERROR_LOGON_NOT_GRANTEDLogon failure: the user has not been granted the
13810x00000565ERROR_TOO_MANY_SECRETSThe maximum number of secrets that may be
13820x00000566ERROR_SECRET_TOO_LONGThe length of a secret exceeds the maximum
13830x00000567ERROR_INTERNAL_DB_ERRORThe local security authority database contains an
13840x00000568ERROR_TOO_MANY_CONTEXT_IDSDuring a logon attempt, the user's security con-
13850x00000569ERROR_LOGON_TYPE_NOT_GRANTEDLogon failure: the user has not been granted the
13860x0000056AERROR_NT_CROSS_ENCRYPTION_REQUIRED A cross-encrypted password is necessary to
13870x0000056BERROR_NO_SUCH_MEMBERA new member could not be added to or removed
13880x0000056CERROR_INVALID_MEMBERA new member could not be added to a local
13890x0000056DERROR_TOO_MANY_SIDSToo many security IDs have been specified.
13900x0000056EERROR_LM_CROSS_ENCRYPTION_REQUIRED A cross-encrypted password is necessary to
13910x0000056FERROR_NO_INHERITANCEIndicates an ACL contains no inheritable compo-
13920x00000570ERROR_FILE_CORRUPTThe file or directory is corrupted and unreadable.
13930x00000571ERROR_DISK_CORRUPTThe disk structure is corrupted and unreadable.
13940x00000572ERROR_NO_USER_SESSION_KEYThere is no user session key for the specified lo-
13950x00000573ERROR_LICENSE_QUOTA_EXCEEDEDThe service being accessed is licensed for a par-
13960x00000574ERROR_WRONG_TARGET_NAMELogon Failure: The target account name is incor-
13970x00000575ERROR_MUTUAL_AUTH_FAILEDMutual Authentication failed. The server's pass-
13980x00000576ERROR_TIME_SKEWThere is a time difference between the client and
13990x00000577ERROR_CURRENT_DOMAIN_NOT_ALLOWEDThis operation can not be performed on the cur-
the local group.
of the local group.
requested logon type at this computer.
stored in a single system has been exceeded.
length allowed.
internal inconsistency.
text accumulated too many security IDs.
requested logon type at this computer.
change a user password.
from the local group because the member does
not exist.
group because the member has the wrong account type.
change this user password.
nents.
gon session.
ticular number of connections. No more connections can be made to the service at this time because there are already as many connections as
the service can accept.
16090x00000649ERROR_INVALID_HANDLE_STATEHandle is in an invalid state.
16100x0000064AERROR_BAD_CONFIGURATIONThe configuration data for this product is corrupt.
16110x0000064BERROR_INDEX_ABSENTComponent qualifier not present.
16120x0000064CERROR_INSTALL_SOURCE_ABSENTThe installation source for this product is not
16130x0000064DERROR_INSTALL_PACKAGE_VERSIONThis installation package cannot be installed by
16140x0000064EERROR_PRODUCT_UNINSTALLEDProduct is uninstalled.
16150x0000064FERROR_BAD_QUERY_SYNTAXSQL query syntax invalid or unsupported.
16160x00000650ERROR_INVALID_FIELDRecord field does not exist.
16170x00000651ERROR_DEVICE_REMOVEDThe device has been removed.
16180x00000652ERROR_INSTALL_ALREADY_RUNNINGAnother installation is already in progress. Com-
16190x00000653ERROR_INSTALL_PACKAGE_OPEN_FAILEDThis installation package could not be opened.
16200x00000654ERROR_INSTALL_PACKAGE_INVALIDThis installation package could not be opened.
16210x00000655ERROR_INSTALL_UI_FAILUREThere was an error starting the Windows Installer
16220x00000656ERROR_INSTALL_LOG_FAILUREError opening installation log file. Verify that the
16230x00000657ERROR_INSTALL_LANGUAGE_UNSUPPORTED The language of this installation package is not
16240x00000658ERROR_INSTALL_TRANSFORM_FAILUREError applying transforms. Verify that the specified
16250x00000659ERROR_INSTALL_PACKAGE_REJECTEDThis installation is forbidden by system policy.
16260x0000065AERROR_FUNCTION_NOT_CALLEDFunction could not be executed.
16270x0000065BERROR_FUNCTION_FAILEDFunction failed during execution.
16280x0000065CERROR_INVALID_TABLEInvalid or unknown table specified.
16290x0000065DERROR_DATATYPE_MISMATCHData supplied is of wrong type.
16300x0000065EERROR_UNSUPPORTED_TYPEData of this type is not supported.
16310x0000065FERROR_CREATE_FAILEDThe Windows Installer service failed to start. Con-
16320x00000660ERROR_INSTALL_TEMP_UNWRITABLEThe temp folder is either full or inaccessible. Ver-
16330x00000661ERROR_INSTALL_PLATFORM_UNSUPPORTED This installation package is not supported by this
16340x00000662ERROR_INSTALL_NOTUSEDComponent not used on this computer.
cessed. Contact your support personnel to verify
that the Windows Installer service is properly registered.
rently installed.
Contact your support personnel.
available. Verify that the source exists and that
you can access it.
the Windows Installer service. You must install a
Windows service pack that contains a newer version of the Windows Installer service.
plete that installation before proceeding with this
install.
Verify that the package exists and that you can
access it, or contact the application vendor to verify that this is a valid Windows Installer package.
Contact the application vendor to verify that this is
a valid Windows Installer package.
service user interface. Contact your support personnel.
specified log file location exists and that you can
write to it.
supported by your system.
transform paths are valid.
Contact your system administrator.
tact your support personnel.
ify that the temp folder exists and that you can
write to it.
processor type. Contact your product vendor.
TF661058Version: 1.1
Appendix
ErrorDescription
decimalHexadecimalName
16350x00000663ERROR_PATCH_PACKAGE_OPEN_FAILEDThis patch package could not be opened. Verify
16360x00000664ERROR_PATCH_PACKAGE_INVALIDThis patch package could not be opened. Contact
16370x00000665ERROR_PATCH_PACKAGE_UNSUPPORTED.This patch package cannot be processed by the
16380x00000666ERROR_PRODUCT_VERSIONAnother version of this product is already in-
16390x00000667ERROR_INVALID_COMMAND_LINEInvalid command line argument. Consult the Win-
16400x00000668ERROR_INSTALL_REMOTE_DISALLOWEDOnly administrators have permission to add, re-
16420x0000066AERROR_PATCH_TARGET_NOT_FOUNDThe upgrade patch cannot be installed by the
16430x0000066BERROR_PATCH_PACKAGE_REJECTEDThe patch package is not permitted by system
16440x0000066CERROR_INSTALL_TRANSFORM_REJECTEDOne or more customizations are not permitted by
17000x000006A4RPC_S_INVALID_STRING_BINDINGThe string binding is invalid.
17010x000006A5RPC_S_WRONG_KIND_OF_BINDINGThe binding handle is not the correct type.
17020x000006A6RPC_S_INVALID_BINDINGThe binding handle is invalid.
17030x000006A7RPC_S_PROTSEQ_NOT_SUPPORTEDThe RPC protocol sequence is not supported.
17040x000006A8RPC_S_INVALID_RPC_PROTSEQThe RPC protocol sequence is invalid.
17050x000006A9RPC_S_INVALID_STRING_UUIDThe string universal unique identifier (UUID) is in-
17060x000006AARPC_S_INVALID_ENDPOINT_FORMATThe endpoint format is invalid.
17070x000006ABRPC_S_INVALID_NET_ADDRThe network address is invalid.
17080x000006ACRPC_S_NO_ENDPOINT_FOUNDNo endpoint was found.
17090x000006ADRPC_S_INVALID_TIMEOUTThe timeout value is invalid.
17100x000006AERPC_S_OBJECT_NOT_FOUNDThe object universal unique identifier (UUID) was
17110x000006AFRPC_S_ALREADY_REGISTEREDThe object universal unique identifier (UUID) has
17120x000006B0RPC_S_TYPE_ALREADY_REGISTEREDThe type universal unique identifier (UUID) has al-
17130x000006B1RPC_S_ALREADY_LISTENINGThe RPC server is already listening.
17140x000006B2RPC_S_NO_PROTSEQS_REGISTEREDNo protocol sequences have been registered.
17150x000006B3RPC_S_NOT_LISTENINGThe RPC server is not listening.
17160x000006B4RPC_S_UNKNOWN_MGR_TYPEThe manager type is unknown.
17170x000006B5RPC_S_UNKNOWN_IFThe interface is unknown.
17180x000006B6RPC_S_NO_BINDINGSThere are no bindings.
17190x000006B7RPC_S_NO_PROTSEQSThere are no protocol sequences.
17200x000006B8RPC_S_CANT_CREATE_ENDPOINTThe endpoint cannot be created.
that the patch package exists and that you can
access it, or contact the application vendor to verify that this is a valid Windows Installer patch
package.
the application vendor to verify that this is a valid
Windows Installer patch package.
Windows Installer service. You must install a Windows service pack that contains a newer version
of the Windows Installer service.
stalled. Installation of this version cannot continue. To configure or remove the existing version
of this product, use Add/Remove Programs on the
Control Panel.
dows Installer SDK for detailed command line
help.
move, or configure server software during a Terminal Services remote session. If you want to install or configure software on the server, contact
your network administrator.
The system will be restarted so the changes can
take effect.
Windows Installer service because the program to
be upgraded may be missing, or the upgrade
patch may update a different version of the program. Verify that the program to be upgraded exists on your computer and that you have the correct upgrade patch.
policy. It is not signed with an appropriate certificate.
system policy. They are not signed with an appropriate certificate.
valid.
not found.
already been registered.
ready been registered.
TF661059Version: 1.1
Appendix
ErrorDescription
decimalHexadecimalName
17210x000006B9RPC_S_OUT_OF_RESOURCESNot enough resources are available to complete
17220x000006BARPC_S_SERVER_UNAVAILABLEThe RPC server is unavailable.
17230x000006BBRPC_S_SERVER_TOO_BUSYThe RPC server is too busy to complete this oper-
17240x000006BCRPC_S_INVALID_NETWORK_OPTIONSThe network options are invalid.
17250x000006BDRPC_S_NO_CALL_ACTIVEThere are no remote procedure calls active on
50480x000013B8ERROR_CLUSTER_INVALID_REQUESTThe cluster request is not valid for this object.
50490x000013B9ERROR_CLUSTER_INVALID_NET-
WORK_PROVIDER
50500x000013BAERROR_CLUSTER_NODE_DOWNThe cluster node is down.
50510x000013BBERROR_CLUSTER_NODE_UNREACHABLEThe cluster node is not reachable.
50520x000013BCERROR_CLUSTER_NODE_NOT_MEMBERThe cluster node is not a member of the cluster.
50530x000013BDERROR_CLUSTER_JOIN_NOT_IN_PROGRESSA cluster join operation is not in progress.
50540x000013BEERROR_CLUSTER_INVALID_NETWORKThe cluster network is not valid.
50560x000013C0ERROR_CLUSTER_NODE_UPThe cluster node is up.
50570x000013C1ERROR_CLUSTER_IPADDR_IN_USEThe cluster IP address is already in use.
50580x000013C2ERROR_CLUSTER_NODE_NOT_PAUSEDThe cluster node is not paused.
50590x000013C3ERROR_CLUSTER_NO_SECURITY_CONTEXTNo cluster security context is available.
50600x000013C4ERROR_CLUSTER_NETWORK_NOT_INTERNAL The cluster network is not configured for internal
50610x000013C5ERROR_CLUSTER_NODE_ALREADY_UPThe cluster node is already up.
50620x000013C6ERROR_CLUSTER_NODE_ALREADY_DOWNThe cluster node is already down.
50630x000013C7ERROR_CLUSTER_NETWORK_ALREADY_ON-
LINE
50640x000013C8ERROR_CLUSTER_NETWORK_ALREADY_OFF-
LINE
50650x000013C9ERROR_CLUSTER_NODE_ALREADY_MEMBER The cluster node is already a member of the clus-
50660x000013CAERROR_CLUSTER_LAST_INTERNAL_NETWORK The cluster network is the only one configured for
50670x000013CBERROR_CLUSTER_NETWORK_HAS_DEPEN-
DENTS
50680x000013CCERROR_INVALID_OPERATION_ON_QUORUMThis operation cannot be performed on the cluster
50690x000013CDERROR_DEPENDENCY_NOT_ALLOWEDThe cluster quorum resource is not allowed to
50700x000013CEERROR_CLUSTER_NODE_PAUSEDThe cluster node is paused.
50710x000013CFERROR_NODE_CANT_HOST_RESOURCEThe cluster resource cannot be brought online.
50720x000013D0ERROR_CLUSTER_NODE_NOT_READYThe cluster node is not ready to perform the re-
50730x000013D1ERROR_CLUSTER_NODE_SHUTTING_DOWNThe cluster node is shutting down.
50740x000013D2ERROR_CLUSTER_JOIN_ABORTEDThe cluster join operation was aborted.
50750x000013D3ERROR_CLUSTER_INCOMPATIBLE_VERSIONS The cluster join operation failed due to incompati-
50760x000013D4ERROR_CLUSTER_MAXNUM_OF_RE-
SOURCES_EXCEEDED
operation.
The cluster network interface was not found.
The cluster network provider is not valid.
cluster communication.
The cluster network is already online.
The cluster network is already offline.
ter.
internal cluster communication between two or
more active cluster nodes. The internal communication capability cannot be removed from the network.
One or more cluster resources depend on the network to provide service to clients. The client access capability cannot be removed from the network.
resource as it the quorum resource. You may not
bring the quorum resource offline or modify its
possible owners list.
have any dependencies.
The owner node cannot run this resource.
quested operation.
ble software versions between the joining node
and its sponsor.
This resource cannot be created because the
cluster has reached the limit on the number of resources it can monitor.
TF661069Version: 1.1
Appendix
ErrorDescription
decimalHexadecimalName
50770x000013D5ERROR_CLUSTER_SYSTEM_CON-
FIG_CHANGED
50780x000013D6ERROR_CLUSTER_RE-
SOURCE_TYPE_NOT_FOUND
50790x000013D7ERROR_CLUSTER_RESTYPE_NOT_SUP-
PORTED
50800x000013D8ERROR_CLUSTER_RESNAME_NOT_FOUNDThe specified resource name is supported by this
50810x000013D9ERROR_CLUSTER_NO_RPC_PACKAGES_REG-
ISTERED
50820x000013DAERROR_CLUSTER_OWNER_NOT_IN_PREFLIST You cannot bring the group online because the
50830x000013DBERROR_CLUSTER_DATABASE_SEQMISMATCH The join operation failed because the cluster data-
50840x000013DCERROR_RESMON_INVALID_STATEThe resource monitor will not allow the fail opera-
50850x000013DDERROR_CLUSTER_GUM_NOT_LOCKERA non locker code got a request to reserve the
50860x000013DEERROR_QUORUM_DISK_NOT_FOUNDThe quorum disk could not be located by the clus-
50870x000013DFERROR_DATABASE_BACKUP_CORRUPTThe backup up cluster database is possibly cor-
50880x000013E0ERROR_CLUSTER_NODE_AL-
READY_HAS_DFS_ROOT
50890x000013E1ERROR_RESOURCE_PROPERTY_UNCHANGE-
ABLE
58900x00001702ERROR_CLUSTER_MEMBERSHIP_IN-
VALID_STATE
58910x00001703ERROR_CLUSTER_QUORUMLOG_NOT_FOUND The quorum resource does not contain the quo-
58920x00001704ERROR_CLUSTER_MEMBERSHIP_HALTThe membership engine requested shutdown of
58930x00001705ERROR_CLUSTER_INSTANCE_ID_MISMATCHThe join operation failed because the cluster in-
58940x00001706ERROR_CLUSTER_NET-
WORK_NOT_FOUND_FOR_IP
58950x00001707ERROR_CLUSTER_PROP-
ERTY_DATA_TYPE_MISMATCH
58960x00001708ERROR_CLUSTER_EVICT_WITHOUT_CLEANUP The cluster node was evicted from the cluster
The system configuration changed during the
cluster join or form operation. The join or form operation was aborted.
The specified resource type was not found.
The specified node does not support a resource
of this type. This may be due to version inconsistencies or due to the absence of the resource DLL
on this node.
resource DLL. This may be due to a bad (or
changed) name supplied to the resource DLL.
No authentication package could be registered
with the RPC server.
owner of the group is not in the preferred list for
the group. To change the owner node for the
group, move the group.
base sequence number has changed or is incompatible with the locker node. This may happen
during a join operation if the cluster database was
changing during the join.
tion to be performed while the resource is in its
current state. This may happen if the resource is
in a pending state.
lock for making global updates.
ter service.
rupt.
A DFS root already exists in this cluster node.
An attempt to modify a resource property failed
because it conflicts with another existing property.
An operation was attempted that is incompatible
with the current membership state of the node.
rum log.
the cluster service on this node.
stance ID of the joining node does not match the
cluster instance ID of the sponsor node.
A matching network for the specified IP address
could not be found. Please also specify a subnet
mask and a cluster network.
The actual data type of the property did not match
the expected data type of the property.
successfully. The node was not cleaned up because it does not support the evict cleanup functionality.
TF661070Version: 1.1
Appendix
ErrorDescription
decimalHexadecimalName
60000x00001770ERROR_ENCRYPTION_FAILEDThe specified file could not be encrypted.
60010x00001771ERROR_DECRYPTION_FAILEDThe specified file could not be decrypted.
60020x00001772ERROR_FILE_ENCRYPTEDThe specified file is encrypted and the user does
60030x00001773ERROR_NO_RECOVERY_POLICYThere is no valid encryption recovery policy con-
60040x00001774ERROR_NO_EFSThe required encryption driver is not loaded for
60050x00001775ERROR_WRONG_EFSThe file was encrypted with a different encryption
60060x00001776ERROR_NO_USER_KEYSThere are no EFS keys defined for the user.
60070x00001777ERROR_FILE_NOT_ENCRYPTEDThe specified file is not encrypted.
60080x00001778ERROR_NOT_EXPORT_FORMATThe specified file is not in the defined EFS export
60090x00001779ERROR_FILE_READ_ONLYThe specified file is read only.
60100x0000177AERROR_DIR_EFS_DISALLOWEDThe directory has been disabled for encryption.
60110x0000177BERROR_EFS_SERVER_NOT_TRUSTEDThe server is not trusted for remote encryption
60120x0000177CERROR_BAD_RECOVERY_POLICYRecovery policy configured for this system con-
60130x0000177DERROR_EFS_ALG_BLOB_TOO_BIGThe encryption algorithm used on the source file
60140x0000177EERROR_VOLUME_NOT_SUPPORT_EFSThe disk partition does not support file encryption.
61180x000017E6ERROR_NO_BROWSER_SERVERS_FOUNDThe list of servers for this workgroup is not cur-
62000x00001838SCHED_E_SERVICE_NOT_LOCALSYSTEMThe Task Scheduler service must be configured
70010x00001B59ERROR_CTX_WINSTATION_NAME_INVALIDThe specified session name is invalid.
70020x00001B5AERROR_CTX_INVALID_PDThe specified protocol driver is invalid.
70030x00001B5BERROR_CTX_PD_NOT_FOUNDThe specified protocol driver was not found in the
70040x00001B5CERROR_CTX_WD_NOT_FOUNDThe specified terminal connection driver was not
70050x00001B5DERROR_CTX_CANNOT_MAKE_EVENTLOG_EN-
TRY
70060x00001B5EERROR_CTX_SERVICE_NAME_COLLISIONA service with the same name already exists on
70070x00001B5FERROR_CTX_CLOSE_PENDINGA close operation is pending on the session.
70080x00001B60ERROR_CTX_NO_OUTBUFThere are no free output buffers available.
70090x00001B61ERROR_CTX_MODEM_INF_NOT_FOUNDThe MODEM.INF file was not found.
70100x00001B62ERROR_CTX_INVALID_MODEMNAMEThe modem name was not found in MODEM.INF.
70110x00001B63ERROR_CTX_MODEM_RESPONSE_ERRORThe modem did not accept the command sent to
70120x00001B64ERROR_CTX_MODEM_RESPONSE_TIMEOUTThe modem did not respond to the command sent
70130x00001B65ERROR_CTX_MODEM_RESPONSE_NO_CAR-
RIER
70140x00001B66ERROR_CTX_MODEM_RESPONSE_NO_DIAL-
TONE
70150x00001B67ERROR_CTX_MODEM_RESPONSE_BUSYBusy signal detected at remote site on callback.
70160x00001B68ERROR_CTX_MODEM_RESPONSE_VOICEVoice detected at remote site on callback.
70220x00001B6EERROR_CTX_WINSTATION_NOT_FOUNDThe specified session cannot be found.
70230x00001B6FERROR_CTX_WINSTATION_ALREADY_EXISTSThe specified session name is already in use.
70240x00001B70ERROR_CTX_WINSTATION_BUSYThe requested operation cannot be completed be-
not have the ability to decrypt it.
figured for this system.
this system.
driver than is currently loaded.
format.
operation.
tains invalid recovery certificate.
needs a bigger key buffer than the one on the
destination file.
rently available.
to run in the System account to function properly.
Individual tasks may be configured to run in other
accounts.
system path.
found in the system path.
A registry key for event logging could not be created for this session.
the system.
it. Verify that the configured modem name
matches the attached modem.
to it. Verify that the modem is properly cabled and
powered on.
Carrier detect has failed or carrier has been
dropped due to disconnect.
Dial tone not detected within the required time.
Verify that the phone cable is properly attached
and functional.
cause the terminal connection is currently busy
processing a connect, disconnect, reset, or delete
operation.
TF661071Version: 1.1
Appendix
ErrorDescription
decimalHexadecimalName
70250x00001B71ERROR_CTX_BAD_VIDEO_MODEAn attempt has been made to connect to a ses-
70350x00001B7BERROR_CTX_GRAPHICS_INVALIDThe application attempted to enable DOS graph-
70370x00001B7DERROR_CTX_LOGON_DISABLEDYour interactive logon privilege has been dis-
70380x00001B7EERROR_CTX_NOT_CONSOLEThe requested operation can be performed only
70400x00001B80ERROR_CTX_CLIENT_QUERY_TIMEOUTThe client failed to respond to the server connect
70410x00001B81ERROR_CTX_CONSOLE_DISCONNECTDisconnecting the console session is not sup-
70420x00001B82ERROR_CTX_CONSOLE_CONNECTReconnecting a disconnected session to the con-
70440x00001B84ERROR_CTX_SHADOW_DENIEDThe request to control another session remotely
70450x00001B85ERROR_CTX_WINSTATION_ACCESS_DENIEDThe requested session access is denied.
70490x00001B89ERROR_CTX_INVALID_WDThe specified terminal connection driver is invalid.
70500x00001B8AERROR_CTX_SHADOW_INVALIDThe requested session cannot be controlled re-
70510x00001B8BERROR_CTX_SHADOW_DISABLEDThe requested session is not configured to allow
70520x00001B8CERROR_CTX_CLIENT_LICENSE_IN_USEYour request to connect to this Terminal Server
70530x00001B8DERROR_CTX_CLIENT_LICENSE_NOT_SETYour request to connect to this Terminal Server
70540x00001B8EERROR_CTX_LICENSE_NOT_AVAILABLEThe system has reached its licensed logon limit.
70550x00001B8FERROR_CTX_LICENSE_CLIENT_INVALIDThe client you are using is not licensed to use this
70560x00001B90ERROR_CTX_LICENSE_EXPIREDThe system license has expired. Your logon re-
70570x00001B91ERROR_CTX_SHADOW_NOT_RUNNINGRemote control could not be terminated because
sion whose video mode is not supported by the
current client.
ics mode. DOS graphics mode is not supported.
abled. Please contact your administrator.
on the system console. This is most often the result of a driver or system DLL requiring direct console access.
message.
ported.
sole is not supported.
was denied.
motely. This may be because the session is disconnected or does not currently have a user
logged on.
remote control.
has been rejected. Your Terminal Server client license number is currently being used by another
user. Please call your system administrator to obtain a unique license number.
has been rejected. Your Terminal Server client license number has not been entered for this copy
of the Terminal Server client. Please contact your
system administrator.
Please try again later.
system. Your logon request is denied.
quest is denied.
the specified session is not currently being remotely controlled.
TF661072Version: 1.1
Appendix
ErrorDescription
decimalHexadecimalName
80010x00001F41FRS_ERR_INVALID_API_SEQUENCEThe file replication service API was called incor-
80020x00001F42FRS_ERR_STARTING_SERVICEThe file replication service cannot be started.
80030x00001F43FRS_ERR_STOPPING_SERVICEThe file replication service cannot be stopped.
80040x00001F44FRS_ERR_INTERNAL_APIThe file replication service API terminated the re-
80050x00001F45FRS_ERR_INTERNALThe file replication service terminated the request.
80060x00001F46FRS_ERR_SERVICE_COMMThe file replication service cannot be contacted.
80070x00001F47FRS_ERR_INSUFFICIENT_PRIVThe file replication service cannot satisfy the re-
80080x00001F48FRS_ERR_AUTHENTICATIONThe file replication service cannot satisfy the re-
80090x00001F49FRS_ERR_PARENT_INSUFFICIENT_PRIVThe file replication service cannot satisfy the re-
80100x00001F4AFRS_ERR_PARENT_AUTHENTICATIONThe file replication service cannot satisfy the re-
80110x00001F4BFRS_ERR_CHILD_TO_PARENT_COMMThe file replication service cannot communicate
80120x00001F4CFRS_ERR_PARENT_TO_CHILD_COMMThe file replication service on the domain con-
80130x00001F4DFRS_ERR_SYSVOL_POPULATEThe file replication service cannot populate the
80140x00001F4EFRS_ERR_SYSVOL_POPULATE_TIMEOUTThe file replication service cannot populate the
80150x00001F4FFRS_ERR_SYSVOL_IS_BUSYThe file replication service cannot process the re-
80160x00001F50FRS_ERR_SYSVOL_DEMOTEThe file replication service cannot stop replicating
80170x00001F51FRS_ERR_INVALID_SERVICE_PARAMETERThe file replication service detected an invalid pa-
82000x00002008ERROR_DS_NOT_INSTALLEDAn error occurred while installing the directory
82010x00002009ERROR_DS_MEMBERSHIP_EVALUATED_LO-
CALLY
82020x0000200AERROR_DS_NO_ATTRIBUTE_OR_VALUEThe specified directory service attribute or value
82030x0000200BERROR_DS_INVALID_ATTRIBUTE_SYNTAXThe attribute syntax specified to the directory ser-
82040x0000200CERROR_DS_ATTRIBUTE_TYPE_UNDEFINEDThe attribute type specified to the directory ser-
82050x0000200DERROR_DS_ATTRIBUTE_OR_VALUE_EXISTSThe specified directory service attribute or value
82060x0000200EERROR_DS_BUSYThe directory service is busy.
82070x0000200FERROR_DS_UNAVAILABLEThe directory service is unavailable.
82080x00002010ERROR_DS_NO_RIDS_ALLOCATEDThe directory service was unable to allocate a rel-
82090x00002011ERROR_DS_NO_MORE_RIDSThe directory service has exhausted the pool of
82100x00002012ERROR_DS_INCORRECT_ROLE_OWNERThe requested operation could not be performed
rectly.
quest. The event log may have more information.
The event log may have more information.
The event log may have more information.
quest because the user has insufficient privileges.
The event log may have more information.
quest because authenticated RPC is not available. The event log may have more information.
quest because the user has insufficient privileges
on the domain controller. The event log may have
more information.
quest because authenticated RPC is not available
on the domain controller. The event log may have
more information.
with the file replication service on the domain controller. The event log may have more information.
troller cannot communicate with the file replication
service on this computer. The event log may have
more information.
system volume because of an internal error. The
event log may have more information.
system volume because of an internal timeout.
The event log may have more information.
quest. The system volume is busy with a previous
request.
the system volume because of an internal error.
The event log may have more information.
rameter.
service. For more information, see the event log.
The directory service evaluated group memberships locally.
does not exist.
vice is invalid.
vice is not defined.
already exists.
ative identifier.
relative identifiers.
because the directory service is not the master for
that type of operation.
TF661073Version: 1.1
Appendix
ErrorDescription
decimalHexadecimalName
82110x00002013ERROR_DS_RIDMGR_INIT_ERRORThe directory service was unable to initialize the
82120x00002014ERROR_DS_OBJ_CLASS_VIOLATIONThe requested operation did not satisfy one or
82130x00002015ERROR_DS_CANT_ON_NON_LEAFThe directory service can perform the requested
82140x00002016ERROR_DS_CANT_ON_RDNThe directory service cannot perform the re-
82150x00002017ERROR_DS_CANT_MOD_OBJ_CLASSThe directory service detected an attempt to mod-
84700x00002116ERROR_DS_NAME_ERROR_NOT_FOUNDName translation: Could not find the name or in-
84710x00002117ERROR_DS_NAME_ERROR_NOT_UNIQUEName translation: Input name mapped to more
84720x00002118ERROR_DS_NAME_ERROR_NO_MAPPINGName translation: Input name found, but not the
84730x00002119ERROR_DS_NAME_ERROR_DOMAIN_ONLYName translation: Unable to resolve completely,
84740x0000211AERROR_DS_NAME_ERROR_NO_SYNTACTI-
CAL_MAPPING
84750x0000211BERROR_DS_CONSTRUCTED_ATT_MODModification of a constructed att is not allowed.
84760x0000211CERROR_DS_WRONG_OM_OBJ_CLASSThe OM-Object-Class specified is incorrect for an
84770x0000211DERROR_DS_DRA_REPL_PENDINGThe replication request has been posted; waiting
get server already exists.
get server does not exist.
it is replicated to another server.
error.
moved or is not replicated from the specified
server.
version of the directory service.
celled.
requests.
cation requests.
of object names.
quired parent object is missing.
abandoned because of a lack of updates.
the system is shutting down.
The replication synchronization attempt failed as
the destination partial attribute set is not a subset
of source partial attribute set.
The replication synchronization attempt failed because a master replica attempted to sync from a
partial replica.
was contacted, but that server was unable to contact an additional server needed to complete the
operation.
source forest is not compatible with the version of
Active Directory on this computer. You must upgrade the operating system on a domain controller in the source forest before this computer
can be added as a domain controller to that forest.
link identifier already exists.
sufficient right to see name.
than one output name.
associated output format.
only the domain was found.
Name translation: Unable to perform purely syntactical mapping at the client without going out to
the wire.
attribute with the specified syntax.
for reply.
TF661079Version: 1.1
Appendix
ErrorDescription
decimalHexadecimalName
84780x0000211EERROR_DS_DS_REQUIREDThe requested operation requires a directory ser-
84790x0000211FERROR_DS_INVALID_LDAP_DISPLAY_NAMEThe LDAP display name of the class or attribute
84800x00002120ERROR_DS_NON_BASE_SEARCHThe requested search operation is only supported
84810x00002121ERROR_DS_CANT_RETRIEVE_ATTSThe search failed to retrieve attributes from the
84820x00002122ERROR_DS_BACKLINK_WITHOUT_LINKThe schema update operation tried to add a back-
84830x00002123ERROR_DS_EPOCH_MISMATCHSource and destination of a cross domain move
84840x00002124ERROR_DS_SRC_NAME_MISMATCHSource and destination of a cross domain move
84850x00002125ERROR_DS_SRC_AND_DST_NC_IDENTICALSource and destination of a cross domain move
84860x00002126ERROR_DS_DST_NC_MISMATCHSource and destination for a cross domain move
84870x00002127ERROR_DS_NOT_AUTHORITIVE_FOR_DST_NC Destination of a cross domain move is not author-
84880x00002128ERROR_DS_SRC_GUID_MISMATCHSource and destination of a cross domain move
84890x00002129ERROR_DS_CANT_MOVE_DELETED_OBJECTObject being moved across domains is already
84900x0000212AERROR_DS_PDC_OPERATION_IN_PROGRESS Another operation which requires exclusive ac-
84910x0000212BERROR_DS_CROSS_DOMAIN_CLEANUP_REQD A cross domain move operation failed such that
84920x0000212CERROR_DS_ILLEGAL_XDOM_MOVE_OPERA-
TION
84930x0000212DERROR_DS_CANT_WITH_ACCT_GROUP_MEM-
BERSHPS
84940x0000212EERROR_DS_NC_MUST_HAVE_NC_PARENTA naming context head must be the immediate
84950x0000212FERROR_DS_CR_IMPOSSIBLE_TO_VALIDATEThe directory cannot validate the proposed nam-
84960x00002130ERROR_DS_DST_DOMAIN_NOT_NATIVEDestination domain must be in native mode.
vice, and none was available.
contains non-ASCII characters.
for base searches.
database.
ward link attribute that has no corresponding forward link.
do not agree on the object's epoch number. Either
source or destination does not have the latest version of the object.
do not agree on the object's current name. Either
source or destination does not have the latest version of the object.
operation are identical. Caller should use local
move operation instead of cross domain move operation.
are not in agreement on the naming contexts in
the forest. Either source or destination does not
have the latest version of the Partitions container.
itative for the destination naming context.
do not agree on the identity of the source object.
Either source or destination does not have the latest version of the source object.
known to be deleted by the destination server.
The source server does not have the latest version of the source object.
cess to the PDC PSMO is already in progress.
the two versions of the moved object exist - one
each in the source and destination domains. The
destination object needs to be removed to restore
the system to a consistent state.
This object may not be moved across domain
boundaries either because cross domain moves
for this class are disallowed, or the object has
some special characteristics, eg: trust account or
restricted RID, which prevent its move.
Can't move objects with memberships across domain boundaries as once moved, this would violate the membership conditions of the account
group. Remove the object from any account
group memberships and retry.
child of another naming context head, not of an
interior node.
ing context name because it does not hold a
replica of the naming context above the proposed
naming context. Please ensure that the domain
naming master role is held by a server that is configured as a global catalog server, and that the
server is up to date with its replication partners.
(Applies only to Windows 2000 Domain Naming
masters)
85050x00002139ERROR_DS_SENSITIVE_GROUP_VIOLATIONOnly an administrator can modify the membership
85060x0000213AERROR_DS_CANT_MOD_PRIMARYGROUPIDCannot change the primary group ID of a domain
85070x0000213BERROR_DS_ILLEGAL_BASE_SCHEMA_MODAn attempt is made to modify the base schema.
85080x0000213CERROR_DS_NONSAFE_SCHEMA_CHANGEAdding a new mandatory attribute to an existing
85090x0000213DERROR_DS_SCHEMA_UPDATE_DISALLOWEDSchema update is not allowed on this DC be-
85100x0000213EERROR_DS_CANT_CREATE_UNDER_SCHEMA An object of this class cannot be created under
85110x0000213FERROR_DS_INSTALL_NO_SRC_SCH_VERSION The replica/child install failed to get the objectVer-
85120x00002140ERROR_DS_INSTALL_NO_SCH_VER-
SION_IN_INIFILE
85130x00002141ERROR_DS_INVALID_GROUP_TYPEThe specified group type is invalid.
85140x00002142ERROR_DS_NO_NEST_GLOBAL-
GROUP_IN_MIXEDDOMAIN
85150x00002143ERROR_DS_NO_NEST_LOCAL-
GROUP_IN_MIXEDDOMAIN
85160x00002144ERROR_DS_GLOBAL_CANT_HAVE_LO-
CAL_MEMBER
85170x00002145ERROR_DS_GLOBAL_CANT_HAVE_UNIVER-
SAL_MEMBER
85180x00002146ERROR_DS_UNIVERSAL_CANT_HAVE_LO-
CAL_MEMBER
85190x00002147ERROR_DS_GLOBAL_CANT_HAVE_CROSSDO-
MAIN_MEMBER
85200x00002148ERROR_DS_LOCAL_CANT_HAVE_CROSSDO-
MAIN_LOCAL_MEMBER
85210x00002149ERROR_DS_HAVE_PRIMARY_MEMBERSA group with primary members cannot change to
85220x0000214AERROR_DS_STRING_SD_CONVERSION_FAILED The schema cache load failed to convert the
85230x0000214BERROR_DS_NAMING_MASTER_GCOnly DSAs configured to be Global Catalog
85240x0000214CERROR_DS_LOOKUP_FAILUREThe DSA operation is unable to proceed because
ANR bit is valid only on attributes of Unicode or
Teletex strings.
NC head as a descendant are not allowed.
The directory service failed to lock a tree in preparation for a tree deletion because the tree was in
use.
The directory service failed to identify the list of
objects to delete while attempting a tree deletion.
cause of the following error: %1. Error Status: 0x
%2. Click OK to shut down the system and reboot
into Directory Services Restore Mode. Check the
event log for detailed information.
list of an administrative group.
controller account.
class, deleting a mandatory attribute from an existing class, or adding an optional attribute to the
special class Top that is not a backlink attribute
(directly or through inheritance, for example, by
adding or deleting an auxiliary class) is not allowed.
cause the DC is not the schema FSMO Role
Owner.
the schema container. You can only create attribute-schema and class-schema objects under
the schema container.
sion attribute on the schema container on the
source DC. Either the attribute is missing on the
schema container or the credentials supplied do
not have permission to read it.
The replica/child install failed to read the objectVersion attribute in the SCHEMA section of
the file schema.ini in the system32 directory.
Cannot nest global groups in a mixed domain if
the group is security-enabled.
Cannot nest local groups in a mixed domain if the
group is security-enabled.
A global group cannot have a local group as a
member.
A global group cannot have a universal group as
a member.
A universal group cannot have a local group as a
member.
A global group cannot have a cross-domain member.
A local group cannot have another cross-domain
local group as a member.
a security-disabled group.
string default SD on a class-schema object.
servers should be allowed to hold the Domain
Naming Master FSMO role. (Applies only to Windows 2000 servers)
of a DNS lookup failure.
TF661082Version: 1.1
Appendix
ErrorDescription
decimalHexadecimalName
85250x0000214DERROR_DS_COULDNT_UPDATE_SPNSWhile processing a change to the DNS Host
85260x0000214EERROR_DS_CANT_RETRIEVE_SDThe Security Descriptor attribute could not be
85270x0000214FERROR_DS_KEY_NOT_UNIQUE.The object requested was not found, but an object
85280x00002150ERROR_DS_WRONG_LINKED_ATT_SYNTAXThe syntax of the linked attributed being added is
85290x00002151ERROR_DS_SAM_NEED_BOOTKEY_PASS-
WORD
85300x00002152ERROR_DS_SAM_NEED_BOOTKEY_FLOPPYSecurity Account Manager needs to get the boot
85310x00002153ERROR_DS_CANT_STARTDirectory Service cannot start.
85320x00002154ERROR_DS_INIT_FAILUREDirectory Services could not start.
85330x00002155ERROR_DS_NO_PKT_PRIVACY_ON_CONNEC-
TION
85340x00002156ERROR_DS_SOURCE_DOMAIN_IN_FORESTThe source domain may not be in the same forest
85420x0000215EERROR_DS_DRA_SCHEMA_INFO_SHIPSchema information could not be included in the
85430x0000215FERROR_DS_DRA_SCHEMA_CONFLICTThe replication operation could not be completed
85440x00002160ERROR_DS_DRA_EARLIER_SCHEMA_CONLICT The replication operation could not be completed
85450x00002161ERROR_DS_DRA_OBJ_NC_MISMATCHThe replication update could not be applied be-
85460x00002162ERROR_DS_NC_STILL_HAS_DSASThe requested domain could not be deleted be-
85470x00002163ERROR_DS_GC_REQUIREDThe requested operation can be performed only
85480x00002164ERROR_DS_LOCAL_MEMBER_OF_LO-
CAL_ONLY
85490x00002165ERROR_DS_NO_FPO_IN_UNIVERSAL_GROUPS Foreign security principals cannot be members of
85500x00002166ERROR_DS_CANT_ADD_TO_GCThe attribute is not allowed to be replicated to the
85510x00002167ERROR_DS_NO_CHECKPOINT_WITH_PDCThe checkpoint with the PDC could not be taken
85520x00002168ERROR_DS_SOURCE_AUDITING_NOT_EN-
ABLED
85530x00002169ERROR_DS_CANT_CREATE_IN_NONDO-
MAIN_NC
Name for an object, the Service Principal Name
values could not be kept in sync.
read.
with that key was found.
incorrect. Forward links can only have syntax
2.5.5.1, 2.5.5.7, and 2.5.5.14, and backlinks can
only have syntax 2.5.5.1.
Security Account Manager needs to get the boot
password.
key from floppy disk.
The connection between client and server requires packet privacy or better.
as destination.
The destination domain must be in the forest.
The operation requires that destination domain
auditing be enabled.
The operation couldn't locate a DC for the source
domain.
tion forest.
The source and destination object must be of the
same type.
cause of the following error: %1. Error Status: 0x
%2. Click OK to shut down the system and reboot
into Safe Mode. Check the event log for detailed
information.
replication request.
due to a schema incompatibility.
due to a previous schema incompatibility.
cause either the source or the destination has not
yet received information regarding a recent crossdomain move operation.
cause there exist domain controllers that still host
this domain.
on a global catalog server.
A local group can only be a member of other local
groups in the same domain.
universal groups.
GC because of security reasons.
because there are too many modifications being
processed currently.
The operation requires that source domain auditing be enabled.
Security principal objects can only be created inside domain naming contexts.
TF661083Version: 1.1
Appendix
ErrorDescription
decimalHexadecimalName
85540x0000216AERROR_DS_INVALID_NAME_FOR_SPNA Service Principal Name (SPN) could not be
85550x0000216BERROR_DS_FILTER_USES_CONTRUCTED_AT-
TRS
85560x0000216CERROR_DS_UNICODEPWD_NOT_IN_QUOTESThe unicodePwd attribute value must be enclosed
85570x0000216DERROR_DS_MACHINE_ACCOUNT_QUOTA_EX-
CEEDED
85580x0000216EERROR_DS_MUST_BE_RUN_ON_DST_DCFor security reasons, the operation must be run
85590x0000216FER-
ROR_DS_SRC_DC_MUST_BE_SP4_OR_GREATE
R
85600x00002170ERROR_DS_CANT_TREE_DELETE_CRITI-
CAL_OBJ
85610x00002171ERROR_DS_INIT_FAILURE_CONSOLEDirectory Services could not start because of the
85630x00002173ERROR_DS_FOREST_VERSION_TOO_HIGHThis version of Windows is too old to support the
85640x00002174ERROR_DS_DOMAIN_VERSION_TOO_HIGHThis version of Windows is too old to support the
85650x00002175ERROR_DS_FOREST_VERSION_TOO_LOWThis version of Windows no longer supports the
85660x00002176ERROR_DS_DOMAIN_VERSION_TOO_LOWThis version of Windows no longer supports the
85670x00002177ERROR_DS_INCOMPATIBLE_VERSIONThe version of Windows is incompatible with the
85680x00002178ERROR_DS_LOW_DSA_VERSIONThe behavior version cannot be increased to the
85690x00002179ERROR_DS_NO_BEHAVIOR_VER-
SION_IN_MIXEDDOMAIN
85700x0000217AERROR_DS_NOT_SUPPORTED_SORT_ORDER The sort order requested is not supported.
85710x0000217BERROR_DS_NAME_NOT_UNIQUEFound an object with a non unique name.
85720x0000217CERROR_DS_MACHINE_ACCOUNT_CRE-
ATED_PRENT4
85730x0000217DERROR_DS_OUT_OF_VERSION_STOREThe database is out of version store.
85740x0000217EERROR_DS_INCOMPATIBLE_CONTROLS_USED Unable to continue operation because multiple
85750x0000217FERROR_DS_NO_REF_DOMAINUnable to find a valid security descriptor refer-
constructed because the provided hostname is
not in the necessary format.
A Filter was passed that uses constructed attributes.
in double quotes.
Your computer could not be joined to the domain.
You have exceeded the maximum number of
computer accounts you are allowed to create in
this domain. Contact your system administrator to
have this limit reset or increased.
on the destination DC.
For security reasons, the source DC must be
NT4SP4 or greater.
Critical Directory Service System objects cannot
be deleted during tree delete operations. The tree
delete may have been partially performed.
following error: %1. Error Status: 0x%2. Please
click OK to shutdown the system. You can use
the recovery console to diagnose the system further.
cause of the following error: %1. Error Status: 0x
%2. Please click OK to shutdown the system. You
can use the recovery console to diagnose the
system further.
current directory forest behavior. You must upgrade the operating system on this server before
it can become a domain controller in this forest.
current domain behavior. You must upgrade the
operating system on this server before it can become a domain controller in this domain.
behavior version in use in this directory forest.
You must advance the forest behavior version before this server can become a domain controller in
the forest.
behavior version in use in this domain. You must
advance the domain behavior version before this
server can become a domain controller in the domain.
behavior version of the domain or forest.
requested value because Domain Controllers still
exist with versions lower than the requested
value.
The behavior version value cannot be increased
while the domain is still in mixed domain mode.
You must first change the domain to native mode
before increasing the behavior version.
The machine account was created pre-NT4. The
account needs to be recreated.
conflicting controls were used.
ence domain for this partition.
TF661084Version: 1.1
Appendix
ErrorDescription
decimalHexadecimalName
85760x00002180ERROR_DS_RESERVED_LINK_IDSchema update failed: The link identifier is re-
85770x00002181ERROR_DS_LINK_ID_NOT_AVAILABLESchema update failed: There are no link identi-
85780x00002182ERROR_DS_AG_CANT_HAVE_UNIVER-
SAL_MEMBER
85790x00002183ERROR_DS_MODIFYDN_DISALLOWED_BY_IN-
STANCE_TYPE
85800x00002184ERROR_DS_NO_OB-
JECT_MOVE_IN_SCHEMA_NC
85810x00002185ERROR_DS_MODIFYDN_DISAL-
LOWED_BY_FLAG
85820x00002186ERROR_DS_MODIFYDN_WRONG_GRANDPAR-
ENT
85830x00002187ERROR_DS_NAME_ERROR_TRUST_REFERRAL Unable to resolve completely, a referral to another
85840x00002188ERROR_NOT_SUPPORTED_ON_STAN-
DARD_SERVER
85850x00002189ERROR_DS_CANT_ACCESS_RE-
MOTE_PART_OF_AD
85860x0000218AERROR_DS_CR_IMPOSSIBLE_TO_VALIDATE_V2 The directory cannot validate the proposed nam-
85870x0000218BERROR_DS_THREAD_LIMIT_EXCEEDEDThe thread limit for this request was exceeded.
85880x0000218CERROR_DS_NOT_CLOSESTThe Global catalog server is not in the closet site.
served.
fiers available.
An account group can not have a universal group
as a member.
Rename or move operations on naming context
heads or read-only objects are not allowed.
Move operations on objects in the schema naming context are not allowed.
A system flag has been set on the object and
does not allow the object to be moved or renamed.
This object is not allowed to change its grandparent container. Moves are not forbidden on this object, but are restricted to sibling containers.
forest is generated.
The requested action is not supported on standard server.
Could not access a partition of the Active Directory located on a remote server. Make sure at
least one server is running for the partition in
question.
ing context (or partition) name because it does
not hold a replica nor can it contact a replica of
the naming context above the proposed naming
context. Please ensure that the parent naming
context is properly registered in DNS, and at least
one replica of this naming context is reachable by
the Domain Naming master.
TF661085Version: 1.1
Appendix
ErrorDescription
decimalHexadecimalName
90010x00002329DNS_ERROR_RCODE_FORMAT_ERRORDNS server unable to interpret format.
90020x0000232ADNS_ERROR_RCODE_SERVER_FAILUREDNS server failure.
90030x0000232BDNS_ERROR_RCODE_NAME_ERRORDNS name does not exist.
90040x0000232CDNS_ERROR_RCODE_NOT_IMPLEMENTEDDNS request not supported by name server.
138770x00003635ERROR_IPSEC_IKE_RPC_DELETEDeleted via RPC call.
138780x00003636ERROR_IPSEC_IKE_BENIGN_REINITTemporary state created to perform reinitializa-
138790x00003637ERROR_IPSEC_IKE_INVALID_RESPON-
DER_LIFETIME_NOTIFY
138800x00003638ERROR_IPSEC_IKE_QM_LIMIT_REAPSA reaped because QM limit was reached.
138810x00003639ERROR_IPSEC_IKE_INVALID_CERT_KEYLENKey length in certificate is too small for configured
138820x0000363AERROR_IPSEC_IKE_MM_LIMITMax number of established MM SAs to peer ex-
138830x0000363BERROR_IPSEC_IKE_NEGOTIATION_DISABLEDIKE received a policy that disables negotiation.
138840x0000363CERROR_IPSEC_IKE_QM_LIMITReached maximum quick mode limit for the main
ISAKMP/ERROR_IPSEC_IKE service. Kerberos
authentication will not function. The most likely
reason for this is lack of domain membership.
This is normal if your computer is a member of a
workgroup.
ISAKMP/ERROR_IPSEC_IKE service (QueryCredentialsAttributes).
Ipsec driver. The most common cause for this is
that the driver does not have the correct filter.
Check your policy to verify the filters.
Driver. The most common cause for this is if the
IKE negotiation took too long to complete. If the
problem persists, reduce the load on the faulting
machine.
tion. This is not a real failure.
The lifetime value received in the Responder Lifetime Notify is below the Windows 2000 configured
minimum value. Please fix the policy on the peer
machine.
security requirements.
ceeded.
mode. New main mode will be started.
8.5Troubleshooting/diagnostics
1. In the event of connection problems the PING command can be used to ascertain whether the external
controller can be reached via the network connection. If this is not the case, check the configuration/power
supply and the network connection of the adapter module. Instructions for configuring the adapter module
can be found in the manufacturer documentation for the adapter.
2. Sniffer tools such as Wireshark enable logging of the entire network communication. The log can then be
analyzed by Beckhoff support staff.
TF661095Version: 1.1
Appendix
3. Check the hardware and software requirements described in this documentation (adapter manufacturer,
model, firmware version).
4. If you access the external controller via the IBH Link S5++ or IBH Link S7++ adapter in conjunction with
TCP/IP as transport protocol, no connections have to be configured/parameterized in the external controller.
In the event of data access problems, check whether the corresponding data areas (flags, data blocks etc. )
in the external controller are configured correctly and available.
5. Check the input parameters that are transferred to the function blocks (network address, MPI address,
data block number etc.) for correctness. Check whether the function block issues an error code. The
documentation for the error codes can be found here: Overview of error codes [}32].
6. A simple debug output is integrated in the TwinCAT PLC library. This must be activated before
establishing the connection at the FB_NlinkOpen [}20]function block. Open TwinCAT XAE and enable the
error list window. The following image shows some debug output strings.
Sample:
Communication via the IBH Link S7++ (NL-MPI protocol via TCP/IP). Only complete frames are logged (16
byte header + PLC data from the corresponding data area), i.e. byte 16 is followed by the read and written
PLC data.