Server: NetWare 5.1 SP5
Client: 4.90
4.90 SP1
4.90 SP2
We have a database hosted on one of our servers that is accessed by a large
number of users in our company. Currently they open the database using a
batch file. Once we upgraded some users to the 4.9SP2 client they began
receiving the following error:
Opening Database...
The process cannot access the file because it is being used by another
process.
This problem does not appear to occur with the 4.8x client, but does occur
with 4.90, 4.90SP1, and 4.90SP2. I applied the post SP2 patches (including
the NWFS update recommended in TID2970687) but the problem still persists.
Browsing to the database and opening it through explorer works fine, but
opening the file from a command line or batch file does not. The database
in question is flagged as transactional, and this is happening on both
Windows XP and Windows 2k machines with Office 2k or 2003 (all patched to
varying levels of service packs).
Replacing nwfs.sys with the one that came with 4.81 eliminates the issue,
but obviously using such an old version of the file isn't a permanent fix.
Any ideas as to why this might be happening?
Also, if there is a better forum to post this to, please point it out. I looked for a client forum, but could find none.
Client: 4.90
4.90 SP1
4.90 SP2
We have a database hosted on one of our servers that is accessed by a large
number of users in our company. Currently they open the database using a
batch file. Once we upgraded some users to the 4.9SP2 client they began
receiving the following error:
Opening Database...
The process cannot access the file because it is being used by another
process.
This problem does not appear to occur with the 4.8x client, but does occur
with 4.90, 4.90SP1, and 4.90SP2. I applied the post SP2 patches (including
the NWFS update recommended in TID2970687) but the problem still persists.
Browsing to the database and opening it through explorer works fine, but
opening the file from a command line or batch file does not. The database
in question is flagged as transactional, and this is happening on both
Windows XP and Windows 2k machines with Office 2k or 2003 (all patched to
varying levels of service packs).
Replacing nwfs.sys with the one that came with 4.81 eliminates the issue,
but obviously using such an old version of the file isn't a permanent fix.
Any ideas as to why this might be happening?
Also, if there is a better forum to post this to, please point it out. I looked for a client forum, but could find none.