OSEC

Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com
 
From: Pete Davis (pdavisQUETEL.COM)
Date: Tue Jun 26 2001 - 13:34:03 CDT

  • Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

    Steve:

    From MSKB:

    Q289821 FIX: COM+ Application Proxy Does Not Register CLSID After You
    Install COM+ Rollup Hotfix 5

    Now, we did not apply a hotfix. We simply installed SP2, but it was
    definately not registering the components on Win98 clients after running the
    .MSI file. We went into the registry and the components simply were not
    registered. When we uninstalled the SP2, it worked fine.

    I have no other explanation for it.

    Pete

    ----- Original Message -----
    From: "Steve Swartz" <steveswMICROSOFT.COM>
    To: <DCOMDISCUSS.MICROSOFT.COM>
    Sent: Tuesday, June 26, 2001 2:26 PM
    Subject: Re: OT: Re: CoCreateInstance failure on Win2K SP2, but not on prior
    serivce p ack...

    Just to be clear, in Windows 2000 running SP2, the COM+ Explorer and the
    Admin SDK both generate proxy applications that register components
    correctly on clients. We test this scenario. I just did it on a W2K/SP2
    machine, to verify that it works.

    So the situation described below is not something that we've seen any
    evidence of. I'd be interested in more details....

    -----Original Message-----
    From: Brian Muth [mailto:bmuthSWI.COM]
    Sent: Monday, June 25, 2001 12:58 PM
    To: DCOMDISCUSS.MICROSOFT.COM
    Subject: OT: Re: CoCreateInstance failure on Win2K SP2, but not on prior
    serivce p ack...

    This is very interesting. I installed SP2 on our office machines, and
    immediately our ISAServer stopped functioning. On our Exchange Server,
    the STORE.EXE immediately starting consuming 100% cpu. There has been
    lots of chatter on microsoft.public.exchange2000.admin and the general
    consensus was that SP2 had to be removed to solve the the Exchange
    Server problem.

    This is the first I have heard about a COM related problem, but after my
    recent experience, I'm not surprised.

    > We installed SP2 and discovered a whole host of problems. We ended up
    > uninstalling it... I think we'll wait for SP3... Our biggest problem
    was
    > that the Component Services generated proxy applications that wouldn't
    > register the components on the client.
    >
    > The bad thing is after we uninstalled SP2, we built a server
    application
    > to
    > relocate components onto two laptops. It killed COM+ on both of the
    > laptops
    > and required a reinstallation of Win2K to fix the damage, so I don't
    think
    > it uninstalled completely. We can't use that machine to generate
    server
    > applications now.

    ----------------------------------------------------------------
    Users Guide http://msdn.microsoft.com/workshop/essentials/mail.asp
    contains important info. Save time, search the archives at
    http://discuss.microsoft.com/archives/index.html .
    To unsubscribe, mailto:DCOM-signoff-requestDISCUSS.MICROSOFT.COM

    ----------------------------------------------------------------
    Users Guide http://msdn.microsoft.com/workshop/essentials/mail.asp
    contains important info. Save time, search the archives at
    http://discuss.microsoft.com/archives/index.html .
    To unsubscribe, mailto:DCOM-signoff-requestDISCUSS.MICROSOFT.COM