Application Center Usage - Security FIX 828741 (MS04-012) disrupts AppCenter COM+ replication

This is Interesting: Free IT Magazines  
Home > Archive > Application Center Usage > May 2004 > Security FIX 828741 (MS04-012) disrupts AppCenter COM+ replication





You are viewing an archived Text-only version of the thread. To view this thread in it's original format and/or if you want to reply to this thread please [click here]

Author Security FIX 828741 (MS04-012) disrupts AppCenter COM+ replication
GM

2004-05-11, 8:22 pm

We have had a lot of troubles replicating a set of COM+ applications with Application Center 2000 Sp2 after installing last month's security FIX MS04-012. Today we have finally uninstalled the fix and everything has gone back to normal.

Basically, we have a complex application made of of several COM+ packages. All of the packages are server applications, one of them is a Library application. Each of our dlls contains one component that is registered in one server application and some com
ponents that go to the library application. We have been deploying this application for 3 years and everything has always gone fine.

After installing the security fix MS04-012, which contains a bunch of com+ related dlls, Application Center 2000 SP2 is unable to upgrade the dll on the target computer, unless I manually delete both the server and the library application that host the co
mponents contained in the dll.

For example: if I have a dll CompDll.dll that contains the components CompA (server application A), compB and CompC (library application B) and I want to change the component CompA I have to manually uninstall the server application A and the library app
licationB, so that the system deletes CompDll.dll from my target server and then I can deploy with Application Center. If I don't do it, Application center is unable to substitute COMDll.dll with the new version and my application will stop working.

Is anybody else experiencing problems with Application Center 2000 after patching ? Is Microsoft saying anything ?

Best regards
Gianluca
Berrys66

2004-05-12, 7:44 am

We're not getting exactly your problem, but we are having problems. Our production system logs the following to the system log every 4 minutes:

DCOM got error "%%2147749891" from the computer xxx.xxx.xxx.xxx when attempting to activate the server:
{1EE00BE5-A7F3-4ED1-952F-B21256F53BF5}

Whilst our test system suffers from a different problem to do with browse lists.

I'm about to re-apply AC2K SP2 to see whether it makes any difference. :-/
George Cheng [MSFT]

2004-05-20, 5:43 pm

We are looking into this issue currently. I will keep you posted.

Thank You



George Cheng



Microsoft Application Center & Index Server Support



Note: This article has no warranties implicit or explicit.

All the content is given on the "as is" basis and the user

takes full responsibility for its use and assumption.

Microsoft Corporation Copyright 2004

All Rights Reserved

George Cheng [MSFT]

2004-05-20, 5:43 pm

Just wanted to verify that you are deploying from one SP2 machine to
another SP2 machine, and not mixing and matching.

Thank You



George Cheng



Microsoft Application Center & Index Server Support



Note: This article has no warranties implicit or explicit.

All the content is given on the "as is" basis and the user

takes full responsibility for its use and assumption.

Microsoft Corporation Copyright 2004

All Rights Reserved

GM

2004-05-21, 2:52 am

The servers all all exactly the same software level: win2k sp4 +FIX MS04-011&ms04-012+ Appcenter SP2

I am currently working on a lab with that software level only (nothing else installed) and if I use two COM+ application sharing the same bin directory (appcenter sp2 deploys keeping the original path) I simply cannot deploy ugprades (the old dll won't be
deleted and replaced on the target server) UNLESS I manually uninstall both COM+ applications or delete the dll files myself on the target server.

I never have any problems starting with a brand new COM+ application (the problem again seems on the deletion of the previos dll, noi in putting a brand new one).

Since we have this problem in a production environment and we had to uninstall the security fix to go back to working correctly, I hope you can give me some help soon. We are currently in contact with Microsoft Support on the issue too.

Regards
GM
Sponsored Links






Free braindumps | Software forum | Database administration forum

Copyright 2003 - 2008 webservertalk.com