Skip to main content

A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Error 40

Hi there.

This post will use SSMS (SQL Server Management Studio) as well as Redgate SQL Clone.

At the time I am writing this, the latest version of SQL Clone is 4.0.2.19054.


SQL clone is an application that lets you create a copy of an original database (clone) from an image (master file) that you create.

This technology comes in handy because:

  • Developers can test against the clone without altering the original database.
  • The clone is much smaller in size and consumes less storage resources.
  • Once you make an image of a database, you can clone the image to multiple servers. Clones work independently from the image.
  • You can also enforce security by granting/restricting permissions to active directory groups or individuals.


Now it's time for the meat an potatoes.

I received an alert that my SQL Clone process failed and no clones were generated :( .

 Here's the specific error:

Error while opening connection to the SQL server ServerName: 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) (SqlServerConnectionException)
Here's how I fixed the issue:
  1. I logged in to the server with the issue and tried to connect to the SQL instance. I was not able to get into the instance.

    Sql server error 40


  2. I tried to connect to the configuration manager to investigate further and received this error:
    Cannot connect to WMI provider. You do not have permissions or the server is unreachable. Note that you can only manage SQL Server 2005 and later servers with SQL Server Configuration Manager. Invalid class  [0x80041010]

  3. I checked the services for the SQL instance. It turns out that even though the service StartupType is automatic, the service was not running.  I tried to start the service and received this error:
    Windows could not start the SQL Server (MSSQLSERVER) service on the local computer. Error 1069: The service did not start due to a login failure.

    I updated the account that was being used to start the SQL service with an administrator account (database engine) account.



    This resolved the issue. You're all set!




If you have any further questions, please post below.
Thank you and Happy reading,

-marshé hutchinson
#learnSQLwithme
Labels:

Comments

Post a Comment

Popular posts from this blog

event id 101 task start failed - task scheduler event id 101 launch failure

Hello again. This post is related to automating SQL server tasks with Task Scheduler. In this example I was tasked with exporting SQL server agent jobs twice a month. To achieve this, I setup a task scheduler task that ran a PowerShell script that: establishes a local connection to the SQL server. cleans the file before writing to the .sql file to avoid adding on (appending) results on subsequent runs of the task scheduler task. when a connection is established, export the SQL agent jobs on the server to a .sql file on a remote server. sends a confirmation email via the SQL server database mail profile that the SQL agent jobs were exported to the specified remote server path. That was a mouthful. Now that you know my task scheduler task is calling a PowerShell script, let's get back to why it is failing.  The good news is this error is not related to the script. The error launch failure means the task could not even run. This is most likely due to a permissi...
Post a Comment
Read more

Msg 14234, Level 16, State 1, Procedure sp_verify_job, Line 199 The specified '@owner_login_name' is invalid (valid values are returned by sp_helplogins [excluding Windows NT groups]).

Hi guys! Here's another quick and easy post. Scenario I was trying to copy a SQL agent job from one server to another by just copying the script of that SQL job. You can copy any script by right clicking a job > Script job as > create to > new query window. I pasted the job on a different server and tried to execute it and received this error: Msg 14234, Level 16, State 1, Procedure sp_verify_job, Line 199 The specified '@owner_login_name' is invalid (valid values are returned by sp_helplogins [excluding Windows NT groups]). This error message is simply saying for the variable '@owner_login_name', the user account associated with the variable is incorrect because it does not exist. Fix Simply update the variable for '@owner_login_name' to a valid user account for the current SQL instance. Now when you execute the script again to create the SQL agent job your results will be: Command(s) completed successfully. If you have any furt...
2 comments
Read more

Database "" database is not in full recovery mode on each of the server instances. The full recovery model is required for a database to participate in database mirroring or in an availability group. [SQLSTATE 42000] (Error 1465).

Hi there. This post will be a quick and easy fix. If you are not already aware, availability groups are the replacement for mirroring in SSMS (SQL Server Management Studio). We like to utilize availability groups so that there is minimal data loss. Also, in the event of some natural disaster or disk failure on a server that is participating in an availability group, the data will fail-over to a backup server (replica). I was adding a database to an availability group when I received the error: Database "database_name" database is not in full recovery mode on each of the server instances. The full recovery model is required for a database to participate in database mirroring or in an availability group. [SQLSTATE 42000] (Error 1465). The error is exactly as it sounds; The database is not in the full recovery model. To fix this: I. In SSMS, right click the database to see the properties. On the Options page, change the database recovery model to Full. II....
1 comment
Read more