APPENDIX C. ERROR MESSAGES
Errors are displayed in popup warning boxes, the lower-left corner of some MCB Properties dialogs, and the supplementary information line at the bottom of the window.
Acquisition Failure (JOB Error 11)
For some reason an acquisition function failed from a
.JOB
file.
Already started.
Detector already active when a Start Acquisition command was issued.
Altering Detector data.
Restoring data to a Detector would destroy the data already there.
Amplifier not pole-zeroed.
Warning from an MCB with automatic pole zero, indicating that the Detector should be pole-zeroed.
Analysis Completed for ...
WAN32.EXE
has finished executing.
Analysis Error <n>
A call to
DLAN1.DLL
has been completed, but an error was encountered. The error code <n> has the following meaning:
Error #
1
1
2
2
3
4
5
Warning # Reason
1 Read error in UFO peak record
2
1
2
1
Read error in UFO nuclide record
Write error in UFO peak record
Write error in UFO nuclide record
Invalid acquisition date and time
0
1
Illegal absorption correction
Read error in spectrum file
Analysis Failed!
WAN32.EXE
has finished executing, but an error was encountered. Refer to the “WAN32 completion codes...” message.
Analysis Failed (Job Error 18)
The ANALYZE command failed (look for the WAN32 error code for specifics).
457
GammaVision
®
v7 (A66-BW) 783620H / 1013
Analyzing (Please Wait) ...
Analysis via
DLAN1.DLL
is being executed.
Attempt to dynamically link to a task! (WinExec error 5)
Error encountered trying to spawn
WAN32.EXE
or some other application program.
Auto Calibration failed (Job Error 21)
An error occurred when the CALIBRATE_AUTO command was executed.
Auto PZ aborted.
The MCB Auto PZ function was aborted (by <Esc>).
Buffer and Detector not same size or segments.
Error when trying to restore data that does not match the Detector configuration.
Calibration per channel wrong.
Error when trying to calibrate spectrum, arising whenever the calibration slope would be 0, negative or greater than 100 units per channel.
Can’t allocate memory for library.
Attempting to load a library for which there is not enough room in memory. Best dealt with by trying again or removing some other applications from memory.
Can’t find any more peaks!
A peak could not be found in the direction indicated by the function button pressed.
Can’t Find Any More ROIs.
Attempting to index to the next ROI in a direction for which no more ROIs can be located.
Can’t read library file.
Attempting to open or read the library file resulting in some kind of file I/O error, usually because the file doesn’t exist, but also possibly because the disk is defective.
Can’t RESTORE to acquiring Detector.
Error preventing the Restore function from altering data in a Detector in which one or more segment(s) are actively acquiring data.
Can’t Run Protected Mode Application in Real Mode!
(WinExec error 18)
Error encountered trying to spawn
WAN32.EXE
or some other application program.
458
783620H / 1013 APPENDIX C. ERROR MESSAGES
Can’t Run Second Instance of this .EXE (multiple writeable data segments)! (WinExec error 16)
Error encountered trying to spawn
WAN32.EXE
or some other application program.
Can’t Run Second Instance of this .EXE (Non-shareable DLL in use)! (WinExec error 17)
Error encountered trying to spawn
WAN32.EXE
or some other application program.
Cannot get valid Spectral Data!
The File/Save function was not presented with valid spectral data; usually the result of problems obtaining data from a Detector.
Comm. Failure!
Detector communication failure, most likely resulting from a timeout (the Detector failed to respond within a reasonable period of time).
Configuration failed!
Attempted reconfiguration failed, most likely because of some conflict with Detectors physically installed.
Could not properly fit the peak.
Function requiring a fitted peak could not obtain an acceptable peak, probably because of too few counts, too narrow, or non-Gaussian peak shape, or bad statistics such as calculated sigma-squared less than zero.
Couldn’t get background subtracted ROI.
A function requiring a background subtracted ROI couldn’t obtain such, probably because there was no ROI at the point specified, or maybe because there weren’t statistically significant counts above background.
Default Printer Failed! Undefined at Control Panel?
The REPORT or PRINT function was aborted because the default system printer has not been properly set up. Go to the Printers function in Windows Control Panel, install the appropriate printer, and select it as outlined in the Microsoft Windows documentation.
Detector #.. ; ......... ; Error ... (Macro) ... (Micro)
An unresolved error originating in the Detector. The offending Detector command is shown, together with the macro and micro error codes. If the error persists, the error codes should be recorded and the factory should be contacted. These error codes are explained in the hardware manual for the Detector.
459
GammaVision
®
v7 (A66-BW) 783620H / 1013
Detector busy or Segment not responding.
This indicates the Detector was unable to respond within a certain time limit, due to other activities, such as multiple instances of GammaVision accessing the Detector at the same time, or otherwise heavy use of the Detector interface.
Detector does not support Field Mode (Job Error 19)
An attempt was made to execute the LOOP_SPECTRA or VIEW command on a Detector that does not support Field Mode.
Detector Error!
The selected Detector could not be STARTed or STOPped due to some unresolved error condition.
Detector Not Located.
A Detector could not be located at the configured address.
Do you want to save buffer?
A function that would destroy the buffer (such as COPY or EXIT) queries the user unless the buffer has not been modified since last being saved.
Do you want to save Library?
The nuclide library has been modified by the library editor, but the user has not yet saved the changes.
DOS 4.0 Application! (WinExec error 13)
Error encountered trying to spawn
WAN32.EXE
or some other application program.
Error opening file.
If trying to write a file, this would indicate a disk controller problem such as a full disk. If trying to read a file, this would indicate that the filename specified could not be found.
Error reading file -- STRIP aborted.
Could not read the file requested for stripping.
Error reading file.
File read error is usually a result of damaged media.
Error writing file.
File write error is usually a result of damaged media or full disk.
460
783620H / 1013 APPENDIX C. ERROR MESSAGES
.EXE for earlier version of Windows! (WinExec error 15)
Error encountered trying to spawn
WAN32.EXE
or some other application program.
Failure obtaining ROI (or Peak).
A function that requires a defined ROI (or Peak, in the case of the Calibrate function) when the marker is not placed in a channel with an ROI bit set (and if a Peak is not very close by).
Failure of Detector function (JOB Error 12)
This error arises from a JOB that encounters an error when trying to access a Detector.
File already exists!
If the file output function requested would write a file with the same name as another file that already exists, the user is prompted for confirmation of the operation by this warning.
See also “OK To Overwrite Existing File?”
File is wrong size Can’t STRIP.
The STRIP function requires a compatible file for stripping from the spectrum in memory; i.e., must contain the same number of channels.
File Not Found! (WinExec error 2)
Error encountered trying to spawn
WAN32.EXE
or some other application program.
Fine gain is at limit of ...
This message appears in the Information Line when an attempt is made to change the
MCB gain setting with the keyboard function, but while the MCB cannot be decreased or increased any further.
FWHM Fit Error Exceeds 25%.
The peaks entered in an energy calibration produced a FWHM fit with an error on at least one peak greater than 25%.
Hardware failure!
This message appears as the result of a Detector execution error with micro code 137, indicating a hardware failure.
High voltage not enabled.
START was attempted on a 92X while the high voltage was not enabled.
Illegal Entry!
Certain values are not permitted in manual dialog entries or tables.
461
GammaVision
®
v7 (A66-BW) 783620H / 1013
Illegal Detector.
The Detector number for the requested function was not identifiable as part of the active configuration.
Incorrect Windows Version! (WinExec error 10)
Error encountered trying to spawn
WAN32.EXE
or some other application program.
Insufficient memory.
System memory has been exhausted. Usually, this error arises when the buffer cannot be created due to insufficient available memory in the system. Sometimes this error can be eliminated by attempting the buffer operation again, but this is not recommended due to the marginal state of the system, which might result in other errors.
Invalid Argument (Job Error 17)
The ROI limits in SET_PRESET_UNCERTAINTY command were invalid. The VIEW command specified a spectrum that was not stored in the Detector. The ZOOM command did not specify valid integers.
Invalid Command or Missing Argument. (JOB Error 4)
A syntax error in a JOB, meaning that a command could not be interpreted; usually the result of misspelling.
Invalid Device or Segment!
This message arises as a result of a Detector execution error with micro code 134, indicating that an invalid device or Segment was selected.
Invalid .EXE file! (WinExec error 11)
Error encountered trying to spawn
WAN32.EXE
or some other application program.
Invalid File Format!
A function to recall a file could not obtain data in the proper format.
Invalid library format!
An attempt was made to load a nuclide library from a file that was not in the proper format.
Invalid LOOP count. (JOB Error 7)
The LOOP statement could not be executed properly in a JOB.
462
783620H / 1013 APPENDIX C. ERROR MESSAGES
Invalid Start Date/Time -- Battery Backup Lost??
A 919 or 92X Detector contained an unrecognizable start date. This is usually an indication that the backup power was lost.
Invalid Start Record.
No valid Start Record file could be found to provide the start date/time for an installed 917 or 918 Detector.
JOB Aborted or Premature EOF (JOB Error 1)
A JOB was aborted by the user, or an End-of-File was encountered while trying to obtain a command from the executing
.JOB
file.
JOB Error.
A generic error message indicating that an error was encountered while executing a
.JOB
file. Usually some explanatory phrase is given.
Library requires separate data segments for each task!
(WinExec error 6)
Error encountered trying to spawn
WAN32.EXE
or some other application program.
Library too large to load.
Library files larger than 65,000 bytes are not admissible as internally resident libraries.
(However, any size library can be used for Master Library.)
Multiple-device Detector added.
While performing the CONFIGURATION dialog function ADD, a 919 device type was specified, and there is room to add up to four Detectors for each 919 device added; the
ADD function is automatically repeated for each possible Detector number.
Must have a value greater than zero!
Certain analysis or library table entries require values greater than 0.0.
Must have valid calibration!
Certain analysis functions cannot be performed if the calibration is invalid.
Must select 92X type Detector!
This error results from an attempt to perform a function available for only 92X-type
Detectors.
Need an ROI at the desired peak location.
The Stabilizer function requires a valid ROI at the desired peak.
463
GammaVision
®
v7 (A66-BW) 783620H / 1013
No Buffer to RESTORE from!
The RESTORE function requires a valid spectrum in buffer.
No close library match.
The REPORT function could not obtain a library entry close enough to the located peak.
No File Name.
A file function was requested without specifying the filename adequately.
No more library peak energies!
A peak search was attempted in a direction where no more can be found.
No more multiplets!
The multiplet finding sidebar function in Analysis Results display mode cannot find any more multiplets in the direction indicated.
No more peaks for this nuclide!
The “peaks within nuclide” sidebar function in Analysis Results mode cannot find any more peaks within the selected nuclide.
No more unknown peaks!
The unknown peak finding sidebar function in Analysis Results display mode cannot find any more unknown peaks in the direction indicated.
No peaks found!
The peak search function could not find any valid peaks in the spectrum.
No ROI found to report!
The REPORT function could not find any ROIs in range.
No ROI There To Clear.
The Clear ROI function (the <Del> or <Delete> key) requires at least one channel at the marker with the ROI bit set.
No segment selected.
The Detector function could not be performed because no Segment was selected.
Not Allowed During Acquisition!
An execution error (micro 135) arising from the Detector, indicating that the Detector command is not allowed while acquisition is in progress.
464
783620H / 1013 APPENDIX C. ERROR MESSAGES
Not Allowed During Current Mode!
An execution error arising from the Detector (micro 136), indicating that the Detector command attempted is not allowed in the current mode of operation.
Not enough data points for fit.
Efficiency calibration fit for specified type requires a minimum number of table entries for that type; e.g., for a polynomial fit, six or more points are required.
Not enough memory STRIP aborted.
The STRIP function temporarily allocates enough memory to read the file, but the allocation failed in this case, probably due to insufficient available memory in the system.
The STRIP function is discontinued.
Not enough memory for COMPARE.
The COMPARE mode could not be executed due to insufficient memory for the second spectrum.
NOTE: Settings for SEGMENT <n>
GammaVision is informing the user in the case of multi-segment Detector that he is performing settings (e.g., through an ASK function) on a specific segment only.
OK to add another device?
When a 919 device is being added in the CONFIGURATION dialog, the user is prompted for confirmation before automatically proceeding with the addition of up to four Detector numbers.
OK to attempt another instance?
Attempt to start an analysis (via
WAN32.EXE
) while a previous analysis has not yet finished, or had been aborted abnormally. GammaVision is asking the user to allow it to continue with this operation in case it is not properly sensing the state of the previous analysis. If the user permits this to continue (by answering Yes), but if the previous instance was actually still running, then another “WinExec()...” error will occur.
OK to destroy contents of Detector?
The RESTORE function prompts the user for confirmation before writing the contents of the buffer into the Detector.
OK to overwrite ‘...’ ?
A file output function discovered that the specified filename already exists, and will only overwrite the file after the user confirms his intentions. See also “File already exists!”
465
GammaVision
®
v7 (A66-BW) 783620H / 1013
OK to save changes?
The user is being prompted to allow the system to save a modified file such as a library file, table file, or sample-type defaults file.
OK to use it anyway?
A new configuration was applied but failed due to some conflict with the Detectors physically present; it is possible to use the configuration anyway by answering Yes to this query.
OS/2 Application! (WinExec error 12)
Error encountered trying to spawn
WAN32.EXE
or some other application program.
Out of Memory! (WinExec error 0 )
Error encountered trying to spawn
WAN32.EXE
or some other application program.
Path Not Found! (WinExec error 3)
Error encountered trying to spawn
WAN32.EXE
or some other application program.
Peak rejected for asymmetry.
Peak statistics could not be obtained for the function due the calculated non-Gaussian asymmetry of the obtained peak.
Preset already reached.
Acquisition START was attempted on a Detector or Segment that had already satisfied the preset condition(s) in some way.
Presets can’t be changed during acquisition.
Changes in the preset condition(s) are not allowed while the Detector is actively acquiring.
Presets not programmed to Detector correctly!
Usually a failure of the selected Detector to accept the commands from GammaVision to program presets. Often the result of improper configuration or faulty interface.
Previous analysis did not run to completion!
Attempt to start an analysis (via
WAN32.EXE
) while a previous analysis has not yet finished, or had been aborted abnormally. See “OK to attempt another instance?”
Problem with Buffer. (JOB Error 2)
A JOB error resulting from some problem with the buffer, usually indicating insufficient memory to create or enlarge the buffer as needed.
466
783620H / 1013 APPENDIX C. ERROR MESSAGES
Problem with Calculation. (JOB Error 13)
A JOB error resulting from a problem with a calculation.
Problem with RECALL. (JOB Error 10)
The RECALL statement could not be executed in a JOB.
Problem with REPORT. (JOB Error 14)
The REPORT function could not be exercised in a JOB.
Problem with SAVE. (JOB Error 9)
The SAVE function could not be executed in a JOB.
QA failed (Job Error 22)
An error occurred when the QASAMPLE or QABACKGROUND command was executed.
Sample Changer Hardware Failure. (JOB Error 16)
The Sample Changer hardware handshake failed in some way; usually the result of too much time before SAMPLE READY is obtained.
Start/Save/Report sequence aborted!
Start/Save/Report sequence aborted (usually by manual intervention, but also resulting from certain errors.)
Start/Save/Report waiting for completion of previous analysis...
A status message indicating that the Start/Save/Report sequence has been suspended while waiting for completion of an ongoing analysis.
Table is Full!
A limit of 96 entries is allowed in the calibration table.
There are no stored spectra to view (Job Error 20)
An attempt was made to execute the LOOP_SPECTRA or VIEW command on a Detector that does not have any stored spectra.
The Serial I/O Command timed out (Job Error 24)
The WAIT_SERIAL command timed out before receiving a response from the selected
Detector.
The Serial I/O Response did not match (Job Error 25)
The WAIT_SERIAL command did not time out, however, the actual and expected responses did not match.
467
GammaVision
®
v7 (A66-BW) 783620H / 1013
The WAIT program was not started by GammaVision (Job Error 23)
All programs “WAITed for” have to be started by GammaVision.
Token Error.
A token error in a JOB, meaning that some argument to the command was invalid or out of context.
Unable to CALL -- Invalid file name. (JOB Error 8)
A JOB error resulting from a problem with the CALL function (usually because the file does not exist).
Unable to COMPARE files of different sizes.
The COMPARE function requires compatible files.
Unable to cut peak or peak not selected!
The library editor Cut function or Analysis Results Delete library peak function is complaining that it cannot cut or delete a peak from the library for some reason, usually because a peak is not selected.
Unable to open file -- STRIP aborted.
The STRIP function is aborted if the file cannot be read.
Unable to open file for COMPARE.
The COMPARE function is aborted if the second spectrum cannot be read.
Unable to Read Specified File. (JOB Error 3)
A file input/output error encountered while executing a JOB.
Unable to RUN non-executable program. (JOB Error 6)
The specified program could not be RUN from a JOB.
Unable to strip Detector memory.
The stripping function must be performed in the buffer.
Unknown .EXE type! (WinExec error 14)
Error encountered trying to spawn
WAN32.EXE
or some other application program.
Unknown (misspelled) Command. (JOB Error 5)
A command in a
.JOB
file could not be executed because it could not be interpreted as a valid command (usually a result of misspelling).
468
783620H / 1013 APPENDIX C. ERROR MESSAGES
WAIT program was not started by GammaVision (JOB Error 23)
All programs “WAITed for” have to be started by GammaVision. In 32-bit Windows, the
32-bit programs are completely independent.
WAN32 completion codes: i=<i> errnum=<e> warnum=<w>
The following numbers are returned by the analysis routines and displayed on the information line.
5
5
6
6
6
6
10
2
2
2
3
4
4
Error # Warning # Reason
1 ?
Invalid spectrum filename
1
1
1
1
2
3
Read error in UFO peak record
Read error in UFO nuclide record
Read error in spectrum non-data record
1
1
1
1
1
2
4
200
201
202
203
0
Read error in UFO file
Attempt to read start channel after stop channel
Read error on disk for
.CHN
files
Read error on disk for
.SPC
files
Attempt to read invalid spectrum file type
2
2
2
1
2
3
Illegal filename
Write error in UFO peak record
Write error in UFO nuclide record
Write error in other UFO records
4
7
8
0
0
3
Invalid record for UFO file
Write error on report file
Invalid record request for table file
Invalid acquisition date and time
Illegal absorption correction
Spectrum not found
0
3
1
Read error in spectrum file
Spectrum wrong file type
Library not sorted
2
3
Read error on library
Invalid record request for library
4 Library not found
Error # System error (e.g., math overflow)
Warning 128.
Warning 64.
Warning 8.
All three of the above messages are the result of Detector Start or Stop warnings and are hardware dependent.
469
GammaVision
®
v7 (A66-BW) 783620H / 1013
Warning: Buffer was modified.
When the program is being closed, this message will appear if the buffer spectrum had been modified but not yet saved to disk. Thus the user is prompted for confirmation of possibly saving the buffer before proceeding to terminate the application.
Warning: File Changes.
The table editor sensed that modifications were made, but the user had not saved the file.
See “OK to save changes?”
Warning: Library was modified.
The library was edited or modified for analysis but not yet written to a file. See “OK to save changes?”
Warning: Sample Type Defaults changed
Sample type defaults have been modified but not yet written to selected file. See “OK to save changes?”
WinExec() Error <n>!
Error encountered trying to spawn
WAN32.EXE
or some other application program; refer to
Windows SDK documentation for meaning of code <n>.
470
