you're reading...
McAfee Vulnerability Manager

McAfee Vulnerability Manager 7.5 – Engine data is not currently available error message

I recently installed and configured a McAfee Vulnerability Manager 7.5 server (standalone) within our IT infrastructure to assess our server infrastructure security vulnerabilities and to provide remediation guidance for these. Suffice to say now its working we are getting great security reporting from it.

Whilst configuring my test scan after installation however I was unable to run the scan immediately as a Scan Engine was unavailable. Looking on the Manage > Engines page I was presented the error “Engine data is not currently available. Contact your McAfee Vulnerability Manager Administrator.” also shown below:

MVM 7.5 Engine error (Click for larger image)

However when I opened the FCM Console to check the service status all services seemed to be running ok…

FCM Services running without error

…and looking in the MVM log file (C:\Program Files (x86)\Foundstone\Logs) I saw the following errors:

CommHTTP::Connect: Unable to connect to (HTTPS) COpenSSLSocket::Connect – tcp connect failed
CommHTTP::PostResource returns (0xa0fbf061)[E_ENGINE_HTTP_CONNECT_FAIL]
CommHTTP::PostEngineStatus returns (0xa0fbf061)[E_ENGINE_HTTP_CONNECT_FAIL]

To resolve this issue I had to do the following:

1. Under Windows Services (services.msc) start the SQL Server Browser service and ensure it is set to start Automatically
2. In the hosts file (C:\Windows\System32\drivers\etc) I had to add entries for the server by its IP and local loopback. Below is an example:       mymvmserver              mymvmserver

This fixed the issue for me, I hope it helps others. I’m sure this was due to a simple DNS issue, but starting the SQL Server Browser service is also recommended as MVM apparently relies on this – I need to test this out when I get more time to confirm if its an actual requirement.


2 thoughts on “McAfee Vulnerability Manager 7.5 – Engine data is not currently available error message

  1. it works man thanks!

    Posted by Pedro Hdez | August 30, 2013, 9:22 am
  2. Had the exact same problem. Your solution worked for me as well! Thx so much coz McAfee hasn’t got any help about this issue on it’s website.

    Posted by MrManuzz | October 11, 2015, 10:02 am

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

%d bloggers like this: