Windows 7 - Multiple "File not found:" TD build errors with Rollup 1.0

Asked By jimt

02-Jul-07 01:46 PM

Has anyone experienced "File not found:" errors when using Rollup 1.0 to
build an XPe runtime image?  Many many components in my build are showing
this error.  For example, if I open TD, select a new project, and only add
the "First Boot Agent (FBA)" component (viewable with visibility of 100) and
do a build I see these errors:

Building: "First Boot Agent (FBA) [Version 5.1.2600.4010, R4010]"...
Error    1005: File not found: "fbareg.dll"
Error    1005: File not found: "layout.inf"
Error    1005: File not found: "fbastart.exe"
Error    1005: File not found: "fba.exe"
Error    1005: File not found: "fbalib.dll"
Error    1005: File not found: "syssetup.inf"

All of these files are in one or more folders under C:\Windows Embedded
Data\Repositories.  I am using XP Pro for the development pc.  The Rollup
1.0 seemed to work without any problems.  This is the purchased version of
XPe Studio.  Builds of pre-Rollup 1.0 were fine.

I will try rolling back to the backed up FP2007 database.  Sigh.

--
jimt

02-Jul-07 03:18 PM

Are your repositories using shares? Are you connected to the network?

Regards,

Sean Liming
www.sjjmicro.com / www.seanliming.com
Book Author - XP Embedded Advanced, XP Embedded Supplemental Toolkit

02-Jul-07 04:56 PM

Hi Sean,

The repositories are local to the machine using the local MSSQLSERVER
service, no network.  Sorry, I should probably have mentioned that.

BTW the problems disappeared when I rolled back to the pre-Rollup1.0
database.  I guess I could try re-applying the Rollup 1.0 again with the
database having been rolled back to pre-Rollup 1.0???

--
JimT

02-Jul-07 05:37 PM

With a standard single machine installation I have had problems like
you describe in the past if there was no active network on the machine.
In that situation I had to install loopback software.

http://support.microsoft.com/default.aspx/kb/839013


--
-Mike

02-Jul-07 06:08 PM

Hi Mike,

Hmm, I meant to say there was no network database.  The development pc is
connected to our house lan, and the lan is working fine.  In fact I have
successfully built an XP Pro emulation runtime config previously, under
FP2007 (pre-Rollup 1.0), on this pc.  That runtime worked very well.  The
build env stopped working when I added Rollup 1.0.

In an attempt to diagnose the problem I backed out the database changes made
by Rollup 1.0.  Since this dabase restore to version FP2007 (without Rollup
1.0) fixes the problem, I'm thinking I should reapply Rollup 1.0 again.
Maybe it will "take" the second time it is applied.  Any thoughts would be
appreciated.  I just hope it doesn't break again.

--
jimt

02-Jul-07 06:27 PM

Not really. I am not impressed with Rollup 1 so far but that has more to
do with the fact that I am not having any luck getting as small an image
as I could with FP2007.

--
-Mike

03-Jul-07 05:05 PM

I fixed this by going back to an earlier database and reinstalling Rollup
1.0.  My steps were:
(1)  Restore the database to pre-Rollup1.0.  While the local MSSQLSERVER
was stopped,
- Remove the FP2008 repositories
- Remove the SP2, SP2 QFE's, FP2007, FP2007QFE repositories
- Restore the pre-rollup1.0 of SP2, SP2 QFE's, FP2007,
FP2007QFE repositories
(2) Kill all other programs on pc
(3) Stop virus scanner, stop any mail indexing programs you might have.
(4) Remove the second fixed HDD from the development pc (it had more
freespace than C:)
(4) Run the component database Rollup 1.0 executable "XpeRollup1.exe"

Now TD can build a runtime with just the First Boot Agent component, and
those errors don't happen.  I am guessing the anti-virus was causing a
problem during reinstall.  But who knows.

I have also thought about what caused the original problem.  Best guess:  I
used CDM to remove my  custom component from the database.  It complained
that the repository folder that had a file for the custom component could
not be removed.  Later I found that I did not have full control over the
C:\Windows Embedded Data\Repositories folder.  Maybe that got the database
out of wack.

--
jimt

03-Jul-07 10:49 PM

One of the major manual steps that need to take place after installation is
chaning the permission on the \Windows Embedded Data\Repositories to Full
Control.

What antivirus software are you using?

Regards,

Sean Liming
www.sjjmicro.com / www.seanliming.com
Book Author - XP Embedded Advanced, XP Embedded Supplemental Toolkit

09-Jul-07 02:12 PM

Hi Sean,

I see under "Sharing a Repository" where the XPe CDROM #2 Installation Guide
suggests the creation of the WES_Reader, WES_Importer, and WES_Admin user
groups and assigning users to those groups to grant the required
permissions.  Since I was not sharing the Repository with other users I sort
of skipped over that step.  In fact the prompts said "...Setup will now
create a READ/WRITE file share on the system called 'Repositories'."  I
thought that meant the required permissions would be granted to the
installing user.  Clearly the manual addition of Full Control permission is
required to delete the repository of a custom component, as I discovered and
as you have suggested.

I am using the Symantec AntiVirus version 10.1.5.5000.  I recall some
install directions that said to disable the Anti-Virus when installing XPe
Studio, so I did it here as a precaution.  I used to run X1 as well, an
email crossreference program.  That did prevent XPe Studio installs on my
old slower PC, so I made sure it was terminated as well.

The problem probably started with the Repositories folder permissions.  I
remember trying to delete a component's repository using the component
database manager, and it kicked back an error saying the permissions were
wrong.  I bet the XPe component database mgr is not verifying folder
permissions before it makes any changes, which is (imho) awful.  Looks like
it left the database corrupted after it removed the files under my
component's repository when it errored out early while attempting to delete
the custom component folder in the Repositories folder.

IMHO I think the Microsoft "delete repository from database" functionality
ought to check up front if the folder permissions are wrong, and post a msg
to that effect before it does any database modifications.

Thanks

--
jimt