Product Knowledge Base

Space shortcuts

Page tree

Messages for the Scheduler Package

Code Text
SCHEDULER-104 en: There is an error such as the start time set in the begin="(1)" attribute is later than the end time set in end="(2)"

- Example -

An error results from, for example <period begin="23:00" end="01:00"/> as the start and end times must lie within the same day, i.e. between 00:00 und 24:00.

See <period>.

de: Beginnzeit (1) liegt nach der Endezeit (2), oder anderer Fehler bei Attributen begin= und end=

- Beispiel für eine nähere Beschreibung -

Fehlerhaft ist zum Beispiel <period begin="23:00" end="01:00"/>. Eine Periode muss innerhalb eines Kalendertages liegen, zwischen 00:00 und 24:00.

Siehe <period>.

SCHEDULER-105 en: Unknown command: <(1)>
de: Unbekanntes Kommando: <(1)>

Siehe XML-Kommandos.

SCHEDULER-106 en: Unknown command for task: (1)
de: Unbekanntes Kommando an eine Task: (1)
SCHEDULER-107 en: Missing script
de: Skript fehlt
SCHEDULER-110 en: Unknown task state: (1)
de: Unbekannter Zustand einer Task: (1)
SCHEDULER-113 en: Unexpected XML tag: (1)
de: XML-Tag (1) ist hier falsch
SCHEDULER-115 en: Missing XML configuration file, option -config=FILENAME.XML
de: Die XML-Konfigurationsdatei ist nicht angegeben. Option -config=DATEINAME.XML
SCHEDULER-116 en: XML configuration contains no <config spooler_id=(1)> element
de: XML-Konfiguration enthält kein Element <config spooler_id=(1)>
SCHEDULER-117 en: Cannot use different scripting languages in the same scripting engine
de: Verschiedene Skriptsprachen können nicht in derselben Scripting Engine verwendet werden
SCHEDULER-119 en: There is no security level "(1)"
de: Security level "(1)" gibt es nicht
SCHEDULER-120 en: Script has reported an error: (1)
de: Skript meldet Fehler: (1)
SCHEDULER-121 en: The security settings do not allow this operation (or JobScheduler is waiting for database)
SCHEDULER-122 en: Task terminated
de: Task ist beendet
SCHEDULER-125 en: task.wait_until_terminated() cannot be called in its own thread. Deadlock.
de: task.wait_until_terminated() kann nicht im selben Thread verwendet werden. Deadlock.
SCHEDULER-130 en: Job (1) has already been defined
de: Job (1) ist bereits definiert
SCHEDULER-136 en: No history
de: Keine Historie
SCHEDULER-139 en: Operation is not possible when using a plain text file for history
de: Operation bei Historie in Textdatei nicht möglich
SCHEDULER-140 en: Task logged error: (1)
de: Task hat Fehler protokolliert: (1)
SCHEDULER-141 en: History has been suppressed for job (1) (history=no)
de: Die Historie für Job (1) ist ausgeschaltet (history=no)
SCHEDULER-143 en: Task cannot start because it has no start time and no valid <run_time>
de: Element <run_time> sieht keine Periode für eine Task ohne Startzeit vor
SCHEDULER-145 en: <script> com_class= and language= cannot be combined
de: <script> com_class= und language= können nicht zugleich angegeben werden
SCHEDULER-146 en: Missing script
de: Das Skript fehlt
SCHEDULER-147 en: job(1) cannot accept orders because it has not been declared with <job order="yes">
SCHEDULER-148 en: 'object(1)' has been initialized already and cannot be modified
SCHEDULER-149 en: There is no job in job chain "(1)" for the state "(2)"
de: Für den Zustand "(2)" ist kein Job in der Jobkette (1) definiert
SCHEDULER-150 en: The state "(1)" has already assigned a job in job chain (2)
de: Für den Zustand "(1)" ist bereits ein Job in der Jobkette (2) definiert
SCHEDULER-151 en: Job chain is not in use (missing add_job_chain() or job chain is to be removed)
de: Jobkette ist außer Betrieb (add_job_chain() fehlt oder Jobkette wird entfernt)
SCHEDULER-152 en: Job "(1)" is not in job chain "(2)"
de: Job "(1)" ist nicht in der Jobkette "(2)"
SCHEDULER-153 en: 'object(1)' is not in state '(2)'
SCHEDULER-155 en: A temporary job cannot accept orders
de: Ein temporärer Job kann keine Aufträge annehmen
SCHEDULER-156 en: (1) is not in Order_queue(2)
de: (1) ist nicht in der Auftragswarteschlange des Jobs "(2)"
SCHEDULER-157 en: (1) is not in a job chain
de: (1) ist nicht in einer Jobkette
SCHEDULER-159 en: Id and priority of an order placed in an order queue cannot be changed
de: Id und Priorität eines Auftrags können nicht mehr geändert werden, wenn er in einer Auftragsliste steht
SCHEDULER-160 en: There is already a objecttype(1) '(2)'
SCHEDULER-161 en: There is no objecttype(1) '(2)'
SCHEDULER-162 en: There is no order (1) in job chain "(2)"
de: Auftrag (1) ist nicht in der Jobkette (2)
SCHEDULER-163 en: (1) is not in an order queue
de: (1) ist nicht einer Auftragswarteschlange
SCHEDULER-164 en: <show_... what="(1)">: invalid value for attribute what=
de: <show_... what="(1)">: Ungültige Angabe für Attribut what
SCHEDULER-166 en: <script> java_class= and language= cannot be combined
de: <script> java_class= und language= können nicht zugleich angegeben werden
SCHEDULER-167 en: A program source cannot be set with <script> com_class= or java_class=
de: Bei <script> com_class= oder java_class= kann die Programmquelle nicht angegeben werden
SCHEDULER-168 en: com_class= and java_class= cannot be combined in <script>
de: In <script> ist com_class= und java_class= zusammen angegeben
SCHEDULER-172 en: This kind of script (scripting engine, Perl, COM or Java) is not possible here
de: Die Skriptart (Scripting Engine, Perl, COM oder Java) ist hier nicht möglich
SCHEDULER-173 en: Missing script
de: Skript fehlt
SCHEDULER-174 en: Method "(1)" is missing in class "(2)"
de: Methode (1) der Klasse (2) fehlt
SCHEDULER-179 en: <process> task did not terminate. pid=(1)
de: <process>-Task hat sich nicht beendet. pid=(1)
SCHEDULER-182 en: Unexpected XML element <(1)>
SCHEDULER-183 en: Scheduler cannot start because spooler_init() in 'scheduler_script(1)' returned false
SCHEDULER-184 en: Scheduler database cannot be accessed due to a database problem
de: Die Scheduler-Datenbank ist wegen eines Datenbankproblems gerade nicht geöffnet
SCHEDULER-186 en: (1) is already in job chain (2)
de: (1) ist bereits in der Jobkette (2)
SCHEDULER-187 en: Order.setback(): An order can only be set back when it is being executed by a task
de: Order.setback(): Ein Auftrag kann nur zurückgestellt werden, während eine Task ihn ausführt
SCHEDULER-188 en: Order.setback() and Order.state= cannot be combined
de: Order.setback() und Order.state= können nicht zusammen gerufen werden, das ist Unsinn
SCHEDULER-191 en: separate_process: Unexpected state (2) in (1)
de: separate_process: Unerwarteter Zustand (2) in (1)
SCHEDULER-194 en: process_class and separate_process cannot be combined
de: process_class und separate_process können nicht kombiniert werden
SCHEDULER-196 en: use_engine="(1)" is deprecated
de: use_engine="(1)" ist veraltet
SCHEDULER-197 en: Module::java_method_id((1)): unknown Java class
de: Module::java_method_id((1)): Java-Klasse ist unbekannt
SCHEDULER-198 en: Missing variable name
de: Variablenname fehlt
SCHEDULER-199 en: Module instance has been closed
de: Die Modulinstanz ist geschlossen
SCHEDULER-200 en: Remote instance has been closed
de: Die Remoteinstanz ist geschlossen
SCHEDULER-201 en: Missing working directory when calling Java compiler
de: Das Arbeitsverzeichnis zum Aufruf des Java-Compilers fehlt
SCHEDULER-202 en: Connection to task has been lost, state=(1): (2)
de: Verbindung zur Task verloren, state=(1): (2)
SCHEDULER-203 en: Module instance in the server has been closed
de: Die Modulinstanz im Server ist geschlossen
SCHEDULER-204 en: Job "(1)" is in error state. (2)
de: Der Job "(1)" ist im Fehlerzustand. (2)
SCHEDULER-205 en: No database given (entry db= in factory.ini)
SCHEDULER-207 en: Task (1) is unknown (and not noted in the history)
de: Task (1) unbekannt (auch in der Historie)
SCHEDULER-208 en: Only a date without a time is allowed
de: Hier ist nur ein Datum ohne Uhrzeit möglich
SCHEDULER-209 en: Too many objects for Microsoft Windows MsgWaitForMultipleObjects(). MAXIMUM_WAIT_OBJECTS-1=(1) has been reached. Operation is not executable
de: Das Microsoft Windows-Limit der Objekte, auf die gewartet werden kann (TCP-Verbindungen, beobachteten Verzeichnisse etc.) von MAXIMUM_WAIT_OBJECTS-1=(1) ist erreicht. Die Operation ist nicht ausführbar.
SCHEDULER-210 en: Too many processes. The number of processes is limited to (1)
de: Zuviele Prozesse. Die Zahl der Prozesse ist auf (1) begrenzt
SCHEDULER-212 en: Missing entry [spooler] html_dir= in file factory.ini
de: Eintrag [spooler] html_dir= fehlt in der Datei factory.ini
SCHEDULER-213 en: Error in HTTP header: expecting (1)
de: Fehler beim Lesen des HTTP-Kopfs: (1) erwartet
SCHEDULER-214 en: Forbidden path in HTTP request
de: Unzulässiger Pfad in HTTP-Anforderung
SCHEDULER-215 en: Unknown or terminated task (1)
de: Task (1) unbekannt oder beendet
SCHEDULER-217 en: order(1) is being processed by task(2)
de: auftrag(1) ist in Bearbeitung durch task(2)
SCHEDULER-218 en: Subprocess pid=(2) has been terminated with exit code=(1). Command=(3)
de: Subprocess pid=(2) hat sich mit exit code=(1) beendet. Command=(3)
SCHEDULER-219 en: Subprocess pid=(2) has been terminated with signal (1). Command=(3)
de: Subprocess pid=(2) hat sich mit Signal (1) beendet. Command=(3)
SCHEDULER-220 en: <run_time (1)> cannot be carried out for an order
de: <run_time (1)> ist für einen Auftrag nicht möglich
SCHEDULER-221 en: <day day="(1)">: only the days from (2) to (3) are possible
de: <day day="(1)">: Nur die Tage (2) bis (3) sind möglich
SCHEDULER-222 en: This command <(1)> is only executable by way of a TCP connection
de: Das Kommando <(1)> kann nur über eine TCP-Verbindung gegeben werden
SCHEDULER-223 en: Supervisor has reported an error: (1)
SCHEDULER-224 en: Supervisor has closed the connection
de: Haupt-Scheduler hat Verbindung geschlossen
SCHEDULER-225 en: start_new_file() is only applicable for the main protocol
de: start_new_file() ist nur fürs Hauptprotokoll möglich
SCHEDULER-226 en: Order has not been processed because the task has been terminated before the processing step (spooler_process())
de: Der Auftrag ist nicht verarbeitet worden ist, weil die Task vor dem ersten Jobschritt (spooler_process()) beendet worden ist
SCHEDULER-227 en: Scheduler script has logged an error: (1)
de: Scheduler-Skript hat Fehler protokolliert: (1)
SCHEDULER-230 en: Job "(1)" is to be removed - it is not longer usable
de: Der Job "(1)" wird entfernt, er kann nicht mehr verwendet werden
SCHEDULER-231 en: Missing attribute (2) in XML element <(1)>
de: Attribut (2) fehlt im XML-Element <(1)>
SCHEDULER-232 en: Attribute <xml_element_name(1) (2)="(3)"> is not allowed here
SCHEDULER-234 en: The <job (1)="..."> attribute cannot be overwritten
de: <job (1)="..."> Attribut kann nicht überschrieben werden
SCHEDULER-235 en: Unknown web service: "(1)"
de: Web-Dienst "(1)" ist unbekannt
SCHEDULER-236 en: Web service "(1)" has already been declared
de: Web-Dienst "(1)" ist bereits bekannt
SCHEDULER-237 en: XSLT stylesheet "(1)" does not deliver a result
de: XSLT-Stylesheet "(1)" liefert kein Ergebnis
SCHEDULER-238 en: Web service or alias for url_path="(1)" has already been declared
de: Web-Dienst für url_path="(1)" ist bereits bekannt
SCHEDULER-239 en: XML root element <(1)> expected
SCHEDULER-240 en: Order has not been assigned to a web service
de: Auftrag ist keinem Webdienst zugeordnet
SCHEDULER-241 en: Task has not been assigned to a web service
de: Task ist keinem Webdienst zugeordnet
SCHEDULER-242 en: forward_xslt_stylesheet (1) does not deliver <service_request>
de: forward_xslt_stylesheet (1) liefert nicht <service_request>
SCHEDULER-243 en: Property (1) is fixed and is no longer modifiable
de: Eigenschaft (1) ist fixiert, sie kann nicht mehr geändert werden
SCHEDULER-244 en: Element <content> is missing or empty
de: Element <content> fehlt oder ist leer
SCHEDULER-245 en: Element <content> has more than one child element
de: Element <content> hat mehr als ein Element
SCHEDULER-246 en: Order does not belong to a web service operation
de: Auftrag gehört nicht zu einer Web-Dienst-Operation
SCHEDULER-247 en: HTTP response has already been sent
de: HTTP-Antwort wird bereits versendet

Nach Web_service_response.send() kann Web_service_response nicht mehr geändert werden.

SCHEDULER-248 en: web_service_operation has finished and is not longer valid
de: web_service_operation ist abgeschlossen und nicht mehr gültig
SCHEDULER-249 en: Order id cannot be represented as a character string: (1)
de: Order-Id lässt sich nicht als Zeichenkette darstellen: (1)
SCHEDULER-250 en: Order state cannot be represented as a character string: (1)
de: Order-State lässt sich nicht als Zeichenkette darstellen: (1)
SCHEDULER-251 en: Order payload cannot be represented as character string: (1)
de: Order-Payload lässt sich nicht als Zeichenkette darstellen: (1)
SCHEDULER-252 en: Invalid url path - it has to begin with '/': (1)
de: Ungültiger Url-Pfad, er muss mit '/' beginnen: (1)
SCHEDULER-254 en: (1) tasks did not terminate in spite of kill (2) seconds ago. Extending deadline for (3)s
de: (1) Tasks haben sich nicht beendet trotz kill vor (2)s. Die (3)s lange Nachfrist läuft weiter
SCHEDULER-255 en: (1) tasks did not terminate in spite of kill (2) seconds ago. JobScheduler is aborting
de: (1) Tasks haben sich nicht beendet trotz kill vor (2) seconds. JobScheduler bricht ab
SCHEDULER-256 en: Deadline for terminating JobScheduler has been reached, but (1) tasks are still running
de: Frist zur Beendigung des Schedulers ist abgelaufen, aber (1) Tasks haben sich nicht beendet
SCHEDULER-257 en: Job is being removed now
de: Job wird jetzt entfernt
SCHEDULER-258 en: Job will be removed after all its tasks have terminated
de: Job wird entfernt sobald alle Tasks beendet sind
SCHEDULER-260 en: Error in JobScheduler Skript, spooler_exit(): (1)Error in JobScheduler script, spooler_exit(): (1)
SCHEDULER-261 en: Nothing done, event=(1), operations=(2)
SCHEDULER-262 en: Kill signal ((1)) received. JobScheduler is terminating
de: Abbruch-Signal ((1)) empfangen. Der JobScheduler wird beendet
SCHEDULER-263 en: Kill signal ((1)) #(2) received. what to do(3)
SCHEDULER-264 en: SCHEDULER IS TERMINATING AFTER SERIOUS ERROR
SCHEDULER-266 en: Error when writing the history: (1)
de: Fehler beim Schreiben der Historie: (1)
SCHEDULER-267 en: Error when storing the log in table (1): (2)
de: Fehler beim Schreiben des Protokolls in die Tabelle (1): (2)
SCHEDULER-268 en: Log of task (1) is not readable from database: (2)
de: Protokoll der Task (1) lässt sich nicht aus der Datenbank lesen: (2)
SCHEDULER-269 en: Error when closing the job history: (1)
de: Fehler beim Schließen der Job-Historie: (1)
SCHEDULER-271 en: Task is being terminated in favour of job (1)
de: Zugunsten des Jobs (1) wird die Task beendet
SCHEDULER-272 en: Terminating task after reaching deadline <job timeout="(1)">
de: Task wird nach nach Fristablauf von <job timeout="(1)"> abgebrochen
SCHEDULER-273 en: Killing subprocess (1)
de: Subprozess (1) wird abgebrochen
SCHEDULER-274 en: Error when killing subprocess (1): (2)
de: Subprozess (1) lässt sich nicht abbrechen: (2)
SCHEDULER-275 en: Deadline reached, killing subprocess (1)
de: Subprozess (1) wird abgebrochen, weil seine Frist überschritten ist
SCHEDULER-276 en: Could not kill task
de: Task konnte nicht abgebrochen werden
SCHEDULER-278 en: <period> ended, terminating task
de: Laufzeitperiode <period> ist abgelaufen, Task wird beendet
SCHEDULER-279 en: Process terminated with signal (1) (name(2))
de: Prozess hat mit Signal (1) (name(2)) geendet
SCHEDULER-280 en: Process terminated with exit code (1) (0x(2))
de: Prozess hat mit Exit code (1) (0x(2)) geendet
SCHEDULER-281 en: Killing process
de: Prozess wird abgebrochen
SCHEDULER-283 en: Error when loading task (1) from database: (2)
de: Task (1) aus der Datenbank ist fehlerhaft: (2)
SCHEDULER-284 en: Ignoring cmd='(1)' because job is to be removed
de: cmd='(1)' wird ignoriert, weil Job entfernt wird
SCHEDULER-285 en: Max. (1) history records are being read
de: Max. (1) Historiensätze werden gelesen
SCHEDULER-287 en: TCP connection not allowed
de: TCP-Verbindung nicht zugelassen
SCHEDULER-289 en: (1) is blocked. Trying a further (2) seconds before giving up
de: (1) ist blockiert. Wir probieren es (2) Sekunden
SCHEDULER-290 en: Timeout: No job started to execute (1), cancelling order and HTTP operation
de: Kein Job hat während der Frist begonnen (1) auszuführen, Auftrag und HTTP-Operation werden abgebrochen
SCHEDULER-291 en: Error when removing protocol file: (1)
de: Fehler beim Löschen der Protokolldatei: (1)
SCHEDULER-292 en: Missing from, to, subject or body. Suppressing email
de: Email unterdrückt, weil From, To, Subject oder der Nachrichtentext fehlt
SCHEDULER-293 en: Waiting for closing module instance ...
de: Warten auf Schließen der Modulinstanz ...
SCHEDULER-295 en: Error when loading order (1) from database: (2)
de: Auftrag (1) aus der Datenbank ist fehlerhaft: (2)
SCHEDULER-297 en: Order has been carried out without web_service_operation.send(), operation cancelled
de: Auftrag erledigt ohne web_service_operation.send(), Operation wird abgebrochen
SCHEDULER-298 en: Ignoring job=(1) because order is removed from job chain
de: job=(1) wird ignoriert, weil Auftrag bereits aus der Jobkette entfernt ist
SCHEDULER-299 en: Removing process (1) after error
de: Prozess (1) wird nach Fehler entfernt
SCHEDULER-300 en: Monitoring of directory (1) has ended after error: (2)
de: Überwachung des Verzeichnisses (1) wird nach Fehler beendet: (2)
SCHEDULER-301 en: UDP message from (1) is not allowed
de: UDP-Nachricht von (1) nicht zugelassen
SCHEDULER-302 en: Error sending e-mail: (1)
de: Fehler beim eMail-Versand: (1)
SCHEDULER-303 en: Problem with database: (1)
de: Fehler beim Zugriff auf die Datenbank: (1)
SCHEDULER-304 en: Error when reading next id (column "(2)"): (1)
de: Fehler beim Lesen der nächsten Id (Spalte "(2)"): (1)
SCHEDULER-305 en: Error when inserting into table (1): (2)
de: Fehler beim Einfügen in die Tabelle (1): (2)
SCHEDULER-306 en: Error when updating table (1): (2)
de: Fehler beim Update der Tabelle (1): (2)
SCHEDULER-307 en: Not writing history record because of already existing database problem
de: Historiensatz wird wegen vorausgegangenen Datenbankfehlers nicht geschrieben
SCHEDULER-308 en: Ignoring cancel() because response has already been sent
de: cancel() ignoriert, weil die Antwort schon übertragen wird
SCHEDULER-309 en: Error when opening database: (1)
de: Fehler beim Öffnen der Datenbank: (1)
SCHEDULER-310 en: Error when closing the database: (1)
de: Fehler beim Schließen der Datenbank: (1)
SCHEDULER-311 en: Error when processing HTTP request (1): (2)
SCHEDULER-312 en: Variable "(1)" (vt=(2)) cannot be converted to Text: (3)
SCHEDULER-313 en: Cannot store order in database: (1)
SCHEDULER-316 en: <web_service name="(1)"/>: attributes job_chain=/timeout= and request/response/forward_xslt_stylesheet= cannot be combined
SCHEDULER-318 en: Option -env=NAME=VALUE: missing '=' between name and value: -env="(1)"
SCHEDULER-319 en: XML-Element <(1)> is not possible here
SCHEDULER-320 en: Could not send mail
SCHEDULER-321 en: Mail has been sent, but an error occurred when processing the mail queue: (1)
SCHEDULER-322 en: min_tasks=(1) is greater than max_tasks=(2)
SCHEDULER-323 en: exit_code is available only when task module is loaded
SCHEDULER-324 en: Invalid value for attribute exit_code="(1)" in <commands>
SCHEDULER-325 en: Attribute exit_code is not applicable here

See <commands>.

SCHEDULER-326 en: <commands on_exit_code="(1)">: <commands> for exit code (2) is already defined
SCHEDULER-327 en: Last error occurred when executing command: xml_command(1)
SCHEDULER-328 en: Executing <commands on_exit_code="(1)">:
SCHEDULER-329 en: <copy_params from="(1)"/>: requested parameters are not available
SCHEDULER-330 en: job(1) could not be initialized:
error(2)
SCHEDULER-331 en: Scheduler is terminating after error (see last error line)
SCHEDULER-332 en: Error in (1) while switching to state=(2): (3)
SCHEDULER-333 en: "now+SECONDS" expected in "(1)"
SCHEDULER-334 en: Error when building mail: (1)
SCHEDULER-335 en: Only "yes", "no" and a number are allowed with (1)="(2)": error(3)
SCHEDULER-336 en: Only "yes", "no" and a list of signal names are allowed with (1)="(2)": error(3)
SCHEDULER-337 en: Signal (1) is unknown on this operating system and is ignored
SCHEDULER-338 en: Order.payload is not a Variable_set
SCHEDULER-339 en: File does not exist and can therefore neither be moved nor removed: (1)
SCHEDULER-340 en: File still exists. Order has been set on the blacklist
SCHEDULER-342 en: There is no job between order source and order sink in job_chain(1)
SCHEDULER-343 en: This is no file order: order(1)
SCHEDULER-344 en: order.id has more than (2) characters: (1)
SCHEDULER-345 en: order.id has more than (2) characters, the limit of your database column (3) is: (1)
SCHEDULER-346 en: Due to previous error the path will be ignored: (1)
SCHEDULER-347 en: Path has been removed from the blacklist: (1)
SCHEDULER-348 en: Database doesn't deliver width of column (1).(2)
SCHEDULER-349 en: Database column (1).(2) could not be expanded
SCHEDULER-350 en: Width of database column (1).(2) is unknown. We assume (3)
SCHEDULER-351 en: <modify_order_... setback="(1)">: Invalid value for attribute setback=
SCHEDULER-353 en: No immediate response from command <(1)>
SCHEDULER-354 en: Scheduler Java classes (sos.spooler.jar version(1) expected) are not up to date: (2)
SCHEDULER-355 en: SQL update statement changed more than one record, count(1): statement(2)
SCHEDULER-357 en: This is a member of a cluster (option -exclusive or -distributed-orders), and therefore needs role 'scheduler'
SCHEDULER-359 en: For an exclusive or distributed Scheduler, the database (1) is not supported
SCHEDULER-360 en: Error when accessing database table (1)
SCHEDULER-361 en: No database
SCHEDULER-362 en: Scheduler is aborting because it has become inactive
SCHEDULER-363 en: Error when creating SQL table (1): (2)
SCHEDULER-365 en: Illegal character in -id=(1)
SCHEDULER-367 en: Scheduler is aborting because it has lost its exclusivity
SCHEDULER-368 en: Option (1) needs (2)
SCHEDULER-369 en: Option (1) conflicts with (2)
SCHEDULER-370 en: Operation can only be performed on a distributed orders Scheduler
SCHEDULER-371 en: DATABASE INTEGRITY IS BROKEN
SCHEDULER-372 en: Exclusivity has been stolen by JobScheduler member '(1)'
SCHEDULER-373 en: UNEXPECTED DEACTIVATION BY JOBSCHEDULER MEMBER (1)
SCHEDULER-374 en: In job_chain(1), state '(2)' has no job
SCHEDULER-375 en: Order is distributed and therefore does not support operation '(1)'
SCHEDULER-376 en: For a distributed order, this operation is not possible
SCHEDULER-377 en: After own late heart beat, JobScheduler member '(1)' has taken exclusiveness
SCHEDULER-378 en: After own late heart beat, this JobScheduler has been deactivated and the occupied orders have been freed by JobScheduler member '(1)'
SCHEDULER-379 en: order(1) is occupied by JobScheduler member '(2)'
SCHEDULER-380 en: job_chain orders_recoverable="no" cannot be combined with distributed="yes", in (1)
SCHEDULER-381 en: Scheduler is not yet active and cannot execute the operation
SCHEDULER-384 en: job_chain(1) is distributed and therefore does not support operation '(2)'
SCHEDULER-385 en: Deletion of order in database has failed
SCHEDULER-386 en: Last heart beat was time(1), (2) seconds ago. Something is delaying JobScheduler execution, the JobScheduler is aborted immediately
SCHEDULER-389 en: This order stored in database is distributed and cannot be used in a non-distributed job chain
SCHEDULER-390 en: More than (1) nested includes in (2)
SCHEDULER-391 en: Invalid value '(2)' for setting '(1)'. Allowed values are: (3)
SCHEDULER-392 en: heart_beat_warn_timeout=(1) seconds has to be lower than heart_beat_own_timeout=(2), which has to be lower than heart_beat_warn_timeout=(3) seconds
SCHEDULER-393 en: Error when calling <run_time> function '(1)': (2)
SCHEDULER-394 en: <run_time>-Function '(1)' returned start time (2) which is earlier than the requested beginning (3)
SCHEDULER-396 en: Job has not yet reached state '(1)' for operation (2)
SCHEDULER-397 en: A distributed order does not support (1)
SCHEDULER-398 en: After last error, next_start_function='(1)' will no longer be executed for this <run_time>
SCHEDULER-399 en: Error in include_xml_element(1):
(2)
SCHEDULER-401 en: Unknown 'object(1)'
SCHEDULER-403 en: There is no valid state for job chain node state='(1)', action='next_state' (circular next_state)
SCHEDULER-405 en: Setting state='(1)' is not possible while job chain has state '(2)'
SCHEDULER-406 en: Error in job chain node state='(1)': (2)
SCHEDULER-407 en: Attribute (1) is empty
SCHEDULER-408 en: <(1) (2)=...> cannot be changed
SCHEDULER-409 en: XML tag <(1)> expected, instead of <(2)>
SCHEDULER-412 en: Job chains can only be nested once
SCHEDULER-413 en: Nested job chains cannot be combined with distributed orders
SCHEDULER-414 en: There is a circular nesting of job chains: (1)
SCHEDULER-415 en: Error when trying to continue in next job chain: (1)
SCHEDULER-416 en: '(1)' is already known
SCHEDULER-417 en: Invalid name: '(1)'
SCHEDULER-419 en: New Process_class.max_processes=(1) is below current number of processes=(2)
SCHEDULER-420 en: Negative value is not allowed for (1)
SCHEDULER-422 en: 'object(1)' has already been added
SCHEDULER-424 en: '(1)' is being removed before '(2)'
SCHEDULER-426 en: 'job_chain(2)' and 'job_chain(3)' cannot be combined, because of duplicate order id '(1)'
SCHEDULER-427 en: Invalid MD5 hexadecimal coded password for HTTP user '(1)'
SCHEDULER-428 en: Error when reading base file 'path(1)' (timestamp(2)):
error(3)
SCHEDULER-429 en: Current name of '(1)' is fixed and cannot be changed to '(2)'
SCHEDULER-430 en: 'object type(1) name(2)' is unknown
SCHEDULER-431 en: Error when processing configuration directory:
error(1)
SCHEDULER-432 en: object type(1) has no name
SCHEDULER-433 en: 'object(1)' is not in any folder and cannot be replaced or removed
SCHEDULER-434 en: Error when closing 'object(1)':
error(2)
SCHEDULER-435 en: Standing order filename has not expected syntax jobchain,orderid.order.xml: filename(1)
SCHEDULER-436 en: Order id in <order> is different from order id in configuration filename
SCHEDULER-437 en: Attribute job_chain="(1)" is not empty and differs from Job_chain '(2)' in configuration filename
SCHEDULER-438 en: Invalid Job_chain_node for add_order() with state='(1)'
SCHEDULER-439 en: Error when removing after base file 'path(1)' has been removed:
error(3)
SCHEDULER-440 en: Definition of object(1) is incomplete
SCHEDULER-441 en: Invalid value in <element(1) attribute(2)="(3)">
SCHEDULER-442 en: Attribute attribute(1) cannot be combined with attribute(2)
SCHEDULER-443 en: <month month="(1)"> has been defined already
SCHEDULER-445 en: Invalid weekday '(1)'
SCHEDULER-446 en: <weekday day="(1)" which="(2)" has been defined already
SCHEDULER-447 en: Error in job_monitor(1):
error(2)
SCHEDULER-448 en: File '(1)' cannot be read, because it is bigger than (2)MB
SCHEDULER-449 en: Syntax error in order parameters file environment_variable_name(1): Missing '=' after variable name
SCHEDULER-450 en: Java file '(1)' could not be deleted
SCHEDULER-451 en: Database check failed, database is not useable. error(1)
SCHEDULER-452 en: Database does not correctly store test values:
(1) (written value)
(2) (read value)
SCHEDULER-453 en: Database does not respect rollback command
SCHEDULER-454 en: Remote configuration directories '(1)' and '(2)' refer to the same IP number
SCHEDULER-455 en: No configuration directory for '(1)'
SCHEDULER-456 en: Invalid response from supervisor
SCHEDULER-457 en: Remote JobScheduler '(1)' has not been registered
SCHEDULER-458 en: Remote JobScheduler has not sent a notification for (1)s and has been deregistered
SCHEDULER-459 en: Error in dependant after '(1)' has been loaded:
(2)
SCHEDULER-460 en: object(1) is centrally defined and cannot be locally overwritten
SCHEDULER-461 en: Path reaches beyond root (too many '..'): (1)
SCHEDULER-462 en: Attribute live_file= is not possible here. Use attribute file=
SCHEDULER-463 en: schedule(1): substituted 'schedule(2)' is a substitute
SCHEDULER-464 en: schedule(1): valid_from="(2)"> is not before valid_to="(3)"
SCHEDULER-465 en: 'schedule(1)' overlaps schedule(2)
SCHEDULER-466 en: 'schedule(1)' is a substitute for another schedule and cannot be used directly
SCHEDULER-467 en: Attribute 'attribute(1)' is only valid with attribute 'attribute(2)'
SCHEDULER-468 en: Using this call is not possible in this context
SCHEDULER-469 en: try_hold_lock() or try_hold_lock_non_exclusive() has failed and call_me_again_when_locks_available() has not been called
SCHEDULER-470 en: Path is not absolute: (1)
SCHEDULER-471 en: Not supported character for encoding '(1)'
SCHEDULER-472 en: Unknown subsystem "(1)"
SCHEDULER-473 en: operation is not supported for distributed orders: '(1)'
SCHEDULER-474 en: Workload JobScheduler is not responding to UDP message since (1) ((2)s). Workload scheduler's configuration can not be updated.
SCHEDULER-475 en: java_options and java_class_path can only be set in primary XML configuration
SCHEDULER-477 en: Could not re-open log file. Following lines are not written to this file. (2)
SCHEDULER-478 en: Could not re-open '(1)' log file. Following lines are lost. (2)
SCHEDULER-479 en: No entry config/@spooler_id='(1)' found in configuration file 'scheduler.xml'.
SCHEDULER-480 en: No appropriate config element found in scheduler.xml - please remove attribute @spooler_id of the config-element or start JS with the appropriate -id option.
SCHEDULER-481 en: Method '(1)' with signature '(2)' is not implemented.
SCHEDULER-483 en: Order parameter 'scheduler.remote_scheduler' cannot be used in a cluster (option -exclusive or -distributed-orders)
SCHEDULER-484 en: Order parameter 'scheduler.remote_scheduler' can be used only for shell script jobs and is ignored for API jobs
SCHEDULER-485 en: Missing JobScheduler ID (spooler_id="" or -id)
SCHEDULER-486 en: Self-referencing dependency (1)
SCHEDULER-487 en: Role '(1)' needed for this operation
SCHEDULER-488 en: This remote JobScheduler '(1)' is not accessible: (2)
SCHEDULER-489 en: No remote JobScheduler is accessible. Waiting before trying again
SCHEDULER-490 en: The Windows operating system does not support Unix signals (like SIGTERM). kill_task with timeout > 0 is not supported
SCHEDULER-491 en: The process class ((1)) of an API task cannot be changed (to (2)) between two order steps
SCHEDULER-900 en: Scheduler (1) is starting with (2), pid=(3)
de: Scheduler (1) startet mit (2), pid=(3)
SCHEDULER-902 en: state=(1)
SCHEDULER-904 en: Tasks have (1) seconds to terminate
de: Die Tasks haben (1)s sich zu beenden
SCHEDULER-906 en: Restarting Scheduler: (1)
SCHEDULER-907 en: Opening database: (1)
de: Datenbank wird geöffnet(1)
SCHEDULER-908 en: Column (2) is being added to database table (1): (3)
de: Datenbank-Tabelle (1) wird um die Spalte (2) erweitert: (3)
SCHEDULER-909 en: Creating database table (1)
de: Datenbank-Tabelle (1) wird eingerichtet
SCHEDULER-912 en: add_pid((1)), process deadline is (2)
SCHEDULER-913 en: Previous history has been archived under (1)
de: Bisherige Historie ist archiviert worden unter (1)
SCHEDULER-914 en: end() called, task will terminate
de:
SCHEDULER-915 en: Process event
SCHEDULER-916 en: idle_timeout is over, terminating task
de: idle_timeout ist abgelaufen, Task beendet sich
SCHEDULER-917 en: Enqueued task has been loaded from database: id=(1) start_at=(2)
de: Zu startende Task aus Datenbank geladen: id=(1) start_at=(2)
SCHEDULER-918 en: state=(1)(2)
SCHEDULER-919 en: Task (1) enqueued
de: Task (1) in Warteschlange eingereiht
SCHEDULER-920 en: Reading script again (processing again <include>)
de: Skript wird erneut gelesen (<include> wird erneut ausgefhrt)
SCHEDULER-921 en: Next period is (1), Schedule '(2)'
SCHEDULER-922 en: No further period
de: Keine weitere Periode
SCHEDULER-923 en: Repeating at (1) due to delay_after_error
de: Wiederholung wegen delay_after_error: (1)
SCHEDULER-924 en: First start at the start of the period: (1)
de: Erster Start zu Beginn der Periode: (1)
SCHEDULER-925 en: Next start at (2) due to spooler_job.repeat=(1)
de: Wiederholung wegen spooler_job.repeat=(1): (2)
SCHEDULER-926 en: Next start at (2) due to <period repeat="(1)">
de: Nächste Wiederholung wegen <period repeat="(1)">: (2)
SCHEDULER-927 en: Next start time will be determined at beginning of the next period. This is at (1)
de: Nächste Startzeit wird bestimmt zu Beginn der nächsten Periode: (1)
SCHEDULER-928 en: Next single_start at (1)
de: Nächster single_start (1)
SCHEDULER-930 en: Task (1) started - cause: (2)
de: Task (1) gestartet, Anlass: (2)
SCHEDULER-931 en: state=(1)
de: state=(1)
SCHEDULER-933 en: TCP connection accepted
de: TCP-Verbindung angenommen
SCHEDULER-934 en: Compiling Java source: (1)
SCHEDULER-935 en: (1) orders read from database
de: (1) Aufträge aus der Datenbank gelesen
SCHEDULER-936 en: Replacing (1) now
SCHEDULER-937 en: Removing (1) now
SCHEDULER-938 en: Order will be processed at (1)
de: Auftrag wird ausgeführt um (1)
SCHEDULER-939 en: Replacing order with same id: (1)
de: Auftrag mit gleicher Id wird ersetzt: (1)
SCHEDULER-940 en: Removing order from job chain
de: Auftrag wird aus der Jobkette entfernt
SCHEDULER-941 en: Removing order from job chain. Order is still being executed by (1)
de: Auftrag wird aus der Jobkette entfernt, aber weiterhin von (1) ausgeführt
SCHEDULER-942 en: add_or_replace_order(): order delayed until (1) has executed (2)
de: add_or_replace_order(): Auftrag wird verzögert bis (1) (2) ausgeführt hat
SCHEDULER-943 en: setback() called (1) times. Setting order to error state
de: (1) mal zurückgestellt. Der Auftrag wechselt in den Fehlerzustand
SCHEDULER-944 en: End state reached - order will be repeated at (2) with state=(1)
de: Kein weiterer Job in der Jobkette, der Auftrag wird mit state=(1) wiederholt um (2)
SCHEDULER-945 en: No further job in job chain - order has been carried out
de: Kein weiterer Job in der Jobkette, der Auftrag ist erledigt
SCHEDULER-946 en: setback(): order has been set back (1) times, until (2)
de: setback(): Auftrag zum (1). Mal zurückgestellt, bis (2)
SCHEDULER-947 en: setback(): order has been set back (1) times. This is more than (2) - the maximum for this job
de: setback(): Auftrag zum (1). Mal zurückgestellt, das ist über dem Maximum (2) des Jobs
SCHEDULER-948 en: Process (1) started
de: Prozess (1) gestartet
SCHEDULER-949 en: Job will be executed when a process of process class '(1)' becomes available
SCHEDULER-950 en: Scheduler has been registered
de: Scheduler ist registriert
SCHEDULER-951 en: Daylight saving time has begun
de: Sommerzeit beginnt
SCHEDULER-952 en: Daylight saving time has ended, now it's standard time
de: Winterzeit beginnt
SCHEDULER-953 en: Still sleeping (1) seconds ...
de: Noch (1) Sekunden schlafen ...
SCHEDULER-954 en: XSLT stylesheet (1)="(2)" returns:
de: XSLT-Stylesheet (1)="(2)" liefert:
SCHEDULER-955 en: UDP message from (1): (2)
de: UDP-Nachricht von (1): (2)
SCHEDULER-956 en: Scheduler expects commands from (1) port (2)
de: Scheduler erwartet Kommandos über (1)-Port (2)
SCHEDULER-957 en: Closing database
de: Datenbank wird geschlossen
SCHEDULER-958 en: Waiting (1) seconds before reopening the database
de: (1) Sekunden warten bevor Datenbank erneut geöffnet wird ...
SCHEDULER-960 en: Windows service handler: control=(1) event=(2)
SCHEDULER-961 en: Protocol starts in (1)
SCHEDULER-962 en: Protocol ends in (1)
SCHEDULER-963 en: Copying protocol file to (1)
SCHEDULER-964 en: New (1)

The web service has created a new order and handed it over to the job chain.

de: Neuer (1)

Der Web-Service hat einen Auftrag erzeugt und der Jobkette übergeben.

SCHEDULER-965 en: Executing command (1)
SCHEDULER-966 en: Command answer: (1)
SCHEDULER-967 en: start_new_file(): protocol file is being closed now
SCHEDULER-968 en: start_new_file(): intermediate protocol file is: (1)
SCHEDULER-969 en: Less than min_tasks=(1) are running. New tasks will be started. Reason: (2)
SCHEDULER-970 en: task(1) ended immediately after start, so min_tasks=(2) doesn't lead to new tasks
SCHEDULER-972 en: Still waiting until time(1) (object(2)) ...
SCHEDULER-973 en: Killed task does not stop the job because of ignore_signals="..."
SCHEDULER-974 en: Last error does not stop the job if the task aborts (after kill or crash) with any signal listed in ignore_signals="(1)". In this case, expect warning SCHEDULER-279
SCHEDULER-975 en: This file path with ';' will not be included in changed_directory: (1)
SCHEDULER-976 en: This directory path with ';' will not be included in triggered_files: (1)
SCHEDULER-977 en: Job is not stopping because of <job stop_on_error="no">. Task error was: (1)
SCHEDULER-978 en: Job is stopping because of <job stop_on_error="yes">. Task error was: (1)
SCHEDULER-979 en: Removing file (1)
SCHEDULER-980 en: Moving file (1) to (2)
SCHEDULER-981 en: File on blacklist has been removed
SCHEDULER-982 en: File has been removed, so the file order is being removed too
SCHEDULER-983 en: New file, written at ...(2): Added order(1)
SCHEDULER-984 en: Recovered from previous error in directory (1)
SCHEDULER-987 en: Starting process: program and arguments(1)
SCHEDULER-989 en: object_type(1) cannot be removed now, it will be done later
SCHEDULER-990 en: Adding order(1)
SCHEDULER-991 en: Order has been suspended
SCHEDULER-992 en: Order is no longer suspended, next start (1)
SCHEDULER-994 en: No heart beat for (2) seconds (time(1)), expecting heart beat within (3) seconds
SCHEDULER-995 en: No heart beat for (2) seconds (time(1)), ignored for (3) seconds because of recent database reconnect
SCHEDULER-996 en: No heart beat for (2) seconds (time(1)) - JobScheduler seems to be dead
SCHEDULER-997 en: Making up an extra heart beat
SCHEDULER-999 en: Scheduler has been terminated properly
de: Scheduler ordentlich beendet
SCHEDULER-805 en: No JobScheduler is active
SCHEDULER-806 en: This JobScheduler is active and exclusive now
SCHEDULER-807 en: Using database product (1)
SCHEDULER-809 en: Dead JobScheduler record has been removed
SCHEDULER-811 en: Executing command read from database: (1)
SCHEDULER-812 en: Just before processing, order record in database has been occupied or removed
SCHEDULER-813 en: Order is occupied by JobScheduler '(1)'
SCHEDULER-814 en: Inactive JobScheduler '(2)' has the higher backup precedence (1) (http_url(3))
SCHEDULER-815 en: Task should end but it has just been started with an order attached, so one step will be done
SCHEDULER-816 en: Unable to release occupation in database
SCHEDULER-817 en: Missing order record in database
SCHEDULER-819 en: Scheduler becomes active
SCHEDULER-820 en: Watching heart beat of that Scheduler
SCHEDULER-821 en: Scheduler member 'cluster_member_id(1)' seems to be active, claiming its last heart beat was (2)s ago (pid=(4), url(3))
SCHEDULER-822 en: Scheduler member 'cluster_member_id(1)' seems to be exclusive, claiming its last heart beat was (2)s ago (pid=(4), url(3))
SCHEDULER-823 en: Dead JobScheduler member 'cluster_member_id(1)' has resurrected
SCHEDULER-825 en: No exclusive JobScheduler is running
SCHEDULER-826 en: That JobScheduler has terminated
SCHEDULER-827 en: Own heart beat is late: next_heart_beat has been announced for (1) (this is (2) seconds late)
SCHEDULER-829 en: Releasing occupied order job_chain(1):id(2)
SCHEDULER-830 en: Because all JobScheduler tasks have been killed, the order in database has not been updated. Only the occupation has been released
SCHEDULER-831 en: Waiting (1)s for start of non-backup Scheduler
SCHEDULER-832 en: This is a backup Scheduler, waiting for a non-backup Scheduler
SCHEDULER-833 en: Watching heart beat of that exclusive Scheduler, standing by to take over operation
SCHEDULER-834 en: Active JobScheduler has terminated properly
SCHEDULER-835 en: This JobScheduler is becoming exclusive now
SCHEDULER-836 en: Deactivating that dead Scheduler
SCHEDULER-837 en: Taking exclusiveness from that Scheduler
SCHEDULER-838 en: (1). heart beat detected
SCHEDULER-839 en: This order has been replaced
SCHEDULER-841 en: It has been requested that the exclusive operation will not be continued
SCHEDULER-842 en: Task is going to process order(1), state=(2), on JobScheduler (3)
SCHEDULER-843 en: Task has ended processing of order(1), state=(2), on JobScheduler (3)
SCHEDULER-844 en: Scheduler script is not yet active. Operation is executed without the call of function '(1)'
SCHEDULER-845 en: Task ended without processing the order. The order remains in job's order queue in the same state
SCHEDULER-846 en: After task exception and due to stop_on_error='no', the order has been moved to error_state='(1)'
SCHEDULER-847 en: Please use new name '(1)' instead of old '(2)'
SCHEDULER-848 en: Task pid=(1) started for remote scheduler (2)
SCHEDULER-849 en: Timeout is not possible for a subprocess running on a remote host (it cannot be killed), pid=(1)
SCHEDULER-850 en: After lost connection to remote scheduler, process (1) is going to be killed
SCHEDULER-851 en: After possibly volatile error (number (1)), the statement which caused the error will be repeated: (2)
SCHEDULER-852 en: Order not found in database
SCHEDULER-853 en: Order in database could not be updated or deleted.
SCHEDULER-854 en: Closing lock (1) while held by (2)
SCHEDULER-855 en: Task is now holding Lock(1) exclusively/non-exclusively(2)
SCHEDULER-856 en: Lock(1) has been released
SCHEDULER-857 en: Lock(1) has been released, (2) non-exclusive holders remaining
SCHEDULER-858 en: Not longer waiting for lock locknames(1)
SCHEDULER-859 en: Due to action='next_state' the state '(2)' has been skipped. Next state is '(1)'
SCHEDULER-860 en: Waiting for 'lock(1)', exclusive(2), on place (3) (current holders(4))
SCHEDULER-861 en: 'object(1)' has been removed
SCHEDULER-862 en: Continuing in 'job chain(1)'
SCHEDULER-863 en: Continuing from 'job chain(1)'
SCHEDULER-871 en: Closing process class before process(1)
SCHEDULER-872 en: New 'Job_chain(1)' shares order IDs with job_chains(2)
SCHEDULER-873 en: Job_chains job_chains(2) share order IDs because 'Job_chain(1)' has been removed
SCHEDULER-874 en: Order_id_space has been closed
SCHEDULER-875 en: Order_id_space has been closed because 'job_chain(1)' has been removed
SCHEDULER-876 en: Temporary files cannot be deleted. Still trying ..., paths(1)
SCHEDULER-877 en: Temporary files have been deleted now
SCHEDULER-878 en: Temporary files cannot be deleted: paths(1)

In a windows environment it is possible that files can not be deleted, because another process (e.g. a virus scanner) blocked them. JobScheduler try to delete files for a while and if it's failed you'll get the message SCHEDULER-878.

This behaviour should not be the normal case, but it is not excluded.

SCHEDULER-879 en: Deactivating old cluster member with same ID
SCHEDULER-880 en: Error when creating database index is ignored
SCHEDULER-881 en: Error when reading stdout file is ignored: error(1), path(2)
SCHEDULER-882 en: Configuration directory '(1)' has been removed:
error(2)
SCHEDULER-884 en: Configuration directory has been deleted
SCHEDULER-885 en: Task ends because 'lock(1)' is being removed
SCHEDULER-886 en: Lock will be removed later, it is held by '(1)'
SCHEDULER-887 en: More lock holders than new max_non_exclusive=(1): holders(2)
SCHEDULER-888 en: object_type(1) cannot be replaced now, it will be done later
SCHEDULER-889 en: These filenames yield the same object name: '(1)' and '(2)'. The second is ignored
SCHEDULER-890 en: object_type(2) is going to be removed because its configuration file '(1)' has been removed
SCHEDULER-891 en: Configuration file '(1)' (timestamp(2)) is going to be be loaded into this new type(3)
SCHEDULER-892 en: This type(3) is going to be replaced due to changed configuration file '(1)' (timestamp(2))
SCHEDULER-893 en: objecttype(1) is 'state(2)' now
SCHEDULER-894 en: '(1)' will be removed later, it is used by job_chains(2)
SCHEDULER-895 en: Configuration directory '(1)' does not exist, it will be ignored
SCHEDULER-897 en: Error in replacement ignored::
error(2)
SCHEDULER-898 en: Folder is going to be removed because its configuration directory has been removed
SCHEDULER-899 en: Scheduler has no UDP port, so updated configuration files on supervisor will not be noticed
SCHEDULER-701 en: Replicating '(1)'
SCHEDULER-702 en: Removing '(1)'
SCHEDULER-703 en: Local configuration file is ignored, the central configuration file is used instead
SCHEDULER-704 en: Order has reached its end_state='(1)'
SCHEDULER-705 en: Substitute 'schedule(1)' is valid now
SCHEDULER-706 en: Standard 'schedule(1)' is valid now
SCHEDULER-707 en: Creating configuration directory '(1)'
SCHEDULER-708 en: Adding 'job_chain(1)'
SCHEDULER-709 en: Killing descendant pid=(1) (command line(2))
SCHEDULER-710 en: Delayed command <scheduler_log.log_categories.reset> has been executed
SCHEDULER-711 en: Step has run for (2)s, which is shorter than the expected duration of (1)
SCHEDULER-712 en: Task runs longer than the expected duration of (1)
SCHEDULER-713 en: Process handle (1) is already registered
SCHEDULER-714 en: Scheduler (1) is already registered via connection (2). This connection will be closed now. New connection is (3)
SCHEDULER-715 en: The command-line option configuration-directory '(1)' is not a directory
SCHEDULER-717 en: Remote commands are not allowed for the current licence-key(s)
SCHEDULER-718 en: Using '(1)' configuration directory '(2)'
SCHEDULER-720 en: job_chain (1) is deactivated (set max_orders to activate it)
SCHEDULER-721 en: Scheduler is not responding quickly, a microstep took (1)s
SCHEDULER-722 en: Preceding content truncated (field length is limited to (1) bytes)
SCHEDULER-723 en: Cluster member '(1)' has been advised for processing of this order
SCHEDULER-724 en: Error ignored when trying to obtain directory change notifications for (1): (2)
SCHEDULER-725 en: Persistent Order deleted from database
SCHEDULER-727 en: Keep-alive package sent to Agent

Messages for the Separate processes Package

Code Text
Z-REMOTE-100 en: Separate process: (1)
de: Objectserver: Fehler: (1)
Z-REMOTE-101 en: Separate process: pid=(1): Connection lost
de: Objectserver pid=(1): TCP-Verbindung ist abgebrochen
Z-REMOTE-102 en: Separate process: Unknown proxy id (1)
de: Objectserver: Unbekannte Proxy-Id (1)
Z-REMOTE-103 en: Separate process: Not a registered object: (1)
de: Objectserver: Nicht registriertes Objekt (1)
Z-REMOTE-104 en: Separate process: Invalid session id (1)
de: Objectserver: Session-Id ist nicht korrekt
Z-REMOTE-105 en: Separate process: Unknown session command, failure in communication
de: Objectserver: Session-Kommando unbekannt (Fehler in der Kommunikation)
Z-REMOTE-106 en: Separate process: Unknown session class, failure in communication
de: Objectserver: Session-Klasse unbekannt (Fehler in der Kommunikation)
Z-REMOTE-107 en: Separate process pid=(1): Invalid response
de: Objectserver pid=(1): Ungültige Antwort
Z-REMOTE-108 en: Separate process: Variant type (1) is not transmittable
de: Objectserver: Variant-Typ (1) ist nicht übertragbar
Z-REMOTE-109 en: Separate process: Failure in communication (message is too short)
de: Objectserver: Fehler in der Kommunikation (Nachricht ist zu kurz)
Z-REMOTE-111 en: Separate process: Thread (1) tries to use connection owned by thread (2)
de: Objectserver: Zwei Operationen gleichzeitig
Z-REMOTE-112 en: Separate process: Program did not fetch operation's result: (1)
de: Objectserver: Programm hat Ergebnis der Operation nicht übernommen: (1)
Z-REMOTE-113 en: Separate process: pop_operation with different method "(2)" ("(1)" expected) or different object
de: Objectserver: Programm will Ergebnis einer anderen Operation übernehmen
Z-REMOTE-114 en: Separate process: Program did not fetch result of an finished operation, method=(1)
de: Objectserver: Programm will Ergebnis einer nicht abgeschlossenen Operation übernehmen
Z-REMOTE-115 en: Separate process pid=(1): Message length (2) too big or invalid
de: Objectserver pid=(1): Nachricht mit zu großer oder ungültiger Länge (2)
Z-REMOTE-118 en: Separate process pid=(1): No response from new process within (2)s
de: Objectserver pid=(1): Der Objektserver war nicht innerhalb der Wartezeit von (2)s bereit
Z-REMOTE-119 en: Separate process: Two operations on the same connection. First: (1), second: (2)
de: Objectserver: Gleichzeitige Operationen auf derselben Verbindung. Erste Operation: (1); Zweite Operation: (2)
Z-REMOTE-120 en: Separate process: Unknown object id (1)
de: Objectserver: Objekt-Id ist unbekannt
Z-REMOTE-121 en: Separate process: pop_operation() on empty stack, method=(1)
de: Objectserver: pop_operation, aber Stack ist leer, Methode=(1)
Z-REMOTE-122 en: Separate process pid=(1): Caller has killed process
de: Objectserver pid=(1): Der Prozess ist (vom Aufrufer) abgebrochen worden
Z-REMOTE-123 en: Separate process pid=(1): Process lost
de: Objectserver pid=(1): Der Prozess hat sich unerwartet beendet
Z-REMOTE-124 en: Separate process: Named arguments not implemented
de: Objectserver: Benannte Parameter sind nicht möglich
Z-REMOTE-125 en: Separate process: DISPID (1) unknown
de: Objectserver: DISPID (1) nicht bekannt
Z-REMOTE-126 en: Separate process: Default proxy for (1) has no properties
de: Objectserver: Default-Proxy für (1) kennt keine Eigenschaften
Z-REMOTE-127 en: Separate process: More data as announced received. Failure in communication
de: Objectserver: Mehr Daten empfangen als angekündigt. Fehlerhafte Daten empfangen.
Z-REMOTE-128 en: Separate process: v.vt is not the value of SafeArrayGetVartype()
de: Objectserver: v.vt stimmt nicht mit SafeArrayGetVartype() überein
Z-REMOTE-129 en: Separate process: Blocking invocation on asynchronous connection rejected. Object=(1), dispid=(2)
Z-REMOTE-130 en: Connection from unexpected host (1)

Messages for the Charset Package

Code Text
Z-CHARSET-001 en: Unknown character encoding: (1)
de: Unbekannte Zeichen-Codierung: (1)
Z-CHARSET-002 en: Missing character encoding
de: Zeichen-Codierung ist nicht angegeben

 

Pages

 
 

Navigation