Failed to copy Mue.exe to McScript_InUse.exe

[Former Member]

Not to hijack the thread but I've been experiencing the same issue with McScript_InUse.exe process.  I recently upgraded our 4.5 ePO server to patch3 and the McAfee 4.5 agents to build 1499.  This went without a hitch for about 95% of our enterprise but it seems that there are several (20+ users) that are experiencing this issue.  I realized that I had forgotten to update the agent management extensions on the server after the agent upgrade to build 1499.  After I checked in the extensions it seemed to have fixed about half of the users that were experiencing the high CPU utilization due to the McScript process.  I still have several users that I can't seem to fix.

Some of the trouble clients seem to work after I uninstall the older agent manually and install the 4.5.0.1499 agent manually.  The McScript_Inuse process seems to kick off once the agent tries to pull my deployment task from the server.  From that point on the process eats anywhere from 50% to 99% of the CPU and won't stop until I kill the process.

I thought it might have to due with the fact that for some reason the agent is hanging on pulling the update (both for agent and VSE) so I've tried manually installing the 4.5.0.1499 agent and VSE 8.7 with a SuperDAT.  Unfortunately, on the problematic clients, this still does not fix the issue.

Any thoughts?

on 7/16/10 8:46:43 AM GMT-06:00

[Former Member]

The same problem started occurring on a large number of systems within a client network. Seemingly since the weekend on all the systems.

Any solution to this yet?

[Former Member]

UPDATE:

After working on my issue the following weekend after I posted, I noticed that the problematic clients were all pulling from the same repository.  The issue turned out to be that the local repository for that site was a Windows 2k server with the 4.0 Agent installed.  I never had any issues with it before but apparently once the 4.5 patch 3 for the server was put into production it caused issues with the 4.5 agents pulling from a repository that had a 4.0 agent.  I moved that local repository to an Windows 2k3 server with the 4.5 agent installed and it fixed the issue.  Now all the pulls are successful and no high CPU usage.

Hopefully this helps you with your issue Hentie.

[Former Member]

I can concur that there is an emerging issue with MA45 systems updating from an MA40 repository system...

[JoeBidgood]

Hang about, though - I want to make sure we're all talking about the same thing. The original problem was the "failed to copy mue.exe..." message, rather than mcscript_inuse using high CPU. Have you got this message, or a high CPU issue? If it's the latter could you start a new thread for it as I'd very much like to keep track of it...

SuperDAT wrote:
I can concur that there is an emerging issue with MA45 systems updating from an MA40 repository system...

onires wrote:
UPDATE:
After working on my issue the following weekend after I posted, I noticed that the problematic clients were all pulling from the same repository.  The issue turned out to be that the local repository for that site was a Windows 2k server with the 4.0 Agent installed.  I never had any issues with it before but apparently once the 4.5 patch 3 for the server was put into production it caused issues with the 4.5 agents pulling from a repository that had a 4.0 agent.  I moved that local repository to an Windows 2k3 server with the 4.5 agent installed and it fixed the issue.  Now all the pulls are successful and no high CPU usage.
Hopefully this helps you with your issue Hentie.

Are you using superdat repositories? I.e. is the MA4 agent machine a superagent repository serving the MA 4.5 clients?

Thanks -

Joe

[Former Member]

Joe,

Yes... I am using SuperAgent repositories.  So the issue was that the client 4.5 agents were not able to pull the DAT updates from the 4.0 SuperAgent repository.  During the pulls for the DAT updates the McScript_InUse.exe process would hang and eat 50% to 99% of the CPU usage.  The user would have to go into the task manager and kill the McScript_InUse process in order to regain the CPU cycles.  This was affecting about 25-30 users.  Once that repository was moved to a new server that was able to have the 4.5 agent installed and elevated to a SuperAgent all affected agents were able to pull successfully.

I tested this hypothesis out by taking the 4.0 SuperAgent offline and having the afftected agents pull from another SuperAgent 4.5 repository successfully.  I replicated this several times by taking the local 4.0 repository on and offline to see how it affected the agent pulls.  Each time, the agents were able to pull without an issue from the 4.5 but would choke once the 4.0 repository was put back online.

The site that had the 4.0 SuperAgent repository served about 200+ clients; most of which were 4.5 agents.  So this was not affecting all 4.5 agents.  I can't say why the other client agents were able to pull successfully and these weren't.  Either way the upgrade of the repository to the 4.5 agent was 100% successful.

Message was edited by: onires on 9/17/10 11:09:41 AM GMT-06:00

[JoeBidgood]

This is extremely useful information - thanks    It's also very gratifying to hear that it's been confirmed by Jason Smith.

I'll feed this back to the engineering teams - again, thanks very much

Regards -

Joe

[Former Member]

In regards to hijacking this thread. THANK YOU! This was the best thing possible. Ive spent the past 2 weeks SCOURING McAfee forums & the internet, and even called in a case with Platinum support and have gotten nowhere. I have tested out EVERYTHING, added every service to low risk processes, changed update times, etc. When I say I've tried every fix that related to McScript_InUse.exe spiking and holding during a DAT update, I mean it. Many 4am nights, searching for something that made sense.

Finally I come across this post BEFORE the mention about the 4.0Agent on Repository vs 4.5 Agent rollout on workstations. In searching I came across this thread again with more information, and it hit the nail on the head. The next day the repositories (3) were updated to the 4.5 Agent and since then the 10 users affected (yes, out of 20,000) have not spiked even after the 6108 DAT release. The DAT release was the catalyst for the mcscript_inuse activating, and NEVER releasing.

I cant thank you enough for keeping this thread alive! yes, its only one dat update, so cant wait till 6109 is released, but it seems the update of the main ePO server to Agent 4.5 patch 1 and the Repositories has fixed the issue. Its communities like this that keep things running smoothly. Thank you to ALL!

[Former Member]

Jason,

Awesome to hear about your success!!!  I'm so glad to hear that my resolution worked for you as well.  After the fix, I did call McAfee support and asked if they knew about this issue.  The technician said that it makes sense but I dont' think they have a KB article on this.

Now go enjoy your weekend and try not to think about McAfee for awhile.