Video Screencast Help
Give us your opinion and win with Symantec! Please help us by taking this survey to tell us about your experience with Symantec Connect, so that we can continue to grow and improve.  Take the survey.

Security Compliance scan failed

Created: 24 Jun 2009 • Updated: 21 May 2010 | 8 comments
This issue has been solved. See solution.

Hi All,

In Client system SEP is displaying the message as

" Security Compliance scan failed"
"Your computer failed its security compliance check.  Please see the Client Management Security Log for more information."

When checked the Security logs it displays as Host Integrity failed.

I have configured Host Integrity policy to install Microsoft patch and the same patch is already installed in  the client.

We have tried even Unistalling the patch and reinstalled but problem is still pending.

Has any one faced this kind of issue.

Discussion Filed Under:

Comments 8 CommentsJump to latest comment

Thomas K's picture

What version of SNAC are you running? Is this happening on all clients? Whats OS's are you experiencing the issue on? Have you tried testing with a different requirement? If so, does HI work properly?

Can you post the security logs here?

Ajju's picture

Ver: SEPMR4 with SNAC
only some systems we are facing this issue.  In other systems it is working fine.

Thomas K's picture

Can you verify that the computers that fail HI do not have the characters "&" or "%" in the Computer description and Computer name fields.

This has caused issues with clients failing HI when all requirements are met.

Ajju's picture

We have all the computer names as standards and not using any special charcters.

YES the complaince has failed, when Patch HI requirement has met.

Thomas K's picture

So you say that you are running SNAC MR4? Are you running a Japanese OS on these systems?

Ajju's picture


We are using English Operating System with SNAC MR4

Thanks for helping to get support.  

We have found the Solution:

This problem occurs because the Mup.sys driver assumes that there must be no more than three file-system filter drivers running at the same time within Windows XP and Windows 2003. The Mup.sys driver handles Distributed File System (DFS) file I/O requests. If there are four or more file system filter drivers, the I/O request packet (IRP) location buffer that is pre-allocated by Mup.sys will overflow.

For more information: 


We have update the Microsoft patch WindowsXP-KB906866-x86-PLK.exe and the problem is resolved.

We also did the testing by unistalling the Patch mentioned in the Host Integrity and restarted the system.

Once the system was booted it automatically installed the patch as per HI and and Host Integrity was PASSED.