Windows server 2008命名管道连接问题。 | 2008命名管道连接问题

本文介绍了Windows server 2008命名管道连接问题。的处理方法，对大家解决问题具有一定的参考价值，需要的朋友们下面随着小编来一起学习吧！问题描述 29岁程序员，3月因学历无情被辞！ Aaaaaaaaaaaaaaagh这一切的痛苦:( !! 我在VMware内部运行5个虚拟机。 1 Windows Server 2003 32 std R2 - AD和MSExchange 2 Windows server 2003 32 std sp2 - SQL Server 2005 3 Windows server 2003 32 std sp2 - MOSS WFE 4 Windows server 2003 32 std sp2 - MOSS SPSSearch Central Admin 以上四种配置为全部在sharepoint farm。它们已经存在了大约2年。服务器编号5是Windows 2008 x64服务器标准版我想要做的是将一些Sharepointservices迁移到Windows 2008 x64，即web前端。我已经安装了w2k8 x64作为一个新的虚拟机我已经将该机器连接到域并安装了所需的所有功能和角色，根据MS白皮书将32位迁移到64位网页前端 IIS 应用服务器 .Net 3.0 .Net 3.5 Sp1 +修补程序然后我去安装sharepoint，顺利安装SP1后没问题。然后我将Sharepoint安装连接到现有服务器场。我可以在安装向导中看到数据库（通过NetBIOS）我可以将SQL服务器的用户名和密码添加到安装向导中进入下一步。当我点击下一步完成第一阶段然后第二阶段（连接Sharepoint配置数据库）爆炸。错误日志名称：应用程序来源：Windows SharePoint Services 3 日期：19/03/2009 23:27:27 事件ID：5586 任务类别：数据库级别：错误关键词：经典用户：N / A 计算机：wsgdev2008x64.office.stirlinghealthcare.com 描述：发生了未知的SQL异常67。 SQL Server的其他错误信息包含在下面。建立与SQL Server的连接时发生网络相关或特定于实例的错误。服务器未找到或无法访问。验证实例名称是否正确，以及SQL Server是否配置为允许远程连接。（提供程序：命名管道提供程序，错误：40 - 无法打开与SQL Server的连接）事件Xml：<事件xmlns =" http://schemas.microsoft.com/win/2004/08/events/event "> < System> < ; Provider Name =" Windows SharePoint Services 3" /> < EventID Qualifiers =" 0"> 5586< / EventID> < Level> 2< / Level> <任务> 484< /任务> < ;关键字> 0x80000000000000< / Keywords> < TimeCreated SystemTime =" 2009-03-19T23：27：27.000Z" /> < EventRecordID> 1894< / EventRecordID> <频道>应用< /频道> <电脑> wsgdev2008x64.office.stirlinghealthcare.com< /电脑> <安全/> < / System> < EventData> <数据> 67< / Data> <数据>建立时发生与网络相关或特定于实例的错误与SQL Server的连接。服务器未找到或无法访问。验证实例名称是否正确，以及SQL Server是否配置为允许远程连接。（提供者：命名管道提供程序，错误：40 - 无法打开与SQL Server的连接）< / Data> < / EventData> < / Event> AndLog Name：Application 来源：SharePoint产品和技术配置向导日期：20/03/2009 09:39:50 事件ID：104 任务类别：无等级：错误关键词： Classic 用户：N / A 计算机：wsgdev2008x64.office.stirlinghealthcare.com 描述：无法连接到配置数据库。 System.Data.SqlClient类型的例外。抛出了SqlException。其他异常信息：与SQL Server建立连接时发生与网络相关或特定于实例的错误。服务器未找到或无法访问。验证实例名称是否正确，以及SQL Server是否配置为允许远程连接。（提供程序：命名管道提供程序，错误：40 - 无法打开与SQL Server的连接） System.Data.SqlClient.SqlException：建立与SQL Server的连接时发生与网络相关或特定于实例的错误。服务器未找到或无法访问。验证实例名称是否正确，以及SQL Server是否配置为允许远程连接。（提供者：命名管道提供程序，错误：40 - 无法打开到SQL Server的连接） System.Data.SqlClient的System.Data.SqlClient.SqlInternalConnection.OnError（SqlException异常，布尔breakConnection）。 System.Data.SqlClient.TdsParser.Connect（ServerInfo serverInfo，SqlInternalConnectionTds connHandler，Boolean ignoreSniOpenTimeout，Int64 timerExpire，Boolean encrypt，Boolean trustServerCert，Boolean integratedSecurity，SqlConnection owningObject）中的TdsParser.ThrowExceptionAndWarning（TdsParserStateObject stateObj） .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， System.Data.S中的SqlConnectionString connectionOptions，Int64 timerStart） System.Data.SqlClient.SqlInternalConnectionTds..ctor中的qlClient.SqlInternalConnectionTds.OpenLoginEnlist（SqlConnection owningObject，SqlConnectionString connectionOptions，String newPassword，Boolean redirectedUserInstance）（DbConnectionPoolIdentity标识，SqlConnectionString connectionOptions，Object providerInfo，String newPassword，SqlConnection owningObject，Boolean redirectedUserInstance ） System.Data.SqlClient.SqlConnectionFactory.CreateConnection（DbConnectionOptions选项，Object poolGroupProviderInfo，DbConnectionPool池，DbConnection owningConnection） System.Data.ProviderBase.DbConnectionFactory.CreatePooledConnection（DbConnection owningConnection，DbConnectionPool pool，DbConnectionOptions选项） System.Data.ProviderBase.DbConnectionPool.CreateObject（DbConnection owningObject） System.Data.ProviderBase.DbConnectionPool.UserCreateRequest（DbConnection owningObject） System.Data.ProviderBase.DbConnectionPool.Ge System.Data的System.Data.ProviderBase.DbConnectionClosed.OpenConnection（DbConnection outerConnection，DbConnectionFactory connectionFactory）上的System.Data.ProviderBase.DbConnectionFactory.GetConnection（DbConnection owningConnection）中的tConnection（DbConnection owningObject）。 SqlClient.SqlConnection.Open（） at Microsoft.SharePoint.Utilities.SqlSession.OpenConnection（） at Microsoft.SharePoint.Utilities.SqlSession.ExecuteNonQuery（SqlCommand command） at Microsoft.SharePoint.Upgrade.SPDatabaseSequence .GetVersion（Guid id，版本defaultVersion，SqlSession会话，SPDatabaseSequence序列） Microsoft.SharePoint.Administration.SPContentDatabase.ValidateDatabaseSchemaCompatibility（） at Microsoft.SharePoint.SPSite.PreinitializeServer（SPRequest request） at Microsoft .SharePoint.SPWeb.InitializeSPRequest（） at Microsoft.SharePoint.SPWeb.EnsureSPRequest（） at Microsoft.SharePoint.SPWeb.get_Request（）在Microsoft.SharePoint.SPListCollection.EnsureListsData（Guid webId，String strListName） at Microsoft.SharePoint.SPListCollection.EnsureListsData（String strListName） at Microsoft.SharePoint.SPListCollection.Undirty（） at Microsoft.SharePoint .SPBaseCollection.System.Collections.IEnumerable.GetEnumerator（） at Microsoft.SharePoint.Administration.SPAdministrationWebApplication.get_AdministrativeTasks（） at Microsoft.SharePoint.Administration.SPAdministrationWebApplication.EnsureSystemTask（String title，String description，Int32 priority， String actionTitle，String actionUrl，String service，String systemId） at Microsoft.SharePoint.Administration.SPWebApplication.Provision（） at Microsoft.SharePoint.Administration.SPWebServiceInstance.Provision（） at Microsoft.SharePoint。管理.SPFarm.Join（）在Microsoft.Share的Microsoft.SharePoint.PostSetupConfiguration.ConfigurationDatabaseTask.CreateOrConnectConfigDb（） Point.PostSetupConfiguration.ConfigurationDatabaseTask.Run（） at Microsoft.SharePoint.PostSetupConfiguration.TaskThread.ExecuteTask（）事件Xml：<事件xmlns =" http://schemas.microsoft.com/win/2004/08/events/event "> < System> < Provider Name =" SharePoint Products and Technologies Configuration Wizard" /> < EventID Qualifiers =" 0"> 104< / EventID> < Level> 2< / Level> < Task> 0< / Task> < ;关键字> 0x80000000000000< / Keywords> < TimeCreated SystemTime =" 2009-03-20T09：39：50.000Z" /> < EventRecordID> 2769< / EventRecordID> <频道>应用< /频道> <计算机> wsgdev2008x64.office.stirlinghealthcare.com< /计算机> <安全性/> < / System> < EventData> <数据>无法连接到配置数据库。抛出System.Data.SqlClient.SqlException类型的异常。其他异常信息：与SQL Server建立连接时发生与网络相关或特定于实例的错误。服务器未找到或无法访问。验证实例名称是否正确，以及SQL Server是否配置为允许远程连接。（提供程序：命名管道提供程序，错误：40 - 无法打开与SQL Server的连接） System.Data.SqlClient.SqlException：建立与SQL Server的连接时发生与网络相关或特定于实例的错误。服务器未找到或无法访问。验证实例名称是否正确，以及SQL Server是否配置为允许远程连接。（提供者：命名管道提供程序，错误：40 - 无法打开到SQL Server的连接） System.Data.SqlClient的System.Data.SqlClient.SqlInternalConnection.OnError（SqlException异常，布尔breakConnection）。 System.Data.SqlClient.TdsParser.Connect（ServerInfo serverInfo，SqlInternalConnectionTds connHandler，Boolean ignoreSniOpenTimeout，Int64 timerExpire，Boolean encrypt，Boolean trustServerCert，Boolean integratedSecurity，SqlConnection owningObject）中的TdsParser.ThrowExceptionAndWarning（TdsParserStateObject stateObj） .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， System.Data.S中的SqlConnectionString connectionOptions，Int64 timerStart） System.Data.SqlClient.SqlInternalConnectionTds..ctor中的qlClient.SqlInternalConnectionTds.OpenLoginEnlist（SqlConnection owningObject，SqlConnectionString connectionOptions，String newPassword，Boolean redirectedUserInstance）（DbConnectionPoolIdentity标识，SqlConnectionString connectionOptions，Object providerInfo，String newPassword，SqlConnection owningObject，Boolean redirectedUserInstance ） System.Data.SqlClient.SqlConnectionFactory.CreateConnection（DbConnectionOptions选项，Object poolGroupProviderInfo，DbConnectionPool池，DbConnection owningConnection） System.Data.ProviderBase.DbConnectionFactory.CreatePooledConnection（DbConnection owningConnection，DbConnectionPool pool，DbConnectionOptions选项） System.Data.ProviderBase.DbConnectionPool.CreateObject（DbConnection owningObject） System.Data.ProviderBase.DbConnectionPool.UserCreateRequest（DbConnection owningObject） System.Data.ProviderBase.DbConnectionPool.Ge System.Data的System.Data.ProviderBase.DbConnectionClosed.OpenConnection（DbConnection outerConnection，DbConnectionFactory connectionFactory）上的System.Data.ProviderBase.DbConnectionFactory.GetConnection（DbConnection owningConnection）中的tConnection（DbConnection owningObject）。 SqlClient.SqlConnection.Open（） at Microsoft.SharePoint.Utilities.SqlSession.OpenConnection（） at Microsoft.SharePoint.Utilities.SqlSession.ExecuteNonQuery（SqlCommand command） at Microsoft.SharePoint.Upgrade.SPDatabaseSequence .GetVersion（Guid id，版本defaultVersion，SqlSession会话，SPDatabaseSequence序列） Microsoft.SharePoint.Administration.SPContentDatabase.ValidateDatabaseSchemaCompatibility（） at Microsoft.SharePoint.SPSite.PreinitializeServer（SPRequest request） at Microsoft .SharePoint.SPWeb.InitializeSPRequest（） at Microsoft.SharePoint.SPWeb.EnsureSPRequest（） at Microsoft.SharePoint.SPWeb.get_Request（）在Microsoft.SharePoint.SPListCollection.EnsureListsData（Guid webId，String strListName） at Microsoft.SharePoint.SPListCollection.EnsureListsData（String strListName） at Microsoft.SharePoint.SPListCollection.Undirty（） at Microsoft.SharePoint .SPBaseCollection.System.Collections.IEnumerable.GetEnumerator（） at Microsoft.SharePoint.Administration.SPAdministrationWebApplication.get_AdministrativeTasks（） at Microsoft.SharePoint.Administration.SPAdministrationWebApplication.EnsureSystemTask（String title，String description，Int32 priority， String actionTitle，String actionUrl，String service，String systemId） at Microsoft.SharePoint.Administration.SPWebApplication.Provision（） at Microsoft.SharePoint.Administration.SPWebServiceInstance.Provision（） at Microsoft.SharePoint。管理.SPFarm.Join（）在Microsoft.Share的Microsoft.SharePoint.PostSetupConfiguration.ConfigurationDatabaseTask.CreateOrConnectConfigDb（） Point.PostSetupConfiguration.ConfigurationDatabaseTask.Run（） at Microsoft.SharePoint.PostSetupConfiguration.TaskThread.ExecuteTask（）< / Data> < / EventData> < / Event> 我从w2k8框中尝试过的事情： ping sqlserver：成功创建并测试到SQL Server的ODBC命名管道连接：测试成功关闭所有服务器上的防火墙重新连接服务器到域重新安装功能和角色重新安装Sharepoint 我不明白的事实是SQL已经配置为接受命名管道连接作为demostarted by创建的现有服务器场和ODBC连接。困扰我的一件事是当我重新安装sharepoint时，我得到了一些不同的错误，似乎表明Machine对象试图以DomainName的身份连接到sharepoint DB \\ _MachineName，这是正常的吗？我认为它尝试并使用我在sharepoint设置向导中输入的名称（同样用于t他在农场的其余部分。）我查看了SQL以检查其他domainname \machinename登录，这些只是搜索服务器的1个。经过几天的尝试和重试我已经筋疲力尽了。我可以得出的结论是，2K8盒子存在一些核心网络问题，或者某些GPO或防火墙正在阻止命名管道握手。如果有人有其他事情需要检查我的任何服务器请告诉我，因为我正在尝试推动w2k8作为我们的sharepoint环境的下一个平台，因此迄今为止尚未启动。 > 解决方案这个论坛专门讨论有关Windows Server 2008上的应用程序兼容性和认证的问题。如果您的问题不是关于这个主题，请在此处找到正确的新闻组： http://www.microsoft.com/communities/newsgroups/default.mspx 。有关'Certified for Windows Server 2008'和'适用于Windows的信息Server 2008'程序，要求，测试和工具请访问： http://www.innovateonwindowsserver.com/ 最新的Windows Server 2008公共评估下载 http://www.microsoft.com/windowsserver2008/audsel.mspx 一般有关Windows Server 2008的信息 http：/ /www.microsoft.com/windowsserver2008/default.mspx 适用于Windows的TechNet论坛Server 2008 有关Windows Server 2008的一般性讨论 http://forums.microsoft.com/TechNet/ShowForum.aspx?ForumID=570&SiteID=17 用于讨论Windows Server 2008中的特定功能 http://forums.microsoft.com/TechNet/default.aspx?ForumGroupID = 161& SiteID = 17 谢谢， Anand Kumar R Aaaaaaaaaaaaaaaargh the pain of it all :( !!I have 5 virtual machines running inside VMware. 1 Windows server 2003 32 std R2 - AD and MSExchange2 Windows server 2003 32 std sp2 - SQL Server 20053 Windows server 2003 32 std sp2 - MOSS WFE4 Windows server 2003 32 std sp2 - MOSS SPSSearch Central AdminThe four above are configured as all in sharepoint farm. They have been for around 2 years now.Server number 5 is Windows 2008 x64 Server Standard EditionWhat I am trying to do is migrate some Sharepointservices to Windows 2008 x64, namely web front end.I have installed w2k8 x64 as a new Virtual machineI have connectred that machine to the domain and installed all the features and roles required as per MS white paper on migrating 32bit to 64bit web front endsIISApplication Server.Net 3.0.Net 3.5 Sp1 + hotfixesI then go to install sharepoint, no problem after slipstreaming SP1.I then try connect Sharepoint installation to existing farm.I can see the Database in the setup wizard (via NetBIOS)I can add my username and password for the SQL server to the setup wizard and the progress to the next step.When I hit next the first stage completed then the second stage (Connecting Sharepoint configuration database) bombs out. ErrorLog Name: ApplicationSource: Windows SharePoint Services 3Date: 19/03/2009 23:27:27Event ID: 5586Task Category: DatabaseLevel: ErrorKeywords: ClassicUser: N/AComputer: wsgdev2008x64.office.stirlinghealthcare.comDescription:Unknown SQL Exception 67 occured. Additional error information from SQL Server is included below.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)Event Xml:<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Windows SharePoint Services 3" /> <EventID Qualifiers="0">5586</EventID> <Level>2</Level> <Task>484</Task> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2009-03-19T23:27:27.000Z" /> <EventRecordID>1894</EventRecordID> <Channel>Application</Channel> <Computer>wsgdev2008x64.office.stirlinghealthcare.com</Computer> <Security /> </System> <EventData> <Data>67</Data> <Data>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)</Data> </EventData></Event>AndLog Name: ApplicationSource: SharePoint Products and Technologies Configuration WizardDate: 20/03/2009 09:39:50Event ID: 104Task Category: NoneLevel: ErrorKeywords: ClassicUser: N/AComputer: wsgdev2008x64.office.stirlinghealthcare.comDescription:Failed to connect to the configuration database.An exception of type System.Data.SqlClient.SqlException was thrown. Additional exception information: 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)System.Data.SqlClient.SqlException: 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) 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.ExecuteNonQuery(SqlCommand command) at Microsoft.SharePoint.Upgrade.SPDatabaseSequence.GetVersion(Guid id, Version defaultVersion, SqlSession session, SPDatabaseSequence sequence) at Microsoft.SharePoint.Administration.SPContentDatabase.ValidateDatabaseSchemaCompatibility() at Microsoft.SharePoint.SPSite.PreinitializeServer(SPRequest request) at Microsoft.SharePoint.SPWeb.InitializeSPRequest() at Microsoft.SharePoint.SPWeb.EnsureSPRequest() at Microsoft.SharePoint.SPWeb.get_Request() at Microsoft.SharePoint.SPListCollection.EnsureListsData(Guid webId, String strListName) at Microsoft.SharePoint.SPListCollection.EnsureListsData(String strListName) at Microsoft.SharePoint.SPListCollection.Undirty() at Microsoft.SharePoint.SPBaseCollection.System.Collections.IEnumerable.GetEnumerator() at Microsoft.SharePoint.Administration.SPAdministrationWebApplication.get_AdministrativeTasks() at Microsoft.SharePoint.Administration.SPAdministrationWebApplication.EnsureSystemTask(String title, String description, Int32 priority, String actionTitle, String actionUrl, String service, String systemId) at Microsoft.SharePoint.Administration.SPWebApplication.Provision() at Microsoft.SharePoint.Administration.SPWebServiceInstance.Provision() at Microsoft.SharePoint.Administration.SPFarm.Join() at Microsoft.SharePoint.PostSetupConfiguration.ConfigurationDatabaseTask.CreateOrConnectConfigDb() at Microsoft.SharePoint.PostSetupConfiguration.ConfigurationDatabaseTask.Run() at Microsoft.SharePoint.PostSetupConfiguration.TaskThread.ExecuteTask()Event Xml:<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="SharePoint Products and Technologies Configuration Wizard" /> <EventID Qualifiers="0">104</EventID> <Level>2</Level> <Task>0</Task> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2009-03-20T09:39:50.000Z" /> <EventRecordID>2769</EventRecordID> <Channel>Application</Channel> <Computer>wsgdev2008x64.office.stirlinghealthcare.com</Computer> <Security /> </System> <EventData> <Data>Failed to connect to the configuration database.An exception of type System.Data.SqlClient.SqlException was thrown. Additional exception information: 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)System.Data.SqlClient.SqlException: 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) 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.ExecuteNonQuery(SqlCommand command) at Microsoft.SharePoint.Upgrade.SPDatabaseSequence.GetVersion(Guid id, Version defaultVersion, SqlSession session, SPDatabaseSequence sequence) at Microsoft.SharePoint.Administration.SPContentDatabase.ValidateDatabaseSchemaCompatibility() at Microsoft.SharePoint.SPSite.PreinitializeServer(SPRequest request) at Microsoft.SharePoint.SPWeb.InitializeSPRequest() at Microsoft.SharePoint.SPWeb.EnsureSPRequest() at Microsoft.SharePoint.SPWeb.get_Request() at Microsoft.SharePoint.SPListCollection.EnsureListsData(Guid webId, String strListName) at Microsoft.SharePoint.SPListCollection.EnsureListsData(String strListName) at Microsoft.SharePoint.SPListCollection.Undirty() at Microsoft.SharePoint.SPBaseCollection.System.Collections.IEnumerable.GetEnumerator() at Microsoft.SharePoint.Administration.SPAdministrationWebApplication.get_AdministrativeTasks() at Microsoft.SharePoint.Administration.SPAdministrationWebApplication.EnsureSystemTask(String title, String description, Int32 priority, String actionTitle, String actionUrl, String service, String systemId) at Microsoft.SharePoint.Administration.SPWebApplication.Provision() at Microsoft.SharePoint.Administration.SPWebServiceInstance.Provision() at Microsoft.SharePoint.Administration.SPFarm.Join() at Microsoft.SharePoint.PostSetupConfiguration.ConfigurationDatabaseTask.CreateOrConnectConfigDb() at Microsoft.SharePoint.PostSetupConfiguration.ConfigurationDatabaseTask.Run() at Microsoft.SharePoint.PostSetupConfiguration.TaskThread.ExecuteTask()</Data> </EventData></Event>Things I have tried from the w2k8 box:Ping the sqlserver : successfulCreate and test an ODBC Named Pipe Connection to the SQL Server : Test SuccessfulTurn off the firewall on all serversRe-connect server to DomainRe-Install features and rolesRe-Install SharepointWhat I dont understand is the fact that SQL is already configured to accept Named Pipe connection as demostarted by the existing farm and ODBC connection created.One thing that bothers me is when I re-intalled sharepoint I got some different error that seem to indicate that the Machine object was trying to connect to the sharepoint DB as DomainName\MachineName, is this normal?I thought it try and use the name I entered in the sharepoint setup wizard (the same used on the rest of the farm).I looked at the SQL to check for other domainname\machinename logins and these was only 1 the search server.After days of tryting and retrying I'm exhausted of ideas. The conclusion I can come to is that there is some core networking issue with the 2K8 box or some GPO or firewall is blocking Named pipe Hand shake.If anyone has other things to check on any of my servers please let me know as I am trying to push w2k8 as the next platform for our sharepoint environment, thus far a non starter. 解决方案 Hi , Thisforum is dedicated to questions about Application compatibility andCertification on Windows Server 2008. If your question is not aboutthis topic, please find the correct newsgroup here: http://www.microsoft.com/communities/newsgroups/default.mspx. For information on ‘Certified For Windows Server 2008’ and the ‘Works with Windows Server 2008' programs, requirements, tests and tools please visit: http://www.innovateonwindowsserver.com/ Latest public evaluation download of Windows Server 2008http://www.microsoft.com/windowsserver2008/audsel.mspx General information on Windows Server 2008http://www.microsoft.com/windowsserver2008/default.mspx TechNet forums for Windows Server 2008For general discussions on Windows Server 2008http://forums.microsoft.com/TechNet/ShowForum.aspx?ForumID=570&SiteID=17 For discussing specific features in Windows Server 2008http://forums.microsoft.com/TechNet/default.aspx?ForumGroupID=161&SiteID=17 Thanks,Anand Kumar R 这篇关于Windows server 2008命名管道连接问题。的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！上岸，阿里云！