Can you check what MFCOM build you have? And I presume you did re-register
the exe?
ALEX
From: "Schneider, Chad M" <CMSchneider@xxxxxxxxx> Reply-To: thin@xxxxxxxxxxxxx To: thin@xxxxxxxxxxxxx Subject: [THIN] Re: Getting the following MFCOM.exe error after reboot Date: Mon, 17 Oct 2005 22:41:27 -0500
Did that, rebooted, still getting MFCOM.exe memory was unable to be written.
_____
From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On Behalf
Of Jeff Pitsch
Sent: Monday, October 17, 2005 7:18 PM
To: thin@xxxxxxxxxxxxx
Subject: [THIN] Re: Getting the following MFCOM.exe error after reboot
Did you try recreating the LHC?
Jeff
On 10/17/05, Schneider, Chad M <CMSchneider@xxxxxxxxx <mailto:CMSchneider@xxxxxxxxx> > wrote:
Disable Mcafee did not work. Errors still exist.
Anyone else have ideas?
_____
From: thin-bounce@xxxxxxxxxxxxx <mailto:thin-bounce@xxxxxxxxxxxxx> [mailto:thin-bounce@xxxxxxxxxxxxx <mailto:thin-bounce@xxxxxxxxxxxxx> ] On Behalf Of Jeff Pitsch Sent: Monday, October 17, 2005 3:13 PM To: thin@xxxxxxxxxxxxx <mailto:thin@xxxxxxxxxxxxx> Subject: [THIN] Re: Getting the following MFCOM.exe error after reboot
yea I was just trying to see if McAfee was actually the issue or not. Easier to disable it temporarily to see if it is the problem, than wait and see for patching. Immediate answer versus possibly putting on a patch that breaks more stuff.
Jeff
On 10/17/05, Evan Mann < <mailto:emann@xxxxxxxxxxxxxxxxxxxxx> emann@xxxxxxxxxxxxxxxxxxxxx> wrote:
11 has issues on Domain Controllers. It was replaced with 11a which uses the
filter drive from 10. Otherwise, it seems to be fine.
_____
From: thin-bounce@xxxxxxxxxxxxx <mailto:thin-bounce@xxxxxxxxxxxxx> [mailto:
<mailto:thin-bounce@xxxxxxxxxxxxx> thin-bounce@xxxxxxxxxxxxx] On Behalf Of
Schneider, Chad M
Sent: Monday, October 17, 2005 4:03 PM
To: thin@xxxxxxxxxxxxx <mailto:thin@xxxxxxxxxxxxx>
Subject: [THIN] Re: Getting the following MFCOM.exe error after reboot
I will first patch it, I see patches 10 and 11 are out, and reference from an iForum presentation, that 11 is useful.
My Mcafee guy did not even know 11 was available.
_____
From: thin-bounce@xxxxxxxxxxxxx <mailto:thin-bounce@xxxxxxxxxxxxx> [mailto:thin-bounce@xxxxxxxxxxxxx <mailto:thin-bounce@xxxxxxxxxxxxx> ] On Behalf Of Jeff Pitsch Sent: Monday, October 17, 2005 2:55 PM To: thin@xxxxxxxxxxxxx <mailto:thin@xxxxxxxxxxxxx> Subject: [THIN] Re: Getting the following MFCOM.exe error after reboot
Have you tried disabling it to see if it corrects the problem. Lately with my clients, I'm seeing lots of issues iwth mcafee and metaframe.
Jeff
On 10/17/05, Schneider, Chad M < CMSchneider@xxxxxxxxx <mailto:CMSchneider@xxxxxxxxx> > wrote:
I definitely have it, Mcafee, has been on these servers for years. 8.0.
_____
From: thin-bounce@xxxxxxxxxxxxx <mailto:thin-bounce@xxxxxxxxxxxxx> [mailto:thin-bounce@xxxxxxxxxxxxx <mailto:thin-bounce@xxxxxxxxxxxxx> ] On Behalf Of Jeff Pitsch Sent: Monday, October 17, 2005 2:28 PM To: thin@xxxxxxxxxxxxx <mailto:thin@xxxxxxxxxxxxx> Subject: [THIN] Re: Getting the following MFCOM.exe error after reboot
the age old question, Anti-virus?
Jeff
On 10/17/05, Schneider, Chad M < CMSchneider@xxxxxxxxx <mailto:CMSchneider@xxxxxxxxx> > wrote:
"mfcom.exe - Application Error : The instruction at "0x77fcc024" referenced memory at "0x00000000". The memory could not be written."
Information at CTX 105062 is not the answer.
MPS 3.0
W2K SP4.
