RE: DB-Library error 10013
From: vishal subramaniam (vishalsu_at_microsoft.com)
Date: 05/19/04
- Next message: Tim: "Re: What's wrong ...man..."
- Previous message: Jeff: "RE: What's wrong ...man..."
- In reply to: Poonam: "DB-Library error 10013"
- Messages sorted by: [ date ] [ thread ]
Date: Wed, 19 May 2004 07:09:14 GMT
vishalsu@online.microsoft.com
RESOLUTION:
==============
10013 SQLEPARM EXCONSISTENCY Invalid parameter in DB-Library function
reference.
The severity of the error is exconsistency which has a description as AN
Internal software error;
Use sp_trace_create with the TRACE_PRODUCE_BLACKBOX option to define a
trace that appends trace information to a blackbox.trc file in the \Data
directory. Once the trace is started, trace information is recorded in the
blackbox.trc file until the size of the file reaches 5 megabytes (MB). The
trace then creates another trace file, blackbox_1.trc, and trace
information is written to the new file. When the size of blackbox_1.trc
reaches 5 MB, the trace reverts to blackbox.trc. Thus, up to 5 MB of trace
information is always available.
Use the sqldiag utility to collect information about server version and
configuration, .dll file version, error logs, extended stored procedures,
operating system, computer version, configuration data, and additional
data, all of which is put into Sqldiag.txt (by default located in
\Mssql\Log). Also when sqldiag is executed, the two trace files
blackbox.trc and blackbox_1.trc (if it exists) containing trace information
including any server exceptions, are copied to the same output directory as
sqldiag.txt (by default \mssql\log).
For example, the environment in which the error occurred includes this
information:
Microsoft® SQL Server™ version number (as reported to the error log or
returned by SELECT @@VERSION). The first message written to the error log
provides the SQL Server version number.
DB-Library API version number (as reported by the SQL Server Client Network
Utility), ODBC driver version (as reported by ODBC Driver Setup), or OLE DB
provider information.
Application version number (for example, SQL Server Enterprise Manager or
osql.exe).
Operating-system version number.
Hardware platform.
Production or development environment.
This additional information is also helpful in troubleshooting a problem:
The message number, message state, and complete error message text.
Any variables (numbers, database object types, or database object names)
included in the error message.
The context in which the message was generated (what statement was running
at the time).
The number of users who were logged in to SQL Server when the error
occurred.
The frequency with which the error occurs.
If you are using SQL Query Analyzer and you do not see more than 255
characters in the results pane, click Tools, and then click Options. Click
the Results tab, and then increase the value for Maximum Characters Per
Column.
In addition, review the error logs and, if running Microsoft Windows® 2000
or Microsoft Windows NT® 4.0, review the Windows application log and the
Sqlstp.log file, located in the \WINNT directory. You may also want to use
SQL Profiler to monitor events.
LINKS:
========
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/adminsql/ad
_mon_perf_86ib.asp?frame=true
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/adminsql/ad
_perfmon_5qnn.asp?frame=true
hth
This posting is provided "AS IS" with no warranties, and confers no rights.
- Next message: Tim: "Re: What's wrong ...man..."
- Previous message: Jeff: "RE: What's wrong ...man..."
- In reply to: Poonam: "DB-Library error 10013"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
