ACS Blogs

A blog site for Architecting Connected Systems staff to tell the world about their exploits in
SharePoint 2007/2010/2013, Windows Workflow Foundation (3.0/4.0) and other great technologies!
Welcome to ACS Blogs Sign in | Join | Help
in Search
MSPress

CJG

Installing Service Bus 1.0 and Service Bus 1.1 in Azure VM - Exit code: 15010 - Error 1722 - Installation success or error status: 1603

Have been doing a lot of Azure provisioning lately and ran across an interesting issue with the latest VMs in Azure.  Seems some registry keys are missing which will cause you to run across these errors:

MSI (s) (44:CC) [21:33:14:551]: Note: 1: 1722 2: DoFabricSetup 3: C:\Program Files\Windows Fabric\bin\Fabric\Fabric.Code.1.0\MSIHiddenAppLauncher.exe 4: FabricSetup /operation:install /gac /trace:"C:\ProgramData\Windows Fabric\Fabric\log" /fabricDataRoot:"C:\ProgramData\Windows Fabric\\" /traceBufferSizeInKB:128 /traceFileSizeInMB:128 /fabricPrincipal:"contoso\s2admin" CustomAction DoFabricSetup returned actual error code 1 (note this may not be 100% accurate if translation happened inside sandbox)

FabricSetup.EventLog,wevtutil failed to install manifest C:\Program Files\Windows Fabric\bin\Fabric\Fabric.Code.1.0\WF.man. Exit code: 15010 

A partial solution was provided across a couple posts out there, but nothing that comprehensiving fixes it right away:

  • https://blogs.msdn.microsoft.com/distributedservices/2014/12/16/common-appfabric-1-1-installation-errors-with-and-without-sharepoint/ - Talks about various reasons why you might get these errors, none resolved my issue
  • http://sharepoint.stackexchange.com/questions/69320/error-installing-azure-workflow-server-during-2013-install - Talks about a service not being enabled, but in my case it was
  • http://blog.symprogress.com/tag/azure-worker-role/ - Shows that Channel "0" is missing in another instance
  • https://alasdaircs.wordpress.com/2014/08/15/azure-vm-agent-breaks-your-server- Shows that the Azure VM Agent causes an issue with installing and uninstalling things.  This partially fixes the problem, but was missing the "0" channel.  Adding it with the right values fixes the Service Bus install issue:

Here is the full registry file to get Service Bus 1.0 and Service Bus 1.1 to install in Azure VMs:

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WINEVT\Publishers\{9148c98f-152c-44d3-a496-26350c475d74}\ChannelReferences]
"Count"=dword:00000004

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WINEVT\Publishers\{9148c98f-152c-44d3-a496-26350c475d74}\ChannelReferences]
@="Microsoft-WindowsAzure-Diagnostics/GuestAgent"
"Id"=dword:00000010
"Flags"=dword:00000000

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WINEVT\Publishers\{9148c98f-152c-44d3-a496-26350c475d74}\ChannelReferences\0]
@="Microsoft-WindowsAzure-Diagnostics/Diagnostic"
"Id"=dword:00000010
"Flags"=dword:00000000

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WINEVT\Publishers\{9148c98f-152c-44d3-a496-26350c475d74}\ChannelReferences\1]
@="Microsoft-WindowsAzure-Diagnostics/Runtime"
"Id"=dword:00000011
"Flags"=dword:00000000

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WINEVT\Publishers\{9148c98f-152c-44d3-a496-26350c475d74}\ChannelReferences\2]
@="Microsoft-WindowsAzure-Diagnostics/Heartbeat"
"Id"=dword:00000012
"Flags"=dword:00000000

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WINEVT\Publishers\{9148c98f-152c-44d3-a496-26350c475d74}\ChannelReferences\3]
@="Microsoft-WindowsAzure-Diagnostics/Bootstrapper"
"Id"=dword:00000013
"Flags"=dword:00000000

Enjoy!
Chris

Published Friday, August 5, 2016 11:13 PM by cjg
Filed under: ,

Comments

No Comments
Anonymous comments are disabled

This Blog

Syndication

Powered by Community Server, by Telligent Systems