Skip to main content
NetApp Knowledge Base

SnapCenter plugin for Windows fails to deploy with error: EnableMessageQueuing returned actual error code 1603

Views:
101
Visibility:
Public
Votes:
0
Category:
snapcenter
Specialty:
snapx
Last Updated:

Applies to

  • SnapCenter server 4.7P1
  • SnapCenter plugin for Windows 4.7P1
  • Windows server 2022

Issue

SnapCenter plugin for Windows fails to deploy.

The package installation fails while trying to enable MessageQueuing Windows feature.

Error in SMCore_Package_xxx.log

MSI (s) (B8:8C) [17:41:47:217]: Executing op: ActionStart(Name=EnableMessageQueuing,Description=Enabling Windows Message Queuing feature... (this may take a few minutes).,)
MSI (s) (B8:8C) [17:41:47:217]: Executing op: CustomActionSchedule(Action=EnableMessageQueuing,ActionType=1025,Source=BinaryData,Target=EnableMessageQueuing,CustomActionData=true)
MSI (s) (B8:98) [17:41:47:232]: Invoking remote custom action. DLL: C:\Windows\Installer\MSIFA95.tmp, Entrypoint: EnableMessageQueuing
SFXCA: Extracting custom action to temporary directory: C:\Windows\Installer\MSIFA95.tmp-\
SFXCA: Binding to CLR version v4.0.30319
Calling custom action WiXCSCA!SysWin32.WiXCSCA.CustomActions.EnableMessageQueuing
WiXCSCA.EnableMessageQueuing: Begin
Exception thrown by custom action:
System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.Configuration.ConfigurationErrorsException: Configuration system failed to initialize ---> System.Configuration.ConfigurationErrorsException: Unrecognized configuration section startup. (C:\Windows\Installer\MSIFA95.tmp-\CustomAction.config line 3)
   at System.Configuration.ConfigurationSchemaErrors.ThrowIfErrors(Boolean ignoreLocal)
   at System.Configuration.BaseConfigurationRecord.ThrowIfParseErrors(ConfigurationSchemaErrors schemaErrors)
   at System.Configuration.BaseConfigurationRecord.ThrowIfInitErrors()
   at System.Configuration.ClientConfigurationSystem.EnsureInit(String configKey)
   --- End of inner exception stack trace ---
   at System.Configuration.ClientConfigurationSystem.EnsureInit(String configKey)
   at System.Configuration.ClientConfigurationSystem.PrepareClientConfigSystem(String sectionName)
   at System.Configuration.ClientConfigurationSystem.System.Configuration.Internal.IInternalConfigSystem.GetSection(String sectionName)
   at System.Configuration.ConfigurationManager.GetSection(String sectionName)
   at System.Configuration.PrivilegedConfigurationManager.GetSection(String sectionName)
   at System.Net.Configuration.SettingsSectionInternal.get_Section()
   at System.Net.Sockets.Socket.InitializeSockets()
   at System.Net.Dns.GetHostName()
   at SysWin32.WiXCSCA.CustomActions.EnableMessageQueuing(Session session)
   --- End of inner exception stack trace ---
   at System.RuntimeMethodHandle.InvokeMethod(Object target, Object arguments, Signature sig, Boolean constructor)
   at System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(Object obj, Object parameters, Object arguments)
   at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object parameters, CultureInfo culture)
   at Microsoft.Deployment.WindowsInstaller.CustomActionProxy.InvokeCustomAction(Int32 sessionHandle, String entryPoint, IntPtr remotingDelegatePtr)
CustomAction EnableMessageQueuing returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)

 

 

 

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.