cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
mr.9211
Level 7
Report Inappropriate Content
Message 1 of 11

Failed to launch the scan on MVM 7.0

Jump to solution

Hi,

i have installed the MVM 7.0 on windows server 2008 R2 64 Bit,but when i tried to luacnch the scan it gives me the following error:

An error occurred. Could not launch the scan. Your Scan Engine or Scan Controller may be down or unreachable. Contact your McAfee Vulnerability Manager Administrator

Regards,

M-A


1 Solution

Accepted Solutions
cgrim
Level 13
Report Inappropriate Content
Message 2 of 11

Re: Failed to launch the scan on MVM 7.0

Jump to solution

Hi M-A,

Did you check that the Scan Engine or Scan Controller were indeed running?

You can confirm in the FCM, and or login to the system where they are installed.  Check the services, and/or the Daily Log file.

-Cathy

View solution in original post

10 Replies
cgrim
Level 13
Report Inappropriate Content
Message 2 of 11

Re: Failed to launch the scan on MVM 7.0

Jump to solution

Hi M-A,

Did you check that the Scan Engine or Scan Controller were indeed running?

You can confirm in the FCM, and or login to the system where they are installed.  Check the services, and/or the Daily Log file.

-Cathy

View solution in original post

Re: Failed to launch the scan on MVM 7.0

Jump to solution

I am running an eval of MVM 7.5 on a Windows 2008 R2 install as well with the same error message, and yes the scan engine is running, but after a few minutes the FCM tool indicates "The scan engine cannot communicate with any Scan Controller."  Yet all the services are installed on this server and running.  I do wonder why I don't see a listening port for TCP port 3803 when I run netstat -an on the server.  Also, the scan engine does fail to initially start on boot up, but does eventually start.

Here's a snip it of the server log errors.

2012-10-04 08:54:31-05:00 |  | 4 | FSScanCtrl | 0x0D9C | Retry: Instantiating results processor...

2012-10-04 08:54:31-05:00 |  | 4 | ResultProcessor | 0x0001 | MaxDBConnectionPool : Found Value 100

2012-10-04 08:54:31-05:00 |  | 4 | ResultProcessor | 0x0001 | Max DB Pool Size set to : 100

2012-10-04 08:55:13-05:00 |  | 4 | Assessment | 0x0230 | ThreadManager | [P1] | 0 | 0 | 0 | 0 | [TM] | 0 | 10000 | 0 | 0 | 0 | 0 | [Modules] | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | [Process] | 8 | 17328 | 79100 | [System] | 1 | 692 | 0 | [D1] | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 |

2012-10-04 08:55:13-05:00 |  | 4 | ScanEngineSvc | 0x03BC | FSScanEngine: Log=0, LogXML=0, ThreadPool_Debug=0

2012-10-04 08:55:13-05:00 |  | 4 | ScanEngineSvc | 0x03BC | Re-posting EngineStatus...

2012-10-04 08:55:14-05:00 |  | 1 | ScanEngineSvc | 0x03BC | CommHTTP::Connect: Unable to connect to (HTTPS)192.168.1.140:3803. COpenSSLSocket::Connect - tcp connect failed

2012-10-04 08:55:14-05:00 |  | 2 | ScanEngineSvc | 0x03BC | CommHTTP::PostResource returns (0xa0fbf061)[E_ENGINE_HTTP_CONNECT_FAIL]

2012-10-04 08:55:14-05:00 |  | 2 | ScanEngineSvc | 0x03BC | CommHTTP::PostEngineStatus returns (0xa0fbf061)[E_ENGINE_HTTP_CONNECT_FAIL]

2012-10-04 08:56:13-05:00 |  | 4 | Assessment | 0x0230 | ThreadManager | [P1] | 0 | 0 | 0 | 0 | [TM] | 0 | 10000 | 0 | 0 | 0 | 0 | [Modules] | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | [Process] | 8 | 17328 | 79100 | [System] | 2 | 686 | 0 | [D1] | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 |

2012-10-04 08:56:13-05:00 |  | 4 | ScanEngineSvc | 0x03BC | FSScanEngine: Log=0, LogXML=0, ThreadPool_Debug=0

2012-10-04 08:56:13-05:00 |  | 4 | ScanEngineSvc | 0x03BC | Re-posting EngineStatus...

2012-10-04 08:56:14-05:00 |  | 1 | ScanEngineSvc | 0x03BC | CommHTTP::Connect: Unable to connect to (HTTPS)192.168.1.140:3803. COpenSSLSocket::Connect - tcp connect failed

2012-10-04 08:56:14-05:00 |  | 2 | ScanEngineSvc | 0x03BC | CommHTTP::PostResource returns (0xa0fbf061)[E_ENGINE_HTTP_CONNECT_FAIL]

2012-10-04 08:56:14-05:00 |  | 2 | ScanEngineSvc | 0x03BC | CommHTTP::PostEngineStatus returns (0xa0fbf061)[E_ENGINE_HTTP_CONNECT_FAIL]

Re: Failed to launch the scan on MVM 7.0

Jump to solution

I am getting exactly the same thing here and I'm going round in circles.

No matter whether I change the Scan Controller port to be a custom port or the default port of 3803 I cannot get the Scan Engine to speak to the Controller.

I've installed on:

VMWare Workstation 8.0.5

Vanilla Windows 2008 R2 Standard SP1

IIS with .NET 3.5 SP1

Application Server

SQL Express 2008 R2 SP2 with Management Studio

TCP/IP Enabled

Mixed Mode Authentication Enabled

All Foundstone components on the same server. ("Custom" install, but selected all components)

All other services are good and connected.

SSL certificates and Time Stamps are good.

System Locale and Language is English U.K.

No Firewall or AV on the server - it is out-of-the-box Windows install.

I've tried changing the Scan Engine service to run as Local System and re-started the service, no difference.

There is something definitiely wrong with an all-in-one install that isn't documented somewhere, or the logging doesn't show where the problem might be.

Doing the same type of installation on ESXi 4.1 doesn't appear to have this problem - but it does on VMWare Workstation.

Does the Scan Controller use a driver that doesn't work with VMWare Workstation?

A netstat -a doesn't show the Scan Controller listening on port 3803 and in the log I see the same entried as reported above:

2012-10-04 08:56:13-05:00 |  | 4 | ScanEngineSvc | 0x03BC | FSScanEngine: Log=0, LogXML=0, ThreadPool_Debug=0

2012-10-04 08:56:13-05:00 |  | 4 | ScanEngineSvc | 0x03BC | Re-posting EngineStatus...

2012-10-04 08:56:14-05:00 |  | 1 | ScanEngineSvc | 0x03BC | CommHTTP::Connect: Unable to connect to (HTTPS)192.168.1.140:3803. COpenSSLSocket::Connect - tcp connect failed

2012-10-04 08:56:14-05:00 |  | 2 | ScanEngineSvc | 0x03BC | CommHTTP::PostResource returns (0xa0fbf061)[E_ENGINE_HTTP_CONNECT_FAIL]

2012-10-04 08:56:14-05:00 |  | 2 | ScanEngineSvc | 0x03BC | CommHTTP::PostEngineStatus returns (0xa0fbf061)[E_ENGINE_HTTP_CONNECT_FAIL]

Any suggestions would be good here as this thread says it has been "Answered" - but that doesn't seem to be the case - it also seems that there are several people with this issue, so it could be quite a common "gotcha".

Thanks very much.

James

Re: Failed to launch the scan on MVM 7.0

Jump to solution

I agree James.  The issue has been isolated to VMWare Workstation, at least from what I can tell.  A co-worker of mine has it working on VMWare Player.

Re: Failed to launch the scan on MVM 7.0

Jump to solution

Thanks for the feedback Jeff.

I happen to have VMWare Player installed on the same machine as VMWare Workstation. I'm going to give this a go in Player now and see if it works.... here's hoping!

Cheers

James

Re: Failed to launch the scan on MVM 7.0

Jump to solution

Hmm.. No joy.

Opened the same VM in Player, everything starts as expected - except the Scan Controller.

A netstat -a reveals:

0.0.0.0:3800

0.0.0.0:3801

0.0.0.0:3802

No 0.0.0.0:3803 and the same error when trying to run a quick scan.

I'm going to try and import the ESXi-working build from the Host into VMware workstation to see if this makes any difference, but that might several hours.

I'll post the results.

Thanks

James

Re: Failed to launch the scan on MVM 7.0

Jump to solution

Jeff,

Did you work colleague build the install of MVM 7.5 in Player and manage to get it working? Or did he/she just "open" a pre-built image from Workstation in Player and it worked?

Or.... did the image come from a different source such as ESXi/Hyper-V ?

Thanks very much.

James

Re: Failed to launch the scan on MVM 7.0

Jump to solution

Guys,

I was testing with VMware Workstation 7.1.6, and yes my co-worker was just using VMware Player and it worked for him.

dfirstbr
McAfee Employee
McAfee Employee
Report Inappropriate Content
Message 10 of 11

Re: Failed to launch the scan on MVM 7.0

Jump to solution

Hi James\Jeff

Just as an FYI:

McAfee Vulnerability Manager 7.5 is compatible with VMware ESX versions 4.0 and 4.1.

McAfee Vulnerability Manager 7.5 is compatible with VMware Workstation versions 7.0.x.

If you're using any version other than these ones then you'll need to address that accordingly before moving forward with the issue above.

-dene

You Deserve an Award
Don't forget, when your helpful posts earn a kudos or get accepted as a solution you can unlock perks and badges. Those aren't the only badges, either. How many can you collect? Click here to learn more.

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