Re: *asp failure after installing Hotfix MS02-010/Q331953

From: snakpak (shamby222_at_hotmail.com)
Date: 05/01/03


Date: 30 Apr 2003 20:56:30 -0700


Hotfix 814408 was not directly inteded for the issues caused by
331953. It was intended for Microsoft Knowledge Base Article - 814408
-- Printer Operators Group Is Not Listed in the Terminal Server
Redirected Print Queue

located at http://support.microsoft.com/default.aspx?scid=kb;en-us;814408

I spent many hours with a peace of black plastic on my ear talking to
nearly everyone @ Microsoft (except Mr. Gates) on the issue and the
end result was to install the hotfix above. To this day I have not
heard anything from MS as to why 331953 caused such a head-ache for
this particular scenario. This is very disturbing to me since 331953
is still being distrubuted without any warnings or disclaimers
addressing the newly found greys on my head. The only thing I can
think of is SP4 is coming very soon. I hope all this gibberish helps.
By the way hotfix 814408 is not distributed unless you call or
specially request it from MS.

Happy Patching!!!!!!!!

"Brought to by molton boron"

"Mattias Nyholm" <mattias.nyholm@framfab.se> wrote in message news:<uFnnlgxCDHA.28440@TK2MSFTNGP10.phx.gbl>...
> Ah, ok. That is very intresting, I'll have to test that too. Do you
> know if 814408 contains the security updates from 331953?
>
> Mattias
>
> "snakpak" <shamby222@hotmail.com> wrote in message
> news:a45bfe71.0304241516.7f17e403@posting.google.com...
> > This resolved the original problems caused by 331953. Sorry for the
> confusion ;)
> >
> > "Mattias Nyholm" <mattias.nyholm@framfab.se> wrote in message
> news:<#u6qeCZCDHA.3008@TK2MSFTNGP11.phx.gbl>...
> > > Did this patch fix the original problems caused by 331953, or did
> > > it fix the problems you had after uninstalling 331953?
> > >
> > > Regards,
> > > Mattias
> > >
> > > "snakpak" <shamby222@hotmail.com> wrote in message
> > > news:a45bfe71.0304150827.60aa435@posting.google.com...
> > > > After many hours of working with MS they have supplied me with a
> > > > solution to the problems listed above. The knowledge base article is
> > > > locate below:
> > > >
> > > > http://support.microsoft.com/default.aspx?scid=kb;en-us;814408
> > > >
> > > > The article is not directly related to this issue, but does update the
> > > > following files
> > > >
> > > > rpcss.dll
> > > > rpcrt4.dll
> > > > ole32.dll
> > > >
> > > > which are the files that are included in patch 331953. It appears that
> > > > rpcrt4.dll is the file causing the headaches posted above. The hotfix
> > > > explained in aticle 814408 is a pre-sp4 patch and will be included in
> > > > service pack 4.
> > > >
> > > > Hope this helps.
> > > >
> > > > Good Luck and "May the Force be with you"
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > shamby222@hotmail.com (snakpak) wrote in message
> news:<a45bfe71.0304141317.35ab2624@posting.google.com>...
> > > > > I have also come across this error and uninstalled 331953 from our
> > > > > development site. After doing the uninstall the following issues came
> > > > > about:
> > > > >
> > > > > 1. Terminal Services hung during startup
> > > > > 2. The uninstall removed some enviroment variables needed by Commerce
> > > > > Server.
> > > > >
> > > > > Well I had to re-install terminal services (2 reboots) and re-add the
> > > > > environment variables. Being that I am not comfortable with the
> > > > > uninstallation of this on our production servers. I have opened a case
> > > > > with Microsoft on this issue and have spoken to just about everyone at
> > > > > MS besides Mr. Gates. We are working diligently on getting this
> > > > > resolved. This is a pre-SP4 patch and will be included in the new
> > > > > service pack, so just uninstalling will not suffice. I will update
> > > > > upon resolution.
> > > > >
> > > > > Carson Saunders <carson_saunders_remove-this_@yahoo.com> wrote in
> message
> news:<Xns9357721072552carsonsaundersyahooc@130.133.1.4>...
> > > > > > That is the exact issue we were running into. Any call from an ASP
> page
> > > > > > to a COM+ component requiring a new transaction would fail with the
> > > > > > message "Connection to the transaction manager failed." After
> > > > > > uninstalling the patch, everything worked.
> > > > > >
> > > > > > Carson
> > > > > >
> > > > > > "Mattias Nyholm" <mattias.nyholm@framfab.se> wrote in
> > > > > > news:upE3vBR$CHA.2148@TK2MSFTNGP10.phx.gbl:
> > > > > >
> > > > > > > What kind of problems did you have? I've seen problems with
> > > > > > > ASP applications using transactions. Before applying 331959
> > > > > > > they were working fine, but with the patch they fail:
> > > > > > > (0x8004E003)
> > > > > > >
> > > > > > > You made a method call on a COM+ component that has a transaction
> that
> > > > > > > has already aborted or in the process of aborting.
> > > > > > >
> > > > > > > After uninstalling the patch the ASP apps work just fine again.
> > > > > > >
> > > > > > > Regards,
> > > > > > > Mattias
> > > > > > >
> > > > > > >
> > > > > > > "Carson Saunders" <carson_saunders_remove-this_@yahoo.com> wrote
> in
> > > > > > > message news:Xns935254F0717F0carsonsaundersyahooc@130.133.1.4...
> > > > > > >> I've run into the same problem along with several others.
> Currently,
> > > > > > >> the only solution we've come up with is to un-install the patch,
> as
> > > > > > >> you did. Someone had mentioned that the patch worked fine on
> machines
> > > > > > >> where no subsequent patches were installed so it could be a patch
> > > > > > >> compatability issue, but that is just speculation. But we have
> had
> > > > > > >> no problems since un-installing the patch
> > > > > > >>
> > > > > > >> Carson
> > > > > > >>
> > > > > > >> "[sa]" <Apocalyptic@firemail.de> wrote in
> news:057301c2f904$8aefc530
> > > > > > >> $a201280a@phx.gbl:
> > > > > > >>
> > > > > > >> > Hi there,
> > > > > > >> >
> > > > > > >> > anyone got the problem, after installing the latest Win2k
> > > > > > >> > Hotfix "MS03-010: Flaw in RPC Endpoint Mapper Could Allow
> > > > > > >> > Denial of Service Attacks (331953)" some of the Webservers
> > > > > > >> > applications / com+ packets fail to run correctly.
> > > > > > >> > After shutdown on the component, unload, iisreset and
> > > > > > >> > server reboot i decided to uninstall the Q331959 Patch.
> > > > > > >> > After this all the *asp Pages run correctly.
> > > > > > >> >
> > > > > > >> > Anyone got an idea ?
> > > > > > >> >
> > > > > > >> > regards
> > > > > > >> >
> > > > > > >> > [sa]
> > > > > > >> >
> > > > > > >> >
> > > > > > >>
> > > > > > >>
> > > > > > >>
> > > > > > >> --
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > --



Relevant Pages

  • RE: Blue Screen when printing just like Microsoft Knowledge Base Article - 827953
    ... I have the exact problem outlined in Microsoft Knowledge Base Article - 827953, where the PC crashes and a Stop ... Any help would be appreciated as this is occurring on a network of PC's now SP4 has been deployed!! ... I cannot find any reference to this hotfix actually being included in SP4 so I am suspicious ...
    (microsoft.public.win2000.printing)
  • Autoarchive March 24, 2004 hotfix
    ... Using Outlook 2000 I have the Autoarchive problem ... described in the Microsoft knowledge base article 838023 ... The article announces the release of a hotfix to fix the ...
    (microsoft.public.outlook)
  • obtaining hotfixes
    ... apparently I need a particular hotfix: ... Microsoft Knowledge Base Article - 835717 ... The problem has corrupted my spell-checker, which I badly need, and worse, have come to rely upon. ...
    (microsoft.public.word.docmanagement)
  • Re: Spoolsv.exe Problem
    ... Windows Printing Team ... Search the Microsoft Knowledge Base here: ... > If they determine you do indeed need the hotfix, ...
    (microsoft.public.windowsxp.print_fax)
  • RE: Help with EntLib and hotfix from KB 872800
    ... Library but if you can send me the hotfix I can try the code out. ... > g. Pregenerate the serializers for the Web service by using the prepared ... run the following command at a command ... > view the article in the Microsoft Knowledge Base: ...
    (microsoft.public.dotnet.framework)