Client locking PDOSUSRS.NET

[Killiss]

We ave run onto what seems to be an old issue. We recently upgraded the
workstations to XP and the latest Novell clients. All out applicaitons run
fine except for Timeslips which uses the Borland Database Engine. It
appears that the BDE cannot access the PDOXUSRS.NET file since it keeps
getting locked by the Novell client.

Server: Netware 4.11
Network: IP/IPX
Workstations: WinXP SP2
Client: 4.90 SP2
Timelslips; Version 10.x

The most relevant TID I found was TID10069333 (May 2002) which referred to
client 4.83. This problem was supposely fixed with a patch.

Other TIDs refr to LCK files. But these cannot be created since the
pdoxusrs.net file cannot be accessed. Since the workstations are new
installs, there is really nothing locally that I can find that could be
causing this issue.

Any help is appreciated.

Farokh Monajem
Learn.exe
Toronto, Canada

[Klaus Klickermann]

Killiss schrieb:

We had also some problems with the pdoxusrs.net-file on W2K-clients. We
must gave our users (local) right to write, modify and delete this file.
This solves the problem.

Klaus Klickermann

[Killiss]

Thank you for the reply.

The app is installed on the server and all users have those rights to the
folder. So I am not sure what local file or folder to give rights to,
specially since the users in question are logged into the workstation with
admin rights.

Everything was working fine under Win98. The only change we have made is
upgrade the OS and of course the client.

Farokh

"Klaus Klickermann" <PuK.Kli...@T-Online.de> wrote in message
news:GGIpd.2521$0A2....@prv-forum2.provo.novell.com...

[Tony Pedretti]

Farokh,

Is PDOXUSRS.NET locked after the first user hits it and then every user after
that can't use Timeslips?
Is the Novell Client installed IPX only?
Does NetWare 4.11 have support pack 9 installed?
Does disabling File Caching in all the client's Advanced settings tab help any?
Windows Event Viewer logs showing anything unusual?

You might consider testing Update C for SP2 or in combination with some of the
other post-updates...

Production updates for 4.90
http://support.novell.com/filefinder/18193/index.html

Beta updates for 4.90 (beta can be better in some cases than production)
http://support.novell.com/filefinder/18193/beta.html

If you can then isolate the issue to 4.90 SP2 and its post-updates and in
addition of discussing it here, you might try reporting the issue to Novell with
as many
details about your setup (drivers, services, apps, protocols, network traffic
traces, etc.) as requested in the beta update TIDs...

"Thank you for field testing this beta patch. Please send feedback regarding the
results of your testing (positive or negative) to: patchf...@novell.com. Use
the name of the patch as the subject of the message. Your detailed comments are
appreciated."

--
Tony Pedretti
TransUnion LLC

[Killiss]

Thanks for the reply.

PDOXUSRS.net locks when any user attempts to access the Timeline database.
The a launches perfectly but is barred from the data source; so no one can
access the database.

Client is installed IP/IPX since we have a colour printer/copier that is
attached via IP.

All support packs have been installed

File caching turned off: no change

NMAS turned off: no change (saw another post tat mentioned this as a
potential culprit for client issues)

Windows Event Log shows all the usual stuff, nothing unusual, no red "x"s
anywhere

Will attempt the new client tonight. I notice that version 4.91 has been
posted.

If that does not work, then it is off to the beta reporting site!

Farokh Monajem
Learn.exe

"Tony Pedretti" <yno...@nOsPaMhotmail.com> wrote in message
news:VhQpd.2780$0A2...@prv-forum2.provo.novell.com...

[Tony Pedretti]

Farokh,

Are you printing to that colour printer/copier with NDPS or iPrint? If not, the Novell
Client will not need to bind with IP using NetWare 4.x and therefore you should be able to
install the client IPX-only.

Take a look at the Cache Exclusive Open client setting too...

Slow application performance with Novell Client 4.83 for NT/2K/XP
http://support.novell.com/cgi-bin/search/searchtid.cgi?/10076527.htm

[Killiss]

Tha's funny. Right after my last post, I thought I should do exactly that:
not install IP with the client!

Will post results tomorrow.

Thnaks for the help.

Farokh Monajem
Learn.exe

"Tony Pedretti" <yno...@NOSPAMhotmail.com> wrote in message
news:Ewkrd.6067$0A2....@prv-forum2.provo.novell.com...

[Tony Pedretti]

Farokh,

The Cache Exclusive Open settings is not in the client's properties. As the TID mentions,
its a registry value you create manually using something like Regedit or via .reg file.
Do you need help with that?

From the client's view, Opportunistic Locking is a feature of File Caching so disabling it
on all of them would effectively disable op-locking. For simplicity its usually
recommended to disable on the server itself, but since you're using NetWare 4.x I'm not
sure the feature is even available let alone supported.

This could very well be an issue with the 4.9 client and the Timeline/Paradox database.
Have you submitted details to Novell as I mentioned in a prior post?
You might also consider opening a service request with them.

[Killiss]

Uninstalled the client and re-installed with IPX only. No change.

Changing the settings for NMAS or the File Caching had no effect either.

Downloaded rev C, no change. Updated with latest patches, no change.

I coud not find the setting for Cache Exclusive Open in the client. Sorry.

The article below is interesting and once more mentions Opportunistic
Locking. I cannot seem to find anything to tell me how to control this
feature. It seems to be no longer valid with the latest clients. I guess I
will have to venture into the registry...

AAAGGGHHHHHH!

Farokh

P.S. Have I already thanked you for your help?
Thank you again.

"Tony Pedretti" <yno...@NOSPAMhotmail.com> wrote in message
news:Ewkrd.6067$0A2....@prv-forum2.provo.novell.com...

[Killiss]

I have no problems editing the registry. Everyone seems so intimidated by
the beast that is the registry. But you have to go in there so often to
remove virus entries, that it has now become a non-event. Still have to be
careful, back it up and so on, but no mystery there.

I think I read about opportunistic locking on a Windows 95 machine I have
sent the information to Novell as per your request.

I have not opened a service request since we do not have a service contract.

I will make the changes to the registry over the weekend.
I will also install client 4.91 as per " BETA Novell Client v4.91 for
2000/XP English - TID2970098 " if the registry changes do not work.

By the way I keep referring to the offending software as Timeline. It is
actually called Timeslips from Best Software.

You just cannot relax in this business. I just went to the Knowledgebase to
look up opportunistic locking. There is a new article on the topic dated
Nov 30, 2004!
http://support.novell.com/cgi-bin/search/searchtid.cgi?/10095627.htm

And life goes on.

Farokh

"Tony Pedretti" <yno...@NOSPAMhotmail.com> wrote in message

news:X2Ird.7511$0A2....@prv-forum2.provo.novell.com...

[Tony Pedretti]

Fortunately that TID just provides background information and history of
opportunistic locking and not a new issue with it.

[Killiss]

Sorry this took so long.

Made the changes to the registry. Still no go.
Reverted to Client version 4.83 SP2, got a different error message fromt he
Borland Database engine which I am looking into.

And the saga continues.

Farokh.

"Tony Pedretti" <yno...@nOsPaMhotmail.com> wrote in message

news:2Ojsd.9429$0A2....@prv-forum2.provo.novell.com...