Repository backup

[DPM]

I'm trying to verify that I can successfully backup and restore a XPe
database. This is what I did:
1. Using MS Backup, I backed up the entire "Windows Embedded Data" folder
from my current system, and my .slx files.
2. Built a VPC 2007 virtual machine and installed XPpro.
3. Installed SQL 2005 Express SP1 and the Embedded tools (up through
FP2007).
4. Stopped the SQL engine, restored the WED folder, shared it and restarted
SQL.
5. Fired up TD and opened a known-good .slx - configuration activated
without errors.
6. Told TD to build it.
7. TD reports lots of "file not found" errors. So I look at a component
where the files were not found, and see that the file length of the files is
reported as 0. But if I look for a missing file I find it in a repository.
The odd thing is that if I close and reopen TD and activate the same SLX the
file for the failing component are now visible, but a build will show others
not.

Does anyone know what I'm doing wrong?

Thanks.
Dean

 

[Mike Warren]

Does anyone know what I'm doing wrong?

If you look at the repositories in CDM, do the available repository
locations point to paths that actually exist?

 

[Rob]

Dude,

First mistake was using XPe, the tool is so quirky it is shameful. I was
99% done and the system just hosed me. Came in next morning to tweak a few
items and close the system, boom, its been broke for 3+ weeks. Best of luck
to you. I wish I had someone to tell me why "Repository Root is invalid or
not acessible" when that part was working yesterday. Damn!

 

[Mike Warren]

I wish I had someone to tell me why "Repository Root is invalid or
not acessible" when that part was working yesterday. Damn!

It's happened to me in the past and I ended up changing the paths in CDM
to point to the local folder rather than the share.

This will also happen if you don't have a network cable connected to your
dev machine.

 

[DPM]

If you look at the repositories in CDM, do the available repository
locations point to paths that actually exist?

Yep, that's it. The paths are *NETWORK* paths, and include the computer
name. Once I changed the name everything worked like magic.

Thanks,
Dean