how to trace sql anywhere client to database

Let’s start with the trace file from the application server. So getting the exact time of the issue is very important when you have too much data to review. The exact time will help you to find out which trace file you need to start with. Often time you will get significant number of trace files from each server when collecting network traces for intermittent issues because you may have to capture the trace for a long period of time and this can generate quite a number of trace files when configured to save the trace files as chain (for this particular case the customer sent us more than 60 trace files each of size 25MB for the app sever and 6 such files for the SQL Server J). 09:28:08 DataBase Warning OleDB Error Microsoft OLE DB Provider for SQL Server : General network error. Now find out when exactly the issue happened from the error message. Let’s check the IPconfig’s first to find out the IP addresses. IP addresses and exact time stamp of the issue:

However, in this case we used wireshark since traces sent by the customer could not be opened using the Netmon tool (due to a different file extension). You can use Netmon or wireshark to capture and review the traces. You can use the same techniques to analyze the traces collected for the intermittent connectivity issue to the SQL server. If an error message with the timestamp is not available then request to record the exact time of the issue and send to you.īelow I will show step by step how we reviewed the collected network traces. Exact error message that shows the timestamp. ipconfig /all from all the servers involved.Ģ. When you collect network traces always make sure to collect the following two as well.ġ. we collected simultaneous Network traces from both the application server and the SQL server. Check your network documentation.Īfter doing some initial troubleshooting like checking if the TCP chimney was disabled, if the application server was running out of max client port number etc. OleDB Error Microsoft OLE DB Provider for SQL Server : General network error. Here is the error message they were getting. Recently I worked on a case where the customer was seeing intermittent GNE from an application that was trying to connect to the SQL Server remotely. By collecting the network traces and reviewing them we can tell why the connections failed to succeed or if the existing connections were getting closed. Intermittent connectivity issues from a client machine when connecting to a remote database server can be often attributed to the network layer.

How to trace sql anywhere client to database