[THIN] Acrobat Reader consuming CPU once closed

From: Michael Pardee <pardeemp@xxxxxxxxx>
To: thin@xxxxxxxxxxxxx
Date: Tue, 12 Jun 2012 10:16:18 -0400
This is a frustrating one as a search on Google shows lot's have had to
deal with this issue at one time or another.

Environment:
Windows 2003 X64 Standard Edition
Xen5
All systems provisioned

Starting yesterday morning (Monday) we have been battling high CPU usage on
a few of our published desktops.  When you dig in you can see that various
users have taken a full cpu with AcroRd32.exe.  We are running 10.1.3.
 Supposedly the only thing that has changed was a single in house .Net
application getting a new exe.  The developers are in the same building so
they have been part of the troubleshooting process as well.  We even rolled
back to a prior image and can still reproduce the problem.

It has not been easy to get support from Adobe on a free product but we
continue to try that road as well as some others.  Only these 2-3 desktops
are having the issue while 50+ others seem to be just fine.  One thing that
we tried that looked to address the issue was renaming/deleting a file in
%APPDAT%\Adobe\Acrobat\10.0 directory called ReaderMessages.  That seemed
to take care of it in our testing so last night we scripted the deletion of
that file via login script.  This morning we continue to fight high cpu
issues and have people in front of the consoles manually deleting Acrobat
Reader process.  We were even able to reproduce this by just opening Reader
X and closing it.  The app is closed to the user but the process continues
to run.

Personally I don't have this issue but if I grab a copy of the
ReaderMessages file and add it to my own %APPDATA% path I can then
reproduce the problem.  This file is getting recreated from somewhere but
we can't find it yet.  We've check anti virus, GPOs, OS patches, etc and
have not come up with anything.  The only other thing that happened over
the weekend was an extra.dat from McAfee was implemented due to some crazy
printer virus that was discovered last Friday night.  We worked with McAfee
and they provided an extra.dat to address that issue.  I would think that
if the extra.dat was the issue we would see this problem much more wide
spread, but it is only contained to a few desktops.

Has anyone else ever battled something like this?  Same version or Reader
is deployed across the org and this week is the first we have seen anything.

Thanks in advance for any help.

-- 
Michael Pardee
http://blindsquirrel.org
[THIN] Acrobat Reader consuming CPU once closed

Other related posts:
