Keysight Technologies X Series Service Manual page 109

Instrument Messages
-200 to -299, Execution Errors
-250
Mass storage error; Failed
to Load trace. Bad file
format.
-250
Mass storage error; File
<filename> wrong type
-250
Mass storage error; File
<filename> and instrument
version mismatch
-250
Mass storage error; File
contains incorrect data for
this operation
-250
Mass storage error; File
empty
-250
Mass storage error; Invalid
register number for *SAV or
*RCL
-250
Mass storage error; Lock
violation
-250
Mass storage error; No file
names available
-250
Mass storage error; Open
failed
-250
Mass storage error; Read
fault
-250
Mass storage error;
Register <number> empty
-250
Mass storage error; Sharing
violation
-250
Mass storage error; Too
many open files
-250
Mass storage error; Write
fault
-252
Missing media
-253
Corrupt media
Keysight N9010A EXA Service Guide
The load trace operation could not be completed, as the input file was
not in the expected format. You can only load traces that were
previously saved using the 'Save Trace' feature.
Attempt to import a data file that is not the proper type for this
operation.
While opening a file, there was a mismatch between file version or
model number with instrument version or model number. The import
still tried to load as much as possible, but you should check it closely.
There is a mismatch between the file data type of the file specified and
the destination indicated. For example, a correction set cannot be
loaded/imported into a limit line.
Cannot save trace because it contains no data. Check that the trace is
turned on and contains some valid data.
You have used the *SAV command to save a state to a non existent
state register.
Or
You have used the *RCL command to recall a state register that wasn't
previously saved with the *SAV command.
The process cannot access the file because another process has
locked a portion of the file.
Attempt to use the auto file name generation when all 10,000 file
names are taken.
The system cannot open the device or file specified. This could be
because the storage media is full, or possibly due to a filename error.
If using an external storage devise, check that the devise is properly
formatted.
The system cannot read from the specified device.
Attempt to recall a register with nothing in it
The process cannot access the file because it is being used by another
process.
The system cannot open the file.
The system cannot write to the specified device.
A legal command or query could not be executed because missing
media.
A removable media was found to be bad or incorrectly formatted. Any
existing data on the media may have been lost.
109