The Clarion Advisor: Topspeed Driver Error Codes

Published 1999-02-22    Printer-friendly version

Many Clarion developers use the TPS file format for small- to medium-sized databases, and with good success. Through Clarion release 4A, however, some users reported regular data corruption problems.

With driver fixes in 4B these problems seem to have largely gone away, but some forms of corruption are still outside the control of the driver, and network installations can be a particular problem. Anyone storing TPS files on an NT server with Windows '95 workstations should be sure to install Microsoft's redirector patch. You can download it from:

http://support.microsoft.com/ support/kb/articles/q148/3/67.asp

Thanks to Steve Mull for providing the link.

The following table lists the possible Topspeed error codes (thank you to Nigel Hicks for providing this!).

If you have any additional comments you'd like to see added to this list, email the editor.

Error Description
53

May be caused by a relative pathname, may be fixed by specifying the full path. Further information from a newsgroup post by Jeff Slarve:

Today we had a user report an ErrorCode() 53 using the TOPSPEED file driver. This is on an application that has been running for several years at many locations without incident. When I fully qualified the filename, it worked as expected. Before that, it was just the relative path (on a network drive).

Facts about the setup and environment:

  1. File is TOPSPEED
  2. Filename was set as being a relative path. ('MySubDir\MyFile.tps\!YadaYada')
  3. Workstation is XP Pro SP2, but I've seen a different error happen with win98 and relative path.
  4. When the software was loaded on a local drive, there was no error.
  5. Another (seemingly) identical workstation was able to run the software without errror, pointing to the same server.
  6. Many many locations use a similar relative path with no problems.

There must be something about the setup that causes the relative path thing to fail, but I don't know what it is. The problem seems to be solved by using LongPath(), but I would love to know what caused the failure.

112 Not a TPS error, this is an OS error meaning out of disk space.
231 Trying to append a record when the btree is marked read-only
232 Cannot get btree header when trying to append a record
256 Cannot get btree header when trying to get a record;
300 Btree structure corrupt (discovered when deleting a record)
327 Btree structure corrupt (discovered when putting a record)
337 Trying to put a record when the btree is marked read-only
522 Invalid data size found while unpacking record (from disk)
530 Invalid repeat count found while unpacking record (from disk)
706 Btree structure corrupt (discovered when inserting a record)
780 Btree structure corrupt (discovered when removing a record)
824 Btree record size too big (on allocation)
1013 Cannot get btree header (while loading root page)
1043 Cannot get btree header (while packing a record to disk)
1163 Trying to create new record ID when the btree is marked read-only
1164 Cannot get btree header (while allocating new record ID)
1173 Maximum record ID reached on allocation (probably indicating file corruption)
1194 Trying to insert record when the btree is marked read-only
1203 Trying to remove record when the btree is marked read-only
1258 Btree structure corrupt (obsolete in C5
1364 Btree structure corrupt (discovered while splitting a page)
1477 Btree page size (from header) does not match size stored on disk , could result in a truncated file, run tpsfix
1602 Btree unpacked page size (from header) does not match size loaded from disk
1659 Btree page size increased after packing
1678 Btree page size larger than maximum allowed
1735 Btree header corrupt (discovered when trying to calculate disk file size)
1781 Btree structure corrupt (discovered while shifting btree pages up)
1891 Btree structure corrupt (discovered while moving btree pages)
1894 Btree structure corrupt - invalid page parent level (discovered while moving btree pages)
2172 Reading of btree page from disk failed
2183 Too many files logged out
2272 Encryption block invalid size (discovered when reading page from disk 32-bit)
2277 ReadFile Win32 API function failed (when reading page from disk)
2286 Encryption block invalid size (discovered when writing a page to disk)
2328 Invalid internal btree locking mode (on lock (32 bit))
2352 Invalid internal btree locking mode (on unlock (32 bit))
2341 SetFilePointer Win32 API function failed (when reading page from disk)
2361 UnlockFile Win32 API function failed (obsolete on C5)
2447 16 bit close file failed
2458 16 bit handle duplicate failed (during commit)
2460 16 bit close file failed (during commit)
2476 Invalid internal btree locking mode (on lock (16 bit))
2519 Invalid internal btree locking mode (on unlock (16 bit))
2528 Unlock dos function failed (obsolete on C5)
2572 Encryption block invalid size (discovered when reading page from disk 16-bit)
2582 Encryption block invalid size (discovered when writing a page to disk 16-bit)

Printer-friendly version

 
 

Search

 

Advanced Search
Topical Index

Related Articles

Subscribe to
ClarionMag

One year: $184

(includes all back issues since '99)

Renewals from $134

Two years: $274

Renewals from $224

More Info

Subscribe Now!

ClarionMag Blog

RSS Feeds

Updates via Email

Enter your Email


Powered by FeedBlitz

Quick Links