STEP 7 Error Codes Version 01/2014

Error number: Text: Cause: Remedy:

1:2063 TBI error 2063 Error during the function chdir TBI can occur with the call AUTgetlinkedObjects. There should be an
AUT API tracer in the meantime.
7:6160 CPUs can only be connected via K bus or MPI bus Split the desired path of the global data into several circuits. Make sure that
(line 1) you only use on bus per circuit.
11:103 Cannot read CPU information on module, such as Check the logical address of the module. Check the slot and the configured
rated type, actual type and status of the module. slot.
Module might not be configured.
13:31 The online connection from the PG to the module (SDB addressee) could Clear the fault in the connection to the module (SDB addressee) and you
not be set up. Connection hardware is faulty (e.g. connection cable can then repeat the attempt to set up the connection in this dialog.
removed).
The online connection from the PG to the module (SDB addressee) could Change the operating mode of the module (SDB addressee) and you can
not be set up. The module (SDB addressee) is in the wrong operating then repeat the attempt to set up the connection in this dialog.
mode.
The online connection from the PG to the module (SDB addressee) could If you have specified an incorrect MPI address, then:
not be set up. You have specified an incorrect MPI address with STEP 7. 1. Acknowledge this dialog
2. Correct the MPI address with STEP 7
3. Restart the "Load" function
13:32 There is a problem with the connection to the The online connection from the PG to the module (SDB addressee) could Clear the fault in the connection, change the operating mode of the module
receiver of the HW configuration not be set up. The module recognized an error with the next or clear the storage bottleneck on the module and then you can repeat the
communications call. attempt to set up the connection in this dialog.
Connection hardware is faulty (e.g. connection cable removed) Plug the cable in.
Module is in the wrong operating mode Check the operating mode.
Storage bottleneck on the module
Inconsistent HW configuration in the PG If the HW configuration is inconsistent in the PG, then:
1. Acknowledge this dialog
2. Correct the HW configuration in the configuration table
3. Restart the "Load" function
When loading the system data on to the memory card, this message is Delete the system data in the SIMATIC Manager and then restart the HW
displayed if there are invalid SDBs in the SDB folder. Config.
13:48 Internal error 0400 Station cannot be generated. The station cannot be created in the selected project because ...
The project directory is write-protected Remove the write-protection for the project directory
The project directory is on a network drive and the connection cannot be Set up the connection to the network drive
set up
No more storage capacity on the target drive Delete any data no longer needed on the target drive
13:76 Inconsistent hardware configuration in the Inconsistent HW configuration in the PG In HW Config analyze the HW configuration via the menu "Station\Check
programming device. consistency".

Frei verwendbar Page 1 / 62

 STEP 7 Error Codes Version 01/2014

Error number: Text: Cause: Remedy:

Folder "...\SIEMENS\STEP7\S7TMP" is missing or write-protected
Missing authorization or an options package that generates the SDBs for
a specific module.
"Error in generating the system data" when The environment tag S7TMP is not set. The path Check that the paths in your Autoexec.bat are set as follows:
downloading or saving a station in HW Config c:\\SDBDATA\s7hwcnfk\down\r00s02\sdb0.dat is completely or partly SET PATH="C:\SIEMENS\COMMON\SQLANY"
invalid SET SQLANY=C:\SIEMENS\Common\sqlany
SET S7TMP=C:\SIEMENS\STEP7\S7TMP
13:77 While interpreting the system data blocks (SDBs) Inconsistent HW configuration in module, occurs when previous loading
uploaded from the module, an error was of SDBs into the module was incomplete or faulty.
recognized in the programming device and
processing halted.
Options package for configuring specific modules (e.g. CPs) is not
installed
In STEP 7 V5.x, when an S7-300/S7-400 CPU This may be due to the absence of option packages or GSD(ML) files, the Based on the upload, it is not possible to find out which option packages or
loads a station into an empty project, the following recompilation of which requires the installation of the option package or GSD(ML) files are missing. Check the hardware configuration to see if
error message occurs: “Upload Station to PG the GSD (ML) file. option packages or GSD(ML) files are required for your configuration. The
(13:77)(2000) Error while uploading the missing option packages or GSD (ML) files must then also be installed on
configuration to the programming device (PG).” the PC/PG where the upload is to be performed.

Basically, we recommend that you always use the original project instead of
a station upload, as a station upload cannot read all the files back.

13:136 The maximum possible number of slots within all More slaves have been configured than permitted by the master system Split the slaves across different segments if possible or reduce the number
inserted slaves has been exceeded by %1 slot(s)." of slaves for the master system concerned.

13:181 Internal error:Multicomputig cannot have the type Error in HW Config of first 4.02.x version Add another CPU and then deleted it. The CPU is then automatically set to
"inhomogenous" single-computing again
13:422 No master system is assigned to the DP slave. Missing object Right-click for pop-up menu, select "Add master system" and then configure
the CP again as slave
13:520 The address entered is already occupied. STEP 7 Confirm the address suggested by STEP 7 or enter a new address.
has already calculated the next free address.

13:4003 Module cannot be inserted here. You can use only An attempt was made to connect a device directly to the DP bus, which In the HW catalog insert a hierarchy level for this device as DP slave
DP slaves in a master system. does not have its own interface.
13:4040 The number of slots of the CPU or the master Maximum number of modules already configured. New modules can only be slotted after deleting slaves or their modules.
system has been exceeded or exhausted.

Frei verwendbar Page 2 / 62

 STEP 7 Error Codes Version 01/2014

Error number: Text: Cause: Remedy:

13:4241 The offline configuration (%2) differs from the An external module (interbus interfacing) from the Phoenix company was Remove external module (error can be ignored)
hardware configuration of the PLC (%3). Do you slotted
still want to continue?
13:4337 Unable to set up connection to module %1 The online connection from the PG to the module (SDB addressee) could
(R%3!d!/S%4!d!). not be set up.
Connection hardware is faulty. Make physical check of connections (cable break,...). Repeat attempt to set
up connection.
Module (SDB addressee) is in the wrong operating mode. Check operating mode. Repeat attempt to set up connection.
You have specified an incorrect MPI address in the dialog box when If you have specified an incorrect MPI address in the dialog box, then
loading to a PLC. proceed as follows: 1.
Acknowledge this dialog
2. Correct the MPI address and trigger the Load function again.
PG/PC with PROFIBUS interface is connected directly with an intelligent Proceed as follows if the PG/PC interface is set incorrectly:
DP slave (e.g. ET 200X BM147/CPU) and the PG/PC interface is set 1. Navigate from the Windows Start bar (Start button) to SIMATIC > Step7 >
incorrectly. Set PG-PC interface.
2. In the Access Path tab mark the PROFIBUS CP and click the Properties
button. 3. In the Station
Parameters group, deactivate the check box "Do not activate as only
master".
13:4343 An update is presently not possible. In one or more In the different S7 applications there are objects (stations) open in which Please close the station window in the hardware configuration and all other
STEP 7 applications at least one GSE file or type DP slaves are used. Thus it is no longer possible to install new GSD or STEP7 applications (such as NETPRO, for example) that could access the
file is being referenced. type files, or even to update them. GSD file . The Hardware Configuration application remains open however
without content. Then you can install the GSD file.
13:4341 The GSE file (type file) %1 contains syntax errors. STEP7 V5 + SP3 does a strict check of the GSD files. Some are not Create a backup copy of the GSD files; open file (e.g. with Wordpad) and
For this reason it cannot be interpreted. accepted, e.g. when the name is longer than 23 characters edit excerpt from the file Vendor_Name =
"1234567890123456789012345678901234567890Machine Factory". The
name is longer than the max. 23 characters permitted. Correct to:
Vendor_Name = " xxxxx Machine Factory". Save the file and re-incorporate
it.
13:4366 Error during complete restart of the module. An error has occurred when attempting to start the module (restart). Start the module or all the modules of the multicomputing station from the
Possibly not all the CPUs of the multicomputing station have been SIMATIC Manager via PLC and Operating Status.
started.
An error has occurred when attempting to start the module (restart). Set the key switch of the CPU/FM to RUN or RUN-P.
The key switch of the CPU/FM is in the STOP position
An error has occurred when attempting to start the module (restart). The Set the operating mode switch of the CP to RUN.
operating mode switch of the CP is in the STOP position

Frei verwendbar Page 3 / 62

 STEP 7 Error Codes Version 01/2014

Error number: Text: Cause: Remedy:

13:4589 Details: (D221); cannot load SDB 7XX". H connections are configured in your project. The configuration of high- In the SIMATIC Manager delete the "System Data" folder in "CPU > S7
availability S7 connections has changed in STEP 7 V5.1. There are program > Blocks". Then regenerate the system data in "NetPro".
individual old configurations whose system data after a change can no
longer be assigned to the latest configured high-availability S7
connections. This then leads to abortion of the download.
15:20533 The maximal length of debug info (max. 64 Kbyte) The maximal length of debug info of 64 Kbyte is dependent of the system The debug info will be increased very fast if there is a lot of accesses to data
is reached. and can not be added. blocks. We recommend in refer to the debug info to reduce the access of
only few data blocks.
16:5016 Parameter can not be controlled You are trying to control an operand whose address is outside the Comment out the relevant line in the VAT.
permitted range of the controlling CPU.
You are trying to control an operand outside the process image for which It is possible to control of the operand inside the process image even if no
there is no module available. module is slotted for the operand.
The data block (DB) that is to be controlled is not in the CPU to be Load the DB into the relevant CPU.
controlled. The data block (DB) is write-protected.
The data block (DB) is write-protected. You have no write access to this DB. You must disable the READ-ONLY
attribute for this DB to have write access to it.
You are trying to control a periphery input (PI). Direct write access to an input module is not permitted.
With the function "Release PQ" you can only control peripheral outputs Direct write access to an input module is not permitted.
(PQ).
16:5053 In "Process Mode" it is not permitted to control or monitor I/Os. Consider whether you achieve the desired result by monitoring the process
image. Otherwise parameterize the CPU for Test Mode (Configure Hardware
/ "CPU Properties" dialog box / "Protection" tab).
30:13 The interface of a called block has been changed. This means that the STEP 7 up to V4.02.x:
parameters are not transferred properly to the changed block. The block In the case of expanded block calls you delete the complete call sequence
call is expanded and then displayed marked as faulty. (all statements between the limiting PICTURE commands, including the red
CALL / END_CALL lines) and then re-enter the CALL.
STEP 7 V5.x and higher:
In the case of incorrectly marked block calls you position the cursor in the
CALL line and select the menu Edit>Block Call>Update. This adapts the
block call to the new interface. Then check the new assignment of
parameters.
30:15 The type object has a different time stamp to the opened block. The local Blocks have been opened either by available users or the blocks have been
symbols are displayed as pseudosymbols. copied with the SIMATIC Manager from the CPU into the OFFLINE
database. However, since the CPU knows no symbols, the variable names
are replaced by default names.

Frei verwendbar Page 4 / 62

 STEP 7 Error Codes Version 01/2014

Error number: Text: Cause: Remedy:

30:50 Error while generating the STL source. The STL source cannot be generated, e.g. because it exists already and Generate a source with a new name or make sure that there is enough
is write-protected, or because there is no more memory available on the memory available for the source to be generated.
drive.
30:484 The displayed block cannot be monitored because This is found to be caused by a discrepancy in the time stamps between The programs which are generated with CFC must be downloaded from the
it does not match the block in the CPU. the online block and the offline block and means that the blocks are CFC to the PLC because only this loading function guarantees that the
Do you want to download the displayed block to different. Since the online information relating to the block sequence configuration data will be consistent with the PLC data. The same loading
the CPU and then monitor it? cannot be assigned to the individual program elements of the offline function is also used if you compile and load the "PLC > Objects" menu
block, the block status cannot be displayed. command in the SIMATIC Manager or highlight the chart folder and select
the "PLC > Load" function. You may not, however, highlight the block folder
or individual blocks and PLC > Load, as well as copy the blocks in the
"Block folder offline" in order to insert them into the "Block folder online".

30:504 There are no parameter and local variable names The description of the parameter and local variable names has a different This conflict first arises when you open a block and interface changes made
available because there is a time stamp conflict time stamp to the interface of the opened block. This is why the online have not been stored in the S7 user program offline and now the
between the interface of the block and the parameters and local variables are displayed as pseudosymbols without online block is being opened.
description of the parameter and local variable comments. Interface changes made offline have not been loaded into the CPU and now
names. the online block is being opened.
The interface of a function block or UDT has been changed and now the
associated instance data block or the data block derived from the UDT is
being opened.
An online block that already has a time stamp conflict is copied offline into
the S7 user program and now the offline block is being opened.

The cause for this can be an actual hardware fault, or an interrupt conflict In this case the customer can check whether the MPI LED lights on the
with another module. CP5611 during this time.
- If the LED does not light, the module could be defective or there is an
address conflict on the PCI bus (though unlikely).
- If the LED lights, then there is an interrupt conflict.
- NT Diagnostics ->Resources.
- Warning: with some modules you have to switch the computer off/on
after BIOS changes.
A possible remedy could also be to plug the CP5611 into a different PCI
slot.

30:53 Problems occurred during the automatic There are protected blocks in the selection list of the STL source to be Remake the selection list, but without the protected blocks. Press the Details
generation of STL sources. See Details! generated. button in the error message to obtain a Detailed List of the protected blocks.

Frei verwendbar Page 5 / 62

 STEP 7 Error Codes Version 01/2014

Error number: Text: Cause: Remedy:

30:202 The test that "strikes" should check whether the block is there online and Save the project under a different name.
offline.
30:473 This operation is not possible in this position. Programming error. Correct the code.
30:503 The type object of the block is not available, so the variable description is User error.
missing. The local symbols are displayed as pseudosymbols.

The block is available online in the automation system, but not offline in
the S7 user program.
The block has been copied from the automation system into an S7 user
program and now this S7 user program is to be opened where it did not
exist before.
A block is opened via "Available Users". In this case there is no S7 user
program linked with the automation system.
The associated function block of an instance data block to be opened
does not exist.
32:282 PG Resourcen Error, by program status of a longer In Step7 V5.0 SP2 with PLCSIM V4.0 under NT, project and block were In Step7 V5.0 SP2 with PLCSIM V4.0 do not open the project online, but
FB in PLCSIM opened online. This probably led to high internal use of resources. select the status function from the offline project. Setting the virtual memory
to 256MB does not help
33:11
33:384 The triggered action cannot be executed at this The communications module is probably already being operated with Please check the baud rate on the PG/PC via "Set PG/PC interface" and the
time. Check all other STEP 7 applications and exit other settings (e.g. with a different transmission rate). baud rate of the CPU configured.
them where necessary.
There might be other online functions active. Close any other active online functions (e.g. by closing the relevant
windows) and try again.
Attempt to run the firmware update of a CPU directly via STEP 7 on a Firmware update is only possible via flash card.
CPU.
33:496 The called function is not available in S7-DOS or in Deinstallation and reinstallation of STEP7
the CPU.
33:498 Internal error: Function '%1' not implemented. Delete metafiles
33:501 System error! Attempt to get online as normal user under WinNT.
33:511 System error! Mixed installation Manual deinstallation of STEP 7 and S7 options packages
NT: insufficient access rights. You must have at least main user access rights!
NT: main user access rights already assigned! Check that the domain user with the main user rights has also been
transferred into the Main User group on the local computer.
EPROM: Memory card is missing

Frei verwendbar Page 6 / 62

 STEP 7 Error Codes Version 01/2014

Error number: Text: Cause: Remedy:

The CP 1413 occupies the memory area 000D Can occur if the new connection to the database is not set up; for With laptops, disable the power-save mode. Under WinNT check the user
0000 to 000D FFFF (complete D segment) or example when closing and opening available users, S7db_close and rights (only with Administrator rights in V3.x).
000E 0000 to 000E FFFF (complete E segment). open is executed. Sometimes these do not match the current connection.
Normally MPI boards also use address areas in
the D segment (from 000D C000) meaning they
interfere with communication with the CP 1413.

Bus monitor Amprolyzer has been installed. Manual deinstallation of STEP 7 and S7 options packages according to
FAQ.
30:527 The interface of the multi instance call can only be If you click "Yes" in the dialog box, the system corrects the corresponding In case it is impossible to acknowledge the dialog box with "Yes" and, hence
updated, if the declaration of the multi instance is entry in the detailed variable view for you. to have the corresponding entry corrected by the system in the tag detail
valid in the tag declaration table. view, verify the system date of your PC. The system date of your PC has to
be set to the current date.
If you want to carry out the necessery changes yourself, proceed as follows:
1. Click "No" in the dialog box.
2. Eliminate the invalid multiple instance declaration by highlighting the
relevant line in the detailed variable view and selecting the pop-up context
menu command "Update Declarations".
3. Position the cursor on the block call in the code section and repeat the
function.

33:3100 When you have set the option "PG/PC is the only master on the bus" in
the dialog by "Set PG/PC Interface" and you will make an online
connection by "Display Accessible Notes" to the CP5412 A2, so you will
receive this error number if not a partner is connected on this modul.

33:8242 The EPROM driver cannot support the set PC + external prommer. Cause of error not yet known: probably a setup Under
programming interface on this computer problem where the Registry entries are not checked. HKEY_LOCAL_MACHINE\SOFTWARE\SIEMENS\SINEC\LOGDEVICES
there exist the directories MCDCENT and MCDPG. Where this is the case,
when using an external prommer, you must delete the MCDPG directory.
When using an internal prommer, you must remove the MCDCENT
directory.
Same message with a PG 720/740/760 Bad installation of STEP 7
33:8256 The external prommer is not connected to the The external prommer is not connected to the configured LPT interface. Connect the external prommer to the configured LPT.
corresponding port or the power supply has been
interrupted.

Frei verwendbar Page 7 / 62

 STEP 7 Error Codes Version 01/2014

Error number: Text: Cause: Remedy:

The power supply of the external prommer is interrupted. Reestablish the prommer's power supply.
LPT on PC faulty.
LPT incorrectly set. The LPT port must be set to EPP in the BIOS.
33:16399 System error by S7OTBL Server Client- When this message appears, the S7DOS server (S7otblsx.exe or The files S7otblsx.exe and/or S7otbxsx.exe are not available.
Communication. S7otbxsx.exe) doesn't want to start.
This server is a relatively conventional Exe that receives data from the S7otblsx.exe or S7otbxsx.exe are not in the search path? Is the server
line as proxy for programs that want to go online. It therefore has nothing normally in S7bin or in the system directory? The S7bin directory is
to do with databases or OLE/COM - yet. registered at Setup as CurrentWorkingDir of the applications. If this doesn't
work, then this message might also be displayed.
What is the purpose of the server. S7DOS recognizes four call types, 3 of Remainders in the memory after manual closing of the server. The server
which are asynchronous. So that the application can continue to run in allocates shared memory. When it starts and finds its memory still allocated,
the case of asynchronous calls and exported if necessary, there must be then it discontinues the startup or if it can't allocated the shared memory.
a proxy that constantly "listens" to the line and receives any data that The first case might occur if you close the server with the Task Manager and
arrives. If the PLC sends data directly, only then can you start to store the then continue without shutting down. The server needs approx. 400 KB
applications again from the swap-out file. shared memory. This should not be a problem nowadays.

The S7DOS-DLL attempts to start the server. If this does not work, then it In STEP 7 V5 and higher the server checks whether it has the same version
tries again and again. It has a timeout of 30 seconds in which time the as the DLL. If not, it doesn't start.
server should be up. If nothing happens during 30seconds - no refresh of
the application - then this is a clear indication of an unsuccessful server
start.
33:16418 The monitoring time for a STEP 7 frame was
exceeded.
33:16418 Timeout by wait of WM_ENDE_L7. The monitoring time for a STEP 7 telegram has expired.
Faulty parameterization of the access point on the MPI, L2 and H1 card or Correct the access point via "Set PG/PC interface" or PG/PC ONLINE card.
on the corresponding bus.
There is already a communications load at the moment due to a Repeat attempt to set up connection or check the S7 connections in the S7
configured S7 communication and therefore no ONLINE connection is project.
possible.
Cold or warm restart of communications partner. Repeat attempt to set up connection or check the power supply of the
communications partner.

Frei verwendbar Page 8 / 62

 STEP 7 Error Codes Version 01/2014

Error number: Text: Cause: Remedy:

33:16642 Online: Internal error - wrong configuration of Occurs when TeleService is in operation. Error image: a TeleService
telegram. connection is set up between a US-Robotics Sportster Voice 33.6 fax
modem (local; analog, external) and an M1 GSM module (system side).
With this constellation an online connection is set up in TeleService, the
available users are displayed, but if you double-click on, for example,
MPI=2 (direct), you get this error message. When you close this error
message, the block container is displayed and the remote connection to
the system is disconnected (295:20493).
Error described above also occurs with a connection between US-
Robotics Sportster Voice 33.6 fax modem (local; analog, external) and the
Penril Data Link 19.2 modem (system side, analog, external).
33:16647 The online connection was interrupted.
33:16654 Online: The connection was broken. Check the HW connection interrupted. Check the connecting cables and for correct connection to the network.
online connection and select the instance data
block again.
CPU has no power supply. Reestablish the power supply.
Power supply failure.
S7-300: Locate problem by replacing modules. One possible cause could be that the
Group error LED (SF) lights. bus is unstable or the interface on the module is defective.
Interface is already occupied by another PG connection. Check whether a remote connection is set up.
Power-save Management is active in the computer. Go online again and set up a new connection.
If the behavior occurs again after a short time, then deactivate the Power-
save Management.
Warning: in some computers this can only be done via the BIOS SETUP.
33:16656 The error occurs frequently if a station address is The error occurs frequently if an MPI address is set, which deviates from Check the connecting cables and for correct connection of the network.
set which differs from the actual network the actual network configuration. The error can occur in particular with the
configuration following operations:
A block has been copied from an S7 program that is directly under a Check the PLC for power failure.
project and inserted in the block container of an S7 program that is under
a module.

Frei verwendbar Page 9 / 62

 STEP 7 Error Codes Version 01/2014

Error number: Text: Cause: Remedy:

For setting up the online connection it is no longer the MPI address in the Check whether when configuring the hardware that an MPI address has
Properties of the S7 program that is valid, but the configured MPI address been configured for the module and stored offline, under which no user
of the module. exists as yet. In this case open the window for configuring the hardware.
Then either adapt the MPI address in the module (by loading the
configuration (see HW Config) with the changed MPI address) or change the
MPI address configured offline to an existing address and save the change
offline.
A block has been opened in the "Available Users" window and then an Check whether the configured MPI address in the project actually
attempt was made to save the block in a project. corresponds to the loaded MPI configuration of the MPI network.
For setting up the online connection it is no longer the MPI address from Check whether the MPI address is available in the MPI network.
the "Available Users" window that is valid, but the MPI address configured
in the project.
In the "Available Users" window a user has been marked and the "Monitor Check the "Group error message" (SF) LED of the module (CPU).
and control variable" function called. Then an attempt was made to save
the variable, which is only possible offline in a project.
For setting up the online connection it is no longer the MPI address from Check the configuration in the SIMATIC Manager and the network
the "Available Users" window that is valid, but the MPI address configured addresses set. (Network addresses must not be assigned twice.)
in the project.
Reset the CPU and CP, then reload the configuration and under NCM read
out the address so that you can access the S7 controller online with the CP
1413.
The block container of a CPU with several DP interfaces cannot be 1. Check the settings in the SIMATIC Manager: By clicking on "Extras >
opened over the DP interface in the online view. This online view is Settings > Register: View" the option "Enable MPI address to be modified"
however possible over the MPI/DP interface. A online connection can be should be active.
built up with the function "Available station" via the DP-interface of the 2. Switch in the Simatic manager to online view and mark with the cursor the
CPU. S7 program. Right-click, load the object properties and choose the register
"Addresses: Module". Select the correct PROFIBUS address, with which the
PG is connected via the DP-interface of the CPU.
3. We recommend to notify STEP 7 of the location change of the PGs, if
you have disconnected and reconnect the PC from the subnet to an other
with your networked STEP 7 project. This can be executed under
"Targetsystem > Assign PG/PC".

Frei verwendbar Page 10 / 62

 STEP 7 Error Codes Version 01/2014

Error number: Text: Cause: Remedy:

33:16662 Online: No connection. Node does not accept the The partner is neither a CPU nor a CP. Check that the configuration and the actual hardware configuration match.
connection setup. Check the online connection and
select the instance data block again.

The partner is not a module in the PLC. Check the addresses given.
The partner is a different PG or an external device. Using the "Module Status" function check whether the selected partner is a
CPU. Check whether its communications partner is slotted in the place
configured (rack/slot).
The partner cannot set up any more connections. Close any further connections to the partner.
Connection setup via DP interface without the CPU retaining it's relevant First configure the CPU also as DP master and load the SDBs onto the
SDBs. CPU.
33:16914 Online: Station not online. Power supply of the S7 is switched off. Check whether the CPU is switched on.
Connecting cable is not plugged in or is defective. Check that the MPI cable is plugged in.
Check the cable for breaks.
Configured bus parameters do not match the S7 system. Check the following bus parameters: Baud Rate, Highest User Address
(these parameters must be set correctly on all stations in the network) and
Timeout.
In the Control Panel call "Set PG/PC interface" to correct the bus
parameters.
Restart MS-Windows and check the error messages of the drivers.
Incorrect access point is selected. Select correct access point.
PG: hardware fault Send PG to PG service shop to have the interface checked.
33:16917 The function is not supported by the selected Occurs if you set up an ONLINE connection via a CP5412 A2 with the Incorrect message, the connection is set up as soon as a user is connected.
hardware. option "PC is the only master" (in the "Set PG/PC interface" tool) via
"Available Users" and there is no user connected to the CP 5412 A2.
33:16944 Online: It is not found an active contact. User not connected to the bus. Check the connecting cables and the connection to the network. Check the
PLC for power failure.
On the PC/TS adapter the LED for correct power supply lights. This LED Check the connection and whether the 24V and 5V power supplies reach
lights if only the 24V supply is connect and the 5V supply is missing. The the PC/TS adapter.
PC/TS adapter however needs the 24V and the 5V power supply through
the PLC.
The TS adapter is set to the wrong transmission rate on the MPI side. Correct the network transmission rate under Set PG/PC interface -> MPI.
The PC/TS adapter hardware is damaged. Replace the TS adapter or send it in for repair.
The wrong driver is preset under "Set PG/PC interface". Preset the correct driver for the TS adapter.
33:17072 Online: no hardware is found. No driver selected or incorrect address area of the MPI interface PG/PC interface - MPI Properties
->Select or add driver

Frei verwendbar Page 11 / 62

 STEP 7 Error Codes Version 01/2014

Error number: Text: Cause: Remedy:

With Windows NT, check that the PC has an MPI-ISA card and not a Can be determined in the BIOS (PCI).
CP5611.
33:17074 ONLINE: driver is wrong configured or not valid MPI-ISA card: installation of an PG/PC interface - MPI Properties
parameter in the registry STEP7 version (also upgrade and corrections) ->Delete all unnecessary drivers
-Win95 hardware recognition has been run ->Re-insert and parameterize drivers
-other drivers (also CP...) tried out
-another card installed in the PG/PC
-sometimes hardware is defective
33:17075 All stations on this subnet must have the same With this message there is usually an interrupt that is double-occupied. Attempt to set a different interrupt once.
value for the transmission rate. The interrupt may
not be assigned for other hardware components.
The MPI addresses in the network must be unique,
meaning each address may only be assigned
once. The local Station address must also not be
greater than the highest station address in the
programmable controller.

Occurs with SCENIC PRO M6, Onboard Controller occupies many IRQs Deactivate primary and secondary controllers in the BIOS.

WIN 95 does not clearly recognize the interrupt occupied through the Select a different interrupt for MPI card.
3Com-Etherlink 3 (ISA) 3c0509b. This can lead to interrupt sources being
double-occupied.
The reason for this can be an actual fault in the hardware, or an interrupt In this case the customer can check whether the MPI LED on the CP5611
conflict with another module. lights during this time.
-If the LED does not light, the module might be defective or there is an
address conflict on the PCI bus (not very likely).
-If the LED lights, then there is an interrupt conflict.
-NT diagnostics ->Resources.
-Warning: with some modules it is necessary to switch the computer
off/on after BIOS changes
Under circumstances, one remedy is to plug the CP5611 into a different
PCI slot.

33:17077 Online: The setting local address of participant is The TS adapter had the same MPI address (0) as another user in the MPI Via the "Parameterize Adapter" function, assign to the TS adapter an MPI
assigned network. address that has not yet been assigned and save it. The TS adapter has
MPI address 0 as works default setting.

Frei verwendbar Page 12 / 62

 STEP 7 Error Codes Version 01/2014

Error number: Text: Cause: Remedy:

33:17088 Online: The selected communication driver can not In V2.1 the PG/PC interface hardware is set to "none" Select card
be loaded. File is not found.
Possibly wrong or no driver selected with Windows NT. Install driver or select card.
33:17090 Logical device is not in the registry.
The LogDev is in the Registry under the following key: This sequence of drivers should be of one mold, i.e. from the same
HKEY_LOCAL_MACHINE\SOFTWARE\SIEMENS\SINEC\LogName\S7O generation.
NLINE\LogDevice A mixture of drivers from different STEP7 releases is fatal!

No, that would be too simple.

As usual for such a communication, each layer is implemented as an
application layer. There is therefore at least one driver for Layer 7
(s7otbldx,s7otblsx), one for Layer 4 (s7otransx) and one for Layer 2
(s7ospc2). The drivers for Layer 2 still run in the Ring 0 of Windows, the
remaining drivers in the Ring 3. There is also a central program that
manages the transition from Ring 3 to Ring 0 including the transferring
data to and fro (s7onlinx).
With the CP 5611: driver warped in the Registry. Deinstall and then reinstall under "Set PG/PC interface".
"PG/PC is the only master on the bus" is not activated (not checked) Active "PG/PC is the only master on the bus".
although the PG/PC is the only master.
33:17104 The version of the adapter connected does not Probably the versions of the drivers and the PC Adapter or PC/MPI card Check in the PG/PC interface whether a TS adapter is addressed with the
support the bus parameters set or it is not are incompatible. PC Adapter driver. Also check the settings of your PG and the PC Adapter
connected to the adapter type assigned to it in the (Informations you will find in the FAQ !10420976!).
program "Setting the PG/PC Interface".
33:17106 Communication to the PC/TS adapter is faulty. The PC/MPI cable is plugged into a module that provides no power Connect external power supply.
supply.
The connection between PC adapter and CPU is defective. Check hardware. Warning: PC adapter needs direct connection to the CPU
since no external power supply is possible.
Connection between PC adapter and PC is defective. Check connector pin assignments.
The TS adapter is not yet set under "Set PG/PC interface". Enter the TS adapter correctly under Step7 Options --> Set PG/PC interface.
Also pay attention to the properties Direct Connection/Modem Connection.

33:17108 Exit the application which is currently using the Another application already occupies the serial interface or faulty setting With NT check in the Control Panel that STANDARD is not set for
required port (COM port or USB) of COM-IF upon display under NT. Addresses and INT in the settings of the COM interfaces under "Advanced".
If not, remove COM IF and then restart the PC. Now COM IF should be
newly installed with the STANDARD option.

Frei verwendbar Page 13 / 62

 STEP 7 Error Codes Version 01/2014

Error number: Text: Cause: Remedy:

33:17109 The driver for the required port is currently being The item Direct Connection has been selected in the SIMATIC Manager Select the item Modem Connection under Options --> Set PG/PC interface.
used by another application. Another interface under Options --> Set PG/PC interface.
parameter assignment configuration may also be
in use.
After interruption of a TS connection the serial driver is still reserved by Close TeleService and STEP 7, then restart STEP 7 first followed by
STEP 7. TeleService.
33:17110 The interface TS adapter is set for a modem After dialing into a remote system via TeleService (connection is set up), Acknowledge error message with OK and simply reselect PLC --> Display
connection and there is no remote connection to a the TeleService window was minimized and PLC --> Display Available Available Users. The error should then no longer appear and the available
TS adapter. Users was selected and then this error message was displayed. The users are displayed as long as the modem connection is still set up.
reason is probably a bad telephone line or a connection that is too slow.

33:33285 It is a copied object variant available. Please set up the connection by closing all the S7 applications and then
restarting them.
33:33540 Message from the module. Too few resources Message from the PLC when reading block when, for example, two Start Trace (Level=0x11000000)
available. upload processes are triggered simultaneously by 2 PG.
33:33794 Illegal request of service The CFB in the communications partner is in the wrong state. Check the block call in the user program of the communications partner.

PRINT block: Paper out. Check the printer when printing via the module.
The program instance in the communications partner is in the wrong state Set the key switch to RUN or RUN-P before starting the module.
(cf. START, STOP, RESUME block).
When implementing a CPU with DP interfacing, you might get the Download the SDBs and restart manually.
following situation: a user is not available on the DP bus, the CPU
remains about 30 seconds in startup and the RUN LED blinks. Then the
CPU goes into RUN (as long as no I/O access to the missing I/Os puts
the CPU into STOP). This is obviously a TIMEOUT effect, because the
CPU doesn't acknowledge the service in the relevant time.

33:34562 The service requested is not supported by the The service requested is not supported by the module. Note the restrictions of the CPU used (menu command PLC > Module
module. status, Performance Data tab or look up the performance data in the
documentation for the module used).
Use a more powerful module.
The object addressed does not exist on the module. Check the addressing of the object.

Frei verwendbar Page 14 / 62

 STEP 7 Error Codes Version 01/2014

Error number: Text: Cause: Remedy:

33:42418 Message comes when executing the function The module on which you wish to execute this function does not yet support
RAM TO ROM: The service requested is this function. Note the restrictions of the CPU used (menu command PLC >
not supported by the module. Module status, Performance Data tab or look up the performance data in the
documentation for the module used).
Use a more powerful module.
The addressed object does not exist on the module. Check the addressing of the object.
33:53315 D043: Data Error: The references order is not When controlling by monitoring variables, it might happen that when too Acknowledge the message and reduce the frequency of the control jobs.
available. many control jobs are sent to the CPU, the CPU rejects them because its
buffer is too full.
33:53343
33:53346 Resources error (D062), job list is too full The variable table (VAT) can no longer be opened although the table Please switch off the power supply of your CPU and then on again. Delete
could be opened previously without any problems using the same jobs no longer required (for example, deleting breakpoints, terminating the
program and with the same CPU. Probably the VAT concerned has not function "Monitoring/Modifying Variables", terminating the function "Program
be closed correctly in the CPU. Status"). You will then be able to go online again with the VAT.

33:53347 (D063) Resources error: the trigger event is It is no longer possible to monitor a block. This behavior is triggered by 1. Unplug the online cable of the CPU and wait at least 1 minute. It is not
occupied. irregular termination of the process in the operating system. enough to unplug the CPU just briefly.
2. Shut down your programming device and wait 1 minute before switching it
on again. A simple reboot is not always sufficient.
Message from the module. This function cannot be executed at the Delete the jobs that you no longer need (e.g. delete stop points, close the
moment, because the resource required is already occupied. There are "Monitor/control variables" function, close the "Program Status" function).
also too many test functions activated at the same time and the resources
available on the module are exhausted.
33:53772 Note the restrictions of the module being used. Message from a module. Note the restrictions of the module implemented. (See also in the Message
from Modules area.)
33:53790 The module to be assigned parameters is currently Remedy: reset the CP via Online HW Config and Download HW Config.
busy assigning parameters to subordinate devices. Repeat the module download when all stations and field devices on the bus
It was been by the modules: 416-2DP + CP443-5 are started up and in operation. To ensure that the module to be
Extended downloaded temporarily cannot assign parameters to subordinate devices,
remove the interconnecting bus cable from the DP interface for the duration
of the downloading process.

In the case of an IM 467, you must do a POWER OFF/ON. This resets the
IM and the HW Configuration can now be downloaded.
33:53797 The distributed I/O system data block is structured A diagnostics address outside the address area has been specified. (For Change the diagnostics address.
incorrectly. example, Win AC lite was installed.)

Frei verwendbar Page 15 / 62

 STEP 7 Error Codes Version 01/2014

Error number: Text: Cause: Remedy:

33:53798 A mismatched CPU type or an internal structural When evaluating the blocks, an incompatible CPU type or internal Please check whether the type (MLFB) of the CPU that you have configured
error has been detected during block analysis. structure error was detected. matches the CPU type onto which you are loading.
Match the CPU types and reload.
If this is not the case, nevertheless regenerate the configuration data
(blocks) and load the data onto the CPU. Please check that you are using
the latest version of the configuration software (with the latest Service Pack).

33:53824 D204: The rules of coordinations were broken. When attempting to load the system data, there was still a variable table Close the variable table and retransfer the system data.
open online.
33:59906 The communication software (S7DOS) and the The customer has a STEP 7 V5+SP1 + new PDM and a CP 443-5 Ext > Upgrade CP 443-5 to a version >V2.7.
interface module (CP) have not the same protocol. V2.7. The new protocol RPC 7 that is used for data record routing
between the CP and S7DOS. Unfortunately versions up to version V2.7 of
the CP do not have this function.
The user is implementing the right components STEP 7 V5 + SP2 + PDM, Check the configuration and replace the CP implemented with a different CP
but has a CP that does not include the DSGW. that includes this function.
34:11 Compiler information: handle not valid. When monitoring an empty network with the LAD/FBD/STL editor. Delete empty network.
34:21 Compiler information: element not found. The element could not be found in the referenced database. Check the spelling of your search key and your database reference.
34:38 Compiler information: Compiler error
34:39 You have attempted to rename a variable, but the name is already being
used.
34:152 Reference data could not be generated. Error in the database. The project can be correct+D191ed with "Save As with reorganization".
34:168 The moduls in the comand structure are protected One or more direct or indirect reference module is know how protected Please deactivate the option "Include reference blocks" in the menue
and can not be generated. and can not be generated "Generate source ...". You have to create the list of the moduls via manual
without the protected moduls.
34:173 At least one symbol assignment has changed If you copy a symbolically addressed block from the library of an S7 1. Please make sure that the source is generated with the setting "absolute".
project into another project and after you open the block. 2. Copy the source into the new project; the project can be configured as
In the original project you generate an STL source from the block. symbolically addressed.
3. Now compile the source and so generate the block.
After that you can adapt the symbols as required without the behavior
described above occurring.

34:178 Block call invalid because interface was changed With Step7 V5.0 the instance DB of the DB type is entered in the symbol Enter the instance DB of the FB type in the symbol list.
in the meantime. list for an FB call. This is no longer permitted with Step7 V5.0. In this case
the "Update Call" function doesn't work.

Frei verwendbar Page 16 / 62

 STEP 7 Error Codes Version 01/2014

Error number: Text: Cause: Remedy:

34:4321 Error in column 1, distribute the program in little
blocks.
34:4355 F Ze %2!06d! Sp %3!03d!: No PLC type The block called is not available. The block is to be compiled before the call.
description found for called or addressed block
%4.
In the case of SFB/SFC calls, please copy into your offline database with the
SIMATIC Manager (block container).
If the SFB/SFC is not available on the CPU addressed, then it should not be
called!
34:4461 The block %4 that was called/used is protected or You are trying to generate a KNOW_HOW_PROTECT block into an STL The block named is protected and cannot be generated into an STL source.
created by S7-GRAPH and cannot be generated. source.

34:4469 The declaration range of your formal parameter It is not allowed, that an OUT variable of the calling function block is We recommend first saving the data temporarily on a static variable. In a
does not match the declaration range of the actual parameterized with the IN variable of the function block called. further network this static variable is parameterized with the IN variable of
parameter, for example, no OUTPUT paramater the FB called. The output variable of the higher-level block, the static
from the actual end can be assigned to an INPUT variable and the input variable of the lower-level block must be of the same
parameter from the formal end. data type.
34:4485 The parameter assignments can be specified in any order in the ASCII If you have entered comments for parameters, then when assigning the
source. The comments, however, are stored separately from the actual parameters, please keep to the order in which the parameters of the block
online block in the order entered. Thus, when exchanging parameters in called are declared.
the source, the order of comments might then be wrong. When the block
is opened, the comments are then assigned incorrectly. In the worst case
comments might even be lost. The following comments in the network are
also affected, even when the exchanged parameters are not even
commented.
Message appears when opening a VAT. The directory S7USS is missing Reinstall STEP 7.
in the SIEMENS\STEP7 directory.
88:47 Unable to reach the module %1 by means of the Programming device is connected to the MPI interface of the CPU. Check whether the CPU is routing-compatible. If Not, then please set your
online interface that is set. MPI driver to PROFIBUS and connect up with the PROFIBUS DP. Then
repeat the desired function.
256:24 Function open Environment is not implemetiert Multiple start of the SIMATIC Manager In the STEP7_V2/S7met directory delete the files S7CacheA.dat and
S7ser.dat with Win95 Explorer. The ending .dat can be left out; depending
on the options package, there is also an S7CacheB -E.dat
256:26 Internal OLE Error. Not enough space on the hard disk, the database cannot be started. Create space on the hard disk and set user-defined virtual memory.
Wrong DLL in Windows/System and/or wrong Registry entry. Start program editor via Explorer and evaluate error message.

Frei verwendbar Page 17 / 62

 STEP 7 Error Codes Version 01/2014

Error number: Text: Cause: Remedy:

If the following message appears: "The file S7HRVERX.DLL is linked with
the missing export S7OTBLDX.DLL: s7_set_password.", then check
whether the file 'S7OTBLDX.DLL' is in the Windows system directory. When
implementing STEP 7 V4.02, you must delete this file from the Windows
system directory.
If the following message appears: "The file S7KAFAPX is linked with the
missing export OT5050R.DLL:4224", check whether the OT5050R 2x is on
the computer. Rename all except those that are in the S7BIN directory.

With V3.1 when printing With V3.1 copy block comment into network comment.
WIN 95: the OLE was not installed properly when installing WINDOWS. Delete Windows directory and then reinstall WINDOWS.

Message appears when opening a VAT. Reinstall STEP 7.

The S7USS directory is missing in the directory SIEMENS\STEP7.
256:30 SCL: Programming of S7 moduls. The object was Error occurs when you export an SCL source, delete it in the SIMATIC Delete the block contained in the source in the SIMATIC Manager first and
deleted. Manager and then import it again and compile it. only then compile.
256:31 This object was not found. An object that fulfills the criteria specified is not available. The function You can reorganize the addresses with key combination
triggered cannot be executed. The assignments in the OFFLINE <CTRL>+<ALT>+<F11>.
database with regard to the HW configuration are no longer consistent.

256:32 Not valid objects. A link has obviously been lost. In V2.1 projects the solution is to use "Save As with Reorganization"
256:35 Internal system error is not repairable.
256:49 The quoted entry is not in the registry by Windows Error occurred when downloading SDBs into a remote CPU via Set up the connection over and over again and wait for a better line quality.
or contains a not valid value. TeleService. The cause here was a bad telephone line connection Try to get a higher transmission rate (<- indicator for better line quality at
(analog) (in the USA). After several attempts to set up an ONLINE the time of connection set up).
connection, the SDBs could be transferred without this error message. An
attempt was also made to achieve a higher transmission rate with the
ONLINE connection.
256:53 Internal error: Not valid pointer. In PLCSIM an attempt was made to load the last simulation in PLCSIM Create a new simulation via Simulation -> New PLC. The next time you run
via the menu item Simulation -> Last Simulation. Since the old project the last simulation the latest new simulation will be loaded without error
data (e.g. also block interfaces) has perhaps changed in the meantime, message.
some of the data of the simulation originally created no longer matches
the current project.
256:56 There is an internal error in the system. Project might be damaged. Terminate application and restart.

If the error re-occurs, restart Windows.

Frei verwendbar Page 18 / 62

 STEP 7 Error Codes Version 01/2014

Error number: Text: Cause: Remedy:

STEP 7 V5.x: There is an internal error in the Send project in to the Technical SIMATIC Customer Support.
system.
256:57 There is an not repairable error in the system ProjID.pro might possibly exist when dearchiving. Copy/move ProjID.pro.
during the programming. The function can not be
implemented.
256:62 Not repairable internal system error in refer to the Project might be damaged. Computer might have crashed. Save as ... with consistency check or recreate the project.
file "symlist.dbf".
256:63 Please see the remedies by errror number 258:15.
256:68 The object ... cannot be edited because it is This message appears when you start the "File > Save as..." function Before reorganizing, close all the applications in the project.
currently opened by another application or another together with the "With reorganization (slowly)" option if there are still
user. applications open (e.g. Symbol Table) in the project which is being
reorganized.
256:85 SIMATIC Manager expects formatted names. Enter correct name with VAT<digit>.
256:89 The version 513 of the objekt XR00001 is not Legacy from V2 in XUTIL catalog Delete the XUTIL directory in the project path
compatible in refer to the installed software.
256:92 The data can only be read. This might be data, for example, from a project or library. The cause Make sure that you have the appropriate rights to access the drive or
might be that there are no write rights for the directory or drive in which directory where the data is located.
the data are located. Remedy:
Using a virus scanner in Runtime mode can lead to faults. Do the virus
scanning offline (i.e. at times when you are not working on your STEP 7
project) or disable the virus scanner on your computer.
The data is being processed by a different application or by a different Save the modifications made in a different application and make sure that
user. no other user processes this data at the time in question.
The data are read-only. You have copied a data backup of a project from a CD onto your hard 1. Mark the project in the explorer, where is saved in the folder and click on
disk and now cannot open this project. The reason for this is that all the the right mouse botton (example: D:\...\Siemens\Step7\S7Proj\<Project>).
files of the project have the attribute "write-protected" set. There are 2. Open in the context menu the "Properties" and select "Security".
various ways of removing the write-protection from files. One such is 3. Here you can allow the "Read" and other functions by "Permissions for
described below. Administrators".
4. Click after on "Apply" and "OK".

256:93 The rights of write is missing in the directory. The directory in which the S7P file is located is write-protected. Remove the write-protection from all directories that have to do with the
project.
Not enough space on the disk < 100 bytes
If STEP 7 V4.x is concerned, then it might be that a file has not been Delete S7APROMX.TXT in the root directory of the project.
deleted, which still specifies that the project is still on a write-protected
drive.

Frei verwendbar Page 19 / 62

 STEP 7 Error Codes Version 01/2014

Error number: Text: Cause: Remedy:

256:94 Problems with the offline folder. This message may be due to the fact that the project has been First of all check the versions of all the options packages installed on your
dearchived on a computer and edited with an options package whose computer which are required for editing the project. You may need to install
version is no longer compatible with the current STEP 7 version. one or other update (service pack) or upgrade (new version).
You can find information about compatibility with SIMATIC software
packages for your STEP 7 version in Entry ID 18734363.
Then make a copy of your project with "File > Save as..." and the option
"With reorganization (slow)".
256:100 Authorization of STEP 7 is not found. No Basic Authorization installed. Error occurs when attempting to start an Install Basic Authorization
installed options package. Probably STEP 7 is only authorized as Mini.

256:104 Authorization of optional package is not found. No user rights (authorization) found for the options software on drive C:. Install the options authorization from the authorization floppy disk included in
the delivery package. If you have lost the authorization (e.g. through a fault
on the hard disk), you can install the emergency authorization to be able
continue working for a limited period of time. You must then procure a
replacement for the lost authorization during this limited time.

WIN NT: insufficient access rights. To operate S7 software under NT you need at least main user rights.
256:107 The object specified could not be copied. There might not be enough Press the "Yes" button to continue the copy or save operation for the
space left on the data medium. Possibly the target directory is remaining objects. The copied objects might possibly be incomplete or
momentarily blocked by another application. defective in the new environment. If you press the "No" button, the copy or
save operation is aborted.
Possibly another STEP 7 application has opened the object to be copied
and has thus blocked it. In this case, close all other STEP 7 applications
and trigger the process again.
256:111 Access denied Your have repeatedly loaded a program in the SPS and now it is not Start the service "Server" in the control panel.
possible to load the program again, also not after a new start.
256:119 There is no authorization for STEP 7. To operate No authorization installed or the path in which the STEP 7 project is Install the authorization or shorten the project path as appropriate.
this optional package, you require the authorization located is too long.
for "STEP 7 V4.x".
257:5 One or more objects of a type cannot be The process variable server cannot be started. Installation problem with Please check the version of the software package installed against the
represented. Unable to load the server STEP 7. There must not be any incompatible version of WinCC installed compatibility list. This is located in your STEP 7 directory as the file
's7uvpomx.dll' for _S7UV_LIST_CT-objects. Make on the computer. S7KOMP_x.PDF. x stands for the language:
sure that the required optional packages are a=German b=English, c=French, d=Spanish, e=Italian.
installed.
Mixed installation, a V4.0 or V4.01 was installed before the installation Deinstall STEP 7 manually and then reinstall it.
STEP 7 V5.x. See FAQ 189025

Frei verwendbar Page 20 / 62

 STEP 7 Error Codes Version 01/2014

Error number: Text: Cause: Remedy:

Paths in Autoexec.bat are not set. Edit Autoexec.bat so that the paths are set or not overwritten, as the case
may be.
One or more objects of a type cannot be A file required by STEP 7 has not been found. Probably the project Reinstall the DVA_S7 package.
represented. contains objects for which you need an options package that is not
Unable to load the server 's7hkdmax.dll' for installed to process them.
_S7H_DP_ETCR_INTGR_414_2_ROCF_CT-
objects.
Make sure that the required optional packages are
installed.
One or more objects of a type cannot be There is no authorization permitting you to integrate SIMATIC PDM in You must install the options authorization for integrating SIMATIC PDM in
represented. STEP 7. This authorization is an options authorization which has to be STEP 7.
Unable to load the server 'p7spumax.dll' for installed in addition to the basic authorization of SIMATIC PDM.
_SIPROM_CONTAINER_CT-objects.
Make sure that the required optional packages are
installed.
One or more objects of a type cannot be The S7 project to be opened contains an object that has been created Reinstall the options package Technological Hierarchies.
represented. with the options package Technological Hierarchies. This package is not
Unable to load the server 's7jthomx.dll' for installed or has not been recognized properly after an over-installation of
_AUT_TH_AT-objects. STEP 7.
Make sure that the required optional packages are
installed.
One or more objects of a type cannot be Toolbox of SINUMERIK 840D is missing or is badly installed. Reinstall the toolbox for SINUMERIK 840 D.
represented.
Unable to load the server 's7hk31ax.dll' for
_S7H_PLC315_2DPD_Modul_CT-objects.
Make sure that the required optional packages are
installed.
The S7 project is opened with STEP 7 V5.x and the SINUMERIK 840D The SINUMERIK 840 D V4.x toolbox is incompatible with STEP 7 V5.
toolbox is installed with version under V5. Please install the toolbox for SINUMERIK 840 D V5.
One or more objects of a type cannot be Your project contains objects that have been created with the options Please install the options packages concerned; in this case C7_626P.
represented. package C7_626P, but this options package is now not installed.
Unable to load the server S7HK31AX.DLL for
_S7H_6ES7_315_1AF03_0AB0_CT - objects.
Make sure that the required optional packages are
installed.

Frei verwendbar Page 21 / 62

 STEP 7 Error Codes Version 01/2014

Error number: Text: Cause: Remedy:

The message appears with each project you open, even if it doesn't In STEP 7 you have installed the options package C7_626P with an older
contain a C7_626P object. version than the version of STEP 7. Please upgrade the package C7_626P.

One or more objects of a type cannot be The NCM package is not installed and the S7 project contains Please install the options packages concerned; in this case the NCM
represented.Unable to load the server 's7wb53ax corresponding objects. options package.
dll' for _S7H_6GK7_443_1BX00_0Xe_CT-objects.
Make sure that the required optional packages are
installed.

One or more objects of a type cannot be Toolbox of SINUMERIK 810 is missing or badly installed. Reinstall the toolbox for SINUMERIK 810.
represented.Unable to load the server
S7HK31AX.DLL for
_S7H_PLC314_Modul_CT_objects. Make sure
that the required optional packages are installed.

One or more objects of a type cannot be The error is probably caused by the permanent upgrading of STEP 7. Deinstall STEP 7 manually and then reinstall it.
represented.Unable to load the server There are several older versions of STEP 7 one on top of the other.
"s7hsl7ax.dll" for
_S7H_DP_PA_LINK_1_ETER_CT-objects. Make
sure that the required optional packages are
installed.
One or more objects of a type cannot be
represented.Unable to load the server
"p7ss357x.dll" for
_P7_FM357_6ES7_4AH00_0AE0_CT-objects.
Make sure that the required optional packages are
installed.
One or more objects of a type cannot be
represented. Unable to load the server
S7HK31AX.DLL for _P7_PUSTCH_CPU
314_CT_objects. Make sure that the required
optional packages are installed.

Frei verwendbar Page 22 / 62

 STEP 7 Error Codes Version 01/2014

Error number: Text: Cause: Remedy:

One or more objects of a type cannot be Either the tool MCU-Pit is not installed at all (product of Install the tool MCU-Pit V4.10. Also, in the directory Drive:\
represented.Unable to load the server Simodrive/Sinumerik) or the tool MCU-Pit V4.x has been installed in Siemens\Step7\S7MET you must change the name of the file
S7HK31AX.DLL for _P7_POSTECH_CPU combination with STEP 7 V5.x. Warning: only "p7skmcux.mv5" to "p7skmcux.met". Then you must delete all the remaining
314_CT_objects. Make sure that the required the version V4.10 of MCU-Pit is released for STEP 7 V5.x. *.DAT files in this directory and restart STEP 7 (so that the metafiles can be
optional packages are installed. recompiled).
257:7 Type of object is not declared A file needed by STEP 7 has not been found. Possibly the project
contains objects for which you need an options package that is not
installed to process them.
257:8 One or more objects of a type (%1!X!) cannot be There is an object in the project that has to be parameterized with an S7 Install the missing S7 options package.
represented. Make sure that the required optional options package. This options package is not installed.
packages are installed.
One or more objects of a type (%1!X!) cannot be There is an object in the project that has to be parameterized with an S7 Please import the type file for the sensor module IF961-ENC4 configured on
represented. Make sure that the required optional options package. This options package is not installed. the FM456.
packages are installed.
257:9 The project contains objects of the optional The project probably contains objects for which you need an options Please install the options package concerned.
package 'xxxx' that cannot be processed because package that is not installed to process them, or a newer version of the
the optional package is not installed or an outdated options package.
version is installed.
In the SIMATIC Manager create a copy of your project (with File > Save
as..., Option "With Reorganization (slow)"). Here, the objects that belong to
non-installed options packages are deleted in the target project. This error
message will then no longer be issued when working with the copy of the
project.
257:24 creat environment is not implemented. SIMATIC Manager has been started double or computer has crashed. With V2.x, delete the *.dat files in the S7met directory. In any case, procure
the latest correction version.
257:26 Not repairable internal system error. The link could Message appears when you trigger the function "Display Reference Use the function "Save as" together with the option "With Reorganization
not be inserted. Data". Links are distorted in the project. (slowly)".
Message also appears when forwarding a project in conjunction with the
symbol table.
257:79 The project or parts of it are currently being edited This message appears when you start the "File > Reorganize..." function Before reorganizing, close all the applications in the project.
by another application. if there is still an application open (e.g. Symbol Table) in the project which
is being reorganized.

Frei verwendbar Page 23 / 62

 STEP 7 Error Codes Version 01/2014

Error number: Text: Cause: Remedy:

257:90 The project '%1' contains errors in the internal data Project data damage by a crash/power failure on the computer. 1. Close all the STEP 7 applications except the SIMATIC Manager.
structure. With the "Details" button you can receive more information on the error, if 2. With the menu command "File > Save as (with reorganization (slow)) "
available. create a of the project which you can then continue to work with. Because of
the faults in the existing project, this copy might not contain all the data of
the original project.
257:94 Open of project: <Date and Time> Inconsistent project. 1. Close all the STEP 7 applications except the SIMATIC Manager.
S7fupos: Internal error during save of data of Application FM 453 has registered errors when saving the machine DBs. 2. With the menu command "File > Save as (with reorganization (slow)) "
server S7ombstx.dll. A possible cause is the shortage of storage space on the computer. create a of the project which you can then continue to work with. Because of
the faults in the existing project, this copy might not contain all the data of
the original project.
258:1 Unable to open project data %1. IDB defined as GDB in the symbol table. Define IDB correctly. In the case of V2.1, use Save as… for the project.
258:17 The directory C:\Siemens\STEP7\S7proj\temp The temporary SDBDATA directory created must have been destroyed by In the directory [DRIVE]:\Siemens\STEP7\S7TEMP delete the directory
exist already. the crash. SDBDATA including subdirectories.
258:20 After archiving call File > Title Field and note the Title Field specifications.
After dearchiving you can reestablish these specifications manually via File
> Title Field.
258:15 Some files or data blocks are write-protected and, therefore, the data can Ensure that you are authorized to access the drive or folder where the data
only be accessed on a read-only basis. This may be due to the fact that is located.
write access does not exist for the directory or drive where this data is
located, or the block may have been saved as write-protected for
reference purposes.
There are still blocks (FCs, FBs, DBs and/or OBs) open and, as a result, Close any STEP 7 (and WinCC flex) editors which are still open. We also
the associated projects and directories cannot be deleted. advise you to close STEP 7 (and WinCC flex). Go to the Task Manager to
check whether there are still any S7 processes in operation and, if so, close
them. Then start STEP 7 again and delete the project via "File > Delete".

If the remedies under the last above points do not help, close STEP 7 again
and delete the project in the Explorer. You can find the folder for the saved
project in Fig. 01 under
"<Drive>\Program Files\Siemens\Step7\S7Proj\<Project>
It is possible that the data areas of the HW Config, NetPro, Symbol Table or
other STEP 7 components have not been released again completely after
being closed. You should be able to delete the projects again after rebooting
your PC.

Frei verwendbar Page 24 / 62

 STEP 7 Error Codes Version 01/2014

Error number: Text: Cause: Remedy:

If the last remedy point does not help either and the project which you Otherwise, we recommend that you uninstall STEP 7 completely beforehand
wish to delete is still present under the menu commands "File > Open..." and also delete the directories in the Registry Editor. Follow the procedure
and "File > Delete...", some of the files in the SIMATIC software may be precisely as described in our FAQ on "Complete Deinstallation of STEP 7
damaged. In most cases, the repair function on the STEP 7 CD can be including all Software Packages". You can find this FAQ in Entry ID 189025.
used to restore the software status on your PC.
275:5020 There is an internal error in the file S7nlvblx.dll. Save your entries and close the application. Switch your computer off/on
and restart the application. If the error reoccurs, then please get in touch
with your system administrator.
276:27 No valid connection path between local and remote partners (e.g. HotFix 1 for SP2 clears this problem. This error is still in SP3 at the moment,
because of missing network connection or exhausted resources). but will be cleared by another Add On.
276:42 Loopback - Connecting are not allowed! Loopback connections are not permitted. You can specify an identical Problem (V4.02 and higher) is cleared with correction release K4.02.5. You
address as local and remote user address, but then SDB generation is can ignore this error message, because the communication functions
rejected with an error message. despite this error message.
276:5020 An internal error occurred. (Call:
AUTReloadObject)
288:48 Unable to reach the module (z.B.) 413-2DP by In a new project, for example, a hardware upload was made from the Under Properties in Options -> Set PG/PC interface, set the local user
means of the subnet assigned to the programming CPU to the PG. In the attempt to immediately download this upload, this address to 0 (or the one configured previously).
device/PC. error message appears. Problem: under Properties in
Options -> Set PG/PC interface, 1 is preset as local user address on the
MPI bus. But this does not match the address configured in the hardware
upload and hence the error message.
289:2 The data base is write-protected or there are not XREF with V2.1.0 + standard control ->Correction K2.1.3 or higher
enough memory.
289:25 Two modules could not be translated back. XREF with V2.1.0 + standard control ->Correction K2.1.3 or higher
289:35 The selected button can not be executed for the You have selected a block folder and triggered printing. This is how you print out the reference data for the blocks contained in the
selected menu. folder:
1. Mark the block folder.
2. Select the menu command Options > Reference Data > Display.
In this way you display the reference data first. A check is made as to
whether reference data is available and whether it is up to date. If necessary
you can have the data updated. You can choose which table you want to
have printed with which filter setting.

Frei verwendbar Page 25 / 62

 STEP 7 Error Codes Version 01/2014

Error number: Text: Cause: Remedy:

This is how you print out the all the blocks of the container with the editor
with which they have been created: 1. Open the
block folder.
2. Select all the blocks (e.g. via the menu command Edit > Select All).
3. Select the menu command File > Print > Object.
291:416 The file is occupied by another application for writing. Close all the applications that have opened the symbol table and restart the
function.
291:416 The symbol table is being by another process. In the window that opens, the symbols are greyed out since editing is not Editing the entries in the symbol editor is still possible. Make the changes
possible. The Symbol Editor does not show any changes (it is not directly in the symbol table and save it. After saving the table, you can edit
possible to save the table) and it is not possible to access the symbols. the symbols in the LAD/FBD/STL editor after closing and opening the dialog
box again.
If you want to edit the symbols directly in the LAD/FBD/STL editor, close the
symbol editor and reopen the dialog box "Edit symbols" in the LAD/FBD/STL
editor. Editing is now possible. You can also simultaneously open the
symbol table. Changes in other applications are automatically applied in the
table.

291:416 The symbol table is occupied by another process In this case you can no longer edit, delete or import the symbol table. The One possible cause of the error is that after a program crash of the symbol
symbol table is not occupied by any other application for writing. You editor, temporary files are not deleted in the S7 data management. In order
have stored the project locally on the hard disk. The same error is also to control this, check your project:
displayed with the "Save with Reorganization" function of the project. 1. In each project there is a "..\YDBs" directory where all the symbol lists are
stored.
2. Use Explorer to find files with the suffix .dbf__tmp in this and all
subordinate directories.
3. Terminate the STEP7 applications and delete these files. Then you can
edit all the symbol lists again.
It is imperative to make sure that you do not delete other files by mistake in
the project, because this could destroy the project.

Frei verwendbar Page 26 / 62

 STEP 7 Error Codes Version 01/2014

Error number: Text: Cause: Remedy:

1. First of all try closing all the STEP 7 applications including the SIMATIC
Manager. If the symbol table is then opened via the SIMATIC Manager, an
attempt is first made to clear any inconsistencies in the symbol table through
a sort of internal "repair" service.
2. If editing the symbol table continues to be impossible, then please reboot
your computer to make sure that all the STEP 7 applications have been
closed. Then open the symbol table again.
3. If none of the above steps is successful, open the "..\YDB" path
mentioned above in the project directory. In this directory delete any files
with the file name "deleted.txt" and "update.txt" and a size of 0 KB and any
empty folders. You will then be able to edit the symbol table again

291:560 Internal error: Incorrect object ID. The symtabs function has failed - ambiguous entry in the symbol list for Delete the line for the FC in the symbol table.
FC names.
When calling an FB, a DB was assigned that is already assigned to Assign a different DB in the call or correct the assignment in the symbol
another FB in the symbol table. table.
Copy out the symbol table, then open and close the block, and then copy
back the symbol table.
291:1392 No symbol table found. No symbol could be
created.
292:19 Error by opening of a file. The file either has no valid B+C287trieve format or it is damaged. Replace the file or delete it.
293:1 The reference data could no be generated. The data medium is write-protected. Remove write-protection.
Under NT: possibly insufficient access rights. You need at least main user rights.
293:2 The reference data could no be generated for the Use the function "Save as" together with the option "With Reorganization
SFC14 or the FC22. (slowly)".
294:6 Unable to copy the block %2. The OBxy is not supported by the CPU. This OBxy cannot and must not be downloaded into this CPU. You can
possibly use another OBxy with a similar function, which is suitable for this
CPU and then download it.
When programming an EPROM via an external prommer: the prommer Plug in the prommer cable so that the connector with the yellow sticker is
cable is plugged in incorrectly. connected to the prommer.
Illegal command in the modul The module FCxx could not be copied. This message appears, if your program has a marker (example M8000.0)
(D280) Error during compiling of module in the S7-300. which address is not supported in the CPU. Change the address and repeat
the download. If the SF LED is not still erased after download, switch the
CPU into STOP and after in RUN again.
294:23 Unable to copy the block %2. Do you want to A block of this type already exists and it may not be overwritten. Delete the equivalent block in the ONLINE database and repeat the transfer.
continue the copy procedure?
The automation system is in the RUN operating mode. Put the automation system into an operating mode that permits copying.

Frei verwendbar Page 27 / 62

 STEP 7 Error Codes Version 01/2014

Error number: Text: Cause: Remedy:

SDBs can only be transferred in the STOP mode.
A block of this type and number is not permitted on the automation Check whether a block of this type and this number may be copied onto an
system. automation system of the present type.
The block is using operands beyond the area of the CPU (e.g. EW 128 Check the block with reference to the addresses used whether they do not
with S7-300 CPU). exceed the permitted address area in the CPU implemented.
The block is using statements that are not realized in the CPU (e.g. ENT Check the block with reference to the commands used based on the
with S7-300 CPU). operations list for the CPU implemented.
The block has to much local data (e.g. more than 256 bytes with S7-300 When implementing an S7-300, you must reduce the local data area for this
CPU). block. If you implement an S7-400 CPU, you can parameterize the
necessary local data area for each run level.
Referenced block SFC, SFB is not permitted in this module. Check whether the blocks that are to be downloaded are permitted on the
CPU concerned.
It is not possible to download the safety program In your distributed safety project is the specify for the safety program not Open the CPU properties in the hardware configuration and activate by
on the F-CPU. The hardware configuration as well activated. "Protection" the checkbox for "CPU contains safety program". Save and
as standard blocks can be loaded. When the compile the program and download again.
safety program is loaded, message 294: 23
appears; Block could not be copied.
Individual F blocks were loaded directly from the block folder. Load the F program from the editor "Safety program edit".
Check the following by the ET 200S F-CPU: Is the bus termination module inserted?
Check the online connection between the configured modules in the
hardware configuration and the inserted modules.
If a DP master module is inserted next to the CPU, check in particular the
plug contacts. A bent shroud can lead to a short-circuit on the bus, as a
result of which the bus termination module will no longer be reached, which
ultimately leads to the Report 294:23.
294:27 The block %2 is being processed by another Multi-users: the block specified is being processed at the moment by If you are working with several colleagues on your S7 project, then it is
application or another user at the moment.\nDo another application or by another user. You can create a copy of the last recommended not to process this block without prior synchronization with
you want to create the reference data for the saved version saved or cancel the function. your colleagues.
version of the block?
Single Users: the block is opened ONLINE as OFFLINE. Close the block once; ONLINE or OFFLINE.
295:17240
295:17248 The order was interrupted to the TS-Adapter The initialization string is not correct or in this form does not work together The initialization string in the TS adapter must be modified in the direct
because of transmission error. with the modem connected to the system. operating mode so that it matches the modem.

Frei verwendbar Page 28 / 62

 STEP 7 Error Codes Version 01/2014

Error number: Text: Cause: Remedy:

On the system there is not a TS adapter but a PC adapter on the modem. Exchange the adapter for a TS adapter.
The TS adapter has order number
6ES7972-0CA3x-0XA0

Possibly the terminator on the PROFIBUS cable on the system side Switch off the bus terminator.
(TeleService) is switched on.
Possible the modem is sending too much information to the TS adapter Add W0 to the Initstring in the adapter (this suppresses the sending of
so that it doesn't get the CONNECT. (Occurs with V5 adapters) extended data)

If you attempt to get connected via long telephone routes (abroad), then it In TeleService under Options -> Settings -> Monitoring Times, change the
might happen that some feedback messages have too long a runtime. value for Acknowledgment/Signal from Automatic to 5000ms / 4000ms.

295:20484 There is not installed a modem which is Install a suitable modem and set the modem to correspond with your
compatible with teleservice. configuration. Define the TeleService-specific properties of your installed
modem in the menu command Options > Settings.
295:20486 The TAPI-Order was closed with the error "Order Basically communication between (local) PC and modem (via the serial Check the connection between the (local) PC and modem for both hardware
failure". connection) is not correct or cannot even be started. and software/driver faults.
Under Windows (Start --> Settings --> Control Panel --> Modems) an Install the appropriate modem driver for this modem. Also set this new
incorrect (or no) modem driver has been installed, which does not work in modem in TeleService under Set Connection ---> Modem (double-click the
conjunction with the modem connected. telephone book entry and then select the Modem item).
The wrong modem driver was selected under TeleService from the Set the correct modem driver in the selection list.
selection list of modems that are already installed under Windows.
The modem is not connected to a serial interface (or to the wrong one). Connect the modem to the correct serial interface.

The modem is switched off. Switch on the modem.

295:32768 TAPI-subsystem dues supply not expected error
code <TAPI-Error-Code>
ALLOCATED 0x80000001
INVALDEVICECLASS 0x80000023
296:5309 The variables of the instance data block which Clearance: check the function block and save it again if necessary.
contain system attributes for messages are not
aggree with the variables in the function block.

Frei verwendbar Page 29 / 62

 STEP 7 Error Codes Version 01/2014

Error number: Text: Cause: Remedy:

300:13 Data basis could not be started. Occurs as a consequence of message 256:94 and details 256:24/256:63 The problem can be solved by deleting the file AMDBASE.LOG. Search in
when executing the function "Reorganize" or "Save as… with consistency your project path for the log file of the SYBASE database (Amdbase.db).
check". WARNING: if this file does not exist, then search the project for LOG or LOC
This occurs when a link is lost in the SYBASE database. files.

If you cannot find this file, then proceed as follows.

Restore the log file by entering the following start line via "Start/Run..." on
the Windows user interface:
dbsrv50 -f D:\..Project path..\Project\AMOBJS\Amdbase.db

For example, for the "Deissw01" project on drive "C" in the standard STEP 7
project directory you enter
dbsrv50 -f c:\Siemens\step7\S7proj\deissw01\Amobjs\Amdbase.db

The -f (force) switch has the effect that the DB file is recovered to the last
status saved even if the necessary log file is not available.

Occurs after dearchiving a project in STEP 7 V5.0. It has been created in After <Save as...><with reorganization> again clears the problem.
the version V4.02.x.
314:8 At least one of the selected variables cannot be If, while you are processing a project in STEP 7 V5.3 which has been In this event, the name "Ret_Val" must be renamed.
inserted at this point. created with STEP 7 V5.1 and the error message described above 1. From STEP 7 version V5.2 onwards, users may no longer define the key
appears in the LAD/STL/FBD editor when you insert a declaration line term "Ret_Val" for the formal parameters. Version V5.2 still supported the
within an FB or FC, please check the names of the formal parameters in entry "Ret_Val" in the declaration line in STEP 7 projects which were
the declaration line for the block in question. This could be due to the fact created in V5.1 and did not stop the block.
that the name "Ret_Val" has been assigned to a formal parameter (IN, 2. However, STEP 7 version V5.3 no longer supports the name "Ret_Val" in
OUT, IN_OUT, STAT or TEMP variable). the declaration line, and the behavior described above occurs.
724:21 OM TD/OP: Data basis conflict of version The versions of STEP 7 and ProTool are incompatible with those of the Upgrade STEP 7 to V5.x or deinstall ProTool and install V4.02 of ProTool
file: C:\[step7-pfad]\[Projektname]\S7TDOP.DBF project. STEP 7 is V4.02.x and ProTool V5.
has the version 50000.
This program expected the version 10000.
1230:1001 Opening of the station failed.
1230:2001 Unable to insert the object. You have tried to slot an object that is not available (e.g. the header for an Select an object (subrack, module, interface module...) from the hardware
object group or module class). catalog, which you can slot in the required location.

Frei verwendbar Page 30 / 62

 STEP 7 Error Codes Version 01/2014

Error number: Text: Cause: Remedy:

1230:2009 Changes cannot be made. Save your changes in The error message indicates that access to the object is not possible at The following steps permit you to process the object:
other applications the moment and that the object could not be blocked. This error message 1. Save the changes made in all other applications and make sure that no
can have various causes: other user is currently processing this object.
1. The object is currently being processed by another application or user 2. Make sure that there is sufficient virtual memory on your computer, see in
and has therefore been blocked. this case the informations of the Readme file of STEP 7 by 3.2 Memory
2. There is insufficient memory available. Requirements.
Notes:
Please consider the requirements of the actual installed STEP 7 software in
refer to your PC, which are described in the readme file.

1230:2015 Creating the configuration data failed. Hard disk is full. Deleted all the unnecessary files on the hard disk.
No folder "...SIEMENS\STEP7\S7TMP" available or the folder is write- Remove the write-protection from the folder "...SIEMENS\STEP7\S7TMP" or
protected. create the folder.
S7 program or M7 program container is missing. Create S7 program or M7 program container.
Defective project? Use "Save as... with reorganization"
The compilation (= creation of the configuration data) has been Reinstall STEP 7.
interrupted.
Error attempting to generate the configuration data. Subnet addresses of different networks are identical. Check the subnet addresses and make appropriate corrections in the case
Message refers to the V2-projects by Save as with of identical subnet addresses.
Reorganization.
1230:2016 No changes can be made in this station. No more modules can be inserted in the HW Config. Use "Save as... with reorganization" for the project. Please see also the
instruction by the error message 256:92.
1230:2018 Another application made changes to your station. Another S7 application has changed, for example, via network, the station You can remove the block by closing the station and re-opening it. This
Close this station and re-open it. currently being processed. The changed objects (subrack, modules, makes the changes of the other application effective.
slaves, etc.) can no longer be displayed.
The station has been blocked for further processing.

1230:3000 The system data could not be recreated because Check consistency.
the configuration is inconsistent.
2508:1099 Error by programming of error diagnostic data for Group message, behind it detailed messages are listed that occurred Please press the "Details" button and analyze the detailed messages.
<name of variable>. during the last function executed.
2517:5 The start of an application has occurred an error. Message appears when opening a HIGRAPH source. Cleared with K4.01.2.
With the following software constellation:
STEP 7 V5.0 + SP 3
S7-HIGRAPH V4.01.1
S7 project created with S7-Higraph V5.x

Frei verwendbar Page 31 / 62

 STEP 7 Error Codes Version 01/2014

Error number: Text: Cause: Remedy:

2665:4156 Because of the changes made to the configuration,
the configuration file for this SIMATIC PC station
has to be created again with NetPro. To do this,
use the NetPro menu command "Network > Save
and Compile ..."
2760:11 communication to higraph cannnot be accessed

2775:777 Address is not correct. You have selected a user address that is already occupied. Please select another address or connect your user to another subnetwork.

2775:785 The bit rate of 187,5 kbit/s for the modul MBK-P is In STEP7 V5+SP3 and higher the baud rate must not be written with a Open and edit the file: enter '187.5_supp =1' instead of '187,5_supp =1'.
not supported in station SIMATIC 400(1). comma, e.g. 187,5_supp =1 Execute Options -> UPDATE CATALOG.
2775:1829 The data management of "Set PG/PC interface" An attempt was made to save a parameter value in the database of the
can not save the requested value. program "Set PG/PC interface". This write procedure could not be
concluded successfully.
2775:1834 The highest address on PROFIBUS subnet <xx> is In the properties of the PROFIBUS system, you can set the highest Open in the HW Config the properties of PROFIBUS interface your CPU and
set to <xx>. "The highest PROFIBUS subnet permitted Profibus address. If you have set the address e.g. 32, a higher click in register "General" on "Properties". Select in the follow dialogue the
'PROFIBUS(1)' is set to 32. Due to the steps PROFIBUS station address is no longer permitted and the message PROFIBUS network and click on "Properties". Set the value for the highest
available for the settings, this cannot be set". appears. PROFIBUS address, e.g. 126 in register "Network Settings".

2775:1860 Caution: there are other active nodes (sender

parameter assignment master) in station %1 which
also have to be reloaded.
3020:13 File name entered is not valid, or This message appears when you stored your project on a network drive In order to be able to open your project, please connect the share (without
Project is invalid, which is connected to the following path via the Internet Explorer or a the domain name) via
if you attempt to open a project. logon script: \\<Servername>\<share> (Example: \\COMPUTER\share).
\\<Servername>.<DNS-Suffix>\<Share> (Example: Note:
\\computer.siemens.de\share) or If you have to enter the pathname via the IP address, you can establish a
\\<IP address>\<share> (Example: \\192.168.1.1\share). connection between the IP address and the computer name in the "hosts"
However, this path cannot be found since the network connection is file. The file can be found with the Windows path "\system32\drivers\etc"
stored only symbolically in the registry. (Example: C:\WINNT\system32\drivers\etc).

Frei verwendbar Page 32 / 62

 STEP 7 Error Codes Version 01/2014

Error number: Text: Cause: Remedy:

3020:25 Projects which are opened can not be archived. The reason for this error message are blocked files, which are also With WinCC or WinCC flexible will be started a SQL server which should be
Make sure that in non STEP 7 application objects blocked though all the windows of editors and projects are closed. This is stopped. You will find this in the task bar. You will also find here icons of
of the projects ... are opened in the directory C:... possible when the program is activ and the last access was to the WinCC flexible, which are mini web or smart server. If you will stop these
archived project. Souch programs are not always to see as user window. applications the archiving should be possible again. If not, then start the task
manager and check in the process list whether the process "hmies.exe" is
activ. If you delete this process, then the archiving should be possible again.

3020:47 This processing status is triggered by PKUnZip in different situations, in In this - most common - case you can ignore the message.
particular always when an existing project is overwritten during
dearchiving and in the dearchiving options the entry "Overwrite objects
with identical names" is not set to "All Files".
The archive file has not been created with PKZip. In particular archives Execute dearchiving with the archiving program used to create the archive.
that have been created with WinZip or "PKZip for Windows" and contain
"long file names" can lead to this error.
The archive file has been created with a version of PKZip that is newer If you are using an old version of PKUnZip, install the latest version.
than the version of PKUnZip that is installed on the computer.
The archive file is damaged. Checksum errors (so-called CRC errors)
have been detected for one or more files. Therefore the files could not be Try to get a good copy of your archive file. If this is not possible, you can try
dearchived correctly. The cause of such checksum errors can in particular to save what is possible to save using the repair option of PKZip. Start the
be: MS-DOS prompt and enter the command 'pkzipfix archiv'. A file is created
damaged floppy disks, transfer errors when copying, called pkfixed.zip - if pkzipfix can even identify the file as being ZIP-
in particular with network drives, file transfer or e-mail, compatible. From the SIMATIC Manager dearchive the file pkfixed.zip
or at the time of archiving the project or parts of it were still open. instead of your original archive file.
The directories in the archive file have too great a nesting depth to be You can either dearchive the archive file with PKUnZip as follows: select the
able to be unpacked under the specified target directory. PKUnZip cannot target directory for dearchiving the Root directory of drive. Close all the
create any directories whose absolute path name is longer than 66 STEP 7 applications. Move the dearchived project directory with the
characters (from the drive designation to the ‘\’ at the end of the path). Explorer to the location where the project is to be stored. Start the SIMATIC
Manager and open the project via the "Browse" button in the "Open" dialog.
Or you can use WinZip or PKZIP 2.50 directly at the required location.

The project already exists and individual files could not be overwritten Delete the file attribute "write-protected". You can do this for example for
when dearchiving, because they are write-protected. individual files from the Explorer via the file properties, or you start the MS-
DOS prompt, get into the project directory using "cd" and then enter the
command "attrib -r /s". Now repeat the dearchiving procedure.
D330

Frei verwendbar Page 33 / 62

 STEP 7 Error Codes Version 01/2014

Error number: Text: Cause: Remedy:

The project already exists and individual files could not be overwritten Close all the STEP 7 applications, restart the SIMATIC Manager and
when dearchiving, because the project or objects from the project are dearchive the project without opening the project to be overwritten
already open. beforehand.

3020:49 Unable to retrieve the project. The archive file The archive file has not been created with PKZip. In particular archives Dearchive using the archiving program with which the archive was created.
might be defective. that have been created with WinZip or "PKZip for Windows" and include
"long file names" can lead to this error.
The archive file has been created with a version of PKZip that is newer If you are using an old version of PKUnZip, then install the latest version.
than the version of PKUnZip installed on this computer.
The archive file is damaged. Try to get a good copy of your archive file. If this is not possible, you can try
to save what is possible to save using the repair option of PKZip.
1. Start the MS-DOS prompt and enter the command 'pkzipfix archiv'. A file
is created called pkfixed.zip - if pkzipfix can even identify the file as being
ZIP-compatible. From the SIMATIC Manager dearchive the file pkfixed.zip
instead of your original archive file.
The data medium or the directory in which the dearchived project is to be Remove the write-protection or obtain write authorization for the network
stored is write-protected, or you have no write authorization for the drive or dearchive the project into a different directory.
network drive.
3022:4121 The FB is not available If during compilation in S7-PDIAG the mentioned error message, then it is 1. Delete all SFBs. Open and save the FBs, FCs and OBs, which fetches
The instance declaration is missing probably the case that the S7-PDIAG blocks have also been copied from the SFBs from the current library.
another STEP 7 during the copying procedure. This is not permissible, 2. Now compile the blocks of the S7 program again with S7-DIAG, which
because the associated SFBs are then no longer up to date. should solve the problem.

Make the Check Block Consistency and compile the complete STEP 7
program.
3022:4121 Invalid data type...", The error message is probably caused by an associated value with an Excerpt of the Online Help of S7-PDIAG:
invalid data type. Please also refer to the information in the Online Help of "This associated value can have a parameter of the type BOOL, BYTE,
S7-DIAG concerning the data types that are valid for associated values. CHAR, WORD, INT, DWORD, DINT or REAL from the E, A, M or DB areas.
Likewise you can enter local variables of an FB to which an error definition is
attached. These are extended upon generation according to the type
instance concept.
3280:503 The registry database is not set up correctly for the Installation is faulty.
SIMATIC Manager. Install STEP 7 again.

Frei verwendbar Page 34 / 62

 STEP 7 Error Codes Version 01/2014

Error number: Text: Cause: Remedy:

3280:708 No objects can be copied or moved from In STEP 7 there is no downward compatibility, the data management in An attempt was made to copy or move an object from a version V3 project
projects/libraries of the current version to V2 and >V3 is not the same, so blocks created with STEP 7 V3 or higher or from a version V3 library into a version V2 project or library. This is not
projects/libraries of version 2.x. cannot be copied or moved into V2.x projects . possible because of incompatibility.
3280:709 The project or the library '%1' is on a write- The project is either located on a write-protected floppy disk or you do not Remove the write-protection if you want to modify objects in this project.
protected medium. have write authorization for the drive. Please see the instruction by error message 256:92.
The project catalog was released in the Windows Explorer with read/write Release higher-level catalog of the project (e.g. Step7\S7Proj) for access
access. via network drive.
3280:712 File name entered is not valid. Please see the informations by error message 3020:13.
Project is invalid.
(If you attempt to open a project)
3280:999 The internet explorer is not installed in your PC. STEP 7 V5 has been installed without the Internet Explorer and you are Please install the Internet Explorer V4.0 and then reinstall STEP 7.
trying to start the ONLINE Help.
The ONLINE Help was started and the Internet Explorer was installed Reinstall STEP 7.
after the installation of STEP 7.
3531:1 The diagnostic block could not be created. Standard blocks in the program originate from the PLC and not from the Check your interface to the user block.
library. If your user program contains standard blocks with Default Symbolic, then
If the project has been created per upload by the PLC with an earlier please delete these SFBs and SFCs and reinsert them from the library. This
version of STEP 7 or standard blocks have been copied from the PLC corrects the interface of these blocks.
into the offline program, then the interface of the SFBs and SFCs in the
project only has a Default Symbolic (parameter name = "IN0", "IN1" etc.
instead of symbolic names as described in the Help). In this case the
same error is reported.
3534:63 While reporting a system error: an internal error To be able to generate the reference data without this message, proceed You can regenerate the FB49 and DB49 in the Hardware-configuration as
has ocurred as follows: follows:
1. Delete Diagnostics-FB49 and Diagnostics-DB49 from your STEP 7 1. Highlight the CPU with the cursor. Under "Extras > reporting system
Project resp. Block container. errors... > Register: General", you can now newly generate the Diagnostics-
2. Newly generate the reference data by selecting the block container and FB and the Diagnostics-DB. Finally, save and translate the Hardware
the menu task Extras > Reference data > generate. configuration once more.
This message does no longer appear when generating reference data. 2. You can also newly generate the Diagnostics-FB and the Diagnostics-DB
by means of "Save and translate" if you change the following setting: Under
"Station > Properties ... > Register: Settings" the option "Calling when saving
and translating" has to be activated.

3534:94 Inconsistent of hardware configuration The hardware configuration is either inconsistent or it was made changing If it is not possible to compile the hardware configuration after this message,
which are not still save and compiled. so make a little change in the hardware configuration. After it is possible
again to save and compile.

Frei verwendbar Page 35 / 62

 STEP 7 Error Codes Version 01/2014

Error number: Text: Cause: Remedy:

4050:1 The resources file for this language is not in the directory in which you Install the files that are required for the language desired. If necessary,
have installed this program. This is why the menus, dialog boxes and the reinstall S7-PLCSIM and select the required language.
online Help are in English in S7-PLCSIM.
4050:2 Closing the subwindow "CPU" simultaneously closes the simulation Make sure that you always have on subwindow open in S7-PLCSIM. If you
session. However, you can close a CPU and start a new simulation need more space on your screen, you can reduce the subwindow to icon
session with another CPU. size.
4050:3 You can only change the MPI address if there are no applications linked Close all the associated applications or disconnect from the simulation.
with the simulation.
4050:4 You can only ever have one simulated automation system activated. If
you open a second simulated automation system, the one opened first is
closed. If you want to continue the function, press "Yes". Press "No" to
cancel.
4050:5 You cannot exit S7-PLCSIM if there is still a connection set up to STEP 7 Before exiting S7-PLCSIM you must close the associated applications in
(e.g. SIMATIC Manager, variable table, program editor). STEP 7 indicates STEP 7 or clear down the connection to STEP 7. (In order to disconnect the
in a message that the connection to the CPU has been interrupted. You SIMATIC Manager from S7-PLCSIM you must close both the online program
can then continue working offline. and the offline program.)
4050:6 When doing an overall reset (MRES), all the blocks are deleted and the If you want to abort the overall reset, click "No". If you wish to do an overall
memory of the simulated automation system is reset. reset, click "Yes" to continue the function.
4050:7 You have attempted to open a simulation that has just recently been Find the simulated program using the menu command Simulation > Open
used, but which is no longer available or cannot be found. S7-PLCSIM PLC. If the program is no longer available, you must recreate the simulation.
deletes the file name from the menu.
4050:100 The address you have specified has a format that STEP 7 does not Enter the address in a format that is supported by STEP 7 (IEC or
support. SIMATIC).
Examples:
IEC: PIB0, PQB0, PIW2, PQW2, I0.0, Q0.0
C1SIMATIC: PEB0, PAB0, PEW2, PAW2, E0.0, A0.0, Z1
4050:101 The value you have entered is not in the valid range for the selected Enter the value in a valid format or change the format of the field.
format. For example, you cannot enter "FF" (hexadecimal value) in a field
in which binary values are supposed to be entered.
4050:102 The value you have entered is not a decimal number. Enter decimal number (e.g. 0, 1, 13).
4050:200 Since there is a danger of changing an actual online program by mistake, Close all the windows and applications that have been used in the
you cannot communicate with "real" CPUs whilst the simulation is simulation of your program before going online with an actual CPU.
activated.
4299:158 No connection to FM355/455. Old firmware on the FM. Upgrade the firmware of FM.

Frei verwendbar Page 36 / 62

 STEP 7 Error Codes Version 01/2014

Error number: Text: Cause: Remedy:

4431:2011 The Authorisation for SIMATIC PDM is not Authorization permitting you to integrate SIMATIC PDM in STEP 7 is You must install the additional authorization for integrating SIMATIC PDM in
installed. SIMATIC PDM could not be started. missing. This authorization is an option authorization that has to be STEP 7.
installed in addition to the basic authorization of SIMATIC PDM.
4502:298 System error 33 This meesage appears during the upload of the hardware configuration. It Make a reset of the CPU modul and load the hardware configuration of the
is possible that the load of the SDBs was not complete or incorrect. offline project again.

4502:625 An error occured while creating or interpreting the Regarding mentioned messages occur while saving and translating in HW Step7 has to be reinstalled or the missing ".err" files have to be copied from
system SDB's....". config if the following applies: a different computer in order to be able to translate the hardware
Error while creating systemdata....". 1. You projected and assigned a CP to a subnet in your Hardware configuration again.
configuration. Files with the extension ."err" are missing in the folder Attention:
"<Siemens-index>\Step7\S7WBX\RUL". If you copy the files from a second STEP 7 installation, please make sure
2. Files with the extension ."err" will be deleted by some optimization that this installation contains exactly the same STEP 7 version, the same
programs - like e.g. TuneUp. servicepack and the same hotfix.
4561:142 The Authorisation for Standard PID Control is not .. ..
installed.
Meldung von
Baugruppen
D033 Error of protokol Job jam on the CPU. In the HW Config increase the setting for the communications load for the
CPU.
D042 Error during notice by module status of CPU400. A PQW is being monitored. You cannot read back PQWs, the CPU then Monitor values with VAT and wait for new CPUs.
reports this error.
D043 Error of data: The reference order is not available. When controlling using Variable Monitoring it might happen that if too Acknowledge the message and reduce the frequency of control jobs.
many control jobs are sent to the CPU, they are rejected by the CPU
because its buffer is full.
D062 Resources error, job list is too full. Please see the informations by error message 33:53346.
D063 Same as D064
D064 CPU 300 does not delete trigger events, the events then build up. Switch CPU off/on. Problem cleared in the following CPUs:
6ES7 313-1AD01-0AB0
6ES7 314-5AE01-0AB0
6ES7 314-1AE02-0AB0
6ES7 315-1AF01-0AB0
6ES7 315-2AF01-0AB0
D0AA D0AA: The time limit is exceeded in process Communications load is too high. Increase the communications load of the CPU from (default) 20% to 50%.
operating.

Frei verwendbar Page 37 / 62

 STEP 7 Error Codes Version 01/2014

Error number: Text: Cause: Remedy:

Message appears with the function "Control via VAT" to an address from Please check the syntax of the address in the VAT, or whether the address
the memory areas I, O, M, Timer, Counter, DB, which is not available in is available in the system or perhaps not addressable (wiring fault, hardware
the broadest sense. fault).
D204 D204: An error in the rules of coordinating has When attempting to load system data, in the background a variable table Close the variable table and retransfer the system data.
occured. was still open online.
D20C The OB can not be copied because the belong Message comes from a CPU. An attempt is being made to transfer an OB If possible, rename the OB or even delete it in the OFFLINE database and
layer is not available. onto this CPU, which is not permissible. retrigger the transfer.
D240 An error in the rules of coordinating has occured. Occurs if a block that is to be overwritten online is still being accessed. In Deactivate the setting "Call path with test/call environment", then the block
V4.01 with blocks in the call environment. can be downloaded.
An error in the rules of coordinating has occured. Occurs when an object is accessed online (also VAT). Close everything except HW Config.

Error during opening of a empty document. Error An incompatible OPC Manager is installed. In the system path of Delete this file and the file vcf132.ocx and reinstall STEP 7.
during opening of a symbolic table. Windows vcf1.lic is responsible for this.
Setup does not start with error message: in The _isres.dll is needed for switching languages. Start Setup with the extension ol:b, then the Setup is forced to start in
function "Sdbitmap":unable to crate dialog make English.
sure the _isres.dll is in _setup.lib
D280 Error during compilation of a modul in S7-300. The This message appears, when the defined variable (marker, in- or output) Example, this message appears if the number of outputs is 8192 byte by the
module OB1 could not be copied. in a module is not in the power range of the CPU. CPU and you have defined a variable outside of this range. Check the
addresses with the definition of your variables.
D406 The requested informations are not available. Number of possible connections has been exceeded. Check the connections and reduce where appropriate. Static connections
can be converted into dynamic connections.
EA 02 The protocols of communication software (S7DOS) The customer has a STEP 7 V5+SP1 + recent PDM and a CP 443-5 Ext Upgrade CP 443-5 to a version >V2.7.
and the interface module (CP) are not compatible. > V2.7. The new RPC 7 protocol is used for data record routing between
the CP and S7DOS. Unfortunately the CP up to version V2.7 does not
support this function.
The user is using the correct components STEP 7 V5 + SP2 + PDM, but Check the configuration and replace the CP being used with a different CP
has a CP that does not have the DSGW. that has this function.
Set PG/PC interface
None Error message by diagnostic: "Profibus/MPI Firmware/driver error This behavior no longer occurs in SOFTNET PROFIBUS S7 V5.0.
Network diagnostic".
Error: requested parameter could not be read from
the register data basis!
Message without numerical order
S7OTBLSTX Incompatible versionen by S7OTBLDX.DLL and S7 applications are still running at Setup of STEP 7. Please close all S7 applications and restart SETUP.
S7OTBLSX.DLL.

Frei verwendbar Page 38 / 62

 STEP 7 Error Codes Version 01/2014

Error number: Text: Cause: Remedy:

STEP 7 has been installed on a computer on which an S7 options Please search for "S7OT*.*" on all your local drives and delete them. Then
package or version of ProTool /WIN CC is already installed which is not please restart the Setup of STEP 7.
compatible with the version of STEP 7.

Frei verwendbar Page 39 / 62

AUTAPI 8001 s7aaaem?.dll s7aaaeh?.hlp 257
cmnerr 8000 s7acerr?.dll s7aceeh?.hlp 256
s7apromx 8002 s7aprem?.dll s7apreh?.hlp 258
S7 Archive-Services 0 s7arcem?.dll s7arceh?.hlp 3020
S7asrcom 0 s7asrer?.dll s7asreh?.hlp 2517
S7ifx 8035 S7BIN\S7IFXEM?.DLL S7BIN\S7IFXEH?.HLP 309
S7ndi 0 s7bin\s7ndiem?.dll s7bin\S7NDEHP?.HLP 1229
Netpro 0 s7bin\s7nnems?.dll s7bin\s7nnehp?.hlp 2263
TBI FFFF s7dbiem?.dll 1
HW-Konfig 0 s7hcoem?.dll s7hcoeh?.hlp 1230
S7HWOM FFF3 s7homem?.dll s7homeh?.hlp 13
RESOURCE_OM 8020 s7hrsem?.dll s7hrseh?.hlp 288
Comp-IF_V3 FFDE s7iccem?.dll s7icceh?.hlp 34
Comp-IF FFF7 s7iecem?.dll s7ieceh?.hlp 9
S7-Info Applikation FFF5 s7inf\s7usiem?.dll s7inf\s7usieh?.hlp 11
M7Config 0 s7mfger?.dll s7mfgeh?.hlp 4049
GD-Konfig FFF9 s7ngd\s7lerms?.dll s7ngd\s7lgdeh?.hlp 7
OM Homo 8014 S7NHEMS?.DLL S7NHEHP?.HLP 276
OM VerbList 8013 S7NLEMS?.DLL S7NLEHP?.HLP 275
OM Fremd 0 s7noems?.dll s7noehp?.hlp 2775
S7nonfgx 0 s7noems?.dll s7noehp?.hlp 2775
OM PtP 0 S7NPEMS?.DLL S7NPEHP?.HLP 3225
OM Block 8026 s7ombem?.dll s7ombeh?.hlp 294
S7DOS FFDF s7otbem?.dll s7otbeh?.hlp 33
SCL FFF1 S7scl\s7sclem?.dll S7scl\s7scleh?.hlp 15
S7KAF FFE2 s7ska\s7kafem?.dll s7ska\s7kafeh?.hlp 30
Symbol Editor FFFD s7sym\s7yedem?.dll s7sym\s7yedeh?.hlp 3
s7tgtop 0 s7topem?.dll s7topeh?.hlp 3280
s7tbrow 0 s7topem?.dll s7topeh?.hlp 3280
S7ubsdh 802C s7ubseh?.DLL s7ubseh?.HLP 300
S7UMG 8024 s7umgem?.dll s7umgeh?.hlp 292
S7MSG 0 s7ums\s7umsem?.dll s7ums\s7umseh?.hlp 1489
s7upomx 802A s7upoem?.dll s7upoeh?.hlp 298
S7USF 0 s7usf\s7usfem?.dll s7usf\s7usfeh?.hlp 3534
S7USS FFF0 s7uss\s7ussem?.dll s7uss\s7usseh?.hlp 16
OM Text 802B s7utoem?.dll s7utxeh?.hlp 299
S7UVPV 802D s7uvpeh?.dll s7uvaeh?.hlp 301
SINEC NCMS7 0 s7wber1?.dll s7wber1?.hlp 4502
S7WBPCAX 0 s7wbpca?.dll s7wbpca?.hlp 1474
S7WBPCHX 0 s7wbpch?.dll s7wbpch?.hlp 1481
S7WBPCLX 0 s7wbpcl?.dll s7wbpcl?.hlp 1485
OM Alarm 8028 s7wmxeh?.dll s7wm_eh?.hlp 296
NCM DIAG 0 S7WNDXE?.DLL 1425
S7WNSRVX 0 s7wnsrv?.dll s7wnsrv?.hlp 4576
S7WRI 0 s7wri\s7wriem?.dll s7wri\s7wrieh?.hlp 2511
S7XUTOM 8025 s7xomeh?.dll s7xomeh?.hlp 293
S7XUT 8021 s7xut\s7xuaem?.dll s7xut\s7xuteh?.hlp 289
OM Symbol 8023 s7yomem?.dll s7yomeh?.hlp 291

Frei verwendbar
 ARJ Fehlertexte

Fehlermeldung:
<filename> does not exist

<filename> exists

<filename> is not an ARJ archive

<filename> is not the same date/time

<filename> is same or newer

Archive name argument missing

Arg table overflow

*** Valid ARJ-SECURITY envelope signature:

Bad command syntax

Bad file data

Bad file data or bad password

Bad header

Bad or missing SECURITY key

Break signaled

Can´t copy temp <filename> to archive <filename>

Can´t delete <filename>

Can´t find <filename>

Can´t find restart file: <filename>

Frei verwendbar Seite 41

 ARJ Fehlertexte

Can´t find restart information

Can´t get volume label

Can´t handle ARJ-SECURITY version <number>

Can´t make directory <directoryname>

Can´t open <filename>

Can´t order a multiple volume archive

Can´t read file or unexprcted end of file

Can´t rename <filename> to <filename>

Can´t reset <filename>

Can´t seek to position <number> in file

Can´t update an ARJ-SECURED archive!

Can´t use -jt1 or -jt2 with -e or -e1

Can´t use -v with -je1

Can´t write file. Disk full?

CRC error

Critical device error

*** Damaged ARJ-SECURED archive!

Delete argument missing

Frei verwendbar Seite 42

 ARJ Fehlertexte

*** Detected an OBSOLETE ARJ-SECURITY envelope.

NOT verified!

Exceeded maximum path size of <number> at

<filename>

Exceeded name limit of <number> at <filename>

File is password encrypted

Found <number> error(s)

Garbled files are not allowed for SFXJR

Header CRC error

Invalid command: <command>

Invalid comment header

Invalid date string: <date>

Invalid multiple volume file sequence

Invalid switch: <option>

Invalid use of self-extraction switch

Invalid volume size

Missing filename argument for <command>

Multiple volume updates are NOT supported

Must specify only non-wildnames for order command

NOT found

NOT matched

Frei verwendbar Seite 43

 ARJ Fehlertexte

No avaiable memory to store <filename>

Nothing to do

No strings were entered

Not a valid method for SFX

Not enough disk space for extraction. overflow by over

<number> bytes

Not enough disk space

Not enough free disk space

Order command file count mismatch

Out of near memory

Password option missing

Passwords did not match

Read/Write error <message> on drive <letter>

Set label error

Signal failed

Skipping a possible ARJ-SECURED archive

Text mode (-t1) files are not allowed for SFXJR

The ARJ-SECURITY envelope on this archive has

been violanted

This archive HAS a valid ARJ-SECURITY envelope

Unknown file type: <number>

Frei verwendbar Seite 44

 ARJ Fehlertexte

Unknown method: <number>

Unknown version: <number>

***Verifying ARJ SECURITY envelope ...

Volume labels are not allowed for SFX

Warning! Only <number> bytes of free disk space.

Continue?

end of document

Frei verwendbar Seite 45

 ARJ Fehlertexte

Fehlerursache:
The file <filename> could not be found on the disk
This error may occur in a multiple volume extraction if ARJ is trying to
extrace a split file. If this split file is not the file on the disk. If thie is
missing, ARJ will report this error.
This error will also occur during an extraction to freshen existing files.

The file <filename> already exists on the disk.

The file <filename> does not have a valid ARJ archive header in the initial
portion of the file. This file may not be an ARJ archive or it may be
demaged.

The file <filename> that is being appended to does not have the correct
file date-time stamp. This message occurs during multiple volume
extraction was interrupted by a "quit" response.

The <filename> has the same or newer file date-time stamp than the
matching file in the archive.

The ARJ command is missing the name of the ARJ archive filename

There are more than 64 arguments on the ARJ command line.

This message is displayed when ARJ has verified that the archive has a
valid ARJ-SEC envelope. This indicates that the archive contents are
intact and unmodified as originally distributed by the individual indentified
in the text that follows this message

The ARJ command line is not correct syntactically.

The file in the ARJ archive is damaged and has invalid data in it. It is not
possible to recover thes file in an undamaged format.

The file in the ARJ archive is damaged or you may have supplied the
wrong password to the "-g" option. Check the password that you specified.

The ARJ archive file description information record is damaged.

An invalid or missing security key was provided to ARJ. Check to see if

the security key is correct.

The user pressed Control C or Control BREAK.

This error usually means that there is not enough disk space to copy the
intermediate archive file to its destination drive. ARJ does not purge the
intermediate archive file so that the file can be copied manually to a drive
with enough disk space.

ARJ cannot delete the file <filename>. Most likely, the file is in use or is
set as readonly.

The file <filename> does not exist.

The file <filename> does not exist.

Frei verwendbar Seite 46

 ARJ Fehlertexte

During the scan of the specified index file, ARJ could not find a line of text
similar to the following: Next volume - 001 1 19931 C:\ARC\VGA640.DRV
This can happened if the index file is damaged or was created by a
version of ARJ prior to 2.39.

ARJ could not read the volume label of the drive specified.

This version of ARJ encountered an ARJ-SECURITY envelope version of

whitch it does not know how to verify the integrity.

ARJ could not create the directory <directoryname>. The name

<directoryname> may already exist.

ARJ cannot open the file <filename>. The file may be set to readonly or it
may already be in use.

Re-ordering a multiple volume archive is NOT allowed.

This error message usually occurs if the end of the file has been reached
when ARJ is expecting more data.

ARJ could not rename <filename>. The target filename may already exist.

ARJ could not restart the archive bit attribute of <filename>

ARJ could not seek to the position in the file. This file may not be as large
as the position specified.

Modification of an ARJ-SECURED archive is NOT allowed.

ARJ always uses the filename stored in the archive ta access the file
during the compare operation. The -e and -e1 options strip significant
information from the filename.

The small self-extraction module does not support multiple volume

archives.

Self-explanatory.

The file in the ARJ archive is damaged and has involid data in it. It is not
possible to recover this file in an undamaged format. If this error is
encounted when ARJ initally starts up, this indicates that the ARJ runfile is
probably damaged.

A DOS critical error has occurred. ARJ has trapped this error condition
and returned a error.

This ARJ archive has been damaged or corrupted. The contents of the
archive are not in the same condition as when it was created.

The ARJ delete command requires that a filename or wildspec be

specified on the command line. It does not assume "*.*".

Frei verwendbar Seite 47

 ARJ Fehlertexte

ARJ has detected a version 1 ARJ-SECURITY anvelope. ARJ has not

verified the validity of the ARJ-SECURITY envelope because of the
obsolescence of version 1 envelopes.

The maximum pathname length is limited in size to <number> characters.

The number of filenames encountered by ARJ has exceeded the

documented limited of <number> filenames.

ARJ is skipping the current file because it is password encrypted (garbled)

and no password has been specified on the command line with the "-g"
option.

ARJ has encountered <number> of non-fatal errors.

The small self-extractor module does not support the extraction of garbled
files.

The file description header record in the archive is damaged. This cannot
be fixed. The use of the "-jr" option will allow the recovery of files after the
damaged section.

The specified <command> is not a valid ARJ command.

This error should never happen.

The <date> contains an invalid date. It should be specified in

YYMMDDHHMMSS format where YY represents two digit year, MM
represents the month, DD represents the day, HH represents the hour,
MM represents the minutes, and SS represents the seconds.

ARJ has detected a sequence error in a series of multiple volume

archives. This error should never occur.

The switch option <option> is not a valid option.

The -je or -je1 switch was used with a non-modification command.

The specified volume size was too small. Only 360,720,1200, and 1440
are acceptable abbreviations.

A filename must be specified for <command>

The modification af ARJ multiple volume archives is not supported of

recommended. You can use the "-vu" option to override this prohibition.
Do so at your own risk.

The ARJ order command does not accept wildcards.

This message is displayed when the filename in the archive is not found
on disk.

This message is displayed when the contents of the filename in the

archive does not match the contents of the same filename on disk.

Frei verwendbar Seite 48

 ARJ Fehlertexte

ARJ has run out of memory and cannot store the name <filename>.
Specifying fewer filenames or using a listfile are two ways to work around
the lack of memory. The new "-hm" option sets ARJ to use disk space to
store avoiding this memory problem.

This message is displayed if you try to restart a multiple volume archival

process that did not about but actually completed.

At least one search string must be specified for the ARJ "w" command.

The ARJ self-extraction modules do not support extraction of files

compressed with the "-m4" option.

Self-explanatory.

Self-explanatory.

Self-explanatory.

This error should not happen. Please report this problem.

There is not enough small model memory for ARJ to complete iis
operation. It can occur if there is a large amount of enviroment space
allocated to enviroment variables. the use of "COMMAND /C/E:200 ARJ
<command>..." can work around this problem.

The "-g" option requires the specification of a password.

The two passwords entered did not match exactly.

...

ARJ could not set the volume lable to the volume lable stored in the
archive. This can happen if the volume label in the archive is not standard
DOS volume label.

This error should not happen. Please report this problem.

This message is displayed when the option (-he1) has been specified and
ARJ has just accessed an ARJ archive that has an ARJ-SECURITY
envelope on it. This does NOT indicate the validity or integrity of the ARJ-
SECURITY envelope.

The ARJ small self-extraction module (-je1) does not support extraction of
files compressed in text mode (-t1).

This ARJ archive has been damaged or corrupted. The contents of the
archive are not in the same condition as when it was created.

This ARJ archive has been ARJ-SECURED and most probably is in the
same condition as when it was created.

ARJ has encountered an unknown file type in the archive. You may need
a newer version of ARJ to process this archive.

Frei verwendbar Seite 49

 ARJ Fehlertexte

ARJ has encountered an unknown compression method in the archive.

You may need a newer version of ARJ to process this archive.

ARJ has encountered an unknown extraction version in the archive. You

may need a newer version of ARJ to process this archive.

ARJ is testing the integrity of the ARJ-SECURITY envelope on the

archive. If the envelope has been corrupted or damaged, ARJ will display
a message to that effect.

The ARJ self-extraction modules, ARJSFX and ARJSFX, do not support

the extraction of volume labels.

Self-explanatory.

Frei verwendbar Seite 50

 SQLANY-Fehler

Nr. Datum Problembeschreibung/ CS-Aktivität

Beim Booten Meldung: S7udbex.dll ist verknüpft mit

1 22.07.1997 dem fehlenden Export WSOCK32.DLL
2 15.07.1997
3 29.07.1997
4 02.06.1997
5 02.06.1997

1 21.07.1997 Beim Booten S7ubtoox.exe wird nicht gestartet

1 15.07.1997 Beim Booten wird DFÜ-Netz gestartet

1 30.06.1997 Beim Booten Meldung: dbl50t.dll nicht gefunden

2 30.06.1997
3 16.06.1997
4 16.05.1997
5 13.05.1997
6 12.05.1997
7 07.05.1997
8 02.05.1997
9 28.07.1997
10 30.06.1997
11 18.07.1997

1 26.06.1997 Beim Booten öffnen sich Datenbankfenster

2 13.06.1997

1 09.07.1997 Beim Booten Meldung: Instruction at 004BF827-

Referenced Memory at FFFFFFFF the memory could
not be read from

1 07.05.1997 Beim Booten Meldung: RESOURCE.DLL

ODBCINT.DLL is not valid

1 05.08.1997 Beim Booten wird MS-Dos Fenster gestartet

1 01.10.1997 Beim Booten Meldung: DBL50T.DLL ist verknüpft mit

der fehlernen .. DBL50T.DLL

1 10.07.1997 Beim Starten von TONLINE Meldung: der 32

Bit WINSOCK Support konnte nicht installiert werden
da die Datei zur Zeit in Benutzung ist

1 07.07.1997 Beim Starten von Word o. Excel hängt sich Rechner

auf im Taskmanager ist POINT32 aktiv (Powerpoint)

1 06.05.1997 Beim Starten des Programms Fehler: dbl50t.dll

in Regestrie fehlen SQLANY-Einträge

1 08.08.1997 Beim Start von Excel und MS WORD

es ist eine POINT32.DLL/EXE installiert

Frei verwendbar Seite 51

 SQLANY-Fehler

1 16.06.1997 Beim Runterfahren hängt sich Rechner auf

1 22.07.1997 Diagnosepuffer auslesen Meldung: kann

2 26.05.1997 S7wmedbx.dll nicht finden
3 21.05.1997

1 27.06.1997 Symboleditor läßt sich nicht starten

bei Doppelklick auf S7ubtoox.exe Meldung:
S7udbex.dll ist verknüpft mit dem fehlenden Export
WSOCK32.DLL

1 27.06.1997 Fehler mit Ereignisdatenbank S7wmedbx.dll

1 26.06.1997 256:22 interner OLE_Fehler beim

2 26.06.1997 Baugruppenzustand auslesen
1 09.04.1997 DBSRV50 und S7UBTOOX in Taskleiste
Oracle, Sybase und Smart reagieren nicht
lassen sich nicht installieren

1 17.09.1997 Beim Booten von WinNT

S7WMEDAX.EXE konnte nicht gestartet werden

Frei verwendbar Seite 52

 SQLANY-Fehler

Abhilfe/ Problembehebung Kunde Betr. betroffene Anzahl

Case Produkte
Original WSOCK32.DLL von Windows 95 besorgen
Achtung auf Zeitstempel achten Siemens 80129 1
ZWN Zahnrad 78078 1
Heller 82081 1
Siemens 63783 1
Siemens 64025 1

S7ubtoox.exe auf single stellen und alle Netze aus Phoenix 79742 1

S7ubtoox.exe auf single stellen und alle Netze aus Siemens 77940 1

SQLANY-Pfad an Path-Anweisung anhängen GIA 72836 1

oder Bayer AG 72944 1
Loginscript verändert den Suchpfad, Pfad im User MK 59959 1
Login abändern Siemens 63091 1
oder Index 58334 1
Autoexec.bat nicht Original Roll 57794 1
oder Haas 57214 1
Autoexec.bat nicht vorhanden UEG 56049 1
oder Schneider 82005 1
Autoexec.bat wird nicht abgearbeitet Bayer AG 72944 1
Giddings 79405 1

S7ubtoox.exe auf single stellen und alle Netze aus Krauss-Maffei 67726 1
Siemens 68026 1

S7ubtoox.exe auf single stellen und alle Netze aus Romero 65983 1

ODBC32.DLL sollte V250.306 sein evtl. von Venjakob 57150 1

anderem Rechner nehmen

S7ubtoox.exe auf single stellen und alle Netze aus Siemens 84269 1

Im Windows/System-Verzeichnis ist die KKW 201244

DBL50T.DLL vorhanden --> löschen

S7ubtoox.exe auf single stellen und alle Netze aus Benteck 76740 1

POINT32 beenden bzw. entfernen Siemens 75296 1

Installation von STEP 7 mit der Option UEG 56840 1

NORMAL durchführen

S7ubtoox.exe auf single stellen und alle Netze aus Siemens 1

Frei verwendbar Seite 53

 SQLANY-Fehler

S7ubtoox.exe auf single stellen und alle Netze aus Siemens 68303 1

S7ubtoox.exe auf single stellen und alle Netze aus Siemens 80012 1
Siemens 62107 1
IFA Flensburg 60490 1

Original WSOCK32.DLL von Windows 95 besorgen Elteba 72392 1

Achtung auf Zeitstempel achten

Autoexec.bat wurde nicht abgearbeitet Siemens 72223 1

SET SQLANY-Pfad in Autoexec.bat fehlt Kugler 72307 1

Siemens 71704 1
S7ubtoox.exe auf single stellen und alle Netze aus Siemens 1

C:\TMP bzw. TEMP hat gefehlt 96125 1

Frei verwendbar Seite 54

 WIN NT

Fehlertext: Fehlerursache:

DDE Server Window: S7XUDIAX.EXE -Application error

The instruction at "0x78001799" referenced memory at
"0x00000004". The memory could not be written.

Frei verwendbar Seite 55

 WIN NT

Abhilfe: Aktuell

Frei verwendbar Seite 56

TBI FFFF s7dbiem?.dll
Symbol Editor FFFD s7sym\s7yedem?.dll
GD-Konfig FFF9 s7ngd\s7lerms?.dll
Comp-IF FFF7 s7iecem?.dll
S7-Info Applikation FFF5 s7inf\s7usiem?.dll
S7HWOM FFF3 s7homem?.dll
SCL FFF1 S7scl\s7sclem?.dll
S7USS FFF0 s7uss\s7ussem?.dll
S7KAF FFE2 s7ska\s7kafem?.dll
S7DOS FFDF s7otbem?.dll
Comp-IF_V3 FFDE s7iccem?.dll
S7JSEXP FF0F S7JSEXP?.dll
S7JSWGN FF0E s7jswgn?.dll
S7JM7CG FF0D S7JM7CG?.dll
S7JS7CG FF0C S7JS7CG?.dll
S7JDBMS FF0B s7jcomf?.dll
S7JUTLS FF0A s7jcomf?.dll
S7JM7EF FF09 S7JM7EF?.dll
S7JS7EF FF08 S7JS7EF?.dll
S7JM7TI FF07 S7JM7TI?.dll
S7JS7TI FF06 S7JS7TI?.dll
S7JM7IM FF05 S7JM7IM?.dll
S7JS7IM FF04 S7JS7IM?.dll
S7JSFCA FF03 s7jsfca?.dll
S7JCFCA FF02 s7jcfca?.dll
S7JCOMF FF01 s7jcomf?.dll
cmnerr 8000 s7acerr?.dll
AUTAPI 8001 s7aaaem?.dll
s7apromx 8002 s7aprem?.dll
OM VerbList 8013 S7NLEMS?.DLL
OM Homo 8014 S7NHEMS?.DLL
RESOURCE_OM 8020 s7hrsem?.dll
S7XUT 8021 s7xut\s7xuaem?.dll
OM Symbol 8023 s7yomem?.dll
S7UMG 8024 s7umgem?.dll
OM Block 8026 s7ombem?.dll
OM Alarm 8028 s7wmxeh?.dll
s7upomx 802A s7upoem?.dll
OM Text 802B s7utoem?.dll
S7ubsdh 802C s7ubseh?.DLL
S7UVPV 802D s7uvpeh?.dll
S7UVMAP 802E S7uvmeh?.dll
DOCPRO 8030 C:\SIEMENS\STEP7\s7dpr\s7ppdem?.dll
S7ifx 8035 S7BIN\S7IFXEM?.DLL
S7OMWINX 8036 s7wierr?.dll
S7jwzlr 0 S7jwzlr?.dll
HW-Konfig 0 s7hcoem?.dll
NCM H1 DIAG 0 S7WNDHE?.DLL
NCM L2 DIAG 0 S7WNDLE?.DLL
OM VERB FMS 0 S7WNFME?.DLL
S7MSG 0 s7ums\s7umsem?.dll
Netpro 0 s7bin\s7nnems?.dll

Frei verwendbar
OM VERB UDP 0 S7WNUDE?.DLL
S7WRI 0 s7wri\s7wriem?.dll
S7asrcom 0 s7asrer?.dll
OM Fremd 0 s7noems?.dll
S7nonfgx 0 s7noems?.dll
S7 Archive-Services 0 s7arcem?.dll
OM PtP 0 S7NPEMS?.DLL
s7tgtop 0 s7topem?.dll
s7tbrow 0 s7topem?.dll
S7jthom 0 S7jthom?.dll
OM VERB FDL 0 S7WNFDE?.DLL
OM VERB RFC1006 0 S7WNRFE?.DLL
S7NAKVAX 0 s7nakva?.dll
M7Config 0 s7mfger?.dll
OM VERB ISO 0 S7WNISE?.DLL
SINEC NCMS7 0 s7wber1?.dll
S7WNSVVX 0 s7wnsvv?.dll

Frei verwendbar
 1
s7sym\s7yedeh?.hlp 3
s7ngd\s7lgdeh?.hlp 7
s7ieceh?.hlp 9
s7inf\s7usieh?.hlp 11
s7homeh?.hlp 13
S7scl\s7scleh?.hlp 15
s7uss\s7usseh?.hlp 16
s7ska\s7kafeh?.hlp 30
s7otbeh?.hlp 33
s7icceh?.hlp 34
S7JSEXP?.hlp 241
S7Hlp\s7jswgn?.hlp 242
S7JM7CG?.hlp 243
S7JS7CG?.hlp 244
s7jcomf?.hlp 245
s7jcomf?.hlp 246
S7JM7EF?.hlp 247
S7JS7EF?.hlp 248
S7JM7TI?.hlp 249
S7JS7TI?.hlp 250
S7JM7IM?.hlp 251
S7JS7IM?.hlp 252
s7jsfca?.hlp 253
s7jcfca?.hlp 254
s7jcomf?.hlp 255
s7aceeh?.hlp 256
s7aaaeh?.hlp 257
s7apreh?.hlp 258
S7NLEHP?.HLP 275
S7NHEHP?.HLP 276
s7hrseh?.hlp 288
s7xut\s7xuteh?.hlp 289
s7yomeh?.hlp 291
s7umgeh?.hlp 292
s7ombeh?.hlp 294
s7wm_eh?.hlp 296
s7upoeh?.hlp 298
s7utxeh?.hlp 299
s7ubseh?.HLP 300
s7uvaeh?.hlp 301
S7uvmeh?.hlp 302
C:\SIEMENS\STEP7\s7dpr\s7ppdeh?.hlp 304
S7BIN\S7IFXEH?.HLP 309
310
S7Hlp\S7jwzlr?.hlp 732
s7hcoeh?.hlp 1230
1417
1419
S7WNFME?.HLP 1420
s7ums\s7umseh?.hlp 1489
s7bin\s7nnehp?.hlp 2263

Frei verwendbar
S7WNUDE?.HLP 2443
s7wri\s7wrieh?.hlp 2511
s7asreh?.hlp 2517
s7noehp?.hlp 2775
s7noehp?.hlp 2775
s7arceh?.hlp 3020
S7NPEHP?.HLP 3225
s7topeh?.hlp 3280
s7topeh?.hlp 3280
S7Hlp\S7jthom?.hlp 3283
S7WNFDE?.HLP 3463
S7WNRFE?.HLP 3467
s7nakve?.hlp 3785
s7mfgeh?.hlp 4049
S7WNISE?.HLP 4495
4502
s7wnsve?.hlp 4578

Frei verwendbar
 a

Fehlernummer:Fehlertext: Fehlerursache:

Frei verwendbar Seite 61

 a

Abhilfe: Aktuell

Frei verwendbar Seite 62