Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

WDS causes file locking errors

0 views
Skip to first unread message

Jeremy Gollehon

unread,
Dec 4, 2005, 5:04:39 PM12/4/05
to
I have a small network (10 clients, 1 Windows 2003 File Server).

When using the NON-enterprise version of WDS we found a big problem when
saving large (and somtimes small) files. All the client machines have a
mapped network drive from the server and all the WDS are set to index this
drive.

Let's say User1 begins to save a 30MB Excel file. The save time is about 35
seconds and the whole time a randomly named temp file is being built which
is eventually renamed to the original name of the file being saved. The
problem we had was that the WDS Indexer on User2, User3, User4, etc... would
start to index the TEMP file. The first user to start indexing the file
would put a lock on the file and when Excel was done building the temp file
and went to rename to the file to it's real name, a "Application Sharing
Violation" error would be thrown.

The problem would almost always happen with our 30MB file, but would
randomly happen on other occasions with any number of other files in the
share. The solution obviously ended up being "Turn off indexing of the
network share".

With the release of WDS Enterprise edition I expected a way of indexing
mapped network drives that solved this problem. However, reading through
the Windows Desktop Search Administration Guide gives me little hope.

The "don't index these file types", which has always been an available
option, might be helpful except for the fact that the Excel temp files have
no extension.

I thought maybe there would be a multiple index solution involved. One
where the server indexes it's own files and sends updates to the user
indexes. Something like this would solve the problem of the over zealous
user indexing as the server is the only machine indexing it's files and
wouldn't index while there's hard drive activity. I can see where this
would be a problem in larger organizations however because maybe hard drive
activity never subsides.

Anyway, is there any hope to get the mapped network drives indexed or am I
out of luck?
As others might not have run into this problem, and Microsoft Support never
even thought to check this with me, I'm not sure the WDS development team
knows about this problem. Maybe a [MSFT] person can chime in on that one.

Thanks for your time,
Jeremy


gxdata

unread,
Dec 13, 2005, 3:55:46 AM12/13/05
to
I would suggest trying the MSN search weblog at http://blogs.msdn.com/msnsearch/default.aspx
and also the "tech" blog at http://spaces.msn.com/members/wdstech/

However, those guys aren't Support - they're developers or project managers.  You might leave a comment, but it's not their job to provide answers or support.  
 
There is a Support page where you can post your issues.
 
I must say that I have not had any satisfaction there. Just the reverse - I don't know how MS puts up with the contracted-out support which has no idea, and no interest in responding in a professional way.
 
I posted a remark about the (totally unsatisfactory) integration of the user interface for Enterprise version of WDS into the Windows XP SP2 search via Windows Explorer. I received a reply which was totally unrelated -
 
Thank you for contacting Microsoft Online Customer Service.
From your message and information, I understand you are located in Australia. There are significant programming differences between North American and localized versions of software. You will be best assisted by the subsidiary that specializes in your specific version. If you have obtained your Microsoft software in  Australia, I suggest you contact Microsoft  Australia as they are in a better position to assist you.
To contact Microsoft  Australia, please visit ....
I should add that the email respondent's email adress was "Abuse at Microsoft" ab...@microsoft.com - obviously, my post was regarded as abusive, rather than a legitimate complaint with suggestions for remedies.
 
So, I contacted his manager, and received a similarly unhelpful and dismissive response:
I'm sorry you were not completely satisfied with the technical support you received.  Our goal is that every customer be completely satisfied so we appreciate the feedback that you have offered.  
Please continue to offer us feedback in the future as it is the only way we can know, what we are doing well and the areas in which we may need to improve.
Thank you for using Microsoft products and services.
I wish you luck!!
 
--
IL Thomas
 
0 new messages