I've been called to help with a problem that was originally reported as a GFE. Now, attempted updates to a file are met with FS102. We use the NLM using the REVELATION user. Things I've tried:

* All files have owners.

* User doing access has full rights.

* REVELATION user has full rights.

* Both the directory and all files are flagged read, write, and shareable.

* Unloaded and reloaded NLM.

* Restarted file server.

Anything else to try?

Victor

I forgot to mention that I created a REVPARAM file which hadn't previously existed, and put SERVERONLY=1 on the first line.

Victor,

Are you positive that the TSR is being loaded on the client and that the NLM is running on the server?

Also, have you verified that the frame type for the client matches the frame type for the server?

That's all I can think of at the moment.

msorrel@greyhound.com

Greyhound Lines, Inc.

I haven't checked frame types. I'll pass that on the the Netware administrator to check. Another thing I've suggested he check is quotas. But if a quota was reached wouldn't we expect an out of disk space message instead?

BTW, I suspect some other networking-related issue is the problem, because I cannot connect to that server using the userid we normally use to connect to it. But the user having the problem has that server as their home server, so connecting to it is not an issue (they're already connected).

Is the max users being exceed on the Novell license?

I can't recall the specifics of problem we had many years ago, but the users could log onto Novell, and then Arev gave us issues of some kind.

More Netware licenses solved the problem.

That situation usually results in the "Attempt to log in too many users" message, even if you have sufficient licenses for ARev.

msorrel@greyhound.com

Greyhound Lines, Inc.

View this thread on the forum...