Read errors

[driessen]

Hello,

Some of my customers get a read error on a DBF-file now and then.

But when the application is started again, everything runs fine.

The error generated show me DOS-error somtimes :

DOS error 58 (= incorrect response from network)
or
DOS error 64 (= network name deleted)

Can someone assure me that this is not a FWH or xHarbour problem ? These kinds of errors occur only in my application, although the error tells us that something might be wrong with the network.

I have this kind of problem at 3 different customers. It looks strange to me that all these customers should have a network problem.

What is the opinion of the FWH-users ?

Thanks a lot for any idea in advance.

[ukoenig]

Hello Michel,

there seem to be something wrong with the network-install.
The english error-messages are very short and hard to understand.
I found a complete specification ( in German ) with detailed informations for XP-errors.
If somebody need it, here is the link :
P.C.H. - MS Windows XP Home Edition
Error Messages (Fehlermeldungen) and Codes
http://www.pch.co.at/P.C.H.%20-%20MS%20 ... 0Codes.htm

Error No.
1 Invalid function number
2 File not found
3 Path not found
4 Too many open files (no handles left)
6 Invalid handle
7 Memory control blocks destroyed
8 Insufficient memory
9 Invalid memory block address
10 Invalid environment
11 Invalid format
12 Invalid access code
13 Invalid Data
14 Reserved
15 Invalid drive was specified
16 Attempt to remove current directory
17 Not same device
18 No more files
19 Attempt to write on write-protected diskette
20 Unknown unit
21 Drive not ready
22 Unknown command
23 Data error (CRC)
24 Bad reuest structure length
25 Seek error
26 Unknown media type
27 Sector not found Signs of HDD corruption.
28 printer out of paper
29 write fault
30 Read fault
31 General failure
32 sharing violition
33 lock violition
34 Invalid disk change
35 FCB unavailable
36 Sharing buffer overflow
37 - 49 Reserved
50 Network request not supported
51 Remote computer not listening
52 Duplicate name on network
53 Network name not found
54 Network busy
55 Network device no longer exists
56 Network BIOS command limit exceeded
57 Network adapter hardware error
58 Incorrect response from network
59 Unexpected network error
60 Incompatible remote adapter
61 Print queue full
62 Not enough space for print file
63 Print file deleted (not enough space)
64 Network name deleted
65 Access denied
66 Network device type incorrect
67 Network name not found
68 Network name limit exceeded
69 Network BIOS session limit exceeded
70 Temporarily paused
71 Network request not accepted
72 Print or disk redirection paused
73-79 Reserved
80 File already exists
81 Reserved
82 Cannot make directory entry
83 Fail on INT 24H
84 Too many redirections
85 Duplicate redirections
86 Invalid password
87 Invalid parameter
88 Network device fault

------- In English / German -------
58 The defined Server cannot start the requested process
58 Der angegebene Server kann den angeforderten Vorgang nicht ausführen.
64 The defined network-name is unavailably.
64 Der angegebene Netzwerkname ist nicht mehr verfügbar.
---------------------------------------

DOS Error Code/Classes
Error Classes
----------------
01 Out of resource, out of space, channel, etc
02 Temporary situation, not an error, ex: file lock
03 Authorization, permission denied
04 Internal, system detected internal error
05 Hardware failure, serious problem related to hardware
06 System failure, ex: invalid configuration
07 Application error, inconsistent request
08 Not found, file/item not found
09 Bad format, file/item in invalid format
0A Locked, file/item interlocked
0B Media failure, ECC/CRC error, wrong or bad disk
0C Already exists, collision with existing item
0D Unknown, classification doesn't exist or is inappropriate

Regards
Uwe

[StefanHaupt]

Michel,

I assume, the dbf-files are installed on network drive. Where is the network drive located, is it on a client or on a server with a domain environment ? At what operations does the error occur ?

I have a similar problem sometimes, the answer of the server lasts longer than normal and so the client thinks the connection is lost. I have this problem only on clients with two network cards.

You can write your own error handler for these situations to get rid of the error message and give your application more time to finish the operation.

[Antonio Linares]

Michel,

Harbour/xHarbour manage those DBF read operations, not FWH.

FWH just asks Harbour/xHarbour to read records for a browse, a database object, etc. but all those read operations are performed by Harbour/xHarbour.