Error: "Target Designer was unable to clear the contents of the de

[Guest]

I have been getting this error message for 2 days now when trying to build an
image:

Target Designer was unable to clear the contents of the destination folder
that you have specified. Please check the permissions on these files.

I have searched all over the internet and not been able to find any answers.
I have successfully built images in the past, but this just started
happening yesterday. I have tried different folders, different partitions,
and even a network share but the message is consistent. I have tried
everything I can possibly think of, and Im going crazy.

Can anyone please HELP!!

gkc

 

[Lynda Allen [MS]]

Is this when you are trying to build an image? If so, TD is unable to
overwrite a previous image that you have stored at the same location. Delete
the previous image or point TD to build your current image to a differnt
location.

Thanks,

 

[Doug G]

I just had this happen myself today. It was apparently due to some exploring
that I had been doing in the previous image directories, and TD was
detecting that some application still had files open in the directory. I
couldn't find anything running that might be doing that, but logging off and
back on certainly cleared the condition and all went well.

The other thing to do is just to go to your image root directory folder and
manually delete everything in there from Windows Explorer. If Explorer also
tells you that it can't delete something, then if you have already tried the
logon or reboot trick, then you might have a protection/privilege issue.

Doug G

 

[Guest]

Doug and Lynda,

Unfortunately, I have tried all of your suggestions....many times already
with no resolve.

I rebooted many times since yesterday, being that XPE is on a virtual
machine. I have created new folders everywhere, and checked the permissions
on them. I have also tried a network share. I still have not been able to
figure this out.

Any more suggestions?

 

[JC]

Sounds elementary, but make sure nothing else is looking at the target
location (I.E. windows Explorer, Virus tools, ETC... ) after all this time,
windows still does not do locking and unlocking well. I have had this
problem many times in the past, and sometimes it's just that simple
HTH,

JC

 

[JC]

Sorry, my system did not get this post in before the others came back...
didn't mean to be redundant

JC

 

[Robert]

Hi GKC,

You said you were running your development environment
on a Virtual Server right? If so, it may not be anything
you changed. It may be something someone else changed.
Are you the network admin? Our network team just went
through and converted a bunch of old servers over to
Virtual Servers, and we had alot of problems with
privelage issues in the beginning. Did someone change
anything as far as security is concerned. That would be
the route I would take at this point since it sounds like
you have done everything you can possibly think of and it
is still not working.

Robert

-----Original Message-----
Doug and Lynda,

Unfortunately, I have tried all of your

suggestions....many times already

 

[Guest]

I am going crazy. I still have not been able to resolve this. I have tried
all of your suggestions many times, and still nothing!

I spoke to someone at Venturcom that told me it may be an issue with the TAP
file I tried to import. There may be something wrong with it. I somewhat
agree with him since I am able to re-build previous images with no problems.

I deleted the component from the DB and reimported the TAP file. I am still
getting the same message.

Can someone please help!!

gkc

 

[Slobodan Brcin \(eMVP\)]

Hi gkc,

How about creating new empty project.
Adding one or two components manually, and trying to make a build. Does this make a difference?

Regards,
Slobodan

 

[F.BOYER]

This (maybe) is a limitation on a (hidden and system) subfolder ("System
Volume Information") in your folder. You,ve to put all rights to everyone on
this subfolder (with right click on it, property/Security).

This limitation has increased with SP2 of WinXP Pro.

Fred