>>>Hi! I got message: "Record not available please wait" scrolling in a wait window. What happened? Thanx a lot.
>>
>>The message means that a file server ran out of lock resources. One of the reasons could be that you issued to meny RLOCK's w/o unlocking previous recors.
>
>Sergey is right. Few additions :
>
>
As far as I know can happen only on a Novell server.
>This "error" cannot be trapped i.e. is unavoidable.
>Will happen when the user itself runs out of lock-resources or when the total server amount runs out of lock-resources (both can be separately set on the Novell server).
>For 99,99 % sure this can occur due to a malfunction in Novell. So, there ARE not too many locks, but the server indicates as such.
>When the amount for one user is exceeded, it 'll be only this one user seeing this (scrolling) message; when it is about the overall amount, more users will have the message.
>When it is the suspected Novell malfunction, check for each user having the messages what he/she has locked; when nothing strange appears (like hundreds of records locked) one by one clear the connection, and look (one by one) if the others can continue. 10 to 1 this will occur, and you just removed a connection with (prooved) not too many locks. -> the malfunction. This may be a rather time-consuming operation, but will proove it is not your app (or is ;).
>
>HTH,
I have also gotten this message from Fox Dos on NT boxes. Usally once one user gets it the others see it fairly fast. We normally find a startup dbf or foxuser.dbf with a lock on it, once cleared everything goes back to normal.
Michael May
mmay@separts.com
972.484.8808
Précédent
Répondre
Voir le fil de ce thread
Voir le fil de ce thread à partir de ce message seulement
Voir tous les messages de ce thread
Voir tous les messages de ce thread à partir de ce message seulement