View Complete Post
We are trying to add a named instance to our Windows 2003 R2 x64 SP1/SQL Server 2005 SP3 server. It has been running for about 3 years now with a single (default) instance. When trying to add a named instance, it fails when it gets to the point
where it is Updating System Databases - "SQL Server Setup could not connect to the database service for server configuration. The error was:[Microsoft][SQL Native Client]SQL Network Interfaces: Error Locating Server/Instance Specified [xFFFFFFFF]. Refer
to server error logs..." We are using the local service account for both the default and new named instance. Allow Remote Connections to This Server is enabled on the default instance.
In Services, the new SQL Server service has started, but I cannot start the SQL Server Agent - it says it started and then stopped. I cannot access the instance with SMS. I rebooted the server and tried the process again with identical results.
I have successfully added a new instance to my test SQL Server using the same install files. Can anyone shed some light in this issue? Thanks.
I've installed a SQL 2008 R2 failover cluster on Windows 2008. Default instance installed and failover nodes are running just fine. However, when I try to install a second SQL instance (named MSSQLSERVER1) using different cluster drives than
the first instance I get this error.
The new sql cluster computer account is in AD already. I'm using the same sql service account for both instances (however, I got the same error using a differnt account as well). I left the default Use service SIDs (recommended) checked.
On the Properties page for the Server in the SQL Server cluster resource in Failover Cluster Management on the General tab I see Kerberos Status: Access is denied.
I would appreciate any help on this.
Hello everyone! Newbie here. I would like to ask how to start the SharePoint Services Web Application on
(WSS3.0,internal database, stanalone users) without getting error
I would love to provide more information regarding this issue but what I got is error 1387 displayed in the browser.
I look forward to seeing you guys feedback from your expertise angle.