0 Replies Latest reply on Aug 24, 2015 9:35 AM by atrick

    MVM database install problems

    atrick

      Hello,

      We are trying to install the foundstone/MVM software 7.5 – R2 (which appears to be the latest available) on a Windows 2012 R2 server and running into a problem with the database creation. 

         

      We are doing a custom install so everything is on one server except the database which points to one of our existing SQL database servers (that way we won’t need another SQL licence)

         

      The specs on the download page list server 2012 R2 as OK, but it comes with .NET 4.5 installed by default, and there is also a note here:

       

      http://b2b-download.mcafee.com/products/evaluation/mcafee_risk_compliance/v7.5/m anuals/mvm750_readme.html#unique_3

         

      saying:

        Issue

      Installation fails when trying to install the McAfee Vulnerability Manager database on a system running .NET 4.0. (589403)

      Resolution

      Remove NET 4.0 before installing McAfee Vulnerability Manager. This is documented in the McAfee Vulnerability Manager Install Guide.

       

      We found that note after attempting the install several times.

       

      The problem is removing .NET 4 on windows 2012 R2 will remove the windows GUI among other things since its all integrated.

      http://blogs.technet.com/b/askcore/archive/2014/04/24/removing-net-framework-4-5 -4-5-1-removes-windows-2012-2012r2-ui-and-other-features.aspx

       

      When we run the installer, it does a quick check and says everything is OK (even though .NET 4.5 is installed) and proceed to install, but the database creation fails.

       

      We’ve tried using different methods, both the “sa” password and the windows authentication to the database.  Both fail, and looking at the database logs on the SQL server, all attempts show a failed “sa” login with a bad password (even when trying the windows authentication it shows a failed “sa” login attempt),  we’ve tried both SQL 2012 SP2 and SQL 2008 R2 SP2 and get the same result. 


      Does anyone have any ideas?