Hi Michael,
The uphclean msi consists of 3 files, uphclean.exe (v 1.6.30.0), msvcp60.dll (v
6.0.8972.0) and readme.txt.
The version of msvcp60.dll (Microsoft (R) C++ Runtime Library) is a lot older
than the one that ships with 2003 or 2003 SP1 (v 6.5.2144.0) and is included
for backward compatibility with NT 4.
If you're paranoid install the msi and if not just copy the new version of
uphclean.exe to your servers and install it with "uphclean -install".
regards,
Ulrich Mack
Volante Systems
________________________________
From: thin-bounce@xxxxxxxxxxxxx on behalf of Michael Pardee
Sent: Fri 17/03/2006 20:57
To: thin@xxxxxxxxxxxxx
Subject: [THIN] Re: Office 2003 applications hang
No, we are running 1.5.4.20. Disabling the service and booting is what is
working for us to temporarily get it out of production. When we just stopped
the service is when the servers crashed shortly after.
We are about to test with the new 1.6d. We put it on a couple boxes last night
so today should be our first real experience with it. Since I need to get it
out to a little over 200 servers I was wondering if I could just push out the
new exe via a for loop or do we really have to run the install process.
On 3/17/06 3:32 AM, "BRUTON, Malcolm, FM" <Malcolm.BRUTON@xxxxxxxx> wrote:
Is this with the latest UPHCLean 1.6d? We are about to upgrade form
1.5 something tomorrow to hopefully correct a few issues after reading all
these posts...I wouldn't have thought disabling this service should cause a
problem unless you had massive log on and offs in a short period. My guess is
there must also be another fault somewhere.
-----Original Message-----
From: thin-bounce@xxxxxxxxxxxxx
[mailto:thin-bounce@xxxxxxxxxxxxx] On Behalf Of Michael Pardee
Sent: 16 March 2006 21:29
To: thin@xxxxxxxxxxxxx
Subject: [THIN] Re: Office 2003 applications hang
The mother of all lessons learned today: If I stop the
UPHClean service on 13 servers, I can expect them all to crash within 10
minutes! I have the best luck ever.
On 3/15/06, Jeff Pitsch <jepitsch@xxxxxxxxx> wrote:
Yes it was something they actually went to Robin about
and he said it was an undocumented fix and that everyone should be running the
latest and greatest.
Jeff
On 3/15/06, Michael Pardee <pardeemp.list@xxxxxxxxx
<mailto:pardeemp.list@xxxxxxxxx> <mailto:pardeemp.list@xxxxxxxxx> > wrote:
We are using 1.5.4.20 <http://1.5.4.20/>
<http://1.5.4.20/> - the latest is 1.6d. We will definitely test and look at
updating...
On 3/15/06, Michael Pardee <pardeemp@xxxxxxxxx
> wrote:
We are using 1.5.4.20
<http://1.5.4.20/> <http://1.5.4.20/> - the latest is 1.6d. We will
definitely test and look at updating...
On 3/15/06, Michael Pardee <
pardeemp.list@xxxxxxxxx <mailto:pardeemp.list@xxxxxxxxx>
<mailto:pardeemp.list@xxxxxxxxx> > wrote:
checking our version right now.
UPHClean is installed everywhere here.
On 3/15/06, Jeff Pitsch
<jepitsch@xxxxxxxxx <mailto:jepitsch@xxxxxxxxx> <mailto:jepitsch@xxxxxxxxx>
> wrote:
I don't remember what version it was.
Jeff
On 3/15/06, Jeremy Saunders
<jeremy.saunders@xxxxxxxxxxx <mailto:jeremy.saunders@xxxxxxxxxxx>
<mailto:jeremy.saunders@xxxxxxxxxxx> > wrote:
Interesting. I can't believe that no
one has come across that before. So
what version of UPHClean were they
using?
Cheers,
Jeremy.
"Jeff Pitsch"
<jepitsch@xxxxxxx
<mailto:jepitsch@xxxxxxx> <mailto:jepitsch@xxxxxxx>
om>
To
Sent by:
thin@xxxxxxxxxxxxx <mailto:thin@xxxxxxxxxxxxx> <mailto:thin@xxxxxxxxxxxxx>
thin-bounce@freel
cc
ists.org
<http://ists.org/> <http://ists.org/>
Subject
[THIN] Re: Office 2003 applications
16/03/2006 04:18
hang
AM
Please respond to
thin
Ok, in the final analysis from
Microsoft, the problem was the simple fact
that the customer was using an older
version of UPHCLEAN. UPHCLEAN was
deleting some registry entries too
early and Office was trying to write to
them after they were removed sending
the process into a nasty little loop.
Jeff
On 3/14/06, Michael Pardee <
pardeemp.list@xxxxxxxxx <mailto:pardeemp.list@xxxxxxxxx>
<mailto:pardeemp.list@xxxxxxxxx> > wrote:
Jeff, just following up on this one.
Did disabling the error Reporting
Service eventually fix the issue?
On 1/25/06, Jeff Pitsch <
jepitsch@xxxxxxxxx > wrote:
No. It's other applictions as well
as Outlook and it affects
applications that don't necessarily
access the network.
Jeff
On 1/25/06, Ruben Spruijt <
Ruben.Spruijt@xxxxxxxxxxxx > wrote:
Hi Jeff,
It's not this issue ..? (below)
Ruben
> > If you have any Servers with
HP NC7781 NIC's installed (Hp DL
> 380's, DL 360's and others), you
may experience excessive
> retransmits, Outlook hangs, file
copy performance issues, cluster
> failovers, etc.
> >
> > Cause:
> > The driver defaults to
"Offload TCP transmit Checksum"
and "Offload
> Ip Transmit
> > Checksum". This is a
performance enhancement designed to relieve
> the TCP and IP
> > components of the IP checksum
calculation overhead and assign that
> duty to the NIC.
> > Normally this is a preferred
method of operation. The HP NC7781
> NICS periodically
> > miscalculate the TCP checksum.
This causes connection timeouts
> periodically and
> > more importantly, Outlook
hangs between 10 and 20 seconds. With
the
> latest firmware
> > and drivers installed, the
issue is still prevalent. The box that
> receives a
> > response with an incorrectly
calculated checksum simply throws the
> malformed
> > response away, never
delivering the data to the application.
> > Resolution:
> > In the Netcard driver
configuration dialog box, disable Offload
> checksum
> > calculations. This will allow
the TCP and IP components to
> calculate their own
> > checksums.This change does not
require a reboot or involve a
> service interruption, normal
> >
> > change control procedures
should of course, always be followed!
--
Michael Pardee
www.blindsquirrel.org
<http://www.blindsquirrel.org/> <http://www.blindsquirrel.org/>
************************************************
For Archives, RSS, to Unsubscribe,
Subscribe or
set Digest or Vacation mode use the
below link:
//www.freelists.org/list/thin
************************************************
#####################################################################################
This e-mail, including all attachments, may be confidential or privileged.
Confidentiality or privilege is not waived or lost because this e-mail has been
sent to you in error. If you are not the intended recipient any use,
disclosure or copying of this e-mail is prohibited. If you have received it in
error please notify the sender immediately by reply e-mail and destroy all
copies of this e-mail and any attachments. All liability for direct and
indirect loss arising from this e-mail and any attachments is hereby disclaimed
to the extent permitted by law.
#####################################################################################
