• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 439
  • Last Modified:

ERROR_SHARING_VIOLATION when multithreading

Hi!

Not quite sure which topic to use here, if it's a Windows7-problem or a general network problem.

I make  a program that can run heavy calculations on several pcs connected (a little like SETI@home). It uses files as interface between processes. The program can run on different threads on the same machine. Almost.

It has been working fine for a long time on WinXP. But one beta-customer has problems with the new version (which introduces the hyperthreading) on Windows 7. On his machine, if I call:

MoveFile(fileA, fileB);

for a file on the network at the same time from 2 different threads, none of them get access! Both get ERROR_SHARING_VIOLATION. On the network here at work that _never_ happens.

If I do the same with local files, everything is OK.

What can the difference be? Some access rights on this directory related to sharing?

Shouldn't one of them be the first anyway and get full access, while the next one can only read? As it is now, the file doesn't even get _copied_!

Are there any other more threadsafe ways to achieve this? I wouldn't like to rewrite the whole structure of the program.
0
Knut Hunstad
Asked:
Knut Hunstad
  • 3
  • 2
1 Solution
 
strivoliCommented:
You should enable the appropriate auditing level on the destination system. Once you get the error, check the Windows Security Log on the destination and you should get a better idea why it fails.
0
 
Knut HunstadAuthor Commented:
The file system is a DFS system with the files residing on non-Windows-servers, as I understood it. So there is no Windows security log to check on the destination.

The user was able to use a Windows server instead, so they have a workaround now. I still would like to find some solution to the original problem. The IT-people at the customer thought it might have something to with "opportunistic locking", but I haven't been able to find any conclusion as to why that would trigger this problem.
0
 
strivoliCommented:
Even non-Windows-servers do have auditing. Usually it is syslog. I still suggest you to have a look at any syslog messages reporting locks that might be the reason of the problem. Syslog is configurable in a more or less verbose mode. You should find the better verbose level that suits your case: if it is too low you might miss important warning messages, if it is too high you might get too many messages (hundreds and even thousands per second) and as a result it could be very hard to find the messages related to your problem.
Please let me know.
0
 
Knut HunstadAuthor Commented:
Thanks for trying! But since this user has a workaround and no other users have reported the same problem, I will simply let it rest. I can't really expect this user's it-department to be interested in helping me further when they have a solution for themselves...

I am confident that your suggestions are valid, however, and very happy that someone bothered to try to help me along! So I award you full points for your last answer.
0
 
strivoliCommented:
Thank you for closing the question. Hope my suggestion will help in the future with the same or similar problem. Have a nice day!
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Introducing Cloud Class® training courses

Tech changes fast. You can learn faster. That’s why we’re bringing professional training courses to Experts Exchange. With a subscription, you can access all the Cloud Class® courses to expand your education, prep for certifications, and get top-notch instructions.

  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now