|
U00022000 |
Automic Service Manager, Version '&01' (changelist '&02') started.
&01 = Version name
|
|
|
U00022001 |
Automic Service Manager, Version '&01' ended normally.
&01 = Version name
|
|
|
U00022002 |
Automic Service Manager, Version '&01' ended abnormally.
&01 = Version name
|
|
U00022003 |
Cannot interpret statement '&01' in line '&02'.
|
|
|
U00022004 |
Starting process '&01' ...
Explanation: &01 = Process name
|
|
|
U00022005 |
... with command line '&01'.
Explanation: &01 = Content of the command line
|
|
|
U00022006 |
... and start directory '&01'.
Explanation: &01 = Start directory
|
|
|
U00022007 |
Process '&01' (ID '&02') successfully started.
|
|
|
U00022008 |
Could not start process '&01'. Error Code '&02'.
Explanation: User name, domain or password are incorrect. Check this data. &01 = Process name &02 = Error code
|
|
|
U00022009 |
Cannot interpret line '&01' with contents '&02'.
|
|
|
U00022010 |
Terminate process '&01' (ID '&02') with mode '&03'.
|
|
|
U00022011 |
Keep in status 'waiting' for '&01' seconds.
Explanation: &01 = Number of seconds
|
|
|
U00022012 |
Process '&01' (ID '&02') ended.
|
|
|
U00022013 |
Cannot create the pipe '&01' , error code '&02'.
|
|
|
U00022014 |
Received statement '&01' .
|
|
|
U00022015 |
Command file '&01' was re-created.
|
|
|
U00022016 |
Monitoring protocol for service '&01'.
|
|
|
U00022017 |
Automic Service Manager Version '&01' ready.
Explanation: &01 = Version name
|
|
|
U00022018 |
User '&01' starts UserInterface on host '&02'
Explanation: &01 = Name of the User object &02 = Computer name
|
|
|
U00022019 |
Client statement: process '&01' should be started.
|
|
U00022020 |
Client statement: process '&01' should be stopped
|
|
|
U00022021 |
Logon of user '&01' to domain '&02' successful.
Explanation: &01 = User name &02 = Domain
|
|
|
U00022022 |
Process '&01' ended, exit code='&02'.
|
|
|
U00022023 |
No associated window can be found for process '&01'.
|
|
|
U00022024 |
The ServiceM anager was started with INI-file '&01'
Explanation: &01 = Path and name of the INI file
|
|
|
U00022025 |
The file '&01' containing the definitions will be opened and interpreted.
Explanation: &01 = Path and name of the SMD file
|
|
|
U00022026 |
The command file '&01' containing the statements will be opened and interpreted.
Explanation: &01 = Path and name of the SMC file
|
|
|
U00022027 |
The sub-service '&01' was installed.
Explanation: The name of the service (sub-service) can freely be selected and is displayed: * in the ServiceManager dialog program in the column "Service" * in the definition file Phrase.SMD * in the output of the call GET_PROCESS_LIST &01 = Name of the service
|
|
|
U00022028 |
Unable to open file '&01', error code: '&02'
|
|
|
U00022029 |
Cannot load the user profile, error code: '&01'
|
|
|
U00022030 |
Cannot load environment variables, error code: '&01'
|
|
|
U00022031 |
Client data: User '&01' of computer '&02'.
Explanation: &01 = User name &02 = Computer name
|
|
|
U00022032 |
'&01' socket with port '&02' successfully created.
Explanation: &01 = Socket name &02 = Port
|
|
|
U00022033 |
Cannot create '&01' socket with port '&02'.
Explanation: &01 = Socket name &02 = Port
|
|
|
U00022034 |
Socket call '&01' returned error code '&02'.
|
|
|
U00022035 |
Process '&01' will be started in '&02' seconds.
Explanation: An interval can be specified in the properties of each individual service for which the start should be delayed. Call this window via the popup menu in the Service Manager dialog program. We recommend starting the Server processes on after the other with a delay of 10 seconds each. This also holds for all other UC4 components such as Agents, for example. &01 = Name of the service &02 = Number of seconds
|
|
|
U00022036 |
The number of Service Manager instances is limited to '&01' instances.
|
|
|
U00022037 |
Start method '&01' was not found.
|
|
|
U00022038 |
Service '&01' automatically starts in '&02' seconds.
|
|
|
U00022039 |
Service '&01' will not be restarted because it has already been started '&03' times during the past '&02' minutes.
|
|
|
U00022040 |
Error in function '&01', error code '&02'.
|
|
|
U00022041 |
Process '&01' cancelled.
|
|
|
U00022042 |
Process '&01' abnormal ended with access violation.
|
|
|
U00022043 |
Operation in Windows Safe Mode not supported.
|
|
|
U00022044 |
Real user '&01' and effective user '&02'.
|
|
|
U00022045 |
Build Date: '&01', '&02'
|
|
|
U00022046 |
Service Manager has been started on Host '&01' ('&02') with process ID '&03'.
|
|
|
U00022047 |
The restart file '&01' will be opened and interpreted.
|
|
|
U00022048 |
Successfully attached to process '&01' with pid '&02'.
|
|
|
U00022049 |
Error starting the restart process, error code '&01'.
|
|
|
U00022050 |
Upgrade description file '&01' has been opened, upgrade process starts.
|
|
|
U00022051 |
Error: Upgrade description file '&01' not found, upgrade process has not started.
|
|
|
U00022052 |
Error in file processing, the previous processing will be rolled back.
|
|
|
U00022053 |
Upgrade process already active.
|
|
|
U00022054 |
Service Manager upgrade process has been initiated.
|
|
|
U00022055 |
Service Manager shut down initiated.
|
|
|
U00022056 |
Service Manager upgrade canceled.
|
|
|
U00022057 |
Process '&01' (ID '&02') ended. Return code not available.
|
|
|
U00022058 |
Service Manager upgrade: Upgrade files installed, Service Manager restarts.
|
|
|
U00022059 |
Service Manager upgrade: Initializing.
|
|
|
U00022060 |
Service Manager upgrade complete. The new Service Manager uses the same PID='&01' as its predecessor.
|
|
|
U00022061 |
Service Manager upgrade complete. Service Manager was started in a new process with PID='&01'. Its predecessor used PID '&02'.
Service Manager upgrade complete. Service Manager started in a different process with PID='&01'. As a result, child tasks of the old Service Manager instance needs polling as parent-child relationship to old tasks does not exist anymore, because previous Service Manager instance ran with another PID ('&02').
|
|
|
U00022062 |
Service Manager upgrade failed: Child processes of previous Service Manager instance could not be attached. (smr file could not be executed)
|
|
|
U00022063 |
Service Manager upgrade error: cannot remove file '%s'.
|
|
|
U00022064 |
Service Manager upgrade error: cannot access directory '&01' to delete files matching the pattern '&02'.
|
|
|
U00022065 |
Service Manager upgrade error: cannot open directory '&01' to delete files matching the pattern '&02'.
|
|
|
U00022066 |
Service Manager upgrade error: Upgrade description file '&01' empty.
|
|
|
U00022067 |
Service Manager upgrade error: Cannot open upgrade description file '&01'.
|
|
|
U00022068 |
Successfully detected PID of Service Manager instance which initiated the Service Manager upgrade: '&01'
|
|
|
U00022069 |
Service Manager upgrade error: upgrade description file '&01' is empty.
|
|
|
U00022070 |
CAPKI Library not available.
CAPKI Library not available on this system. Servicemanager will start in unsecure mode.
|
|
|
U00022071 |
CAPKI Library available.
CAPKI Library is available. Service Manager starts in secure mode.
|
|
|
U00022072 |
CAPKI Library initialization failed.
CAPKI Library initialization failed.
|
|
|
U00022073 |
reserved
|
|
|
U00022074 |
ServiceManager upgrade blocked.
|
|
|
U00022075 |
ServiceManager upgrade blocked for another '&01' seconds.
|