Anyone experience this error when a user id trying to log in? We are running Enterprise 2000 and have 30 licenses currently.
Error:
File is currently in use.
Waiting for access to file.
Original Post
Replies sorted oldest to newest
Hi,
This problem is caused by the User file becoming locked by a client Machine. There are a number of reasons this can happen which we can go into once we have everyone logged in to the Database again!
On the server, I would suggest restarting the Pervasive services. In the folder where the database is stored there will be a File named ~pvsw~.loc, open this file using Notepad, it will give the name of the machine that is locking the database.
Delete the ~pvsw~.loc file, your users will now be able to log in again.
Try opening the database on the affected machine, this may work successfully or we may have to restart the process again.
If this machine persistantly locks the database then we may need to check its name resolution and the mode in which it has been installed.
Post back if you want to go into more detail.
Regards
Nick Welburn
CABC Support
This problem is caused by the User file becoming locked by a client Machine. There are a number of reasons this can happen which we can go into once we have everyone logged in to the Database again!
On the server, I would suggest restarting the Pervasive services. In the folder where the database is stored there will be a File named ~pvsw~.loc, open this file using Notepad, it will give the name of the machine that is locking the database.
Delete the ~pvsw~.loc file, your users will now be able to log in again.
Try opening the database on the affected machine, this may work successfully or we may have to restart the process again.
If this machine persistantly locks the database then we may need to check its name resolution and the mode in which it has been installed.
Post back if you want to go into more detail.
Regards
Nick Welburn
CABC Support
Please send me more info as I have a user or two (they used to be remote users and have recently requested to be connected to the local -server- database) that are still locking the files out. Help !!!!!
Ok,
There are two ways really that this can happen, first a little bit of Background,
Pervasive the database engine behind the Maximizer clients has two modes when it is installed on a local machine. It can either open the data itself or it can request the data from another machine.
What we have happening here is that some of your machines are trying to open the data themselves.
!!I am assuming that your Network is TCP/IP based and running Pervasive Client Server!!
If the machines have been recently installed or have never worked on the Main database then I suspect they have been installed in the wrong mode, reinstall the Maximizers in the Client Server mode, this is pretty obvious on the install if you know to change it, if not then I don't think its the default option...
If the machines used to work correctly but have recently stopped then I suspect that the Name resolution from those clients is not working correctly, either it doesn't resolve or resolves to the wrong IP address.
If this is the case then the request for data from these machines is routed to the wrong server, this times out; then the Maximizers try to open the data themselves this locks the files...
Hope this helps
Regards,
Nick Welburn
CABC Support
There are two ways really that this can happen, first a little bit of Background,
Pervasive the database engine behind the Maximizer clients has two modes when it is installed on a local machine. It can either open the data itself or it can request the data from another machine.
What we have happening here is that some of your machines are trying to open the data themselves.
!!I am assuming that your Network is TCP/IP based and running Pervasive Client Server!!
If the machines have been recently installed or have never worked on the Main database then I suspect they have been installed in the wrong mode, reinstall the Maximizers in the Client Server mode, this is pretty obvious on the install if you know to change it, if not then I don't think its the default option...
If the machines used to work correctly but have recently stopped then I suspect that the Name resolution from those clients is not working correctly, either it doesn't resolve or resolves to the wrong IP address.
If this is the case then the request for data from these machines is routed to the wrong server, this times out; then the Maximizers try to open the data themselves this locks the files...
Hope this helps
Regards,
Nick Welburn
CABC Support
Thank you very much, this has helped a lot.