CMI error after installing the latest QFEs

[Guest]

I also experienced similar behaviour on a new system that I set up from
scratch when I tried to open my .slx which was working properly on the older
system.

I'll try this recommendation, but don't you mean Q824151 rather than Q824141?

Joe

 

[Guest]

I have performed the delete process on the two QFEs as stated except I did it
with 824151, not 824141. Older slx files seem to upgrade fine, I will
continue testing and if I see any issues I will post them. However the slx
that I had first tried to upgrade and had failed continues to fail. I think I
have lost this file. I will build back up to this file level (not hard, I
saved in an iterative process). Thank you for all of your help out there. It
is nice to know when you have an oops like this there are helpful minds to
reach out to. Thanks again.

Paul

 

[J. Kremer [MS]]

That's great Paul! I'm glad to hear you have things
working for you again.

You and Joe were right, I meant 824151, not the other.

-J
"This posting is provided "AS IS" with no warranties, and
confers no rights"

 

[Guest]

Paul,

When I try to upgrade the IIS Common Lib component (which was updated in
Q824151) the upgrade seems to fail. If I then upgrade the entire slx then the
process stops at this component with the CMI error.

 

[Guest]

Paul,
I have tried deleting Q8411114 and Q824151. My system works without errors.
If I then install Q8411114 I get the problem that the IIS common Lib
component will not update / cause CMI error. If I install Q824151 (Q8411114
is uninstalled) the tool reports an error missing IIS Common lib component.

I can build an image with both of these updates removed but the system is
now vulnerable as the security updates to IIS are no longer in place.

Regards,
Paul M. Mair

 

[Guest]

KM,

Are you using a pre-release version of SP2 in order to get revision 2117 of
this component. The version Paul Lowe and I are using is the hotfix Q811114
version which is as far as I can tell the latest available until SP2 is
released.

Regards,

Paul M Mair.

Paul,

The "IIS Common Libraries" does not have Hotfix in the name.
It is "IIS Common Libraries" [Version 5.1.2600.2171, R2117], [Visibility=200] (please note the Revision number)

I may guess that the IIS Common Libraries - Hotfix Q811114 component you saw is the legacy component that is in your database from
SP1.
In your configuration, go to the component Advanced Properties dialog (Advanced button) and check what the extended property
cmiServicePackLevel is set to. If it is "1", it is SP1 component.
You may want to switch using just the "IIS Common Libraries" component (see above).

--
Regards,
KM, BSquare Corp.

I have taken a pevious slx and gotten it to the same point as my first slx
that is now locked up. I then right clicked on each component that was marked
with a blue up arrow and selected upgrade. All components upgraded except IIS
Common Libraries - Hotfix Q811114 (Version 5.1.2600.1125.2,R1901. My slx
saves, runs dependency checker (no errors or warnings) and builds (no errors,
no difference from what was happening before I installed the QFEs).
Why is TD telling me I need to upgrade the configuration but I cannot
manually upgrade the only component that is marked with a blue up arrow?

Paul

 

[KM]

Paul,

Yes, I was using SP2 TP when I listed the components. For whatever reasons I thought Paul was struggling with SP2.
My bad. Nevermind.

KM

KM,

Are you using a pre-release version of SP2 in order to get revision 2117 of
this component. The version Paul Lowe and I are using is the hotfix Q811114
version which is as far as I can tell the latest available until SP2 is
released.

Regards,

Paul M Mair.

Paul,

The "IIS Common Libraries" does not have Hotfix in the name.
It is "IIS Common Libraries" [Version 5.1.2600.2171, R2117], [Visibility=200] (please note the Revision number)

I may guess that the IIS Common Libraries - Hotfix Q811114 component you saw is the legacy component that is in your database from
SP1.
In your configuration, go to the component Advanced Properties dialog (Advanced button) and check what the extended property
cmiServicePackLevel is set to. If it is "1", it is SP1 component.
You may want to switch using just the "IIS Common Libraries" component (see above).

--
Regards,
KM, BSquare Corp.

I have taken a pevious slx and gotten it to the same point as my first slx
that is now locked up. I then right clicked on each component that was marked
with a blue up arrow and selected upgrade. All components upgraded except IIS
Common Libraries - Hotfix Q811114 (Version 5.1.2600.1125.2,R1901. My slx
saves, runs dependency checker (no errors or warnings) and builds (no errors,
no difference from what was happening before I installed the QFEs).
Why is TD telling me I need to upgrade the configuration but I cannot
manually upgrade the only component that is marked with a blue up arrow?

Paul

:

Hi KM
1) No antivirus or firewall. Not networked. This is a Dev machine and
management prefers it not on the main network
2) Dev machine is running XP Pro SP1. Company does not allow us to upgrade
to SP2 yet. Corporate IT is still reviewing.
3) I am just now getting close to finding the guilty file(s). After I locate
them how do I remove the QFE and install again?
4) Where is the build/dependency log normally stored? What could its name be?

Paul

:

Paul,

Just a few points that you may check on your dev.machine:
- Any antivirus, firewall or similar apps running in background?
- Do you have XP Pro/SP2 installed? Or just SP1?
- Did you try to remove the QFE you suspect broke your build from database and try to build it again?
- Can you send us your build/dependency log here?

--
Regards,
KM, BSquare Corp.


Configuration Management Interface (CMI) Error
Code=0x800a01c9
Description=

this is the error I got.

Paul

:

Paul,

What CMI error exactly?
I could not quite understand #3.

--
Regards,
KM, BSquare Corp.


After installing the latest QFEs that were posted Oct 22-25, I am now getting
a CMI error.
1) I have searched this NG and found others with the same error but no
solutions.
2) I have updated WSH, still have problem
3) I cannot open a file I have updated but I can open files that have not
been updated.

Does anyone have a fix?
Or, What additional data do you need that could help solve this problem?

Paul

 

[Guest]

Paul
Sorry for not getting right back with you. Have another issue unrelated that
was taking my time. IIS security is not major issue here, network is real
closed up. If I reinstall Q811114, I also get the error again. I think MS
needs to look closer at what is interacting between these updates.
Does anyone out there at MS have a suggestion?
Paul