Logo 
Search:

Sharepoint Forum

Ask Question   UnAnswered
Home » Forum » Sharepoint       RSS Feeds

SQL Remote connection error when creating new site

  Asked By: Scot    Date: Mar 11    Category: Sharepoint    Views: 1489

Anyone seen this before? Our environment has been working fine for some time
now and all of a sudden I'm getting SQL exception errors indicating an issue
regarding remote connection configuration. This only seems to occur when trying
to create a new top-level site. Events with an ID of 5586 are also being stored
in the app log when the error appears.
Here's a capture of the log message:

Unknown SQL Exception -1 occured. Additional error information from SQL Server
is included below.
An error has occurred while establishing a connection to the server. When
connecting to SQL Server 2005, this failure may be caused by the fact that under
the default settings SQL Server does not allow remote connections. (provider:
SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified)
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

I've confirmed that the server is accepting remote connections on both named
pipes as well as TCP/IP. We've rebooted the SQL boxes as well as the front ends
and nothing seems to help. A blog entry indicates that they went ahead and ran
the STSADM -o updatefarmcredential operation but I wanted to check here first.

Share: 

 

7 Answers Found

 
Answer #1    Answered By: Damon Garner     Answered On: Mar 11

Have you seen this blog?

blogs.msdn.com/.../database-disconnect-issu
es-with-sharepoint.aspx

 
Answer #2    Answered By: Matt Prince     Answered On: Mar 11

But it doesn't seem relevant. The error  we are
experiencing only seems to occur when we are trying to create  a top-level  site
and it is consistent in its behavior. It's really bizarre because everything
else seems to be running fine. Could it be an issue with the job itself,
perhaps?

 
Answer #3    Answered By: Brooks Bond     Answered On: Mar 11

Is the database online in SQL (not SharePoint)? Does the Central Admin
application pool identity and the hosting Web app application pool
identity have access to the content db where the site  collection is
being created?

 
Answer #4    Answered By: Gregg Wilkinson     Answered On: Mar 11

Yes, the DB is online and seems to be running fine. Both application pools are
running using an account that has dbowner priviledges on the content DB.

 
Answer #5    Answered By: Darrel Sexton     Answered On: Mar 11

I would try setting the trace log settings to 'Verbose' for 'Database'
and 'Site Management' and take a look.

 
Answer #6    Answered By: Tory Sellers     Answered On: Mar 11

I did that this weekend while troubleshooting. The log entry seems to match the
error I get on the CA page. I rechecked the remote  connections settings on the
SQL box but they look fine. Here's what I'm seeing:

An error  has occurred while establishing a connection  to the server. When
connecting to SQL Server 2005, this failure may be caused by the fact that under
the default settings SQL Server does not allow remote connections. (provider:
SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified)
at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception,
Boolean breakConnection)
at
System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject
stateObj)
at System.Data.SqlClient.TdsParser.Connect(ServerInfo serverInfo,
SqlInternalConnectionTds connHandler, Boolean ignoreSniOpenTimeout, Int64
timerExpire, Boolean encrypt, Boolean trustServerCert, Boolean
integratedSecurity, SqlConnection owningObject)
at System.Data.SqlClient.SqlInternalConnectionTds.AttemptOneLogin(ServerInfo
serverInfo, String newPassword, Boolean ignoreSniOpenTimeout, Int64 timerExpire,
SqlConnection owningObject)
at System.Data.SqlClient.SqlInternalConnectionTds.LoginNoFailover(String
host, String newPassword, Boolean redirectedUserInstance, SqlConnection
owningObject, SqlConnectionString connectionOptions, Int64 timerStart)
at
System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(SqlConnection
owningObject, SqlConnectionString connectionOptions, String newPassword, Boolean
redirectedUserInstance)
at
System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity
identity, SqlConnectionString connectionOptions, Object providerInfo, String
newPassword, SqlConnection owningObject, Boolean redirectedUserInstance)
at
System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions
options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection
owningConnection)
at
System.Data.ProviderBase.DbConnectionFactory.CreatePooledConnection(DbConnection
owningConnection, DbConnectionPool pool, DbConnectionOptions options)
at System.Data.ProviderBase.DbConnectionPool.CreateObject(DbConnection
owningObject)
at System.Data.ProviderBase.DbConnectionPool.UserCreateRequest(DbConnection
owningObject)
at System.Data.ProviderBase.DbConnectionPool.GetConnection(DbConnection
owningObject)
at System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection
owningConnection)
at System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection
outerConnection, DbConnectionFactory connectionFactory)
at System.Data.SqlClient.SqlConnection.Open()
at Microsoft.SharePoint.Utilities.SqlSession.OpenConnection()
at Microsoft.SharePoint.Utilities.SqlSession.ExecuteReader(SqlCommand
command, CommandBehavior behavior)
at Microsoft.SharePoint.Utilities.SqlSession.ExecuteReader(SqlCommand
command)
at
Microsoft.SharePoint.Administration.SPConfigurationDatabase.CheckForDuplicateSit\
eNameInPairedWebApplication(SPWebApplication application, String path, Boolean
useHostHeaderAsSiteName)
at
Microsoft.SharePoint.Administration.SPConfigurationDatabase.CreateSite(SPWebAppl\
ication application, SPContentDatabase database, String originalPath, Guid id,
Pairing pairing, Uri redirectUri, Boolean useHostHeaderAsSiteName, Boolean
bypassExistingSiteCheck)
at
Microsoft.SharePoint.Administration.SPConfigurationDatabase.CreateSite(SPWebAppl\
ication application, SPContentDatabase database, String path, Boolean
useHostHeaderAsSiteName)
at Microsoft.SharePoint.Administration.SPSiteCollection.Add(SPContentDatabase
database, String siteUrl, String title, String description, UInt32 nLCID, String
webTemplate, String ownerLogin, String ownerName, String ownerEmail, String
secondaryContactLogin, String secondaryContactName, String
secondaryContactEmail, String quotaTemplate, String sscRootWebUrl, Boolean
useHostHeaderAsSiteName)
at Microsoft.SharePoint.Administration.SPSiteCollection.Add(String siteUrl,
String title, String description, UInt32 nLCID, String webTemplate, String
ownerLogin, String ownerName, String ownerEmail, String secondaryContactLogin,
String secondaryContactName, String secondaryContactEmail, Boolean
useHostHeaderAsSiteName)
at Microsoft.SharePoint.Administration.SPSiteCollection.Add(String siteUrl,
String title, String description, UInt32 nLCID, String webTemplate, String
ownerLogin, String ownerName, String ownerEmail, String secondaryContactLogin,
String secondaryContactName, String secondaryContactEmail)
at
Microsoft.SharePoint.ApplicationPages.CreateSitePage.BtnCreateSite_Click(Object
sender, EventArgs e)
at System.Web.UI.WebControls.Button.OnClick(EventArgs e)
at System.Web.UI.WebControls.Button.RaisePostBackEvent(String eventArgument)
at
System.Web.UI.WebControls.Button.System.Web.UI.IPostBackEventHandler.RaisePostBa\
ckEvent(String eventArgument)
at System.Web.UI.Page.RaisePostBackEvent(IPostBackEventHandler sourceControl,
String eventArgument)
at System.Web.UI.Page.RaisePostBackEvent(NameValueCollection postData)
at System.Web.UI.Page.ProcessRequestMain(Boolean
includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)

 
Answer #7    Answered By: Agustin Miranda     Answered On: Mar 11

It definitely looks SQL related. I got this same error  once, but I had
lost all database connectivity (host firewall got turned on and blocked
TCp1433).

Please let us know how you fix it. I think you have this correct, but be
sure central admin app pool has db creator and security administrator in
SQL Server Mgmt Studio.

 
Didn't find what you were looking for? Find more on SQL Remote connection error when creating new site Or get search suggestion and latest updates.




Tagged: