locked
Error when Validatin Cluster Cluster creation tool Validate the cluster Error Test report isn't available, try to validate again. RRS feed

  • Question

  • Hi,

    I get this error at validating the cluster when using the cluster Creation tool. 

    Error:"Error Test report isn't available, try to validate again." 

    Notification Pannel shows "Successfully validated the cluster."

    <label for="applicationVersion" style="box-sizing:inherit;vertical-align:middle;font-size:12px;line-height:16px;letter-spacing:0px;font-variant-numeric:normal;font-variant-east-asian:normal;text-rendering:auto;-webkit-font-smoothing:antialiased;">Version</label>
    2007
    <label for="buildNumber" style="box-sizing:inherit;vertical-align:middle;font-size:12px;line-height:16px;letter-spacing:0px;font-variant-numeric:normal;font-variant-east-asian:normal;text-rendering:auto;-webkit-font-smoothing:antialiased;">Build</label>

    1.2.2007.18002

    Cluster Creation extension ver 1.294.0

    Has anyone else got the Same issue?


    Thursday, July 23, 2020 10:50 AM

Answers

  • Hi Erik,

    Fix = Install hosts as English (United States)

    ***********************EDIT********************

    A quick bit of google-fu and the error indicated a Time date format issue. So on a hunch I re-installed the hosts and with the US locale (I'm in UK so previously was using en-GB). Have also updated the locale of the server with WAC (did no bother to re-isntall) and now to all works. You could probably just change the local with power shell on the hosts and reboot.

    Set-WinSystemLocale 'en-US'

    But in summary I make sure all your date formats are in US and it works.

    MS please fix this bug in the next release.

    ************************************************

    I have this same problem. I have previously tried to POC an Azure Stack HCI cluster after seeing a deep dive demo from ignite and got this same error as you and in the end binned it and went another way. Should also not I tried with Windows Admin center to create just a bog standard cluster which also failed with same error (I was able to create a cluster on same hosts with the Cluster manager).

    I saw at MS inspire this week there is an updated OS specific for Azure stack HCI and the WAC was also updated so thought I would give it another go. Completely different kit, same error. I can only conclude Windows Admin Center has some sort of bug. I also asked about this issue during the "ask an expert session" at MS inspire but the question was ignored.

    Frustrating...



    • Marked as answer by Erik-_- Friday, July 24, 2020 3:11 PM
    • Edited by KrisTurk Saturday, July 25, 2020 9:17 AM
    Friday, July 24, 2020 1:11 PM

All replies

  • Hi Eric,

    Thanks for your question.

    As per my understanding, you get this error when you tried to create a failover cluster. Please correct me if any misundstanding. To attempt to fix the issue, please help to answer the questions below

    1.Did you run this validation in Windows Admin Center?

    2.Could you run the validation successfully in the Failover Cluster Manager? 
    If no, you could check the path C:\Users\<your user name>\AppData\Local\Temp for the validation report file. If yes, it could be the issue of Window Admin Center and you may try to reinstall it.

    Best Regards,

    Ian Xue


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.



    • Edited by Ian Xue Friday, July 24, 2020 8:21 AM
    Friday, July 24, 2020 8:18 AM
  • Looks like issue with MMC or DOT.

    Try ordinary diagnostics tools:

    sfc /scannow

    Dism /Online /Cleanup-Image /ScanHealth (/CheckHealth)

    dism /online /cleanup-image /restorehealth

    Friday, July 24, 2020 9:31 AM
  • Hi,

    thx for your help. yes validaiton was run in windwos admincenter.

    Yes there is a report in the temp folder. Already tryed reinstalling admincenter (same error with 1910.2 and 2007)

    Failover cluster manager sees no error when validating. 

    There is an eventviwer error on the admincenter host when validatiog:

    sessionId : 639f0655-ac2a-4f6f-8b1e-bb217158d52e
    eventId : Trace
    level : Error
    sourceName : msft.sme.cluster-creation
    source : ClusterReportService.loadReport
    timestamp : 1595538737992
    message : InvalidPipeArgument: 'Unable to convert "Invalid Date" into a date' for pipe 'e'
    stack : 
    moreEventData : 


    Friday, July 24, 2020 9:51 AM
  • No erros found. Still same error in admincenter

    thx tough

    Friday, July 24, 2020 9:52 AM
  • Hi Erik,

    Fix = Install hosts as English (United States)

    ***********************EDIT********************

    A quick bit of google-fu and the error indicated a Time date format issue. So on a hunch I re-installed the hosts and with the US locale (I'm in UK so previously was using en-GB). Have also updated the locale of the server with WAC (did no bother to re-isntall) and now to all works. You could probably just change the local with power shell on the hosts and reboot.

    Set-WinSystemLocale 'en-US'

    But in summary I make sure all your date formats are in US and it works.

    MS please fix this bug in the next release.

    ************************************************

    I have this same problem. I have previously tried to POC an Azure Stack HCI cluster after seeing a deep dive demo from ignite and got this same error as you and in the end binned it and went another way. Should also not I tried with Windows Admin center to create just a bog standard cluster which also failed with same error (I was able to create a cluster on same hosts with the Cluster manager).

    I saw at MS inspire this week there is an updated OS specific for Azure stack HCI and the WAC was also updated so thought I would give it another go. Completely different kit, same error. I can only conclude Windows Admin Center has some sort of bug. I also asked about this issue during the "ask an expert session" at MS inspire but the question was ignored.

    Frustrating...



    • Marked as answer by Erik-_- Friday, July 24, 2020 3:11 PM
    • Edited by KrisTurk Saturday, July 25, 2020 9:17 AM
    Friday, July 24, 2020 1:11 PM
  • That looks promising. I tought about something similar but i only tried changeing time format not region.

    Set-WinSystemLocale 'en-US' doesnt work tough.

    Currently re installing. Will tell if it works or not.

    Edit:

    Yes Reinstalling in EN_US worked no errors now when validatng thx alot




    • Edited by Erik-_- Friday, July 24, 2020 6:55 PM
    Friday, July 24, 2020 3:19 PM
  • No worries, happy to help :)
    Friday, July 24, 2020 8:58 PM
  • Reporting in from Australia, this was also the fix for me. Just changing the locale with powershell wasnt enough, had to reinstall OS.
    Friday, July 31, 2020 3:27 AM