AzureStack new installation: Wire server is unavailable

mytest321 Admin 1 Reputation point
2022-05-23T14:04:20.317+00:00

Im testing the azurestack dev kit and ran into this (tested installation several times):

"Wire server is unavailable"

On previous version I would not get this error.
Cant seem to find any documentation about it.

Any ideas?

Not Monitored
Not Monitored
Tag not monitored by Microsoft.
36,160 questions
{count} votes

3 answers

Sort by: Most helpful
  1. risolis 8,701 Reputation points
    2022-05-24T04:14:41.55+00:00
                                                     **SUMMARY NOTES FOR ORIGINAL CONCERN**  
    												   
    

    PROBLEM/POST DESCRIPTION:

    AzureStack new installation: Wire server is unavailable

    Im testing the azurestack dev kit and ran into this (tested installation several times):

    "Wire server is unavailable"

    On previous version I would not get this error.
    Cant seem to find any documentation about it.

    Any ideas?

    -RELEVANT ERRORS LOGS BELOW**

    [ INFO, 20484] DynamicSettingsStorageImpl::SetInternal - Succesfully set setting: Agent.WireServerDeadHeartbeatTimeoutInMs
    [ INFO, 20484] AgentSetSetting - Setting:Value = Agent.WireServerDeadHeartbeatTimeoutInMs:0
    : [ERROR, 20484] Failing HRESULT detected 0xd0000061 [x:\bt\1135275\repo\src\lib\wireprotocol\protocolmanager\wireserverlifecyclemanager.cpp] line 356
    [ERROR, 20484] <- WireServerLifecycleManager::Initialize(0x000002296F59E480) =0xd0000061

    [ INFO, 20484] SaveSettingInAgentConfig - pathBuffer:C:\NugetStore*\Microsoft.AzureStack.Fabric.Compute.RdAgent.Service.Preview.150.900.2107.28*\content\rdagent.ini

    AZURE STACK PREVIEW RELEASE NOTES

    https://learn.microsoft.com/en-us/azure-stack/operator/known-issues?view=azs-2108

    Metrics unavailable for container registries in the user portal
    Applicable: This issue applies to the public preview release of Azure Container Registry on Azure Stack Hub.
    Cause: An issue is preventing metrics from displaying when viewing a container registry in the Azure portal. The metrics are also not available in Shoebox.
    Remediation: No remediation available, will be addressed in an upcoming hotfix.
    Occurrence: Common

    CUSTOMER CONFIRM THE FOLLOWINF DETAIL AFTER THE POWERSHELL TEST WAS ISSUED

    It looks like im on 2108 (1.2108.0.29 according to the test PowerShell command)

    WIRE SERVER IS UNAVAILABLE ON AZURESTACK.

    Finally, after all the steps taken stated during the thread, was confirmed the behavior observed.

    1 person found this answer helpful.
    0 comments No comments

  2. risolis 8,701 Reputation points
    2022-05-24T04:17:20.757+00:00

    Hello @mytest321 Admin

    I hope you are doing fine.

    I am leaving a summary notes for the communication exchange for this issue and It was a pleasure to work together to get this clarify.

    Best Regards,

    Please "Accept the answer" if the information helped you. This will help us and others in the community as well.

    0 comments No comments

  3. mytest321 Admin 1 Reputation point
    2022-05-24T13:13:02.007+00:00

    Found the answer in a previous post. Missing registry key 'OsImageName' under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Azure!

    https://social.msdn.microsoft.com/Forums/azure/en-US/db94c1f2-ba0d-49c9-b518-c34e2873d7bb/asdk-new-install-unable-to-deploy-a-vm-timeouts?forum=AzureStack