locked
Health scan: Invoke-MBCAModel failed error after automatic upgrade to BPA 2.0 RRS feed

  • Allgemeine Diskussion

  • Hello,

    I have a daily error reporting on my SBS Standard 2011 ever since the upgrade to Microsoft Baseline Configuration Analyser 2.0 and BPA 1.1

    Detailed Network Report shows:

    "An error occurred while the computer was performing a Windows Server Solutions BPA scan. For information about the error, review the log file at %installation folder%\wssgbpa.log, or manually run Windows Server Solutions BPA."

    Viewing the bpa.log shows the following:

    10/27/2011 02:05:03          running under silent mode

    10/27/2011 02:05:03          Self Update key value: 1

    10/27/2011 02:05:03          Exe path for BPAUpdate.exe:C:\Program Files\Windows Server Solutions BPA\Bin

    10/27/2011 02:05:05          BPAUpdate.exe launched.

    10/27/2011 02:05:27          InvokeModel: MBCA module has been imported.

    10/27/2011 02:05:33          WSSG MBCA Model has been invoked.

    10/27/2011 02:05:33  !Error! Invoke-MBCAModel failed!

    10/27/2011 02:05:33          ConsoleIntegrationWritter: ErrorsFound is updated with 2

    10/27/2011 02:05:34  !Error! Error details: Microsoft.WindowsServerSolutions.BPA.Common.BPAException: Health scan: Invoke-MBCAModel failed!

       at Microsoft.WindowsServerSolutions.BPA.Common.MBCA.InvokeModel()

       at Microsoft.WindowsServerSolutions.BPA.UI.Program.RunSilentMode()

    However, when I manually invoke the Best Practices Analyzer and run it, no errors are detected and the issue in the Daily Network Log is removed.

    Any ideas as to what is causing the automated system task to fail?

    • Typ geändert Sean Zhu - Freitag, 4. November 2011 03:20
    Donnerstag, 27. Oktober 2011 04:02

Alle Antworten

  • "An error occurred while the computer was performing a Windows Server Solutions BPA scan. For information about the error, review the log file at %installation folder%\wssgbpa.log, or manually run Windows Server Solutions BPA."

    That's the only error you encountered while running automated task in BPA and the error does not occur when you run it manually?


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
    Montag, 31. Oktober 2011 07:54
  • Hi Sean,

    That is correct. The only other error that appears to occur at a similar time to the BPA error reports as follows:

    Event Source: Instrumentation  Event ID: 1 Total Occurences: 1

    A search of the net on this error has turned up very little and once again, this error seems to have commenced showing in the error logs on 9th of October, the same date as the BPA issue.

    • Bearbeitet nicknotes Mittwoch, 25. Januar 2012 03:01
    Freitag, 4. November 2011 05:08
  • I am also receiving this error.  It started showing up only after I cleaned up the non-best practices that the BPA was identifying.  Running the BPA manually returns no errors.

    Also, I cannot locate the wssgbpa.log to try to see more about the error.

     

    Sonntag, 11. Dezember 2011 21:19
  • Exactly the same issue, including the misnamed (I think) wssgbpa.log reference) which makes it impossible to find.  When I run it manually, all is good.
    Donnerstag, 29. Dezember 2011 14:51
  • Sean,

    Did you discover a fix for this as the problem continues...

     

    Mittwoch, 25. Januar 2012 03:01
  • Exactly the same here. I've tried uninstalling and reinstalling. Does not look good on daily reports when there really is no problem with the server.


    David
    Dienstag, 31. Januar 2012 14:28
  • It really is ProgramData\Microsoft\Windows Server Solutions BPA\BPA.log
    David
    Dienstag, 31. Januar 2012 14:33
  • Had the same problem myself after removing Acronsis Online Backup and MozyPro (Not sure if there is any connection to this problem)

    The daily Scheduled Task that runs BPA is run with the SYSTEM account. By changing to an Administrator account, the problem goes away.

    If anyone can tell me why the SYSTEM account maybe having problems, I'd appreciate it.

     

    Cheers

    Samstag, 4. Februar 2012 08:41
  • Lazy Slug,

    That did it. Try Administrator, works. Try System, does not. Try Administrator, works.

    Thank you for making my SBS daily report look better!


    David
    Samstag, 4. Februar 2012 14:20
  • I changed the scheduled task to run under administrator credentials, and that fixed it for me as well!  Thanks!!
    Dienstag, 14. Februar 2012 04:42
  • I'm now getting a new, but perhaps related, error - ever since the upgrade came out a few days ago.  Inititally, I was getting 2 errors - both related to the fact that the upgrade would not be installled while the job was running.  Today I found the upgrade in the blog, and downloaded it and applied it.  Now when I run it manually, I get the a pop-up error message that "Microsoft Baseline Configuration Analyzer was not able to obtain the resuls or data successflly.  There has been a Best Practice Analyzer error for Model Id 'WSSGBPA'.  The Result file has not yet been generated.  Please perform the scan first and try again."   The log reports that:

    02/25/2012 17:28:01          Running under normal mode
    02/25/2012 17:28:01          Self Update key value: 1
    02/25/2012 17:28:01          Exe path for BPAUpdate.exe:C:\Program Files\Windows Server Solutions BPA\Bin
    02/25/2012 17:28:01          BPAUpdate.exe launched.
    02/25/2012 17:28:01          MBCA Exe is: C:\Program Files\Microsoft Baseline Configuration Analyzer 2\MBCA.exe
    02/25/2012 17:33:26          MBCA.exe exited with return code 0
    02/25/2012 17:33:29          GetLatestResult: MBCA module has been imported.
    02/25/2012 17:33:30          MBCA Result got.
    02/25/2012 17:33:30          ConsoleIntegrationWritter: ErrorsFound is updated with 0
    02/25/2012 17:33:31          GetLatestResult: MBCA module has been imported.
    02/25/2012 17:33:31          MBCA Result got.
    02/25/2012 17:33:31          Start collecting SQM data.
    02/25/2012 17:33:31          Called upload. Waiting for it to finish now.
    02/25/2012 17:33:34          Upload attempt done. filePath:C:\ProgramData\Microsoft\Windows Server Solutions BPA\sqm\sqmdataWSSGBPA00.sqm, hr:0x0, dwHttpResponse:200

    When I run it through task manager (using admin credentials) the return code in task manager shows 0xFFFFFFFF with no explanations.  The log says:

    02/25/2012 17:26:05          running under silent mode
    02/25/2012 17:26:05          Self Update key value: 1
    02/25/2012 17:26:05          Exe path for BPAUpdate.exe:C:\Program Files\Windows Server Solutions BPA\Bin
    02/25/2012 17:26:06          BPAUpdate.exe launched.
    02/25/2012 17:26:11          InvokeModel: MBCA module has been imported.
    02/25/2012 17:26:17          WSSG MBCA Model has been invoked.
    02/25/2012 17:26:17  !Error! Invoke-MBCAModel failed!
    02/25/2012 17:26:17          ConsoleIntegrationWritter: ErrorsFound is updated with 2
    02/25/2012 17:26:17  !Error! Error details: Microsoft.WindowsServerSolutions.BPA.Common.BPAException: Health scan: Invoke-MBCAModel failed!
       at Microsoft.WindowsServerSolutions.BPA.Common.MBCA.InvokeModel()
       at Microsoft.WindowsServerSolutions.BPA.UI.Program.RunSilentMode()

    Samstag, 25. Februar 2012 22:36
  • Not sure if this is related, but see: http://www.sbsfaq.com/?p=3319. There is at least one issue with the latest BPA update.

    "...we’ve figured out that the latest Best Practice Analyzer (BPA) is the culprit and that removing it from the server has 'resolved' this issue for the moment.  Microsoft [is] aware of the issue..."


    David

    Samstag, 25. Februar 2012 23:23
  • That seems to be SBS Essentials and Storage Server Essentials specific.  Might be related, who knows!  But thanks for pointing that out - I was sporadically getting that message on my Storage Server, so it's good to know the cause!

    It is too much of a coincidence to think they are not related, but I don't really want to uninstall as a solution!

    Sonntag, 26. Februar 2012 02:28
  • Hi All,

    Just to let you all now (if you have not already found the answer) that i have fixed this problem. in the following steps

    1) down load the Microsoft Baseline Configuration Analyser 2.0 http://www.microsoft.com/en-gb/download/details.aspx?id=16475, run the file to uninstall the application

    2) Run the Microsoft Baseline Configuration Analyser 2.0 installer again to reinstall it.

    3) Delete the log files in folder "C:\ProgramData\Microsoft\Windows Server Solutions BPA" 

    4) From the Admin menu open the windows event viewer: 

    5) Clear the windows logs 

    6) Expand the tree item in the event viewer  as follows "Applications ans services logs" -> "Microsoft" -> "BaselineConfigurationAnalyzer" ->"Instrumentation"

    7) Clear the Admin log

    8) Then Refresh the Securit tab on the SBS Console.

    Hope this helps.


    Its life but not as we know it Jim!

    Montag, 8. April 2013 22:19
  • Freitag, 8. November 2013 08:35