Database Connector Error: ' [Database Vendor Code: 8114 ]' Database Connector Error

1081 Views

Hi,

We are using .net web forms, SQLOLEDB data source for launching the reports.

Reports are launching fine in the environment having windows server 2003 R2 and Crystal Reports XI Release 2.

But the same reports are not launching in a new server having windows server 2008 R2 and Crystal Reports 2008.

When I analyse the issue in the new server, if I create a new rpt (with the same sql connection and stored procedure) it is working fine. But the existing rpt files are not working. I tried to verify database and save the existing problem rpt then also it fails.

I am getting the error "Database Connector Error: ' [Database Vendor Code: 8114 ]' Error in File RFCReport {4F28DA35-FB07-4D63-BAD4-D5120C5893A2}.rpt: Database Connector Error"

I had verified the SQL profiler the working report (newly created report) is having the following sequence

exec [xxxx]..sp_tables_rowset N'Cat_Salary_Certificate_sp',N'dbo',NULL

exec [xxxx]..sp_procedures_rowset N'Cat_Salary_Certificate_sp',1,N'dbo'

exec [xxxx]..sp_procedure_params_rowset N'Cat_Salary_Certificate_sp',1,N'dbo',NULL

exec "xxxx"."dbo"."Cat_Salary_Certificate_sp";1 1, 3, N'PAYACC1', N'IAKSHS', '3', '0478000', '0478000', '105'

For the same exisiting problematic rpt SQL profiler sequence are as follows

exec [xxxx]..sp_tables_rowset N'Cat_Salary_Certificate_sp',N'dbo',NULL

exec [xxxx]..sp_procedures_rowset N'Cat_Salary_Certificate_sp',1,N'dbo'

exec [xxxx]..sp_procedure_params_rowset N'Cat_Salary_Certificate_sp',1,N'dbo',NULL

exec [xxxx]..sp_tables_rowset N'Cat_Salary_Certificate_sp;1',N'dbo',NULL

exec [xxxx]..sp_procedures_rowset N'Cat_Salary_Certificate_sp',1,N'dbo'

The above both the rpts uses the same connection and stored procedure only.

How to over come this issue ?

Is this the problem is because of the old rpt file version which is not compatible with Crystal Reports 2008?. If so if I install Crystal Reports XI release2 will this problem get solve ?

I had also verified for mdac or any permission issue, but there is no issues found.