Groups | Blog | Home
all groups > sql server clients > december 2003 >

sql server clients : Put a log on mssql client


mcfried NO[at]SPAM yahoo.com
12/29/2003 2:06:26 AM
Hi!
mcfried NO[at]SPAM yahoo.com
1/1/2004 12:28:55 AM
We are using OLE db and it is just the connectivity to mssql server
that is installed on each client. I'm sporedically getting en error
like 'Message number: 11, severity: 16 Message String: :
[DBNETLIB][ConnectionWrite (WrapperWrite()).]General network error.
Check your network documentation.' I can not get any info from tracing
the server because it dose reach server. It seems that the
connectivity is returning the error, so maybe tacing the client will
cgross NO[at]SPAM online.microsoft.com
1/2/2004 10:38:39 PM
First, a warning about turning on ODBC tracing: it can slow down all ODBC
connections due to the overhead of logging. And it creates and writes to
sql.log which can grow quite large and consume all disk space on the
specified drive.

Regarding a general network error, it's unlikely that either an ODBC or OLE
DB type trace would help. The error could be anything from a busy network
to some weird configuration setting. Check your Event Viewer logs and SQL
Server logs to see if you can find any relevant messages. A netmon trace
often helps though you have to be able to interpret the output for it to be
meaningful.

Cindy Gross, MCDBA, MCSE
http://cindygross.tripod.com
This posting is provided "AS IS" with no warranties, and confers no rights.
AddThis Social Bookmark Button