Consider the following scenario:
You have Microsoft SQL Server Management Studio installed on a Windows 8.1-based client computer.
You connect the Object Explorer panel to an instance of Microsoft SQL Server Analysis Services (SSAS) in SQL Server Management Studio.
You try to select Properties for the instance of SSAS in order to view or change the properties of the instance.
In this scenario, the properties dialog box does not appear. Additionally, you receive the following error message:
Cannot show requested dialog.
Cannot show requested dialog. (SqlMgmt)
at Microsoft.SqlServer.Management.SqlMgmt.DefaultLaunchFormHostedControlAllocator.AllocateDialog(XmlDocument initializationXml, IServiceProvider dialogServiceProvider, CDataContainer dc)
at Microsoft.SqlServer.Management.SqlMgmt.DefaultLaunchFormHostedControlAllocator.Microsoft.SqlServer.Management.SqlMgmt.ILaunchFormHostedControlAllocator.CreateDialog(XmlDocument initializationXml, IServiceProvider dialogServiceProvider)
at Microsoft.SqlServer.Management.SqlMgmt.LaunchForm.InitializeForm(XmlDocument doc, IServiceProvider provider, ISqlControlCollection control)
at Microsoft.SqlServer.Management.SqlMgmt.LaunchForm..ctor(XmlDocument doc, IServiceProvider provider)
at Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.ToolMenuItemHelper.OnCreateAndShowForm(IServiceProvider sp, XmlDocument doc)
The type initializer for 'Microsoft.AnalysisServices.ManagementDialogs.ServerPropertiesLanguagePanel' threw an exception. (Microsoft.AnalysisServices.SsmsManagementDialogs)
at Microsoft.AnalysisServices.ManagementDialogs.ServerPropertiesLanguagePanel..ctor(CDataContainer dataContainer)
at Microsoft.AnalysisServices.ManagementDialogs.ServerPropertiesDialog..ctor(CDataContainer dataContainer)
Item has already been added. Key in dictionary: '4096' Key being added: '4096' (mscorlib)
at System.Collections.Hashtable.Insert(Object key, Object nvalue, Boolean add)
at System.Collections.Hashtable.Add(Object key, Object value)
at System.Collections.Specialized.StringDictionary.Add(String key, String value)
Each new cumulative update for SQL Server contains all the hotfixes and all the security fixes that were included with the previous cumulative update. Check out the latest cumulative updates for SQL Server:
If you cannot apply the fix that is discussed in the "Resolution" section, use one of the following workarounds to make the planned changes by using SQL Server Management Studio.
Note These workarounds do not resolve the error in SQL Server Management Studio. They only provide alternate methods to make the planned changes.
Workaround 1: Use SQL Server Management Studio on a different computer
To work around this issue, use SQL Server Management Studio on a different computer that is running an earlier version of the operating system.
Workaround 2: Manually edit the property tags
To work around this issue, manually edit the property tags in the Msmdsrv.ini configuration file on the disk of the Analysis Services server. To do this, follow these steps:
Start Notepad in an elevated administrator mode.
In Notepad, click File, click Open, and then locate the folder that contains the Msmdsrv.ini file.
Note This folder may be located in the default 64-bit program files or on a separate disk drive letter if the original setup choices were customized. For example, the Msmdsrv.ini file may be located in one of the following folders.
Microsoft SQL Server Analysis Services 2008
%ProgramFiles%\Microsoft SQL Server\MSAS10.<Instance name>\OLAP\Config
Microsoft SQL Server Analysis Services 2008 R2
%ProgramFiles%\Microsoft SQL Server\MSAS10_50.<Instance name>\OLAP\Config
Microsoft SQL Server Analysis Services 2012
%ProgramFiles%\Microsoft SQL Server\MSAS11.<Instance name>\OLAP\Config
Note The placeholder <Instance name> represents the instance name. By default, <Instance name> is MSSQLSERVER.
Select the Msmdsrv.ini file.
Edit the value in the tag for the property that needs adjustment.
We recommend that you make a safe backup copy of the Msmdsrv.ini file before you edit the file.
Incorrect or unexpected values or XML tag entries in the Msmdsrv.ini file can cause the Analysis Services service not to start in the future. Therefore, you have to use caution when you edit the Msmdsrv.ini file.
Not all properties can be modified by using the configuration file. For example, security or collation settings can be changed only by using SQL Server Management Studio. In those cases, you will have to either use Workaround 1 or apply the hotfix.
Save the file.
If you receive an "Access Denied" error message, make sure that you are running Notepad as administrator.
Some properties may take affect without a restart of the Analysis Services service after approximately 30 seconds. However, other properties do require the service to be stopped and restarted to take effect.
For more information, please see the following topic in SQL Server Books Online:
Configure Server Properties in Analysis Services
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.