Database Connector Error: '[Database Vender Code: 4413]'

Experts,
While trying to preview a report in a report viewer XI from a VB6 form on one of the clients i got the following error!

Run-time error '-2147189182 (80047e42)':
Database Connector Error: '[Database Vender Code: 4413]'

Why is that??
feesuAsked:
Who is Participating?

[Webinar] Streamline your web hosting managementRegister Today

x
 
mlmccConnect With a Mentor Commented:
Crystal Reports ActiveX Designer Design and Rumtime Library 11.0
Crystal Reports ActiveX Designer Rum Time Library 11.0

You don't need both of them.

All functions in the second one are included in the first.

You only need the first one if you are using some of the special functions from it.  Try deleting it and see if you can run.

mlmcc
0
 
SpykairCommented:
0
 
feesuAuthor Commented:
Hi Spykair,
I have downloaded this fix. But this problem appears on the client's machine! How do i get along with that?
0
Receive 1:1 tech help

Solve your biggest tech problems alongside global tech experts with 1:1 help.

 
dylanyeeCommented:
Did you set your database connection properly? Mind to share with us your code on how did you set the connection?

dylan
0
 
feesuAuthor Commented:
Not at all, here is snapshot:
Private Sub ShowReport()
...  
    Me.rptMain_Init
    Me.rptMain_DataSource
    Me.rptMain_Header
    Me.rptMain_Detail
    Me.rptMain_Footer
...
End Sub

Sub rptMain_DataSource()
        Dim crDBTables As CRAXDRT.DatabaseTables
        Dim paramValueInfos As New ParameterValueInfos
        Dim paramValueInfo As New ParameterValueInfo
        Dim paramValues As New ParameterValues
        Dim paramValue As New ParameterValue
        paramValue.StartValue = 0
        paramValue.EndValue = 0
        paramValues.Add paramValue
        paramValueInfo.parameterName = "@ClientID"
        paramValueInfo.ParameterValues = paramValues
        paramValueInfos.Add paramValueInfo
        Set crDBTables = rptMain.Database.Tables
        crDBTables.AddStoredProcedure sMainTable, , , 2, "p2ssql.dll", "SRVSQL", , "GLOBAL", "sa", "MyPass"   ', paramValueInfos
End Sub
0
 
mlmccCommented:
To get a fix to the client the easiest way is to build a new installation package and reinstall.

If you knew which dlls were changed you could replace them but generally a new installation is easier.

mlmcc
0
 
mlmccCommented:
Are you trying to change the SQL the report is based on?

crDBTables.AddStoredProcedure sMainTable, , , 2, "p2ssql.dll", "SRVSQL", , "GLOBAL", "sa", "MyPass"   ', paramValueInfos

mlmcc
0
 
feesuAuthor Commented:
Hi mlmcc,
I only change the stored procedure name based on the user's selection. But it always uses a stored procedure and the same server/database
0
 
mlmccCommented:
To the best of my knowledge you can't change the stored procedure that way.  You can change the data source but I remember reading that if a stored procedure is used you can't change it.

Do all the stored procedures return the same columns from the database?

mlmcc
0
 
feesuAuthor Commented:
Hi mlmcc,
I don't think that changing the stored procedure is a problem, because this error appears only on the client's PC. My pc works perfect.
And of course not, each SP has it's own structure, and returns different columns.
I think the whole problem is with immegrating to XI. I never faced such errors with 8.5.
0
 
mlmccCommented:
A new piece to the puzzle.  

Did this start with CR XI?

What Crystal references do you have in the application?

Crystal introduced the licensed required dll with CR8 but didn't start enforcing the license requirement until CR9.  If you are using CRAXDDRT.DLL you may be having a license issue.

mlmcc
0
 
feesuAuthor Commented:
:)
It did start with XI.

References:
Crystal ActiveX Report Viewer Library 11.0
Crystal Reports ActiveX Designer Design and Rumtime Library 11.0
Crystal Reports ActiveX Designer Rum Time Library 11.0

Regarding the license issue, it generates a clear error saying something like "Contact Business Objects for license". So it is not.
0
 
feesuAuthor Commented:
I removed the reference. It gave an error on the CRAXDRT.DLL
I replaced all definitions with the new CRAXDDRT.DLL
And I removed the error handler for the "Basic syntax" error and stopped getting that error!

Thanks alot for your help mlmcc!
0
 
mlmccCommented:
Glad i could help

mlmcc
0
All Courses

From novice to tech pro — start learning today.