So I'm still not sure if this is on my side, the service side, or both sides. I have NO idea where the main source of the issue is coming from, but I will try and do my best to explain the steps I have taken and what has happened so far so you guys have
all the info you need to bang your head against this with me.
So we have a Web Service class called API.svc that implements one of our classes containing one method. In the API class is where the call goes out to the service, however it seems to be failing before that so I think that the problem is coming locally.
Note I said I THINK.
The first time we ran into an error was running the code normally, and testing this after not testing it in a while. The error that came back when we clicked the button that ran through all the calls (eventually needing to hit the service call), was this:
System.ServiceModel.FaultException`1[System.ServiceModel.ExceptionDetail]: 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) (Fault Detail is equal to An ExceptionDetail, likely created by IncludeExceptionDetailInFaults=true,
View Complete Post