File share issue

OK, this problem started when the windows 98SE workstations were upgraded to windows XP Pro. The users have quickbooks 2003 installed and open multiple company files. When they change from one file to another using... file, open company ect... they get an error, one of three errors complaining about a lost connection to the drive, unsufficient rights, or unable to create an image file. The users who are accessing this share have full control over the share. The server that the files reside on is a Small Business Server 2000. There is a Q: drive on the workstations mapped directly to the quickbooks share on the server. After the error comes up on the workstation, I open the computer management console and browse to the open files, the last file to successfully open is still showing as opened by the user. I do believe this is an important peice of info, the fact that the files are not closing properly. So i right click the open files, select close open file then the workstations are able to open the file. Unfortunatly this is not an acceptable fix and the users need to be able to open files without any errors.

Quickbooks has already been uninstalled and reinstalled. A new share has also been created just to try and troubleshoot this problem. Ive also added the users to the administrators group on the server to try and resolve any rights issues we might be running into which was not successful.

Any helpful info on this will be greatly appreciated. If you need any more information about this issue please ask.

municoreAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
ShineOnCommented:
I think stevenlewis has you on the right track.  This sounds to me like an issue with using older technology with newer technology in the Windows world.

One of the big changes between Win98SE and WinXP Pro is how much more WinXP Pro uses Opportunistic Locking.

OpLocks can make a great deal of difference in performance, but when working with a shared file not built for oplocks, can cause various issues.

Personally, if the primary function of these users is to use shared Quickbooks files, I would take whatever steps necessary to disable Opportunistic Locking.  I think stevenlewis' links may speak to that, but if they don't, there are quick registry tweaks that can be done to do this.  Let us know - I don't like to recommend registry-tweaking unless it is necessary.
ShineOnCommented:
The way OpLocks works is, the workstation essentially takes over control of the file, caches the file locally, all changes are made locally, and the lock on the shared file does not go away until the cached, updated file is saved and released by the workstation.

It really does speed up update processes, but also tends to cause these issues you are having with the file being locked by another workstation when you need to get at it.

If you take OpLocks out of the picture, the updates happen directly to the shared file, with the lock only in effect during the update.  Because of that, it increases network traffic and slows down local Workstation processing waiting for I/O with the shared resource.  The gain with disabling OpLocks is that you get better, more stable shared access that is less likely to cause file corruption in files that are not built to be shared via OpLocks.  It's kinda related to database referential integrity - not the same thing, but the same concept.
municoreAuthor Commented:
The problem was resolved by installing the latest security update on the server and restarting it.? I am giving the points to these two users for thier input and suggestions which would have led me to the fix. I am still not sure what resolved the issue because the server was restarted numberous times and Im doubting a security update resolved this.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Networking

From novice to tech pro — start learning today.