After sql 2008R2 cluster SAN env. migration, keeps getting error: SQL Server Agent - [165] ODBC Error: 0, Named Pipes Provider: Could not open a connection to SQL Server [2]. [SQLSTATE 08001]

Question

hi all:

  We did a SAN migration over the weekend and all seems fine  (2008R2 Ent. ). All seems to be fine and all sql jobs are running fine.

  However, in the sql agent error log, I kept getting this error:

SQL Server Agent - [165] ODBC Error: 0, Named Pipes Provider: Could not open a connection to SQL Server [2]. [SQLSTATE 08001]



  After searching in this forum, someone suggested it could be related to a job trying to access outside servers. 

My question here: 

1.   I could not find any jobs that are in line with the timeline of those error msgs. 

2.   What to do if say I found those jobs?   

Before migration, no such errors . After migration, this kind of error happens everyday.

Thanks

---

--Currently using Reporting Service 2000; Visual Studio .NET 2003; Visual Source Safe SSIS 2008 SSAS 2008, SVN --

Answer 1

Hi cat_ca,

Based on the above description, my analysis is that this problem is not caused by any jobs. This problem can be caused by that the cluster fails to bring the SQL Server Agent resource online after migrating SAN.

Please refer to this blog to bring it online: https://www.mssqltips.com/sqlservertip/2592/fix-sql-server-agent-on-windows-failover-cluster/

Here is a similar case, please refer to the last reply: https://www.sqlservercentral.com/Forums/Topic983734-391-1.aspx

Best Regards,

Teige

---

MSDN Community Support
Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact [e-mail].

Answer 2

Thanks Teige. The Sql server agent service is actually up and running. All jobs are running fine though. 

Sql Server Agent resource is also online. However, in the sql agent error log, I kept getting this error:

SQL Server Agent - [165] ODBC Error: 0, Named Pipes Provider: Could not open a connection to SQL Server [2]. [SQLSTATE 08001]

---

--Currently using Reporting Service 2000; Visual Studio .NET 2003; Visual Source Safe SSIS 2008 SSAS 2008, SVN --

Answer 3

Hi,

Please follow the link below, may be it helps

https://blog.sqlauthority.com/2009/05/21/sql-server-fix-error-provider-named-pipes-provider-error-40-could-not-open-a-connection-to-sql-server-microsoft-sql-server-error/

---

Cheers,

Amit Tomar

---------------------------------------------------

Please mark this as answer if it solved your query

Please vote this as helpful if it solved your query

---------------------------------------------------

My Blog My Wiki Page

Answer 4

Thanks but   none of the tips mentioned in the link helped. 

---

--Currently using Reporting Service 2000; Visual Studio .NET 2003; Visual Source Safe SSIS 2008 SSAS 2008, SVN --

Answer 5

I would suggest to run profiler or EE trace to capture from where this connection is coming from. 

---

Cheers,

Shashank

Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it

My TechNet Wiki Articles
MVP