Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

NWGetNSEntryInfo() returns "BAD RECORD OFFSET" error.

6 views
Skip to first unread message

grevans

unread,
Nov 11, 2005, 7:03:14 AM11/11/05
to
Netware Server: 4.11 SP9

From a Windows client, we ran a program which generates 50 directories,
each of which contain 50 directories, each of which contains a hundred
files. Each directory has a name from Dir0000 to Dir0049. Each file has a
name conssiting of a long string of random letters and characters.

We then run a backup which backs each directory up in reverse alphabetical
order. While backing up the last directory (Dir0000Dir0000) calls to
NWGetNSEntryInfo() for each and every file in the directory return error
35327 (0x89FF) which means "BAD RECORD OFFSET". The call to
NWGetNSEntryInfo() for the directory itself succeeds.

The online documentation gives no explanation of why this error occurs.
Looks like a NetWare bug probably. I followed the instructions for
submitting a problem report, in return for whcih I am promised "No
technical feedback".

I appreciate that this is an antique version of NetWare, but unfortunately
we have to support it. Any advice/help would be much appreciated.


David Mair

unread,
Nov 11, 2005, 12:05:56 PM11/11/05
to

I have to say that this version of NetWare is so old that it might be
wise to consider it obsolete and not support it.

NB: Was it a typo that you say the last directory was
"(Dir0000Dir0000)", in the first paragraph you describe the directory
name as having the format Dir00nn. If the latter is correct and you use
the former to access files then the files will not be found and, in the
case of a directory enumeration that might be considered to have the
semantics of a bad record offset. Don't take that overly literally, it
might be why that specific error is obtained and it might be because the
programmer that implemented the behaviour overloaded the meaning when
trying to solve the problem but there's no way to know.

grevans

unread,
Nov 30, 2005, 9:23:25 AM11/30/05
to
David Mair wrote:


Dir0000Dir0000 is my web browser mis-interpreting the forward slash. Or
maybe it's a typo.


Guenter Knauf

unread,
Dec 1, 2005, 6:43:40 AM12/1/05
to
Hi,
Alastair...@bakbone.co.uk (grevans) wrote in news:6M%cf.155$E23.53
@prv-forum2.provo.novell.com:

it would help if you can recreate that issue in a small sample; f.e. if you
post the windows part + a small NLM which shows the issue here (with source
of course). Is it a NW4.x-only issue? Does your code run fine on any later
version?? Have you applied latest SP to 4.x? Any later beta patches?

Guenter.

0 new messages