Windows Search and "Problem with Shortcut" popup box

[Guest]

I use Windows Desktop Search, and when it indexes my files in the background
it sometimes starts to pop up an annoying box all the time. The title of the
box is "Problem with Shortcut", and the text is "The drive or network
connection that the shortcut 'target.lnk' refers to is unavailable. Make
sure that the disk is properly inserted or the network resource is available,
and then try again".

I have checked, and the box belongs to the process "searchprotocolhost.exe"
which is spawned by "searchindexes.exe".

I can click ok on the box, but it just pops up again rather quickly. If I
leave it open, it will eventually (after 10-15 minutes maybe) go away, and
then come back after a few minutes.

This is very annoying when I am working or playing games, and I would like
to hear if anyone else have this problem, or of course a solution to the
problem.

I might add that I have a pretty large database. At the moment it has
indexed about 620 900 files, and it has about 96700 left to index. I index 4
hard drives in my computer, and 4 network drives (which are available when
this error occurs).

If I reboot my computer, it can go anywhere from 5 minutes up to several
hours before this error occurs again.

 

[Rock]

I use Windows Desktop Search, and when it indexes my files in the
background
it sometimes starts to pop up an annoying box all the time. The title of
the
box is "Problem with Shortcut", and the text is "The drive or network
connection that the shortcut 'target.lnk' refers to is unavailable. Make
sure that the disk is properly inserted or the network resource is
available,
and then try again".

I have checked, and the box belongs to the process
"searchprotocolhost.exe"
which is spawned by "searchindexes.exe".

I can click ok on the box, but it just pops up again rather quickly. If I
leave it open, it will eventually (after 10-15 minutes maybe) go away, and
then come back after a few minutes.

This is very annoying when I am working or playing games, and I would like
to hear if anyone else have this problem, or of course a solution to the
problem.

I might add that I have a pretty large database. At the moment it has
indexed about 620 900 files, and it has about 96700 left to index. I
index 4
hard drives in my computer, and 4 network drives (which are available when
this error occurs).

If I reboot my computer, it can go anywhere from 5 minutes up to several
hours before this error occurs again.

I suggest you post to the WDS forum.

http://forums.microsoft.com/MSDN/ShowForum.aspx?ForumID=847&SiteID=1