Symptoms

We have a process that looks at a smart object and that smart object makes a connection to a sql server. We have 2 datacenters and we use SQL 2012 always on availability groups and when our sql server is live in one datacenter everything works as expected but if we fail over the sql to the other datacenter the workflow fails on this process and the error message is as follows.

Named Pipes Provider: Could not open a connection to sql server 67]
 

Diagnoses

The issue was caused by the old host file entry on the other Data Center.
 

Resolution

Updating the host file entry on the server once failed over to the other datacenter corrected the issue.