Nearly every week during the past few years has featured a headline about the latest data breach, malware attack, ransomware demand, or unrecoverable corporate data loss. Those stories are frequently followed by news that the CEOs at those companies were forced to resign.
Applications stopped communicating with SQL 2005
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)
Verified that all services were started.
Named pipes were enabled.
TCPIP were allowed.
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)
Verified that all services were started.
Named pipes were enabled.
TCPIP were allowed.
Who is Participating?
Experts Exchange Solution brought to you by
Enjoy your complimentary solution view.
Get this solution by purchasing an Individual license!
Start your 7-day free trial.
I wear a lot of hats...
"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.
LVL 42
This may be due to some DNS (or firewall) issue - did you tried connecting to it via the IP instead?
OK, so can you try a telnet from the app server where you get this error to see if the SQL server can be reached?
like in cmd prompt run:
telnet 111.222.333.000 1433
without any : and use the actual port if is not running on default TCP port 1433 - obviously replace 111.222.333.000 with the actual SQL IP
you can also run a command like below by that SQL IP to see where is your network broken link:
tracert 111.222.333.000
like in cmd prompt run:
telnet 111.222.333.000 1433
without any : and use the actual port if is not running on default TCP port 1433 - obviously replace 111.222.333.000 with the actual SQL IP
you can also run a command like below by that SQL IP to see where is your network broken link:
tracert 111.222.333.000
OK so if the telnet is working fine to IP port 1433 and SQL is running on it so there's no reason why the app cannot connect to that same IP/port number right? Was there any deployment, or windows update in between the time when this was working and current state?
I mean you could try create a ODBC on that app server and "test connection" but that will just proof the SQL is not the issue in this case and I think you need to check app config files and maybe try an IISRESET
Modified the app to bypass checking SQL. The app worked so this showed me that the issue is a connection to SQL. Checked all of the config files and recycled the app pool as well as rebooted both servers. (I have a second server with the same apps and I am getting the same error message)
Could you try create a ODBC on that app server using exact same IP/port/credentials and "test connection"?
Also, on the SQL Side - is there anything error/warning related in the SQL Log files by any chance
Also, on the SQL Side - is there anything error/warning related in the SQL Log files by any chance
you may also try to
Restart your MSSQLSERVER service. sometimes it works. Also, check Instance name(.and /)
have a look here: http://www.sqlserverlogexplorer.com/fix-error-message-40/
hope this will help you.
Restart your MSSQLSERVER service. sometimes it works. Also, check Instance name(.and /)
have a look here: http://www.sqlserverlogexplorer.com/fix-error-message-40/
hope this will help you.
- Enable Named Pipes SQL Config Manager
- Restart the server SQL Config Manager
- Use proper server and instance names
Apparently under Windows Server 2008 R2 it is not followed to the letter adding more websites (IP addresses) to the Server which resulted in the primary address no longer being used. There is a known bug that causes this. Only the primary IP is allowed to communicated with the SQL server or other servers in which we allow. This server is in the DMZ. It in fact assigned one of the other IPs that have been added that this server starting to use as a primary server IP and only the primary IP is allowed communication.
Experts Exchange Solution brought to you by
Your issues matter to us.
Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.
Start your 7-day free trialIt's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft SQL Server 2005
From novice to tech pro — start learning today.
-
Microsoft ApplicationsCertification: MOS Microsoft Office Specialist - PowerPoint 2007… 229 lessons
-
Microsoft ApplicationsCertification: MOS Microsoft Office Specialist - Outlook 2016 Par… 211 lessons
-
Microsoft ApplicationsCertification: MOS Microsoft Office Specialist - Word 2016 Part … 125 lessons
Experts Exchange Solution brought to you by
Enjoy your complimentary solution view.
Get this solution by purchasing an Individual license!
Start your 7-day free trial.