SAP Knowledge Base Article - Preview

1214879 - Creating a Report using ODBC with Stored Procedures and Temp Tables in SP fails

Symptom

An application uses Crystal Reports for Visual Studio as the reporting development tool. 

When attempting to view a report that uses an ODBC connection to connect to a stored procedure that uses temporary tables, the following errors message may appears:

"Server Error in ' Application Name' Application

Exception of type System.Exception was thrown"

Failed to open the connection.:  [Database Vendor Code: 53 ]

Invalid cursor state :  [Database Vendor Code: 55 ]

Why does this error occur and how do you resolve it?

====================

NOTE:

Temp tables are defiend in the Stored Procedure with a preceding # character.

If you attempt to create a report off the same stored procedure, the following error message appears in Crystal Reports Designer:

"Query Engine Error: 24000:[Microsoft][ODBC SQL Server Driver]Invalid cursor state"

====================

 

 

 


Read more...

Environment

  • Crystal Reports 2008
  • Crystal Reports 2011
  • Crystal Reports 2013
  • Crystal Reports 2016
  • Crystal Reports for Visual Studio

Product

SAP Crystal Reports, developer version for Microsoft Visual Studio ; SAP Crystal Reports, version for Visual Studio .NET 2005 ; SAP Crystal Reports, version for Visual Studio .NET 2008

Keywords

.NET DOTNET STORED PROC TEMPORARY TABLE SYSTEM.EXCEPTION RUNTIME Crystal Reports for Visual Studio Stored Procedure Temporary Tables ODBC error 53, error 55, Invalid cursor state , KBA , BI-DEV-NET , BI Software Development Kits (SDKs) - .NET or Other , Problem

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.