From: sparrows on

I am researching this same error. I would ignore it, but it reboots WOW
everytime it occurs, 3-4 times an hour. It's hard to pillage and burn
with this type of ignorable error.

The 3013 error includes a subdir in WOW that for some reason Microsoft's
WDS does not like to eat.

Any ideas how to disable this tool or otherwise "fix" this error?

I realize this is an old post. And an old error, that MS has ignored
for at least 244 days.


--
sparrows
From: Susan Bradley on
sparrows wrote:
> I am researching this same error. I would ignore it, but it reboots WOW
> everytime it occurs, 3-4 times an hour. It's hard to pillage and burn
> with this type of ignorable error.
>
> The 3013 error includes a subdir in WOW that for some reason Microsoft's
> WDS does not like to eat.
>
> Any ideas how to disable this tool or otherwise "fix" this error?
>
> I realize this is an old post. And an old error, that MS has ignored
> for at least 244 days.
>
>
>
And you've posted from a forum interface so that in the newsgroup I
can't tell what you are talking about.

No Microsoft hasn't ignored it. But given that I'm not sure what you
are talking about, I can't help you. Can you post back with better context?
From: Susan Bradley on
sparrows wrote:
> I am researching this same error. I would ignore it, but it reboots WOW
> everytime it occurs, 3-4 times an hour. It's hard to pillage and burn
> with this type of ignorable error.
>
> The 3013 error includes a subdir in WOW that for some reason Microsoft's
> WDS does not like to eat.
>
> Any ideas how to disable this tool or otherwise "fix" this error?
>
> I realize this is an old post. And an old error, that MS has ignored
> for at least 244 days.
>
>
>
Event ID 3013:
http://www.eventid.net/display.asp?eventid=3013&source=

Why do you have desktop search installed on the server anyway?