Code

Cause

0

No error, action successful

1

Tag not found

2

Memory allocation error

3

Overflow error

4

String too long

5

Error in date or in date format

6

Wrong key type

7

Record not found

8

Internal error

9

Error in database handle

10

Index not open

11

Database not open

12

Database read error

13

Database creation error

14

Database search error

15

Database insert error (only for CBF databases)

16

Database info file not open

17

Error in database info file

18

Error writing to database info file

19

Dongle error

20

List empty

21

No index

22

Error making new priref

23

WORDLIST error

24

BTREE error

25

BTREE initialization error

26

Free text search error

27

Key length error

28

Error deleting data file

29

Key truncated error

30

Record not locked

31

Record number out of range

32

Dataset not found

33

Link tag error

34

Record already locked

35

Lock file not open

36

Error searching in lock file

37

Error writing to lock file

38

Error reading lock file

39

Process id error

40

Lock file outdated

41

Divide by zero

42

Out of bounds

43

Invalid object

44

Unimplemented instruction

45

Unresolved reference

46

Array reference error

47

Math domain error

48

Math range error

49

ADAPL file not found

50

FACS file not found

51

Print temp file error

52

Print write error

53

Print spool error

54

Obsolete function

55

1. Invalid FACS name: check if there's an OPEN <facs name> instruction in your adapl. You can only READ from a FACS database after it's been opened first.
2. FACS database cannot be opened. When an OPEN statement is executed, an empty memory record is created in which default values are set. If the FACS declaration is correct and .inf and database are accessible, this error may indicate that an invalid default value has been assigned: then check for all fields with default values if the default values are allowed for the field (for enumerative fields only an English default value matching one of the neutral enumerative values for the same field is allowed).
3. The relative path to an .inf in a FACS declaration may be wrong. The correct path usually starts with ..\data
4. The adapl with a correct relative path to an .inf in a FACS declaration is run by RunAdapl.exe but you had to enter a path in front of RunAdapl.exe because the command prompt was not in the folder containing the tool. In that case the tool may no longer find any relative path to an .inf in a FACS declaration in the adapl, so try running the executable from within the folder containing it.

56

Invalid tag

57

Invalid CVT

58

No write access

59

No control format error

60

Text file error

61

Invalid occurrence

62

Tag list full

63

Data file write error

64

Operating system error

65

Multi-user error

66

Setup file error (Adlib.PBK)

67

Adlib.pbk outdated

68

Setup file (adlib.pbk) not open

69

Object register error

70

Object register access error

71

Record list insert error

72

Hit list add error

73

Hit list remove error

74

No keywords left

75

Adlib.PRM file not open

76

Error in adlib.PRM file

77

Invalid list position

78

Record overflow

79

Import file not open: check that the import file name has no non-ASCII characters in it and that the file is actually present at the location indicated by the Source data file path and can be opened from there.

80

No back-up files available

81

Dump file not open

82

File remove error

83

Duplicate record number

84

Missing record number

85

Error locking the linked record

86

Error initializing image processing

87

Error in the image file

88

Error loading image file

89

Error expanding image file

90

Write protection error

91

Duplication keyword

92

Invalid instruction

93

Error due to physical lock

94

Error searching index file

95

Error writing to index file

96

Error in index page

97

Error reading index page

98

Error in index definition

99

Error opening index definition

100

Index corrupt

101

Stack error

102

Error in temporary file

103

Record not selected (because of SELECT NO in adapl)

104

Record for synonym not found

105

Invalid path

106

Regular expression exceeds max. length

107

Too many parentheses

108

Parentheses do not balance

109

Error at the end of a regular expression

110

* or + error in regular expression

111

Syntax error in regular expression

112

Invalid range in square brackets

113

Square brackets do not balance

114

Syntax error in regular expression

115

Trailing \ error in regular expression

116

Regular expression corrupt

117

Error in regular expression

118

Error initializing image database

119

Return without gosub in ADAPL

120

Wrong image type

121

Narrower relation not mirrored

122

Imagebase create error

123

Imagebase not open error

124

Imagebase index not open error

125

Imagebase insert error

126

Imagebase search error

127

Image base write error

128

Image base read error

129

Image base delete error

130

Adeval procedure interrupted

131

Error in character set conversion table

132

Search file not found

133

Search file syntax error

134

Error writing pointerfile (aka saved search)

135

Error opening pointerfile (aka saved search)

136

Pointer file (aka saved search) format error

137

Error reading pointerfile (aka saved search)

138

Error during import or export job

139

Search interrupted

140

Error reading freelist

141

Error reading block in data file

142

Record header read error

143

Error in record header

144

Error expanding database

145

Error writing block to data file

146

Illegal input file format

147

Field name not found

148

Error writing to disk

149

Error while forcing linked record

150

Forcing not allowed

151

Error reading locked record

152

Logfile open error

153

Logfile write error

154

Circular internal link error

155

No preferred term

156

Field not empty

157

Duplicate term

158

Non-preferred term refers to preferred term

159

Preferred term has relation error

160

Term being used by other user

161-166

Self-issue loan desk error messages

167

No access error

168-170

Programming errors

171

Object file (.inf, .fmt, .pbk, .imp, .exp, etc.) corrupt

172

System file processed with newer version of software than version with which it was called

173

Recovery database path missing

174

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.)

175

Import file has been made via logging, must be imported using recovery

176

Feedback record found using index on link reference field, but link reference not found in record itself

177

Index on linked field wrong type or missing

178

Linked field/link reference field cannot be removed from record retrieved via feedback links

179

Lock-file lock error (not yet used)

180

File cannot be found

181

Access to a file denied

182

File to be copied cannot be opened

183

File to be written to cannot be opened

184

Error reading a file

185

Error writing to a file

186

Cannot read or change date and time of a file

187

Cursor position changed in an adapl

188

User doesn’t have access to a file (authorization failed)

189

General ODBC error. The error message provides more detailed information

190

Domain error: the domain name is too long

191

Left truncation has been set, but the indexes have not been adjusted accordingly

192

Preferred term relation hasn’t been mirrored

193

Mandatory arguments haven’t been submitted

194

Return date was not calculated

195

Location wasn’t found

196

Search time-out

197

The registry can’t be read

198

The registry can’t be written to

199

The log file cannot be locked

200-250

Reserved for errors in AISODBC.dll (the ODBC driver)

251-300

Reserved for errors in Input/Output

301

Parse error: an error in the syntax of a search statement in the advanced search system

302

Semantic factor relation hasn’t been mirrored

303

MS_XML error

304

The record already exists

305

(no longer in use)

306

ADO error

307

Wwwopac error in http form: no request method has been submitted

308

Wwwopac error in http form: no content length has been submitted

309

Wwwopac error in http form: content length doesn’t match

310

Wwwopac error in http form: no query data

311

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

312

Wwwopac error: semaphore error

313

Wwwopac error: error has already been handled

314

Wwwopac error: database header is missing

315

OAI error: wrong argument

316

OAI error: wrong resumption token

317

OAI error: wrong VERB

318

OAI error: cannot disseminate format

319

OAI error: OAI_ID doesn’t exist

320

OAI error: no records found, or the set is empty or cannot be found

321

OAI error: no metadata formats present

322

OAI error: sets are not supported

323

OAI error: no ADMIN_EMAIL has been set

324

OAI error: no REPOSITORY name has been set

325

OAI error: no DELIMITER has been set

326

OAI error: no IDENTIFIER has been set

327

OAI error: no OAI_DIR has been set

328

OAI error: internal error

329

Gdiplus error

330

Not implemented

331

General error when exchanging data via GLUE with ADO

332

E-mail error. One of the possible causes could be that an adapl is trying to send e-mail with multiple attachments through SMTP: SMTP e-mailing allows only one attachment per e-mail.

333

Configuration error

334

Licence file error: licence invalid

335

Licence file error: licence has expired

336

Licence file error: licence cannot be found

337

Licence file error: cannot write to licence file

338

Licence file error: cannot read from licence file

339

Error in automatic numbering

340

Error in automatic numbering: counter file (.cnt) cannot be opened

342

Error in automatic numbering: counter file (.cnt) cannot be read

342

Error in automatic numbering: counter file (.cnt) cannot be written to

343

Error in automatic numbering: counter file error (.cnt)

344

Error in automatic numbering: lock on .cnt file causes error

345

ADLIBWEB error: general error within GLUE ADW

346

wrong lock ID

347

Error in internal link

348

Error with the type of the index file

349

Duplicate link reference tag

350

Duplicate destination tag

351

Link reference tag not filled

352

No linked data

353

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.

369

XML parse error when reading a record: something is wrong with the record XML.

374

Failed to open printer "printer_name". Make sure the printer has this exact name in the Windows system settings. Also try to select the printer again in of Adlib for Windows. Alternatively hold down the Ctrl key when launching Adlib, and click Yes when you are asked to erase all Adlib registry settings, since that’s where Adlib stores the name of the selected printer.

378

Record cannot be created because the relationship dependency rules for an internal link prevent a record with the current record type to have an internal link such as contained in the record.

380

Import procedure tries to add a related name to a record which is a pseudonym for another name. This is not allowed.

Code

Cause

1001-1006

Internal Windows error

1007

The “busy” mouse cursor couldn’t be loaded

1008

The help text file (adlibhlp) couldn’t be opened

1009

The key entered for the help text doesn’t occur in the help text file (adlib#.hlp or adlib#.adh)

1010

Screen definition file (.fmt) not found

1011

Required system field does not occur in screen definition

1012

Internal Windows error

1013

Printer data cannot be read

1014

The “welcome.bmp” file cannot be opened or displayed because of the PC’s colour settings

1015

The printer cannot print on the selected paper format

1016

The printer cannot print in landscape/portrait format

1017-1024

Internal Windows error

-2147467259

Error during e-mailing. This error may be preceded by a Microsoft Office Outlook message stating that there might not be a default mail client or that the current mail client cannot fulfill the messaging request. The error is caused by the incompatibility of 64-bit versions of MS Outlook 2010 or higher with 32-bit MAPI calls from the 32-bit version of adlwin.exe. The error only occurs when the Windows MAPI is used to send e-mail from within Adlib (instead of using SMTP). The issue can be solved by replacing the 32-bit version of the Adlib executables by the 64-bit version.

Culture is not supported. Parameter name: culture #### is an invalid culture identifier.

If the Locale setting for an .inf has been set to a culture that is not supported by the IIS server for the Collections installation, this error pops up when searching in Collections. Supported cultures differ per Windows version. Axiell Designer fills the list with supported cultures from the Windows-version on the system where Designer is installed. So if Designer is installed on a different system than the Collections application that is being edited, it is possible that a culture is selected that is not supported on the other server. The solution is to install Designer on the server that contains the IIS for the relevant Collections installation and select an appropriate (for sorting of search results relevant) culture in the Locale setting for all the .inf's in the \data folder.