Appendix   
A.2 System alarms 
  OP 73micro, TP 177micro (WinCC flexible) 
152  Operating Instructions, 09/2007, 6AV6691-1DF01-0AB0 
Meaning of the system alarms 
 
Number  Effect/cause  Remedy 
10000  The print job could not be started or was canceled 
due to an unknown error. Faulty printer setup. Or: 
Access to the network printer is not allowed. 
Power supply failure during data transfer. 
Check the printer settings, cable connections and the 
power supply. 
Set up the printer once again. Obtain a network printer 
authorization. 
If the error persists, contact the Hotline! 
10001  No printer is installed or a default printer has not 
been set up. 
Install a printer and/or select it as the default printer. 
10002  Overflow of the graphics buffer for printing. Up to 
two images are buffered. 
Allow sufficient intervals between successive print jobs. 
10003  Images can now be buffered again.  - 
10004  Overflow of the buffer for printing lines in text mode 
(e.g.alarms). Up to 1000 lines are buffered. 
Allow sufficient intervals between successive print jobs. 
10005  Text lines can now be buffered again.  - 
10006  The Windows printing system reports an error. 
Refer to the output text and the error ID to 
determine the possible causes. Nothing is printed 
or the print is faulty.  
Repeat the action if necessary.  
20010  An error has occurred in the specified script line. 
Execution of the script was therefore aborted. Note 
the system alarm that may have occurred prior to 
this.  
Select the specified script line in the configuration. 
Ensure that the tags used are of the allowed types. 
Check system functions for the correct number and types 
of parameters. 
20011  An error has occurred in a script that was called by 
the specified script.  
Execution of the script was therefore aborted in the 
called script.  
Take the system alarm that may have occurred 
prior to this into account.  
In the configuration, select the script that has been called 
directly or indirectly by the specified script.  
Ensure that the tags used are of the allowed types.  
Check the system functions for the correct number and 
type of parameters. 
20012  The configuration data is inconsistent. The script 
could therefore not be generated. 
Recompile the configuration. 
20013  The scripting component of WinCC flexible Runtime 
is not correctly installed. Therefore, no scripts can 
be executed. 
Reinstall WinCC flexible Runtime. 
20014  The system function returns a value that is not 
written in any return tag. 
Select the specified script in the configuration. 
Check if the script name has been assigned a value. 
20015  Too many successive scripts have been triggered 
in short intervals. When more than 20 scripts are 
queued for processing, any subsequent scripts are 
rejected. In this case, the script indicated in the 
alarm is not executed. 
Find what is triggering the scripts. Extend the times, e.g. 
the polling time of the tags which trigger the scripts.  
30010  The tag could not accept the function result, e.g. 
when it has exceeded the value range. 
Check the tag type of the system function parameter. 
30011  A system function could not be executed because 
the function was assigned an invalid value or type 
in the parameter. 
Check the parameter value and tag type of the invalid 
parameter. If a tag is used as a parameter, check its 
value. 
40010  The system function could not be executed since 
the parameters could not be converted to a 
common tag type. 
Check the parameter types in the configuration.