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

From: Crimson Star (crimson.star_at_nospam.gov.ab.ca)
Date: 05/01/03 

Date: Thu, 1 May 2003 09:11:13 -0600

We ran into the same problem. Microsoft Premier Support provided 814119 as
the solution, which worked. I do not know if this hotfix is available to
the general public. 

--
Crimson Star, MCSE
Technical Webmaster
Alberta Corporate Service Centre
Government of Alberta
"snakpak" <shamby222@hotmail.com> wrote in message
news:a45bfe71.0304301956.754721b3@posting.google.com...
> 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: hot fix Q331953 causes error in transactional asp pages
    ... Microsoft Premier Support provided 814119 as ... I do not know if this hotfix is available to ... Alberta Corporate Service Centre ... I cannot seem to fix it. ...
    (microsoft.public.win2000.security)
  • experiencing database and sharepoint issues in new/clean install
    ... Thanks to Eric Vogel for #1 I renamed the GUID key to ... >Item #1) Event Viewer Shows an Application Log error: ... >as missing the same patch. ... >major build of sqlservr.exe than hotfix build number ...
    (microsoft.public.windows.server.sbs)
  • RE: MS02-042 Patch on win2k pro kills capability to map to defaul t sh ares
    ... Given that the hotfix is claiming to be an XP one I would ... >Server (SP3 + patch), no problems found. ... >>showed that the error begin occurring immediately after installing the ...
    (Focus-Microsoft)
  • Re: Update for ISA 2004 KB916106 killed access to external web sites
    ... There was a separate hotfix available for the iTunes issue that didn't have ... automatically restart some of the Exchange services. ... The patch does make certain web sites available that aren't available to ...
    (microsoft.public.windows.server.sbs)
  • Re: Update for ISA 2004 KB916106 killed access to external web sites
    ... I'm a little ticked that the ISA folks blew me off when I reported it the first time. ... doesn't automatically restart, the W3 service, and on SBS it doesn't automatically restart some of the Exchange services. ... You'd be doing us all a service if you'd reinstall the patch and see if your web access is restored once you manualy restart the W3 service. ... Incidentally, before this patch was released, it was a hotfix, and the hotfix had the same problem as the patch--didn't automatically restart the W3 and Exchange services, which I reported at the time. ...
    (microsoft.public.windows.server.sbs)