QFE 824704 install problem

[Dr.Packet]

Hi. all.

I have faced the problem about QFE 824704.
It has many new components (hotfixes).
Application Compatibility Core - Hotfix Q824704, one of them, has the
problem during upgrading existing configuration.
After installing Q824704, when I try to upgrade the component in TD (from
the former version. Application Compatibility Core - Hotfix Q328310), the
CMI error message (code 0x800a01c9) occurs.
I have tried to install the QFE again after deleting the component
Application Compatibility Core - Hotfix Q824704. but I can't solve the
problem.

Any solution for it?

 

[Nikolai Vorontsov]

Hello Dr.Packet!

I have faced the problem about QFE 824704.

The same problem.

Andy(MS) ??

 

[Eberhard Schefold]

Nikolai Vorontsov schrieb/wrote:

The same problem.

Same here.

 

[Eberhard Schefold]

Nikolai Vorontsov schrieb/wrote:

The same problem.

A little more about this issue:

Probably like "Dr. Packet", I had Q328310 (WM_TIMER issue) from February
previously installed, and had already upgraded my configuration, including
the "Application Compatibiliy Core" component. When I import Q824704 ("XPE
QFE Rollup, Summer 2003") now and upgrade the configuration, I get the
output

Info 101: Initializing new component: "Application Compatibility
Core - Hotfix Q328310 [Version 5.1.2600.1134.1, R1900]"
Info 104: Upgrading from: "Application Compatibility Core - Hotfix
Q824704 [Version 5.1.2600.1106.1, R1900]"

I would have expected it the other way round. Q824704 should be newer,
right?

Then I get a message box with

---------------------------
Microsoft Target Designer
---------------------------
Changing disk cluster size affects the configuration footprint
calculation.
Rebuild your configuration now to view updated configuration size.

 

[Nikolai Vorontsov]

Hi, All!

I have faced the problem about QFE 824704.

Any solution for it?

One more problem - Windows Script Engines - they are always now marked
as upgradable.

 

[Andy Allred [MS]]

Thanks for the heads up, I've forwarded the issue on to the appropriate
people, they'll look into it and get back the newsgroup as soon as possible.
In the mean time, to continue on with the build process you can delete this
package from the DB so you're not blocked until the versioning details can
be figured out here.

Sorry for the inconvenience.

Andy

 

[Eberhard Schefold]

Andy Allred [MS] schrieb/wrote:

Thanks for the heads up, I've forwarded the issue on to the
appropriate people, they'll look into it and get back the newsgroup as
soon as possible. In the mean time, to continue on with the build
process you can delete this package from the DB so you're not blocked
until the versioning details can be figured out here.

Thanks for your message! As a workaround, I had upgraded every component
manually with the exception of "Application Compatibility Core" and
"Windows Script Engines". Does that make sense, too, or would you rather
advise to shelve the entire QFE until further notice?

 

[Andy Allred [MS]]

The workaround you list will work but it's a hassle you shouldn't have to
endure, and I apologize. If it were me, I'd uninstall this package from your
database and continue on with the rest of your development until we fix this
problem, which shouldn't take long.

Thanks for your patience here!

Andy

--

This posting is provided "AS IS" with no warranties, and confers no rights.
==========================================================

Andy Allred [MS] schrieb/wrote:

Thanks for the heads up, I've forwarded the issue on to the
appropriate people, they'll look into it and get back the newsgroup as
soon as possible. In the mean time, to continue on with the build
process you can delete this package from the DB so you're not blocked
until the versioning details can be figured out here.

Thanks for your message! As a workaround, I had upgraded every component
manually with the exception of "Application Compatibility Core" and
"Windows Script Engines". Does that make sense, too, or would you rather
advise to shelve the entire QFE until further notice?

 

[Nikolai Vorontsov]

Hi, Eberhard!

Thanks for your message! As a workaround, I had upgraded every component
manually with the exception of "Application Compatibility Core" and
"Windows Script Engines". Does that make sense, too, or would you rather
advise to shelve the entire QFE until further notice?

It's much simplier to delete those two components, upgrade the build and
them bring them back during the check process.

 

[Ted Lee]

Thanx a lot, Andy.

I'll keep my work without upgrading components 'til releasing new QFE.

--

Ted Lee [Dr.Packet]
DST Corporation (http://www.dstcorp.co.kr, http://www.dst-asia.com)
Windows Embedded Community in Asia [WECOM Asia]
http://www.wecomasia.com
Windows Embedded Community in Korea [WECOM Korea]
http://wecom.dstcorp.co.kr

The workaround you list will work but it's a hassle you shouldn't have to
endure, and I apologize. If it were me, I'd uninstall this package from your
database and continue on with the rest of your development until we fix this
problem, which shouldn't take long.

Thanks for your patience here!

Andy

--

This posting is provided "AS IS" with no warranties, and confers no rights.
==========================================================

Andy Allred [MS] schrieb/wrote:

Thanks for the heads up, I've forwarded the issue on to the
appropriate people, they'll look into it and get back the newsgroup as
soon as possible. In the mean time, to continue on with the build
process you can delete this package from the DB so you're not blocked
until the versioning details can be figured out here.

Thanks for your message! As a workaround, I had upgraded every component
manually with the exception of "Application Compatibility Core" and
"Windows Script Engines". Does that make sense, too, or would you rather
advise to shelve the entire QFE until further notice?