SQL Server Q&A

As a software engineer, I focus on .NET, especially asp.net, C#, WCF and so on, and I am also very interested in Search Engine Optimization.

Entries Tagged ‘click’

FIX: When you install a clustered instance of SQL Server 2008, account validation fails even though you have specified the correct domain account and password

Symptoms
Consider the following scenario: You are trying to installa clustered instance of SQL Server 2008.In the Server Configuration page of the installation wizard, you click Browse to specify a domain account for a specific service in the Account Name text box.In the Select Users, Computers, or Groups dialog box, you type a letter, and you find the account by clicking Find Now. You select the account, and then you click OK.You specify a password for the account, and then you click Next.In this scenario,account validation fails even though you have specified the correct domain account and password.
Resolution
This issue occurs because the Account Name text box does not bind the data correctly. When the Setup program validates the domain account, it validates the search string value instead of the result value.

Error message when you upgrade from MSDE 2000 to SQL Server 2008 Express: “A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not …

Symptoms
When you upgrade from Microsoft SQL Server 2000 Desktop Engine (MSDE 2000) to SQL Server 2008 Express, you receive thefollowing error message:

Microsoft SQL Server 2008 Setup
A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 – Could not open a connection to SQL Server)
Click ‘Retry’ to retry the failed action, or click ‘Cancel’ to cancel this action and continue setup.
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=0×1BBF2F31%25400×12C2466D If you click Retry, this problem still occurs.
Resolution
To work around this problem, click Cancel to cancel this action, and then continue the upgrade.
Note The final summary page of the upgrade program will contain this error message. However, you can safely ignore this error message, and the upgrade will be finished successfully.

Error message when you change the service account of SQL Server 2008 components to a non-domain administrator account on a Windows Server 2008 domain controller: “The service did not start due to …

Symptoms
On a Windows 2008 domain controller, when you try to use SQL Server Configuration Manager to change the service account of some Microsoft SQL Server 2008 components or of the SQL Server service to a domain user account that is not a domain administrator, you receive one of the following error messages:
Error message 1

The service did not start due to a logon failure. [0x8007042d]You receive this error message if install one or more of the following SQL Server 2008 components, and then you change the service account of the components:SQL Server 2008 Analysis ServicesSQL Server 2008 Integration ServicesSQL Server BrowserTo work around this problem, see Workaround 1.
Error message 2

WMI Provider Error [call to WMI Provider returned error code: 0x800742a2]You receive this error message if you upgrade a named instance of SQL Server from SQL Server 2005 to SQL Server 2008, and then you change the service account of the SQL Server service.
To work around this problem, see Workaround 2.
Resolution
Workaround 1To work around this problem, add the domain user account to the corresponding domain group for the specific SQL Server component according to the following table.
Collapse this tableExpand this table
SQL Server componentCorresponding domain groupSQL Server Analysis Services (InstanceName)SQLServerMSASUser$ComputerName$InstanceNameSQL Server Integration ServicesSQLServerDTSUser$ComputerNameSQL Server BrowserSQLServer2005SQLBrowserUser$ComputerNameTo do this, follow these steps: Click Start, point to Administrative Tools, and then click Active Directory Users and Computers.In the Active Directory Users and Computers snap-in, click Users.Double-click the corresponding domain group.In the Properties dialog box, click the Members tab.On the Members tab, click Add.In the Select Users, Contacts, Computers, or Groups dialog box, type the user in the DomainName\UserName format under Enter the object names to select, and then click OK.In the Properties dialog box, click OK.
Workaround 2To work around this problem, add the domain user account to the SQLServer2005MSSQLUser$ComputerName$InstanceName domain group.
To do this, follow these steps: Click Start, point to Administrative Tools, and then click Active Directory Users and Computers.In the Active Directory Users and Computers snap-in, click Users.Double-click SQLServer2005MSSQLUser$ComputerName$InstanceName.In the Properties dialog box, click the Members tab.On the Members tab, click Add.In the Select Users, Contacts, Computers, or Groups dialog box, type the user in the DomainName\UserName format under Enter the object names to select, and then click OK.In the Properties dialog box, click OK.