Failed to copy Mue.exe to McScript_InUse.exe

[kink80]

I have some of my machines that are showing up as failed deployments when my Deploy Agent, VSE, and HIPS task runs. Below is a section of one of the logs that I am seeing. Has anyone seen this before?

2010-01-15 13:08:00 i #1860 Sched Scheduler: Invoking task [Default - Deploy Agent VSE and HIPS]...
2010-01-15 13:08:00 I #1980 Sched >>--RunTask
2010-01-15 13:08:00 I #1980 Manage Running task SoftwareID:EPOAGENT3000, TaskID:375
2010-01-15 13:08:00 I #3756 FrmSvc User SID is S-1-5-18 and SessionID is 0
2010-01-15 13:08:00 I #3756 UpdEvents Initializing Event Interface
2010-01-15 13:08:00 I #3756 UpdEvents EpoEventInf Interface: Initialization succeeded.
2010-01-15 13:08:00 E #1096 Uec Error trace:
2010-01-15 13:08:00 E #1096 Uec   Failed to copy Mue.exe to McScript_InUse.exe. McAfee Script Engine cannot run
2010-01-15 13:08:00 I #1096 UpdEvents Generating update event:EventId=2412:Severity=4:ProductId=EPOAGENT3000:Locale=0409:UpdateType=N/A:UpdateError=2:NewVersion=N/A:DateTime=N/A
2010-01-15 13:08:00 I #1096 UpdEvents EpoEventInf Interface: Event element created.
2010-01-15 13:08:00 I #1096 muemsg Calling HandlePostpone with TaskID:  UpdateState: 2
2010-01-15 13:08:00 I #1096 muemsg Finished Calling HandlePostpone
2010-01-15 13:08:00 I #1096 UpdEvents EpoEventInf Interface: Update event created.
2010-01-15 13:08:00 I #1096 UpdEvents DeInitializing Event Interface
2010-01-15 13:08:00 I #1096 UpdEvents EpoEventInf Interface: Deinitialization succeeded.
2010-01-15 13:08:00 I #1096 muemsg Updater session finish state value =2
2010-01-15 13:08:00 E #3756 deploy Error trace:
2010-01-15 13:08:00 E #3756 deploy  [start deployment,EPOAGENT3000,4,375,0]->
2010-01-15 13:08:00 E #3756 deploy   Deployment session failed to start
2010-01-15 13:08:00 E #1980 Sched Failed to run the task: error -1000, TaskGUID = 375, SoftwareID = EPOAGENT3000
2010-01-15 13:08:00 E #1980 Sched <<--RunTask hr=-1000(0xfffffc18)
2010-01-15 13:08:00 I #1860 Sched Failed to invoke task Default - Deploy Agent VSE and HIPS due to unexpected error -1000
2010-01-15 13:08:00 I #1860 Sched Default - Deploy Agent VSE and HIPS - Last run time(local) is Fri Jan 15 13:08:00 2010
2010-01-15 13:08:00 I #1860 Sched

[JoeBidgood]

I haven't come across this before... is there an "orphaned" mcscript_inuse process on the machines? If so, if you kill the process and restart the framework, do the tasks run correctly now?

HTH -

Joe

[kink80]

Thanks for the reply Joe. I checked and there are no "orphaned" McScript_InUse.exe processes running. Even after restarting the same error occurs. this is only happening on a few seemingly random machines.

[kink80]

I also noticed that this error is not directly tied to a Deployment task. It also occurs on Update DAT and Engine tasks.

[JoeBidgood]

That would make sense - the same file would be used for deployment and update tasks.

Is there anything on the machine that would prevent the file from being copied? Does the System account have full control over all its files and folders, for example?

Regards -

Joe

[kink80]

No there isn't anything special about these machines that are experiencing this issue. I checked and the System account has full control of everything.

[JoeBidgood]

I'm not sure what to suggest in that case

I'd open a support case so that it can be looked at in detail.

Sorry

Joe

[Sk1dMARK]

I've had this same issue and believe to have the fix.

I was seeing this issue on some Windows 2008 R2 servers running on Hyper-V.  It seems that servers on actual hardware were not experiencing the issue.

The apparent fix was to start the "Application Experience" service and set it to Automatic start type.  I say "apparent fix" as I just found the answer yesterday and have had limited test time.  So far, the tasks are executing every time which was not happening before.

Give it a try if you are still experiencing the issue.

Hope this helps.

Regards,

Mark 

[kink80]

Thanks for your response on this issue. My problems are occurring on actual machines running Windows Xp Pro SP3. All of the ones that were experiencing the issue are now functioning properly. I am not sure how that happened but at least they are fixed.

[Former Member]

so the issue just suddenly stopped happening on those systems? That is strange...I guess you dont know what fixed it huh.

It's been awhile, are you seeing the issue again?