BackPak H4.00 Troubleshooting and Messages Manual

Messages
30 BackPak H4.00 Troubleshooting & Messages
Number Text Explanation Action
1004 Abort in %1 %2, error
code %3 %4
Severe internal error. Refer to the Guardian
Procedure Errors and
Messages manual.
1005 No memory available for
%1
Memory allocation
failed.
Contact the Product
Support.
1006 Unexpected tag %1 Internal error. Contact the Product
Support.
1007 Guardian Error %1
detail %2 from %3 %4
A Guardian procedure
call failed.
Refer to the Guardian
Procedure Errors and
Messages manual.
1008 Internal limit %ld
reached for %s. %s"
A program limitation has
been reached
Contact the Product
Support.
1101 Warning: trace file %1
unavailable, errno: %2
Error accessing the
Domain Manager trace
file.
Refer to the Guardian
Procedure Errors and
Messages manual.
1102 Unable to
open|read|write file %s
'%s' error %ld.
Error accessing a
standard C/stream file.
Refer to the Guardian
Procedure Errors and
Messages manual.
1103 BB000_COLLECT
produced the binary file
%s and text file %s
Information reporting
the result of
BB000_COLLECT macro
initiated through the
BackPak GUI
Note the name of the
files to transmit to
support
1104 BB000_COLLECT failed.
%s file name not found
in the output file %s.
Browse the Utilities log
file configured in the
domain page (currently
%s).
Error while executing
the BB000_COLLECT
macro initiated through
the BackPak GUI.
The cause of error
must be searched in
the execution output.
The execution output is
specified in the domain
configuration as ‘Log
Output’, with the
default value $NULL.
1105 BB000_COLLECT can
only be run from TACL
prompt on Peripheral
node %s where the EMS
Extractor did not run
successfully yet
For a peripheral node,
the BB000_COLLECT
macro cannot be
initiated through the
BackPak GUI, until
BBEXT as not run.
Execute
BB000_COLLECT at
TACL prompt when the
default subvol is the
installation subvol in
the peripheral node.