Registry Warnings on Target Designer Build

[Craig]

We've created a component for MSDE and everything looks good in Component
Designer ....

Part of that process was to import a .REG file with roughly 3300 registry
keys. During the build process, we generated about 2600 warnings of the type
"Invalid registry data fixup:" relating mostly to HKCR\CLSID\ ... there were
a few HKLM warings scattered in the log as well.

The target hung-up during the restart after FBA ... SQL Server (MSDE)
couldn't find our database instance.

Interesting note is that a build that does not include the registry import
is successful and restarts fine. After that, I can import the .REG file and
restart successfully with SQL services running OK.

What does that warning mean ... is it due to an operator error in Component
Designer?

Thanks,

Craig

 

[Heidi Linda]

We've created a component for MSDE and everything looks good in Component
Designer ....

Part of that process was to import a .REG file with roughly 3300 registry
keys. During the build process, we generated about 2600 warnings of the type
"Invalid registry data fixup:" relating mostly to HKCR\CLSID\ ... there were
a few HKLM warings scattered in the log as well.

The target hung-up during the restart after FBA ... SQL Server (MSDE)
couldn't find our database instance.

Interesting note is that a build that does not include the registry import
is successful and restarts fine. After that, I can import the .REG file and
restart successfully with SQL services running OK.

What does that warning mean ... is it due to an operator error in Component
Designer?

Thanks,

Craig

Sounds like the bits of the registry you were trying to modify didn't
exist when your component was getting built.

 

[Sean Liming \(eMVP\)]

Heidi,

You are getting funnier with every post.


Craig,

Sounds like the build might be trying to create the same keys that your MSDE
component is using. Have you tried any of the registry key Write options?
The option is in the Advanced properties for the key. Or change the build
order of the component?

Regards,

Sean Liming
XP Embedded Manager
A7 Enginering (www.a7eng.com)
Author: Windows XP Embedded Advanced and Windows NT Embedded Step-by-Step

 

[Craig]

The keys/values do exist on our host ... I wouldn't expect them to exist in
our image ... I thought that's what a .REG import into Component Designer
was supposed to take care of ... key creation and values.

The inconsistency is that .REG import on the target works fine ...
differently than it does within the XPe IDE.

Craig

 

[Craig]

Sean,

I set the build order in the "MSDE Registry Settings.SLD" to build before
the "MSDE Files.SLD" and received the same errors ... the build order did
change from the original configuration ...

Good news is that we are so close to a working MSDE component.

Thanks,

Craig

Heidi,

You are getting funnier with every post.


Craig,

Sounds like the build might be trying to create the same keys that your MSDE
component is using. Have you tried any of the registry key Write options?
The option is in the Advanced properties for the key. Or change the build
order of the component?

Regards,

Sean Liming
XP Embedded Manager
A7 Enginering (www.a7eng.com)
Author: Windows XP Embedded Advanced and Windows NT Embedded Step-by-Step


the

type

there

were

file

 

[KM]

Craig,

I am wondering if you went through the all registry keys you are importing
on the target? Have you compared them to original registry you tried to
import in CD?
Since it is a huge number of registry keys/values it would probably hard to
check them all on the target.
There was (and I believe there was no QFE for that) a bug in CD that it eats
up spaces in registry paths from a .REG file imported. You may want to take
a look into your .REG file to see if you have registry keys with the names
including spaces. If so, you are in dangerous situation. Some keys might be
very important for the app and loosing them may hang it up.
The only fix I can remember is to go through all registry keys imported in
CD and fix them all manually. Very laborious if you want to integrate an app
with a huge number of registry keys/values.
Or, if you don't want to do so, you can just import your .REG file with
"regedit.exe -s" on the target device at some FBA phase (FBACommand). That
might help you if you know for sure that .REG file is what you need to make
the app working.

KM


C> We've created a component for MSDE and everything looks good in
C> Component
C> Designer ....

C> Part of that process was to import a .REG file with roughly 3300
C> registry keys. During the build process, we generated about 2600
C> warnings of the type "Invalid registry data fixup:" relating mostly
C> to HKCR\CLSID\ ... there were a few HKLM warings scattered in the log
C> as well.

C> The target hung-up during the restart after FBA ... SQL Server (MSDE)
C> couldn't find our database instance.

C> Interesting note is that a build that does not include the registry
C> import is successful and restarts fine. After that, I can import the
C> .REG file and restart successfully with SQL services running OK.

C> What does that warning mean ... is it due to an operator error in
C> Component
C> Designer?

C> Thanks,

C> Craig


With best regards, KM. E-mail: (e-mail address removed)

 

[Heidi Linda]

Heidi,

You are getting funnier with every post.

Ages ago, when I got this error, I was told it was because at the point
of FBA I was trying to do things, the parts of the registry I was trying
to modify hadn't been set up yet, and so it threw up this error.
Importing the keys after FBA worked. Pardon me for believing what I was
told.

 

[Heidi Linda eMVP]

Sean,

I set the build order in the "MSDE Registry Settings.SLD" to build before
the "MSDE Files.SLD" and received the same errors ... the build order did
change from the original configuration ...

Good news is that we are so close to a working MSDE component.

Thanks,

Craig

Coffee has happened since my last post, which was made when I was very
tired, and out of range of a starbucks. It was a long time ago that I was
trying to deal with registry keys that just wouldn't import during FBA.
Someone else mentioned the spaces-in-registry-keys problem, which could be
what's happening here, however, I have had problems with certain keys not
being correctly imported at certain phases of the FBA. I'd like to have a
look at your component, if that's alright.

 

[Sean Liming \(eMVP\)]

Heidi,

I was talking about you signature!!!! It is very great!!!!!!

Regards,

Sean

 

[Heidi Linda eMVP]

See this is what happens when there's no starbucks in a town.

Heidi,

I was talking about you signature!!!! It is very great!!!!!!

Regards,

Sean

 

[Craig]

Here's the latest on this one ...

We were dealing with 2 issues ...

The problem that prevented SQL services from running once the target started
was the bug in Component Designer relative to importing registry keys with
names that have spaces. I guess this is a known bug, so when is Microsoft
going to fix it, or have they already? The solution to this is nasty ... we
had to separate the offending keys into a separate .REG file and use an
editor to search-and-replace the .SLD file to put the spaces back in. There
were 74 broken keys out of the total of 3300+ entries in the original .REG
file.

As far as the 2696 instances of "Warning 1006: Invalid registry data fixup:"
.... these have not been resolved, but so far the target has not exhibited
bad behavior and the keys appear to be intact. It's really going to be a
nuisance to deal with this every time we build, so I'm hoping Microsoft
eventually corrects the problem.

Anyway, what this means is we have a successful MSDE component for XPe
that's a little rough around the edges because of issues with the tools ...
I'm happy with that for now, but hope it runs correctly once we load our
applications on the target.

Craig

 

[Heidi Linda eMVP]

Craig - would you mind sending me a copy of this component at home
([email protected]), so I can have a look at it?

 

[Norman Ott]

Do you mind making your MSDE component available? I would like to use
it as a base line for a development project I'm working on.

Thanks,
Norm