We completed moving our AREV 3.1 database from a Novell 4.11 server to Windows 2000 Server last night.

Since then, users are intermittently locking up (only the AREV application, not Windows) and also, from within AREV, receiving the following message:

"Unable to read from drive ?. Abort, fail, retry?"

At that point, they have to force it shut and try again. Oddly enough, it doesn't call out a drive letter - just the question mark.

There does not seem to be any rhyme or reason as to when this occurs although it usually happens to multiple people at the same time.

All workstations are running Windows 98, Novell Client32 3.3 and using TCP/IP to connect to the Windows server.

Any help would be greatly appreciated.

Tony Hake

tony@codoor.com

My first reaction is that if a changeover was made from Novell to Windows 2000 server, why are the clients still using the Novell client32?

You are correct in that the workstations still have Client 32 on them and this must remain like this for a month or so. We are transitioning our entire network from Novell to MS and can't remove Client 32 until the last step (it is required for other programs we run in the meantime).

I assume you map a drive letter for use by Arev. When this error condition happens, does the drive mapping go away on the client's Windows explorer? When checking this, make sure you do a refresh (F5) because sometimes Windows presents cached information.

If it does appear, what happens when you right click and select properties?

That is what is really odd - the drive mapping stays in place, it never really loses its connection. Pulling up the properties works as it should.

Just a comment:

I have never gotten ARev to behave properly on an MS network unless IPX was running on the workstations and the server.

David

View this thread on the forum...