error codes
Adlib Information Systems
Copyright © 1992-2009 Adlib Information Systems B.V.® All rights
reserved. Adlib® is a product of Adlib Information Systems B.V.®
The information in this document is subject to change without notice
and should not be construed as a commitment by Adlib Information
Systems. Adlib assumes no responsibility for any errors that may
appear in this document. The software described in this document is
furnished under a licence and may be used or copied only in
accordance with the terms of such a licence. While making every
effort to ensure the accuracy of this document, products are
continually being improved.
As a result of continuous improvements, later versions of the products
may vary from those described here. Under no circumstances may
this document be regarded as a part of any contractual obligation to
supply software, or as a definitive product description.
Error codes in Adlib
Code
0
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
Cause
No error, action successful.
Tag not found.
Memory allocation error.
Overflow error.
String too long.
Error in date or date format.
Wrong key type.
Record not found.
Internal error.
Error in database handle.
Index not open.
Database not open.
Database read error.
Database creation error.
Database search error.
Database insert error.
Database Info file not open.
Error in database info file.
Error writing to database info file.
Dongle error.
List empty.
No index.
Error making new priref.
WORDLIST error.
BTREE error.
BTREE initialization error.
Free text search error.
Key length error.
Error deleting data file.
Key truncated error.
Record not locked.
Record number out of range.
Dataset not found.
Link tag error.
Record already locked.
Lock file not open.
Error searching in lock file.
Error writing to lock file.
Error reading lock file.
Process id error.
Lock file oudated.
1
Error messages in Adlib
Code
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
Cause
Divide by zero.
Out of bounds.
Invalid object.
Unimplemented instruction.
Unresolved reference.
Array reference error.
Math domain error.
Math range error.
ADAPL file not found.
FACS file not found.
Print temp file error.
Print write error.
Print spool error.
Obsolete function.
Invalid FACS name.
Invalid tag.
Invalid CVT.
No write access.
No control format error.
Text file error.
Invalid occurrence.
Tag list full.
Datafile write error.
Operating system error.
Multi-user error.
Setup file error (Adlib.PBK).
Adlib.PBK outdated.
Setup file (Adlib.PBK) not open.
Object register error.
Object register access error.
Record list insert error.
Hit list add error.
Hit list remove error.
No keywords left.
Adlib.PRM file not open.
Error in Adlib.PRM file.
Invalid list position.
Record overflow.
Import file not open.
No back-up files available.
Dump file not open.
File remove error.
Duplicate record number.
Missing record number.
Error locking the linked record.
2
Error messages in Adlib
Code
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
Cause
Error initializing image processing.
Error in the image file.
Error loading image file.
Error expanding image file.
Write protection error.
Duplication keyword.
Invalid instruction.
Error due to physical lock.
Error searching index file.
Error writing to index file.
Error in index page.
Error reading index page.
Error in index definition.
Error opening index definition.
Index corrupt.
Stack error.
Error in temporary file.
Record not selected.
Record for synonym not found.
Invalid path.
Regular expression exceeds max. length.
Too many parentheses.
Parentheses do not balance.
Error at the end of a regular expression.
* or + error in regular expression.
Syntax error in regular expression.
Invalid range in square brackets.
Square brackets do not balance.
Syntax error in regular expression.
Trailing \ error in regular expression.
Regular expression corrupt.
Error in regular expression.
Error initializing image database.
Return without gosub in ADAPL.
Wrong image type.
Narrower relation not mirrored.
Imagebase create error.
Imagebase not open error.
Imagebase index not open error.
Imagebase insert error.
Imagebase search error.
Image base write error.
Image base read error.
Image base delete error.
Adeval procedure interrupted.
3
Error messages in Adlib
Code
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161-166
167
168-170
171
172
173
174
175
176
Cause
Error in character set conversion table.
Search file not found.
Search file syntax error.
Error writing pointerfile.
Error opening pointerfile.
Pointer file format error.
Error reading pointerfile.
Errror during import or export job.
Search interrupted.
Error reading freelist.
Error reading block in datafile.
Record header read error.
Error in record header.
Error expanding database.
Error writing block to datafile.
Illegal input file format.
Fieldname not found.
Error writing to disk.
Error while forcing linked record.
Forcing not allowed.
Error reading locked record.
Logfile open error.
Logfile write error.
Circular internal link error.
No preferred term.
Field not empty.
Duplicate term.
Non-preferred term refers to preferred term.
Preferred term has relation error.
Term being used by other user.
Self-issue loan desk error messages.
No access error.
Programming errors.
Object file (.inf, .fmt, .pbk, .imp, .exp, etc.) corrupt.
System file processed with newer version of software than
version with which it was called.
Recovery database path missing.
Index on link reference field is incorrect or missing. (If
your application uses feedback links, check that all forward
reference fields in the primary databases that point to
authority files have integer indexes.)
Import file has been made via logging, must be imported
using Recovery.
Feedback record found using index on link reference field,
but link reference not found in record itself.
4
Error messages in Adlib
Code
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200-250
251-300
301
302
303
304
305
306
307
308
309
310
311
Cause
Index on linked field wrong type or missing.
Linked field/link reference field cannot be removed from
record retrieved via feedback links.
Lockfile lock error (not yet used).
File cannot be found.
Access to a file denied.
File to be copied cannot be opened.
File to be written to cannot be opened.
Error reading a file.
Error writing to a file.
Cannot read or change date and time of a file.
Cursor position changed in an ADAPL.
User doesn’t have access to a file (authorization failed).
General ODBC error. The error message provides more
detailed information.
Domain error: the domain name is too long.
Left truncation has been set, but the indexes have not
been adjusted accordingly.
Preferred term relation hasn’t been mirrored.
Mandatory arguments haven’t been submitted.
Return date was not calculated.
Location wasn’t found.
Search time-out.
The registry can’t be read.
The registry can’t be written to.
The log file cannot be locked.
Reserved for errors in AISODBC.dll (the ODBC driver).
Reserved for errors in Adlib Input/Output.
Parse error: an error in the syntax of a search statement
in the expert search system.
Semantic factor relation hasn’t been mirrored.
MS_XML error.
The record already exists.
(no longer in use)
ADO error.
Wwwopac error in http form: no request method has been
submitted.
Wwwopac error in http form: no content length has been
submitted.
Wwwopac error in http form: content length doesn’t
match.
Wwwopac error in http form: no query data.
Wwwopac error: general Adlib.DLL error, such as: this DLL
not found; no access rights to the DLL; or licence file can’t
be found.
5
Error messages in Adlib
Code
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
342
342
343
344
345
346
347
348
349
350
351
Cause
Wwwopac error: semaphore error.
Wwwopac error:error has already been handled.
Wwwopac error: database header is missing.
OAI error: wrong argument.
OAI error: wrong resumption token.
OAI error: wrong VERB.
OAI error: cannot disseminate format.
OAI error: OAI_ID doesn’t exist.
OAI error: no records found, or the set is empty or cannot
be found.
OAI error: no metadata formats present.
OAI error: sets are not supported.
OAI error: no ADMIN_EMAIL has been set.
OAI error: no REPOSITORY name has been set.
OAI error: no DELIMITER has been set.
OAI error: no IDENTIFIER has been set.
OAI error: no OAI_DIR has been set.
OAI error: internal error.
Gdiplus error.
Not implemented.
General error when exchanging data via GLUE with ADO.
E-mail error.
Configuration error.
Licence file error: licence invalid.
Licence file error: licence has expired.
Licence file error: licence cannot be found.
Licence file error: cannot write to licence file.
Licence file error: cannot read from licence file.
Error in automatic numbering.
Error in automatic numbering: counter file (.cnt) cannot be
opened.
Error in automatic numbering: counter file (.cnt) cannot be
read.
Error in automatic numbering: counter file (.cnt) cannot be
written to.
Error in automatic numbering: counter file error (.cnt).
Error in automatic numbering: lock on .cnt file causes
error.
AdlibWEB error: general error within GLUE ADW.
wrong lock ID
Error in internal link.
Error with the type of the index file.
Duplicate link reference tag.
Duplicate destination tag.
Link reference tag not filled.
6
Error messages in Adlib
Code
352
353
Cause
No linked data.
Missing path DB separator: in a definition of a linked
dataset in DBSETUP the + character cannot be found.
354
String is too short.
355
Import error: existing record for update tag not found.
357
C++ exception: a C++ exception is a programming error
in the core software in Adlib, which may have widely
differing causes. Previously, this type of programming
error resulted in an "Illegal operation", causing adlwin.exe
to shut down. This 357 error message however, is the
result of a new (June 2005) built-in event handler that
catches these illegal operations.
Errors of this type should be reported to the helpdesk of
AIS.
From Adlib 6.0, warnings and errors that Adlib generates, which
usually appear in the screen of the user, are logged in the Windows
Event viewer (Control panel > Administrative tools/System management > Event viewer). The advantage of this is that if you have
clicked an error message away, but want to look it up later once
more, for instance because you need to provide the exact message to
the Adlib Helpdesk, then in the Event viewer you can get an overview
of errors that occurred in the past. By double-clicking an event, you
open the full warning or error message. Do note that a warning
usually does not indicate problems.
The errors associated with the following error codes can appear only
when you are working under Windows.
Code
1001-1006
1007
1008
1009
1010
1011
1012
1013
1014
1015
1016
1017-1024
Cause
Internal Windows error.
The “busy” mouse cursor couldn’t be loaded.
The help text file (adlib.hlp) couldn’t be opened.
The key entered for the help text doesn’t occur in the
help text file (adlib.hlp).
Screen definition file (.fmt) not found.
Required system field does not occur in screen
definition.
Internal Windows error.
Printer data cannot be read.
The “welcome.bmp” file cannot be opened or displayed
because of the PC’s colour settings.
The printer cannot print on the selected paper format.
The printer cannot print in landscape/portrait format.
Internal Windows error.
7