Fix for db library error 10013

Question

Fix for db library error 10013

Linda Scholtz

SSC Veteran

Points: 277
More actions
March 29, 2007 at 1:23 am

#194808

Hi all,
This is my first post so please excuse if I sound like an idiot or havent followed rules...
I am a developer and our application is written in VB using a SQL 2000 Sever.
Some of our customers have recently started getting the DB Library Error 10013 (invalid parameter in db library function reference) whilst using the application. I have searched high and low on the internet for a possible explanation and solution, but could only find one really high level technical post (me not technical ).
Is there anybody that maybe knows what is causing the error and how to resolve.
Any help would really be appreciated..Thank you very much in advance..
Linda

Viewing 4 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic. Login to reply

SQL ORACLE One Orange Chip Points: 27807 More actions · Answer 1

Based on the explanation by Microsoft, it is an error due to Invalid parameter in DB-Library function reference. It means that either you do not provide right number of variables, or the variables have mis-match data type.

http://msdn2.microsoft.com/en-us/library/aa937496(SQL.80).aspx

It is better to obtain detail information on the functions before calling them.

Linda Scholtz SSC Veteran Points: 277 More actions · Answer 2

Thank you for the help.

Just another stupid question , is the function it is trying to execute a user created "procedure" or is it an internal SQL Server procedure which the server is executing?

Will we be able to replicate the error using a trace from profiler on the client's PC or is this error server specific?

Thank you very much!

SQL ORACLE One Orange Chip Points: 27807 More actions · Answer 3

No question is stupid.

Based on my understanding, the error (DB-Library) you mentioned came from a "procedure" built-in SQL Server (internal SQL Server procedure).

Using the SQL profiler may trace some of "procedures", but not all. The basic rule is that the SQL profiler can trace all objects it treats as objects.