Re: Error in Component DataBase manager after upgrading SQLSERVER

Tech-Archive recommends: Fix windows errors by optimizing your registry

Hi KM,

Yes, I did try the script host engine in all cases. Regmon shows ALOT of
info as you know for any app tracking. I wonder if there is something
specific I should be looking for?

I have duplicated what I have posted about here on three different machines
now: One domain joined (full admin), One non-domain joined (never been domain
introduced also full admin), and one machine completely offsite. All freshly
staged XP Pro SP2.

There is one box (my own) that works. The only difference at this point that
I can think of:

The box that is working started off w/o XP Service Pack 2. The XPe SP1 tools
and db were installed on the box at that time. The box was then introduced to
SP2 when it was released, followed up by XPe SP2 tools and db install. When I
introduced FP2007 to this working box, errors began as noted. So I re-imaged
the box back to a non FP2007 exposed scenario, which was three days ago,in
order to get up and running (I make a Ghost image of devp box before doing
any upgrade to XPe tools or db). The box itself has been migrated to (2) dif
hardware platforms now.

What about your development box? Have you restaged at any point in time? If
so, was it at SP2 level OOB?



"KM" wrote:

Just a thought. Did you try [re-]installing Windows Host Script engine
(v5.6) on that development box?

Also, it may be helpful to you if you look at Filemon/Regmon logs while
monitoring the system when the error occurs.

Regards,
KM

Hi Sean,

Thanks for the speedy reply. I have been trying to post in the new forum,
but I have been having problems when submitting posts there. It never
completes upon submitting. Weird...hence the post to the newsgroup. Also
having problem with the new XPe site as well (ece.partners.extranet....),
not
being able to download the FP 07, or any updates for that matter. It
errors
when displaying the agreements, etc with a 404.

We have tried using the Eval version and the full release version.

The strange part about all of this is that these errors occur just by
opening the Component Database Manager. This occurs even on a fresh XP Pro
SP2 system that has never seen XPe ever, with ALL versions of XP Embedded
attempted.

Truly puzzled because we cannot even get a new development box running
whatsoever.

Your thoughts are again appreciated.

"Sean Liming (eMVP)" wrote:


Funny, I haven't seen this exact error. Are you using the Eval version or
the full release version? The database in the eval is slightly different
than the full release - in name only. I have seen an issue where I give
out
an SLX, and there is trouble building it because my database had the
latest
XPe updates.

Please post this to the XPE forum site:
http://forums.microsoft.com/embeddedwindows/default.aspx?siteid=47. I
think
someone from Microsoft might be looking into this issue.

One suggestion that I do have is to architect the components into a macro
component. That way you only have to drop in the macro components, run
dependency check, make changes to the settings for the components that
need
setting changes in order to recreate the SLX.

Regards,

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


"PjS" <PjS@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:68D156BE-88BC-446F-BE04-2A7E52B221EB@xxxxxxxxxxxxxxxx
Hi Sean,

We are seeing the same problems here.

We followed the proceedure listed in the blog archive to no avail.

Related is several CMI errors dealing with vbscript and/or missing
registry
entries after upgrading to FP 2007.

I am especially seeing this when loading a SP2 based SLX into the
FP2007
TD
and/or performing a configuration upgrade. I went as far as to building
a
target, but the result was not so pretty.

Is it recommded to remake new SLXs after upgrading to FP 2007?

Your response is most appreciated and/or any insight you can provide.

PS. For kicks, we installed Xpe SP1 from original media fresh on a
newly
staged XP Pro SP 2 box. Used MSDE. We then upgraded the tools to XPe
SP2,
then the db to XPe SP2, and even then saw MANY CMI errors.

Tried installing windows script engine as well as a possible solution
to
no
avail.

Your response is most appreciated and/or any insight you can provide.



"Sean Liming (eMVP)" wrote:


XPe team blog had this solution:
http://blogs.msdn.com/embedded/archive/2006/01/05/509705.aspx

There is an post some where, but you might want to post to the new
forum:
http://forums.microsoft.com/embeddedwindows/default.aspx?siteid=47 if
the
above doesn't solve to the problem.


Regards,

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


"Henny Karreman" <HennyKarreman@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message
news:D49AFE16-AF2E-49C5-A883-D415ABEEA324@xxxxxxxxxxxxxxxx
Until now I did use MDE and everything works without any problem.
After I installed SQLSERVER 2005 Express Edition I get problems
using
the
Component Database manager:
When I open the package Tab I get the following error:
"Component Database Manager cannot retrieve data from the component
database.
For more information, please see the application eventlog."

In the event log I get a CMI error:
"The CMI encountered the folowwing error: 0x80042343. A utilities
method
referenced a non-existing registry key value:
\utilitiesc-1259"

Does anyone know how to solve this ?









.

Relevant Pages