|
Error codes and their explanation |
Top Up Down
A A |
For Windows-related and other problems, see www.winsteps.com/problems.htm
Error code Diagnosis
F1 "Specification=value" expected
A specification whose first one or two letters is not in the "INDEX OF Facets SPECIFICATIONS" was given.
F2 Number invalid or greater than ___
Integers are usually in range 1 to 2147483647. Facet numbers are integers in the range 1 to 255. Facet 0 can be used to indicate that no facet applies.
F3 Duplicate category label
A category number has been defined twice in a Rating (or partial credit) scale= specification.
F5 More than ___ components in Model= statement
Each Model= statement has as many facet control characters, e.g., "?", as there are facets in the Facets= statement, then a scale character, e.g., "R", followed optionally by a weight, e.g., "1". You specified too many components.
F6 Invalid or undefined scale
The Model= or Rating Scale= statement specified a scale type, e.g., "S", which is neither a scale type itself, e.g., "R", nor defined by "Rating Scale=S".
F7 Duplicate Rating (or partial credit) scale= identifying labels
Two Rating (or partial credit) scale= specifications have the same scale name, e.g., "quality" in
"Rating (or partial credit) scale=quality"
and then again later,
"Rating (or partial credit) scale=quality"
F8 Facets= statement conflicts with prior facet commands
Specify your one Facets= statement before other facet-related commands, such as "Positive=2" to prevent incorrect standard values being used.
F11 All Model= statements must include ____ facet locations + type [+ weight]
Each model statement has as many facet control characters, e.g., "?", as there are facets, followed by a scale character, e.g., "R", followed optionally by a weight, e.g., "1". You specified too few components.
F12 Category is not an integer in range 0 to 255
Valid responses are in the range 0 to 255, after recoding if specified.
F13 Labels= contains the same facet twice
After a Labels= statement, the facets can be in any order, but each facet number can only be used once, e.g.,
Labels=
3=facet 3
1=element 1 facet 3
*
1=facet 1
1=element 1 facet 1
*
3=facet 3 <- this is invalid. The facet is repeated!
F15 Invalid category in Rating (or partial credit) scale= specification
Category values must be integers in the range 0 to 32767, or negative numbers, if they are to be treated as missing.
F17 Extra term on DOS command line
The DOS command line can have
C:>FACETS SPECFILE [OUTFILE [ANCFILE]] Specification=Value .....
[ ] mean "optional".
Your DOS command line does not follow this scheme. Are there blanks before or after "=" signs?
F18 This specification not permitted on DOS command line
You have specified something on the command line that Facets does not allowed there, e.g., Labels=, Model=, Rating (or partial credit) scale=
F20 No element numbers specified after Labels=
Your Labels= command was not followed by a facet number, then element numbers, then "*", e.g., a correct specification is:
Labels=
1, Facet 1 name ; facet number
21=One element ; element in first facet
32=Another element
* ; end of element list for this facet
2, Facet 2 name
1=Element one name
*
F21 Sort length error - contact www.winsteps.com
Internal failure in Facets. Contact us prepared to give details of your specification file.
You can run probably produce useful output from Facets:
1) Remove any Arrange= specification
2) Specify "Vertical=no"
F22 Non-numeric datum treated as missing
An observation is specified with a non-numeric values. It is ignored as missing data.
F23 Invalid element number. Must be integers in the range 0 - 2147483647
0 is the null element number, unless Keepasnull= sets a different element number as the null element.
F24 Invalid group number
Group numbers must be integers in the range 1 to 255
F25 Invalid Model= statement
You did not use a valid facet control character, such as "?", or "#", a valid element number or a valid element-number range.
F26 Invalid response value: non-numeric or too big for model
A response in this data line did not match the Model= or Rating (or partial credit) scale= specification.
F27 Data record does not contain ___ facet references + data
You did not specify enough facet element references, or data elements in your data line.
F28 Non-Integer value where integer expected
Element and category numbers must be integers, not real numbers like 2.5
F29 Only one facet may have a range (-) in a data line
With 2 facets, "1-3,2-3, 1,0,1,0,1,1" is invalid. Enter:
1-3,2, 1,0,1
1-3,3, 1,1,0
F30 Not enough responses for the range: expected: ___
You specified a range of elements, but did not provide one response for each element of the range, e.g., with two facets, "1-3,4, 2, 1" requires one more response, e.g., "1-3,4, 2, 1, 2".
F31 Too many responses: expected: ______
You specified a range of elements, but provided more responses than there were elements in the range, e.g., with two facets, "1-3,4, 2, 1, 2, 2" has one response too many. Also check Dvalues=, if used.
F32 Valid arrangements are facet number (optional) then A,F,M,N,P,a,m,f,n,p
Did you specify some other letter or a non-alphabetic character? Valid arrangements look like: "Arrange=Af,Mp,3M"
F34 Please specify Facets= before this specification
This specification requires a Facets= specification to precede it, e.g., Facets=3.
F35 No usable data. Use Query=Y to check Models= and Labels=
No data match model statements, and reference specified elements, and have valid data values. Query=Y to discover the reason Facets rejected each datum.
F35 may be because there is only one observation for each element.
Here is a way to get your analysis to run ....
1. Put all the data in twice: copy-and-paste the current data after itself.
2. Weight the data 0.5
Models= ?, ?, ?, R, 0.5
F36 All data eliminated as extreme. Are there enough replications?
Extreme scores (zero or perfect) correspond to infinite measures and so provide no useful information about the measures of other elements. Therefore, data included in extreme scores are eliminated. All scores were perfect, so all data were eliminated. Perhaps, the problem is simply that not enough data is present.
This can happen when the data have a Guttman pattern. On first analysis, there are some extreme scores for persons, items, judges, tasks, etc. So these are dropped from immediate estimation. Then, in the remaining data, there are some extreme scores. These are dropped. The process continues until no data are left.
F37 Incompatible file usage: ______
The same file name has been specified for two different files, e.g., a data file and an output file. Rerun Facets with amended file names.
F38 Lsort sequence error
This is an internal sorting error within Facets. Please contact : www.winsteps.com
F39 Umean= must be specified before Labels= and Rating=
User rescaling must be specified in the specification file before any lines to which it applies. Place Facets= and Umean= early in your specification file.
F40 Data= not specified
Data= must be followed by the observations, or be Data= filename.
F41 No file name
A file name is expected in this specification.
F42 File name contains * or ?, or ends with \ / or :
File name does not accord with Windows rules.
F43 File not found
Specified input file does not exist.
F44 Invalid line-end format: only LF code, CR-LF expected
File is not in MS-DOS text with line breaks format. Read it into Word (or such like) and then "Save As" in "DOS text with line breaks" format
F45 Entered= references do not match ________
Entered= specification not compatible with Facets= specification.
F46 File has no contents
Empty input file not allowed.
F47 Invalid line-end format: only CR code, CR-LF expected.
File is not in MS-DOS text with line breaks format. Read it into Word (or such like) and then "Save As" in "DOS text with line breaks" format
F48 Anchor value too extreme
Anchor value set outside the range of the floating-point processor.
F49 Missing quote " in command line
There are unbalanced " " on the DOS command line
F50 Work file problem
Rerun the analysis. If it still occurs, please contact www.winsteps.com
F51 Execution cancelled at user request
Execution cancelled - perhaps from the Files pull-down menu.
F52 File not found in batch mode
Specified input file does not exist. Specifying complete paths may solve this.
F53 Too many Models= specified
More than 32,000 Models= specifications have been given.
F54 Dvalues= must be facet, value e.g., 3,1-4 or facet, facet, start, length, e.g., 3,2,6,2
Check Dvalues= for format and validity.
F57 Required file not found
A specified input file does not exist. Provide complete pathname.
F58 Excel-related error
Facets may not be compatible with your version of Excel.
F59 Field start or length problem in Dvalues=
See the Dvalues= instructions.
F60 Non-numeric weight in Model= specification: "____"
Model= weights can omitted (and assumed to be 1) or specified with numeric values.
F61 Reordered category value not positive integer or zero
Rating scale= reordered-value is incorrect. An anchor file may not have the correct format
F62 No active element numbers: Models= and Labels=
Models= has selected no active element combinations, or Labels= contains no active elements.
F63 ..\winspssf.exe not found
The Facets-to-SPSS file conversion module is missing. Reinstall Facets?
F64 SPSS file creation failed
Does the version of winspssf.exe match the version of Facets.exe?
SPSS Interface: Input work file incorrect
There is a mismatch between Facets components, please contact www.winsteps.com
Internal error in winspssf.exe - perhaps it does not match Facets.exe
Windows-reported file problems:
52 Bad file name or number
53 File not found
54 Bad file mode
55 File already open
57 Device I/O error
58 File already exists
61 Disk full
67 Too many files
68 Device unavailable
70 Permission denied
71 Disk not ready
75 Path/File access error
76 Path not found
These are all filename or file availability problems.
76 Workfile failure.
In your autoexec.bat file, SET TEMP= or SET TMP= are missing or point to invalid paths. Try:
SET TMP=C:\WINDOWS\TEMP
SET TEMP=C:\
Facets runs under Windows-XP, but may initially fail due to Windows-XP not correctly setting up its temporary file directory. If you get a message like:
"Workfile failure 76 path is not found. for:C:\Document\Locals\Temp\"
then right-click on "My Computer"
select "Properties | Advanced | Environment Variables"
edit the User Environment variable called TMP to be C:\TEMP
Create a new folder C:\TEMP if you do not already have one.
Help for Facets Rasch Measurement Software: www.winsteps.com.