Skip to main content
Search Again

We think these articles could help you:

    See More
    Nintex Knowledge Base

    A network-related or instance-specific error occurred while establishing a connection to SQL Server

    Summary
    Error: 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)

    Solution
    The error indicates an issue with your infrastructure allowing the necessary SQL connection between SharePoint and your SQL server. The message is a generic SQL error message that should be investigated by your Infrastructure/DBA team. There are several settings and services you should double check:
    1. Make sure your database engine is configured to accept remote connections
    • Start > All Programs > SQL Server 2005 > Configuration Tools > SQL Server Surface Area Configuration
    • Click on Surface Area Configuration for Services and Connections
    • Select the instance that is having a problem > Database Engine > Remote Connections
    • Enable local and remote connections
    • Restart instance
    1. Ensure that you have configured the firewall on the server instance of SQL Server to open ports for SQL Server and the SQL Server Browser port (UDP 1434).
    2. Ensure that the SQL Server Browser service is started on the server. Two useful resources for troubleshooting this issue can be found here:
    Also, please verify that the application pool account that this database is associated with is a member of the SQL database role: WSS_Content_Application_Pools.
    Here’s a document on how to add the app pool user to that role: http://connect.nintex.com/files/fold...ntry10989.aspx

    Please also ensure that the NW database has the appropriate account configured as either dbo or db_owner on the database. Additionally, check that the timer service and the central admin account pool identity is the same account.

    Please make sure you are following the our latest installation guide located here:
    http://connect.nintex.com/files/fold...entry1548.aspx
    • Was this article helpful?