We have a huge .NET application from 3rd party that would be time consuming to disassemble and understand the code. It is compiled in Release mode. Connection strings to the MS SQL databases are defined to be in config file and they seem to be correct. There are more then 6 different databases it uses.
However when app starts, it throws an error like "a network related or instance specific error occurred while establishing a connection to sql server" Traces of the application doesnt provide enough information where it tries to connect when it fails.
Is it possible to profile which connection a .NET application is trying to open without knowing in advance which SQL server name it tries to connect? SQL Profile traces connections on server side opened from other machines, but what is the best tool there to see on a specific machine to which SQL server it connects (with a possibility to see a non-succesfull connections as well)