Consider the following scenario:
- You have a computer whose System locale is configured as Arabic and User locale is set to English or a different language.
- On this computer you try to install a named instance of SQL Server 2008 and the instance name contains Arabic characters.
In this scenario, the setup program fails with the following error message, though the name conforms with the guidelines documented in Books Online.
The following error has occurred:
The MOF compiler could not connect with the WMI server. This is either because of a semantic error such as an incompatibility with the existing WMI repository or an actual error such as the failure of the WMI server to start.
For help, click: http://go.microsoft.com/fwlink?LinkID=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=10.0.1600.22&EvtType=0x429FDFA3%25400x0A2FBD17%25401211%25401
The Detail.txt setup log will have an error message similar to the following:
2009-02-28 19:03:56 Slp: Configuration action failed for feature SQL_Engine_Core_Inst during timing ConfigNonRC and scenario ConfigNonRC.
2009-02-28 19:03:57 Slp: Microsoft.SqlServer.Configuration.Sco.ScoException: The MOF compiler could not connect with the WMI server. This is either because of a semantic error such as an incompatibility with the existing WMI repository or an actual error such as the failure of the WMI server to start.
2009-02-28 19:03:57 Slp: at Microsoft.SqlServer.Configuration.Sco.WmiProvider.InstallMof()
2009-02-28 19:03:57 Slp: at Microsoft.SqlServer.Configuration.SqlEngine.MofRegistration.RegisterMof()
2009-02-28 19:03:57 Slp: at Microsoft.SqlServer.Configuration.SqlEngine.SqlEngineSetupPrivate.CreateWMIProvider(EffectiveProperties properties)
2009-02-28 19:03:57 Slp: at Microsoft.SqlServer.Configuration.SqlEngine.SqlEngineSetupPrivate.Install_ConfigNonRC_Prepare(EffectiveProperties properties)
2009-02-28 19:03:57 Slp: at Microsoft.SqlServer.Configuration.SqlEngine.SqlEngineSetupPrivate.Install(ConfigActionTiming timing, Dictionary`2 actionData, PublicConfigurationBase spcb)
2009-02-28 19:03:57 Slp: at Microsoft.SqlServer.Configuration.SqlConfigBase.PrivateConfigurationBase.Execute(ConfigActionScenario scenario, ConfigActionTiming timing, Dictionary`2 actionData, PublicConfigurationBase spcbCurrent)
2009-02-28 19:03:57 Slp: at Microsoft.SqlServer.Configuration.SqlConfigBase.SqlFeatureConfigBase.Execute(ConfigActionScenario scenario, ConfigActionTiming timing, Dictionary`2 actionData, PublicConfigurationBase spcbCurrent)
2009-02-28 19:03:57 Slp: at Microsoft.SqlServer.Configuration.SqlConfigBase.SlpConfigAction.ExecuteAction(String actionId)
2009-02-28 19:03:57 Slp: at Microsoft.SqlServer.Configuration.SqlConfigBase.SlpConfigAction.Execute(String actionId, TextWriter errorStream)
2009-02-28 19:03:57 Slp: Exception: Microsoft.SqlServer.Configuration.Sco.ScoException.
Additionally an event similar to the following gets logged to the Windows Application event log:
The SQL Server (<Arabic instance name>) service terminated with service-specific error 17058 (0x42A2).
The file '\\?\C:\Program Files\Microsoft SQL Server\MSAS10.<Arabic instance name>\OLAP\Data\CryptKey.bin' could not be opened. Please check the file for permissions or see if other applications locked it.
Failed to initialize SQLSQM timer. One of the following can be the source of the problem: registry doesn't contain all necessary information, server instance name can not be retrieved correctly, failure during timer creation, etc.
.NET Runtime Optimization Service (clr_optimization_v2.0.50727_32) - Failed to compile: C:\Program Files\Microsoft SQL Server\100\Tools\Binn\VSShell\Common7\Tools\VDT\DataProjects.dll . Error code = 0x8007000b
.NET Runtime Optimization Service (clr_optimization_v2.0.50727_32) - Failed to compile: C:\Program Files\Microsoft SQL Server\100\Tools\Binn\VSShell\Common7\Tools\VDT\DataDesigners.dll . Error code = 0x8007000b
Note: The same issue also exists in the CTP versions of SQL Server 2008 R2.