Can't seem to make a connection to a database (expert help needed)

[Mike in Nebraska]

This issue is SharePoint-based, but mostly involves SQL Server, so I am
posting here as well as here:
http://social.msdn.microsoft.com/Forums/en-US/sharepointadmin/thread/3749640a-4628-4f1a-b474-38b5fbd15973
in hopes of getting some help.

BACKGROUND: Single server deployment of SharePoint Server 2007 Enterprise
on a Windows Server 2003 R2 Standard box, and SQL Server 2008 Standard
(upgraded from SQL Server 2005). SharePoint creates a number of databases
during setup - "it just works" - so that SQL newbies like me don't have to
be DBA's. There is a central portal for SharePoint administration with two
main areas - Operations and Applications. I am unable to access them. I
get this error:
<snip> 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:
SQL Network Interfaces, error: 26 - Error Locating Server/Instance
Specified) </snip>
I haven't been in the central admin portal for many weeks - haven't needed
to - but was going to try something a couple days ago and that's when I
discovered the problem.

A few weeks ago I was looking through SSMS and decided to "tweak" each
database by going to Properties > Options and setting each as being
compatible to SQL Server 2008 instead of SQL Server 2005. I also set each
DB's Recovery mode to "Simple".

No real errors in the Application log. Saw these in a a SharePoint log:
<snip> 10/29/2009 10:29:47.17 Bamboo.SPAnalyzer.exe (0x2520)
0x252C Windows SharePoint Services Database
5big Critical Database 'WSS_Content_baf76d9d14ca41f4b25a45ec4fb27468'
on SQL Server instance 'wct-sharepoint\wctintranet' is not empty and does
not match current database schema.
10/29/2009 10:29:48.39 Bamboo.SPAnalyzer.exe (0x2520)
0x252C Windows SharePoint Services Database
5big Critical Database 'WSS_Content' on SQL Server instance
'wct-sharepoint\wctintranet' is not empty and does not match current
database schema.
10/29/2009 10:29:49.39 Bamboo.SPAnalyzer.exe (0x2520)
0x252C Windows SharePoint Services Database
5big Critical Database
'SharePoint_AdminContent_be8e47d7-571b-4c36-b199-72593e990c9f' on SQL Server
instance 'wct-sharepoint\wctintranet' is not empty and does not match
current database schema.
10/29/2009 10:29:49.95 Bamboo.SPAnalyzer.exe (0x2520)
0x252C Windows SharePoint Services Database
5big Critical Database 'WSS_Content_baf76d9d14ca41f4b25a45ec4fb27468'
on SQL Server instance 'wct-sharepoint\wctintranet' is not empty and does
not match current database schema.
10/29/2009 10:29:50.17 Bamboo.SPAnalyzer.exe (0x2520)
0x252C Windows SharePoint Services Database
5big Critical Database 'WSS_Content' on SQL Server instance
'wct-sharepoint\wctintranet' is not empty and does not match current
database schema.
10/29/2009 10:29:50.41 Bamboo.SPAnalyzer.exe (0x2520)
0x252C Windows SharePoint Services Database
5big Critical Database
'SharePoint_AdminContent_be8e47d7-571b-4c36-b199-72593e990c9f' on SQL Server
instance 'wct-sharepoint\wctintranet' is not empty and does not match
current database schema.
10/29/2009 10:29:59.02 Bamboo.SPAnalyzer.exe (0x2520)
0x252C Windows SharePoint Services Database
5big Critical Database
'SharePoint_AdminContent_be8e47d7-571b-4c36-b199-72593e990c9f' on SQL Server
instance 'wct-sharepoint\wctintranet' is not empty and does not match
current database schema.
10/29/2009 10:29:58.56 Bamboo.SPAnalyzer.exe (0x2520)
0x252C Windows SharePoint Services Database
5big Critical Database 'WSS_Content_baf76d9d14ca41f4b25a45ec4fb27468'
on SQL Server instance 'wct-sharepoint\wctintranet' is not empty and does
not match current database schema.
10/29/2009 10:29:58.80 Bamboo.SPAnalyzer.exe (0x2520)
0x252C Windows SharePoint Services Database
5big Critical Database 'WSS_Content' on SQL Server instance
'wct-sharepoint\wctintranet' is not empty and does not match current
database schema.
10/29/2009 10:29:59.61 Bamboo.SPAnalyzer.exe (0x2520)
0x252C Windows SharePoint Services Database
5big Critical Database 'WSS_Content' on SQL Server instance
'wct-sharepoint\wctintranet' is not empty and does not match current
database schema.
10/29/2009 10:29:59.36 Bamboo.SPAnalyzer.exe (0x2520)
0x252C Windows SharePoint Services Database
5big Critical Database 'WSS_Content_baf76d9d14ca41f4b25a45ec4fb27468'
on SQL Server instance 'wct-sharepoint\wctintranet' is not empty and does
not match current database schema.
10/29/2009 10:29:59.84 Bamboo.SPAnalyzer.exe (0x2520)
0x252C Windows SharePoint Services Database
5big Critical Database
'SharePoint_AdminContent_be8e47d7-571b-4c36-b199-72593e990c9f' on SQL Server
instance 'wct-sharepoint\wctintranet' is not empty and does not match
current database schema. </snip>

I've rebooted a few times to no avail. Saw this in the SharePoint log a
couple hours after the above:
<snip> Timestamp Process
TID Area Category
EventID Level Message Correlation
10/29/2009 12:11:46.62 OWSTIMER.EXE (0x0A38)
0x0AD8 Windows SharePoint Services Database
5586 Critical Unknown SQL Exception 64 occured. Additional error
information from SQL Server is included below. A connection was
successfully established with the server, but then an error occurred during
the login process. (provider: TCP Provider, error: 0 - The specified network
name is no longer available.)
10/29/2009 12:11:47.56 OWSTIMER.EXE (0x0A38)
0x0AD8 Windows SharePoint Services Topology
88bl Monitorable An exception occured while trying to acquire the
local farm: System.Data.SqlClient.SqlException: A connection was
successfully established with the server, but then an error occurred during
the login process. (provider: TCP Provider, error: 0 - The specified network
name is no longer available.) at
System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception,
Boolean breakConnection) at
System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject
stateObj) at
System.Data.SqlClient.TdsParserStateObject.ReadSniError(TdsParserStateObject
stateObj, UInt32 error) at
System.Data.SqlClient.TdsParserStateObject.ReadSni(DbAsyncResult
asyncResult, TdsParserStateObject stateObj) at
System.Data.SqlClient.TdsParserStateObject.ReadNetworkPacket() at...
</snip>

I can get to the Properties section of every database. I ran a Profile
Trace and the only errors I see are:
<snip>
User Error Message Changed database context to 'SharedServices2_DB'.
Windows SharePoint Services SQL2005 WHOOPER\SQL2005
2640 59 2009-10-30 10:04:14.403 5701 18
SharedServices2_DB 100962 WCT-SHAREPOINT
0X010500000000000515000000166D93C56EE082F0BFD5F86152050000 WHOOPER 0
WCT-SHAREPOINT\WCTINTRANET WHOOPER\SQL2005 10
2 0 1

and

User Error Message Changed language setting to us_english. Windows
SharePoint Services SQL2005 WHOOPER\SQL2005 2640
59 2009-10-30 10:04:14.403 5703 18 SharedServices2_DB
100963 WCT-SHAREPOINT
0X010500000000000515000000166D93C56EE082F0BFD5F86152050000 WHOOPER 0
WCT-SHAREPOINT\WCTINTRANET WHOOPER\SQL2005 10
1 0 1 </snip>

Lastly, I verified that remote connections are allowed.

Any ideas?

[Rick Byham, MSFT]

Check the SQL Server error log. You may see a clue there from something that
didn't get written to the Windows Application log.
Did you rename this computer? Connecting with SSMS, execute SELECT
@@SERVERNAME and see if the name of the SQL Server matches the computer name
+ instance name.
--
Rick Byham, MSFT
(Implies no warranty or rights)

Post by Mike in Nebraska
This issue is SharePoint-based, but mostly involves SQL Server, so I am
http://social.msdn.microsoft.com/Forums/en-US/sharepointadmin/thread/3749640a-4628-4f1a-b474-38b5fbd15973
in hopes of getting some help.
BACKGROUND: Single server deployment of SharePoint Server 2007 Enterprise
on a Windows Server 2003 R2 Standard box, and SQL Server 2008 Standard
(upgraded from SQL Server 2005). SharePoint creates a number of databases
during setup - "it just works" - so that SQL newbies like me don't have to
be DBA's. There is a central portal for SharePoint administration with
two main areas - Operations and Applications. I am unable to access them.
<snip> 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
SQL Network Interfaces, error: 26 - Error Locating Server/Instance
Specified) </snip>
I haven't been in the central admin portal for many weeks - haven't needed
to - but was going to try something a couple days ago and that's when I
discovered the problem.
A few weeks ago I was looking through SSMS and decided to "tweak" each
database by going to Properties > Options and setting each as being
compatible to SQL Server 2008 instead of SQL Server 2005. I also set each
DB's Recovery mode to "Simple".
<snip> 10/29/2009 10:29:47.17 Bamboo.SPAnalyzer.exe (0x2520) 0x252C
Windows SharePoint Services Database 5big Critical Database
'WSS_Content_baf76d9d14ca41f4b25a45ec4fb27468' on SQL Server instance
'wct-sharepoint\wctintranet' is not empty and does not match current
database schema.
10/29/2009 10:29:48.39 Bamboo.SPAnalyzer.exe (0x2520) 0x252C
Windows SharePoint Services Database 5big Critical Database
'WSS_Content' on SQL Server instance 'wct-sharepoint\wctintranet' is not
empty and does not match current database schema.
10/29/2009 10:29:49.39 Bamboo.SPAnalyzer.exe (0x2520) 0x252C
Windows SharePoint Services Database 5big Critical Database
'SharePoint_AdminContent_be8e47d7-571b-4c36-b199-72593e990c9f' on SQL
Server instance 'wct-sharepoint\wctintranet' is not empty and does not
match current database schema.
10/29/2009 10:29:49.95 Bamboo.SPAnalyzer.exe (0x2520) 0x252C
Windows SharePoint Services Database 5big Critical Database
'WSS_Content_baf76d9d14ca41f4b25a45ec4fb27468' on SQL Server instance
'wct-sharepoint\wctintranet' is not empty and does not match current
database schema.
10/29/2009 10:29:50.17 Bamboo.SPAnalyzer.exe (0x2520) 0x252C
Windows SharePoint Services Database 5big Critical Database
'WSS_Content' on SQL Server instance 'wct-sharepoint\wctintranet' is not
empty and does not match current database schema.
10/29/2009 10:29:50.41 Bamboo.SPAnalyzer.exe (0x2520) 0x252C
Windows SharePoint Services Database 5big Critical Database
'SharePoint_AdminContent_be8e47d7-571b-4c36-b199-72593e990c9f' on SQL
Server instance 'wct-sharepoint\wctintranet' is not empty and does not
match current database schema.
10/29/2009 10:29:59.02 Bamboo.SPAnalyzer.exe (0x2520) 0x252C
Windows SharePoint Services Database 5big Critical Database
'SharePoint_AdminContent_be8e47d7-571b-4c36-b199-72593e990c9f' on SQL
Server instance 'wct-sharepoint\wctintranet' is not empty and does not
match current database schema.
10/29/2009 10:29:58.56 Bamboo.SPAnalyzer.exe (0x2520) 0x252C
Windows SharePoint Services Database 5big Critical Database
'WSS_Content_baf76d9d14ca41f4b25a45ec4fb27468' on SQL Server instance
'wct-sharepoint\wctintranet' is not empty and does not match current
database schema.
10/29/2009 10:29:58.80 Bamboo.SPAnalyzer.exe (0x2520) 0x252C
Windows SharePoint Services Database 5big Critical Database
'WSS_Content' on SQL Server instance 'wct-sharepoint\wctintranet' is not
empty and does not match current database schema.
10/29/2009 10:29:59.61 Bamboo.SPAnalyzer.exe (0x2520) 0x252C
Windows SharePoint Services Database 5big Critical Database
'WSS_Content' on SQL Server instance 'wct-sharepoint\wctintranet' is not
empty and does not match current database schema.
10/29/2009 10:29:59.36 Bamboo.SPAnalyzer.exe (0x2520) 0x252C
Windows SharePoint Services Database 5big Critical Database
'WSS_Content_baf76d9d14ca41f4b25a45ec4fb27468' on SQL Server instance
'wct-sharepoint\wctintranet' is not empty and does not match current
database schema.
10/29/2009 10:29:59.84 Bamboo.SPAnalyzer.exe (0x2520) 0x252C
Windows SharePoint Services Database 5big Critical Database
'SharePoint_AdminContent_be8e47d7-571b-4c36-b199-72593e990c9f' on SQL
Server instance 'wct-sharepoint\wctintranet' is not empty and does not
match current database schema. </snip>
I've rebooted a few times to no avail. Saw this in the SharePoint log a
<snip> Timestamp Process TID Area
Category EventID Level Message Correlation
10/29/2009 12:11:46.62 OWSTIMER.EXE (0x0A38) 0x0AD8 Windows
SharePoint Services Database 5586 Critical Unknown SQL
Exception 64 occured. Additional error information from SQL Server is
included below. A connection was successfully established with the
TCP Provider, error: 0 - The specified network name is no longer
available.)
10/29/2009 12:11:47.56 OWSTIMER.EXE (0x0A38) 0x0AD8 Windows
SharePoint Services Topology 88bl Monitorable An exception
System.Data.SqlClient.SqlException: A connection was successfully
established with the server, but then an error occurred during the login
process. (provider: TCP Provider, error: 0 - The specified network name is
no longer available.) at
System.Data.SqlClient.SqlInternalConnection.OnError(SqlException
exception, Boolean breakConnection) at
System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject
stateObj) at
System.Data.SqlClient.TdsParserStateObject.ReadSniError(TdsParserStateObject
stateObj, UInt32 error) at
System.Data.SqlClient.TdsParserStateObject.ReadSni(DbAsyncResult
asyncResult, TdsParserStateObject stateObj) at
System.Data.SqlClient.TdsParserStateObject.ReadNetworkPacket() at...
</snip>
I can get to the Properties section of every database. I ran a Profile
<snip>
User Error Message Changed database context to 'SharedServices2_DB'.
Windows SharePoint Services SQL2005 WHOOPER\SQL2005 2640 59
2009-10-30 10:04:14.403 5701 18 SharedServices2_DB 100962
WCT-SHAREPOINT 0X010500000000000515000000166D93C56EE082F0BFD5F86152050000
WHOOPER 0 WCT-SHAREPOINT\WCTINTRANET WHOOPER\SQL2005
10 2 0 1
and
User Error Message Changed language setting to us_english. Windows
SharePoint Services SQL2005 WHOOPER\SQL2005 2640
59 2009-10-30 10:04:14.403 5703 18 SharedServices2_DB
100963 WCT-SHAREPOINT
0X010500000000000515000000166D93C56EE082F0BFD5F86152050000 WHOOPER 0
WCT-SHAREPOINT\WCTINTRANET WHOOPER\SQL2005
10 1 0 1 </snip>
Lastly, I verified that remote connections are allowed.
Any ideas?
--
Mike Webb
Platte River Whooping Crane Maintenance Trust, Inc.
a conservation non-profit (501 (c)(3)) organization
Wood River, NE

[Mike in Nebraska]

Nothing in the Application log.

Ran a Profile Trace, but it came up empty.

Ran the query, and the name\instance verifies.

Mike

Post by Rick Byham, MSFT
Check the SQL Server error log. You may see a clue there from something
that didn't get written to the Windows Application log.
Did you rename this computer? Connecting with SSMS, execute SELECT
@@SERVERNAME and see if the name of the SQL Server matches the computer
name + instance name.
--
Rick Byham, MSFT
(Implies no warranty or rights)

Post by Mike in Nebraska
This issue is SharePoint-based, but mostly involves SQL Server, so I am
http://social.msdn.microsoft.com/Forums/en-US/sharepointadmin/thread/3749640a-4628-4f1a-b474-38b5fbd15973
in hopes of getting some help.
BACKGROUND: Single server deployment of SharePoint Server 2007
Enterprise on a Windows Server 2003 R2 Standard box, and SQL Server 2008
Standard (upgraded from SQL Server 2005). SharePoint creates a number of
databases during setup - "it just works" - so that SQL newbies like me
don't have to be DBA's. There is a central portal for SharePoint
administration with two main areas - Operations and Applications. I am
<snip> 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
SQL Network Interfaces, error: 26 - Error Locating Server/Instance
Specified) </snip>
I haven't been in the central admin portal for many weeks - haven't
needed to - but was going to try something a couple days ago and that's
when I discovered the problem.
A few weeks ago I was looking through SSMS and decided to "tweak" each
database by going to Properties > Options and setting each as being
compatible to SQL Server 2008 instead of SQL Server 2005. I also set
each DB's Recovery mode to "Simple".
<snip> 10/29/2009 10:29:47.17 Bamboo.SPAnalyzer.exe (0x2520) 0x252C
Windows SharePoint Services Database 5big Critical Database
'WSS_Content_baf76d9d14ca41f4b25a45ec4fb27468' on SQL Server instance
'wct-sharepoint\wctintranet' is not empty and does not match current
database schema.
10/29/2009 10:29:48.39 Bamboo.SPAnalyzer.exe (0x2520) 0x252C Windows
SharePoint Services Database 5big Critical Database
'WSS_Content' on SQL Server instance 'wct-sharepoint\wctintranet' is not
empty and does not match current database schema.
10/29/2009 10:29:49.39 Bamboo.SPAnalyzer.exe (0x2520) 0x252C Windows
SharePoint Services Database 5big Critical Database
'SharePoint_AdminContent_be8e47d7-571b-4c36-b199-72593e990c9f' on SQL
Server instance 'wct-sharepoint\wctintranet' is not empty and does not
match current database schema.
10/29/2009 10:29:49.95 Bamboo.SPAnalyzer.exe (0x2520) 0x252C Windows
SharePoint Services Database 5big Critical Database
'WSS_Content_baf76d9d14ca41f4b25a45ec4fb27468' on SQL Server instance
'wct-sharepoint\wctintranet' is not empty and does not match current
database schema.
10/29/2009 10:29:50.17 Bamboo.SPAnalyzer.exe (0x2520) 0x252C Windows
SharePoint Services Database 5big Critical Database
'WSS_Content' on SQL Server instance 'wct-sharepoint\wctintranet' is not
empty and does not match current database schema.
10/29/2009 10:29:50.41 Bamboo.SPAnalyzer.exe (0x2520) 0x252C Windows
SharePoint Services Database 5big Critical Database
'SharePoint_AdminContent_be8e47d7-571b-4c36-b199-72593e990c9f' on SQL
Server instance 'wct-sharepoint\wctintranet' is not empty and does not
match current database schema.
10/29/2009 10:29:59.02 Bamboo.SPAnalyzer.exe (0x2520) 0x252C Windows
SharePoint Services Database 5big Critical Database
'SharePoint_AdminContent_be8e47d7-571b-4c36-b199-72593e990c9f' on SQL
Server instance 'wct-sharepoint\wctintranet' is not empty and does not
match current database schema.
10/29/2009 10:29:58.56 Bamboo.SPAnalyzer.exe (0x2520) 0x252C Windows
SharePoint Services Database 5big Critical Database
'WSS_Content_baf76d9d14ca41f4b25a45ec4fb27468' on SQL Server instance
'wct-sharepoint\wctintranet' is not empty and does not match current
database schema.
10/29/2009 10:29:58.80 Bamboo.SPAnalyzer.exe (0x2520) 0x252C Windows
SharePoint Services Database 5big Critical Database
'WSS_Content' on SQL Server instance 'wct-sharepoint\wctintranet' is not
empty and does not match current database schema.
10/29/2009 10:29:59.61 Bamboo.SPAnalyzer.exe (0x2520) 0x252C Windows
SharePoint Services Database 5big Critical Database
'WSS_Content' on SQL Server instance 'wct-sharepoint\wctintranet' is not
empty and does not match current database schema.
10/29/2009 10:29:59.36 Bamboo.SPAnalyzer.exe (0x2520) 0x252C Windows
SharePoint Services Database 5big Critical Database
'WSS_Content_baf76d9d14ca41f4b25a45ec4fb27468' on SQL Server instance
'wct-sharepoint\wctintranet' is not empty and does not match current
database schema.
10/29/2009 10:29:59.84 Bamboo.SPAnalyzer.exe (0x2520) 0x252C Windows
SharePoint Services Database 5big Critical Database
'SharePoint_AdminContent_be8e47d7-571b-4c36-b199-72593e990c9f' on SQL
Server instance 'wct-sharepoint\wctintranet' is not empty and does not
match current database schema. </snip>
I've rebooted a few times to no avail. Saw this in the SharePoint log a
<snip> Timestamp Process TID Area Category EventID
Level Message Correlation
10/29/2009 12:11:46.62 OWSTIMER.EXE (0x0A38) 0x0AD8 Windows
SharePoint Services Database 5586 Critical Unknown SQL
Exception 64 occured. Additional error information from SQL Server is
included below. A connection was successfully established with the
TCP Provider, error: 0 - The specified network name is no longer
available.)
10/29/2009 12:11:47.56 OWSTIMER.EXE (0x0A38) 0x0AD8 Windows
SharePoint Services Topology 88bl Monitorable An exception
System.Data.SqlClient.SqlException: A connection was successfully
established with the server, but then an error occurred during the login
process. (provider: TCP Provider, error: 0 - The specified network name
is no longer available.) at
System.Data.SqlClient.SqlInternalConnection.OnError(SqlException
exception, Boolean breakConnection) at
System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject
stateObj) at
System.Data.SqlClient.TdsParserStateObject.ReadSniError(TdsParserStateObject
stateObj, UInt32 error) at
System.Data.SqlClient.TdsParserStateObject.ReadSni(DbAsyncResult
asyncResult, TdsParserStateObject stateObj) at
System.Data.SqlClient.TdsParserStateObject.ReadNetworkPacket() at...
</snip>
I can get to the Properties section of every database. I ran a Profile
<snip>
User Error Message Changed database context to 'SharedServices2_DB'.
Windows SharePoint Services SQL2005 WHOOPER\SQL2005 2640 59
2009-10-30 10:04:14.403 5701 18 SharedServices2_DB
100962 WCT-SHAREPOINT
0X010500000000000515000000166D93C56EE082F0BFD5F86152050000 WHOOPER 0
WCT-SHAREPOINT\WCTINTRANET WHOOPER\SQL2005 10 2 0 1
and
User Error Message Changed language setting to us_english. Windows
SharePoint Services SQL2005 WHOOPER\SQL2005 2640
59 2009-10-30 10:04:14.403 5703 18 SharedServices2_DB
100963 WCT-SHAREPOINT
0X010500000000000515000000166D93C56EE082F0BFD5F86152050000 WHOOPER
0 WCT-SHAREPOINT\WCTINTRANET WHOOPER\SQL2005 10 1 0 1
</snip>
Lastly, I verified that remote connections are allowed.
Any ideas?
--
Mike Webb
Platte River Whooping Crane Maintenance Trust, Inc.
a conservation non-profit (501 (c)(3)) organization
Wood River, NE