[John Schilling]

Andy:


This is a purely TD issue. Reproducible pretty much on demand in several
different .SLX files. This is a relatively well known and presistent XPEsdk
problem--there are about 2-3 postings on the issue or what sounds to be a
related TD -issue every month or so in the XPE newsgroups for at least the
past two years. [Google is your friend!]

Now: We start with an SLX that builds a "known good" OS/system image--e.g.
there was a valid dependancy check & build process that produced an OS image
that is in hundreds of deployed HW systems running 7x24x365. The .SLX file
is *NOT* corrupt--the file compares O.K. to its Master.

We load the SLX file. We upgrade components. These is a 50% chance of a
CMI error during the upgrade process. If not, we Dependancy Check, resolve,
rise/cycle/repeat and finally save the .SLX--without error. Now we try to
load the .SLX file again and:

Error Dialog when importing an SLX that saved w/o error:

+---
[Microsoft Target Designer]
Configuration Management Interface (CMI) Error
Code = 0x800a01c9
Description =
+---

....and then a secondary error message that there was a "problem opening the
..SLX" --Thanks!

The problem:

The error makes upgrading XPEsp1 to XPEsp2 basically "Dead in the water".
Given that rebuild a fresh image from start is a two man-week or so process,
with no guarrentee that the new "clean SP-image" would not be impacted by the
some issue, my choices are:

(1) Get Microsoft to fix its tool or find a workaround.

(2) Convince my management, and our end customer, that they "Really want to
stick with XPEsp1/QFE'ed/Hotfixed for the next couple of quarters. [until
there is some action on (1)]


--JSS

--
====
There are no "Good" SW vendors--only those who have not STP--lately!
====


"Andy Allred [MS]" wrote:

> Ouch.
>
> Russell,
> You're welcome to zip the SLX and mail it to the team at wecrt at
> microsoft.com. I'll see if there is anything obvious that caused it to
> become corrupt, if so i'll mail it back 'fixed'. Like I said, i've never
> looked into one of these before so it's possible it's just hosed, but i
> would like to resolve this once and for all. In the mail you send, refer to
> this thread and provide details in the mail, i'll get back to you as soon as
> possible.
>
> You need to send it asap since i'll be OOF at embedded devcon all next week.
>
> Thanks
> Andy
>
> --
> Embedded team blog: http://blogs.msdn.com/embedded/
>
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
>
>
> "RussR" <nospam@nospam.com> wrote in message
> news:OlXlZ$BUFHA.612@TK2MSFTNGP12.phx.gbl...
> >I worked on my image in TD, closed it, shut down my pc and went home for
> >the weekend.
> > When I came back Monday morning, I noticed that I could not open my slx
> > file in TD any longer.
> >
> > It gives the following error:
> > An error occurred while opening file: C:\.......
> > Code = 0x8004232b
> > Description = An internal CMI error occurred. For more information see the
> > application even log.
> >
> > The application even long has this:
> > The CMI encountered the following error: 0x8004232B (-2147212501) Method
> > CMI.CreateFromFile failed.
> >
> > Looked through the group and re-installed Windows Scripting Host, but it
> > did not help anything.
> >
> > Any ideas guys? I spent a lot of time on the image and it sucks to start
> > over.
> >
> > Thanks,
> > Russell
> >
>
>
>

[KM]

John,

I don't have a fix for you but I just wanted to mention that if you totally stuck with upgrading images from SP1 to SP2 and you
absolutely need to do so, you can try and use CMIExplorer (VALUEADD folder on XPe CD).
It is not TD so the result upgraded SLX may not show the bug you are referring to.

--
KM,
BSquare Corp.
www.bsquare.com


> Andy:
>
>
> This is a purely TD issue. Reproducible pretty much on demand in several
> different .SLX files. This is a relatively well known and presistent XPEsdk
> problem--there are about 2-3 postings on the issue or what sounds to be a
> related TD -issue every month or so in the XPE newsgroups for at least the
> past two years. [Google is your friend!]
>
> Now: We start with an SLX that builds a "known good" OS/system image--e.g.
> there was a valid dependancy check & build process that produced an OS image
> that is in hundreds of deployed HW systems running 7x24x365. The .SLX file
> is *NOT* corrupt--the file compares O.K. to its Master.
>
> We load the SLX file. We upgrade components. These is a 50% chance of a
> CMI error during the upgrade process. If not, we Dependancy Check, resolve,
> rise/cycle/repeat and finally save the .SLX--without error. Now we try to
> load the .SLX file again and:
>
> Error Dialog when importing an SLX that saved w/o error:
>
> +---
> [Microsoft Target Designer]
> Configuration Management Interface (CMI) Error
> Code = 0x800a01c9
> Description =
> +---
>
> ...and then a secondary error message that there was a "problem opening the
> .SLX" --Thanks!
>
> The problem:
>
> The error makes upgrading XPEsp1 to XPEsp2 basically "Dead in the water".
> Given that rebuild a fresh image from start is a two man-week or so process,
> with no guarrentee that the new "clean SP-image" would not be impacted by the
> some issue, my choices are:
>
> (1) Get Microsoft to fix its tool or find a workaround.
>
> (2) Convince my management, and our end customer, that they "Really want to
> stick with XPEsp1/QFE'ed/Hotfixed for the next couple of quarters. [until
> there is some action on (1)]
>
>
> --JSS
>
> --
> ====
> There are no "Good" SW vendors--only those who have not STP--lately!
> ====
>
>
> "Andy Allred [MS]" wrote:
>
>> Ouch.
>>
>> Russell,
>> You're welcome to zip the SLX and mail it to the team at wecrt at
>> microsoft.com. I'll see if there is anything obvious that caused it to
>> become corrupt, if so i'll mail it back 'fixed'. Like I said, i've never
>> looked into one of these before so it's possible it's just hosed, but i
>> would like to resolve this once and for all. In the mail you send, refer to
>> this thread and provide details in the mail, i'll get back to you as soon as
>> possible.
>>
>> You need to send it asap since i'll be OOF at embedded devcon all next week.
>>
>> Thanks
>> Andy
>>
>> --
>> Embedded team blog: http://blogs.msdn.com/embedded/
>>
>> This posting is provided "AS IS" with no warranties, and confers no rights.
>>
>>
>>
>> "RussR" <nospam@nospam.com> wrote in message
>> news:OlXlZ$BUFHA.612@TK2MSFTNGP12.phx.gbl...
>> >I worked on my image in TD, closed it, shut down my pc and went home for
>> >the weekend.
>> > When I came back Monday morning, I noticed that I could not open my slx
>> > file in TD any longer.
>> >
>> > It gives the following error:
>> > An error occurred while opening file: C:\.......
>> > Code = 0x8004232b
>> > Description = An internal CMI error occurred. For more information see the
>> > application even log.
>> >
>> > The application even long has this:
>> > The CMI encountered the following error: 0x8004232B (-2147212501) Method
>> > CMI.CreateFromFile failed.
>> >
>> > Looked through the group and re-installed Windows Scripting Host, but it
>> > did not help anything.
>> >
>> > Any ideas guys? I spent a lot of time on the image and it sucks to start
>> > over.
>> >
>> > Thanks,
>> > Russell
>> >
>>
>>
>>

[John Schilling]

I'm going to give it a shot. But this seriously is "not good"...

I'm also running some investigations as to when the "Tipping Point" is in
TD. Also--last year there was a similar stiutation what was caused by a
"Poisoned QFE" involving an IIS component--inclue the QFE component in your
Iamge--boom CMI error.

Since I have to show something to the management soon--I think we are going
to be shipping another SP1+Hotfixes image!


--JSS

(I want my Amiga back!)
--JSS



"KM" <konstmor@nospam_yahoo.com> wrote in message
news:OQPOIQMbFHA.464@TK2MSFTNGP15.phx.gbl...
> John,
>
> I don't have a fix for you but I just wanted to mention that if you
> totally stuck with upgrading images from SP1 to SP2 and you absolutely
> need to do so, you can try and use CMIExplorer (VALUEADD folder on XPe
> CD).
> It is not TD so the result upgraded SLX may not show the bug you are
> referring to.
>
> --
> KM,
> BSquare Corp.
> www.bsquare.com
>
>
>> Andy:
>>
>>
>> This is a purely TD issue. Reproducible pretty much on demand in several
>> different .SLX files. This is a relatively well known and presistent
>> XPEsdk
>> problem--there are about 2-3 postings on the issue or what sounds to be a
>> related TD -issue every month or so in the XPE newsgroups for at least
>> the
>> past two years. [Google is your friend!]
>>
>> Now: We start with an SLX that builds a "known good" OS/system
>> image--e.g.
>> there was a valid dependancy check & build process that produced an OS
>> image
>> that is in hundreds of deployed HW systems running 7x24x365. The .SLX
>> file
>> is *NOT* corrupt--the file compares O.K. to its Master.
>>
>> We load the SLX file. We upgrade components. These is a 50% chance of a
>> CMI error during the upgrade process. If not, we Dependancy Check,
>> resolve,
>> rise/cycle/repeat and finally save the .SLX--without error. Now we try
>> to
>> load the .SLX file again and:
>>
>> Error Dialog when importing an SLX that saved w/o error:
>>
>> +---
>> [Microsoft Target Designer]
>> Configuration Management Interface (CMI) Error
>> Code = 0x800a01c9
>> Description =
>> +---
>>
>> ...and then a secondary error message that there was a "problem opening
>> the
>> .SLX" --Thanks!
>>
>> The problem:
>>
>> The error makes upgrading XPEsp1 to XPEsp2 basically "Dead in the water".
>> Given that rebuild a fresh image from start is a two man-week or so
>> process,
>> with no guarrentee that the new "clean SP-image" would not be impacted by
>> the
>> some issue, my choices are:
>>
>> (1) Get Microsoft to fix its tool or find a workaround.
>>
>> (2) Convince my management, and our end customer, that they "Really want
>> to
>> stick with XPEsp1/QFE'ed/Hotfixed for the next couple of quarters. [until
>> there is some action on (1)]
>>
>>
>> --JSS
>>
>> --
>> ====
>> There are no "Good" SW vendors--only those who have not STP--lately!
>> ====
>>
>>
>> "Andy Allred [MS]" wrote:
>>
>>> Ouch.
>>>
>>> Russell,
>>> You're welcome to zip the SLX and mail it to the team at wecrt at
>>> microsoft.com. I'll see if there is anything obvious that caused it to
>>> become corrupt, if so i'll mail it back 'fixed'. Like I said, i've never
>>> looked into one of these before so it's possible it's just hosed, but i
>>> would like to resolve this once and for all. In the mail you send, refer
>>> to
>>> this thread and provide details in the mail, i'll get back to you as
>>> soon as
>>> possible.
>>>
>>> You need to send it asap since i'll be OOF at embedded devcon all next
>>> week.
>>>
>>> Thanks
>>> Andy
>>>
>>> --
>>> Embedded team blog: http://blogs.msdn.com/embedded/
>>>
>>> This posting is provided "AS IS" with no warranties, and confers no
>>> rights.
>>>
>>>
>>>
>>> "RussR" <nospam@nospam.com> wrote in message
>>> news:OlXlZ$BUFHA.612@TK2MSFTNGP12.phx.gbl...
>>> >I worked on my image in TD, closed it, shut down my pc and went home
>>> >for
>>> >the weekend.
>>> > When I came back Monday morning, I noticed that I could not open my
>>> > slx
>>> > file in TD any longer.
>>> >
>>> > It gives the following error:
>>> > An error occurred while opening file: C:\.......
>>> > Code = 0x8004232b
>>> > Description = An internal CMI error occurred. For more information see
>>> > the
>>> > application even log.
>>> >
>>> > The application even long has this:
>>> > The CMI encountered the following error: 0x8004232B (-2147212501)
>>> > Method
>>> > CMI.CreateFromFile failed.
>>> >
>>> > Looked through the group and re-installed Windows Scripting Host, but
>>> > it
>>> > did not help anything.
>>> >
>>> > Any ideas guys? I spent a lot of time on the image and it sucks to
>>> > start
>>> > over.
>>> >
>>> > Thanks,
>>> > Russell
>>> >
>>>
>>>
>>>
>
>