cancel
Showing results for 
Search instead for 
Did you mean: 
Highlighted
nashcoop
Level 10
Report Inappropriate Content
Message 1 of 14

Move 3.5.1 (Multiplatform) Client log warning details (213: Failed to get for process info of (System))

I have recently upgraded a lot of Move clients to 3.5.1 and I'm seeing the warning details below in the mvagent.log files.  I was hoping someone might be able to translate in plain English what these warnings mean.  Should I be concerned?  Is there a real problem?   Thanks.

U.3500.5388: Jan 21 2015:12:38:53.482:   SYSTEM: eppl_policies.cpp: 1345: sending enable cmd.

K.0004.0072: Jan 21 2015:12:38:53.561:   SYSTEM: epdrv_init.c:  616: MoveAV LogFile Path : \Device\HarddiskVolume2\Program Files (x86)\McAfee\MOVE AV Client\mvagent.log

K.0004.0072: Jan 21 2015:12:38:53.584:   ERROR: scan.c      : 2287: Cannot open cache file 2

K.0004.10128: Jan 21 2015:12:38:53.661:   WARNING: utl_rt.c    :  109: Process info is NULL for proc handle 0x4
K.0004.10128: Jan 21 2015:12:38:53.664:   WARNING: fsh_winnt.c :  213: Failed to get for process info of (System)

U.5440.1092: Jan 21 2015:12:38:54.086:   SYSTEM: utl.c       :  753: McAfee end point driver loaded.

U.5440.1092: Jan 21 2015:12:38:54.087:   SYSTEM: cmdi_process.c:  517: Command 'mvadm.exe enable' returned 0: No error

U.5440.4256: Jan 21 2015:12:38:54.087:   SYSTEM: wsc.cpp     :  414: WSC Integration: Target OS does NOT support WSC

U.5440.3204: Jan 21 2015:12:45:00.865:   SYSTEM: cmdi_process.c:  517: Command 'mvadm.exe status' returned 0: No error

K.0004.0072: Jan 21 2015:12:45:25.454:   WARNING: utl_rt.c    :  109: Process info is NULL for proc handle 0x4
K.0004.0072: Jan 21 2015:12:45:25.456:   WARNING: fsh_winnt.c :  213: Failed to get for process info of (System)

K.0004.0076: Jan 21 2015:12:50:25.446:   WARNING: utl_rt.c    :  109: Process info is NULL for proc handle 0x4
K.0004.0076: Jan 21 2015:12:50:25.450:   WARNING: fsh_winnt.c :  213: Failed to get for process info of (System)

K.0004.0076: Jan 21 2015:12:55:25.441:   WARNING: utl_rt.c    :  109: Process info is NULL for proc handle 0x4
K.0004.0076: Jan 21 2015:12:55:25.444:   WARNING: fsh_winnt.c :  213: Failed to get for process info of (System)

K.0004.0092: Jan 21 2015:13:00:25.436:   WARNING: utl_rt.c    :  109: Process info is NULL for proc handle 0x4
K.0004.0092: Jan 21 2015:13:00:25.438:   WARNING: fsh_winnt.c :  213: Failed to get for process info of (System)

K.0004.0076: Jan 21 2015:13:05:25.430:   WARNING: utl_rt.c    :  109: Process info is NULL for proc handle 0x4
K.0004.0076: Jan 21 2015:13:05:25.433:   WARNING: fsh_winnt.c :  213: Failed to get for process info of (System)

K.0004.0092: Jan 21 2015:13:10:25.424:   WARNING: utl_rt.c    :  109: Process info is NULL for proc handle 0x4
K.0004.0092: Jan 21 2015:13:10:25.427:   WARNING: fsh_winnt.c :  213: Failed to get for process info of (System)

K.0004.0076: Jan 21 2015:13:15:25.419:   WARNING: utl_rt.c    :  109: Process info is NULL for proc handle 0x4
K.0004.0076: Jan 21 2015:13:15:25.421:   WARNING: fsh_winnt.c :  213: Failed to get for process info of (System)

K.0004.0092: Jan 21 2015:13:20:25.410:   WARNING: utl_rt.c    :  109: Process info is NULL for proc handle 0x4
K.0004.0092: Jan 21 2015:13:20:25.414:   WARNING: fsh_winnt.c :  213: Failed to get for process info of (System)

K.0004.0092: Jan 21 2015:13:25:26.069:   WARNING: utl_rt.c    :  109: Process info is NULL for proc handle 0x4
K.0004.0092: Jan 21 2015:13:25:26.071:   WARNING: fsh_winnt.c :  213: Failed to get for process info of (System)

K.0004.0076: Jan 21 2015:13:30:26.476:   WARNING: utl_rt.c    :  109: Process info is NULL for proc handle 0x4
K.0004.0076: Jan 21 2015:13:30:26.479:   WARNING: fsh_winnt.c :  213: Failed to get for process info of (System)

K.0004.0092: Jan 21 2015:13:35:26.616:   WARNING: utl_rt.c    :  109: Process info is NULL for proc handle 0x4
K.0004.0092: Jan 21 2015:13:35:26.617:   WARNING: fsh_winnt.c :  213: Failed to get for process info of (System)

U.5440.8948: Jan 21 2015:13:38:52.078:   SYSTEM: cmdi_process.c:  517: Command 'mvadm.exe status' returned 0: No error

K.0004.0092: Jan 21 2015:13:40:26.670:   WARNING: utl_rt.c    :  109: Process info is NULL for proc handle 0x4
K.0004.0092: Jan 21 2015:13:40:26.672:   WARNING: fsh_winnt.c :  213: Failed to get for process info of (System)

K.0004.0076: Jan 21 2015:13:45:26.688:   WARNING: utl_rt.c    :  109: Process info is NULL for proc handle 0x4
K.0004.0076: Jan 21 2015:13:45:26.690:   WARNING: fsh_winnt.c :  213: Failed to get for process info of (System)

K.0004.0076: Jan 21 2015:13:50:26.699:   WARNING: utl_rt.c    :  109: Process info is NULL for proc handle 0x4
K.0004.0076: Jan 21 2015:13:50:26.701:   WARNING: fsh_winnt.c :  213: Failed to get for process info of (System)

K.0004.0072: Jan 21 2015:13:55:26.711:   WARNING: utl_rt.c    :  109: Process info is NULL for proc handle 0x4
K.0004.0072: Jan 21 2015:13:55:26.713:   WARNING: fsh_winnt.c :  213: Failed to get for process info of (System)

K.0004.0076: Jan 21 2015:14:00:26.698:   WARNING: utl_rt.c    :  109: Process info is NULL for proc handle 0x4
K.0004.0076: Jan 21 2015:14:00:26.700:   WARNING: fsh_winnt.c :  213: Failed to get for process info of (System)

K.0004.0072: Jan 21 2015:14:05:26.679:   WARNING: utl_rt.c    :  109: Process info is NULL for proc handle 0x4
K.0004.0072: Jan 21 2015:14:05:26.681:   WARNING: fsh_winnt.c :  213: Failed to get for process info of (System)

K.0004.0076: Jan 21 2015:14:10:26.660:   WARNING: utl_rt.c    :  109: Process info is NULL for proc handle 0x4
K.0004.0076: Jan 21 2015:14:10:26.661:   WARNING: fsh_winnt.c :  213: Failed to get for process info of (System)

13 Replies
McAfee Employee rajinp
McAfee Employee
Report Inappropriate Content
Message 2 of 14

Re: Move 3.5.1 (Multiplatform) Client log warning details (213: Failed to get for process info of (System))

Is there any other filter driver running in this system ?

nashcoop
Level 10
Report Inappropriate Content
Message 3 of 14

Re: Move 3.5.1 (Multiplatform) Client log warning details (213: Failed to get for process info of (System))

I'm sorry, but I don't understand the question.  Filter driver?

McAfee Employee rajinp
McAfee Employee
Report Inappropriate Content
Message 4 of 14

Re: Move 3.5.1 (Multiplatform) Client log warning details (213: Failed to get for process info of (System))

I was asking apart from MOVE filter driver, if there is any other filter driver running on the system ?

nashcoop
Level 10
Report Inappropriate Content
Message 5 of 14

Re: Move 3.5.1 (Multiplatform) Client log warning details (213: Failed to get for process info of (System))

It's entirely possible that there is another filter driver on the server, but I really can't say with any certainty.  How do I check if there are other filter drivers running on it?

McAfee Employee rajinp
McAfee Employee
Report Inappropriate Content
Message 6 of 14

Re: Move 3.5.1 (Multiplatform) Client log warning details (213: Failed to get for process info of (System))

juat run the command "fltmc" and see which drivers are running.

nashcoop
Level 10
Report Inappropriate Content
Message 7 of 14

Re: Move 3.5.1 (Multiplatform) Client log warning details (213: Failed to get for process info of (System))

When I ran the "fltmc" command it shows the "mvagtdrv" and "luafv" filter driver is also running.  The first is for the Move agent, the second is for the LUA File Virtualization Filter Driver.

McAfee Employee rajinp
McAfee Employee
Report Inappropriate Content
Message 8 of 14

Re: Move 3.5.1 (Multiplatform) Client log warning details (213: Failed to get for process info of (System))

Do we know what is the other filter driver. When there are other filter drivers like this which intercepts file activities there will be problems. So just try to understand more on this.

nashcoop
Level 10
Report Inappropriate Content
Message 9 of 14

Re: Move 3.5.1 (Multiplatform) Client log warning details (213: Failed to get for process info of (System))

luafv.sys – UAC File Virtualization

User Account Control (UAC) used to be known as Limited User Account (LUA). UAC File Virtualization provides a method for applications that aren’t running with administrative privileges to write to system locations in the file system and registry without encountering access denied errors. It does this by transparently redirecting file system requests into the VirtualStore which is not a system location.

Does the mvagtdrv.exe service need to be running with administrator privileges?

McAfee Employee rajinp
McAfee Employee
Report Inappropriate Content
Message 10 of 14

Re: Move 3.5.1 (Multiplatform) Client log warning details (213: Failed to get for process info of (System))

Our driver will run in system account. You don't have to explicitly mention in which account it has to run.

More McAfee Tools to Help You
  • Subscription Service Notification (SNS)
  • How-to: Endpoint Removal Tool
  • Support: Endpoint Security
  • eSupport: Policy Orchestrator
  • Community Help Hub

      New to the forums or need help finding your way around the forums? There's a whole hub of community resources to help you.

    • Find Forum FAQs
    • Learn How to Earn Badges
    • Ask for Help
    Go to Community Help

    Join the Community

      Thousands of customers use the McAfee Community for peer-to-peer and expert product support. Enjoy these benefits with a free membership:

    • Get helpful solutions from McAfee experts.
    • Stay connected to product conversations that matter to you.
    • Participate in product groups led by McAfee employees.
    Join the Community
    Join the Community