SQL Server Q&A

Symptoms
This article describes behavior of the SQL Configuration Manager when it is running on a Windows Server 2008-based domain controller and you change a Microsoft SQL Server 2008 engine service account to either a Network Service or a Local Service.
Note The Network Service account and the Local Service account are not supported service accounts for the engine service on a domain controller.
Resolution
When you change theSQL Server 2008 engine service account to either a Network Service account or a Local Service account, the SQL Configuration Manager that is running on a Windows Server 2008-based domain controller does not restrict the change.
You cannot use the built-in accounts as SQL Server service accounts on a domain controller. Typically, when you try to add the built-in accounts to a service account group by using the SQL Configuration Manager, you receive an error message. The SQL Configuration Manager does not specifically check this scenario.
On Windows Server 2008 domain controller, the Service security ID (SID) is enabled for the SQL Server service. Therefore, the service account is not added to the service account group. Additionally, the SQL Configuration Manager does not return an error message.

Symptoms
Consider the following scenario:Both Microsoft SQL Server 2005 Reporting Services and Microsoft SQL Server 2008 Reporting Services are installed on a computer.You start Reporting Services Configuration Manager by using SQL Server Configuration Manager.In this scenario, Reporting Services Configuration Manager for SQL Server 2005 Reporting Services starts instead of Reporting Services Configuration Manager for SQL Server 2008 Reporting Services. Additionally, the instances of both SQL Server 2005 and SQL Server 2008 appear in the Instance Name list.
Resolution
This issue occurs because SQL Server Configuration Manager uses the SQL Server 2005 registry key to obtain the executable path for Reporting Services Configuration Manager instead of using SQL Server 2008 registry key.

Symptoms
You try to enable FILESTREAM settings by using SQL Server Configuration Manager in Microsoft SQL Server 2008. When you do this, you may receive the following error message:

There was an unknown error applying the FILESTREAM settings. Check the parameters are validThis problem occurs after you upgrade to SQL Server 2008.
Resolution
This problemoccurs because the Filestream file share resource expects the followingMicrosoft Windows NT path:
\\?\GlobalRoot\Device\RsFx0102\MSSQLSERVER However,the Cluster service does not accept a Windows NT path.

Symptoms
On a 64-bit computer, you install an instance of the 32-bit (x86-based) version of Microsoft SQL Server 2008. On the same computer, you install an instance of the 64-bit version of SQL Server 2008. Ifyou then uninstall the 64-bit instance, you receive the following error message when you open SQL Server Configuration Manager:

Cannot connect to WMI provider. You do not have permission or the server is unreachable. Note that you can only manage SQL Server 2005 and later servers with SQL Server Configuration Manager.
Invalid namespace [0x8004100e]This problem also occurs if you uninstall the 32-bit instance, and you then open SQL Server Configuration Manager.
Resolution
This problem occurs because the WMI provider is removed when you uninstall an instance of SQL Server 2008. The 32-bit instance and the 64-bit instance of SQL Server 2008 share the same WMI configuration file. This file is located in the %programfiles(x86)% folder.

Symptoms
When you upgrade an instance of SQL Server to SQL Server 2008, some client-related protocol settings are not automatically applied to the SQL Server 2008 client. For example if you have enabled Secure Socket Layer Encryption (SSL) on a SQL Server 2005 instance either by turning on the Force protocol encryption option in Client Network utility or by using the Properties page of SQL Native Client Configuration in SQL Server configuration manager, the setting is not preserved when you upgrade that instance to SQL Server 2008.
Resolution
This behavior is by design.