Crystal Report 2013 report based on MS-SQL Database where Data-Source is a single Stored Procedure.
All works fine in that state running on SAP-BO-BI-4.1 Platform
For SAP-Security purposes needed to update the format to Crystal Reports for Enterprise 4.1 - opened file in CR4E and used "Set Data Source Location" to move everything to the Target of the Relational Connection to MS-SQL DB as configured on the SAP-BO-BI 4.1 Platform.
Data Source Move & Map went to OK - so uploaded the CR4E file to the Platform to TEST it.
When running as View-On-Demand get the Prompts OK for the Stored Proc - but then it throws an FailedToFetchProcedureFields[CRC00000337]error. The Gory details of that error are in the attached TXT file.
When running as a SCHEDULED Instance - it FAILS with a similar error FailedToFetchProcedureFields (CRS 300003) below
Based on the way the CR-2013 report runs - and the way that other CR4E reports run on the same Platform against the same MS-SQL database, I don't think the issue is with the Reports or the Database.
The error is pretty-specific in this being an issue with a CR4E relational Connection on the Platform calling a StoredProc.
Anyone seen this before, and know a FIX...?
Thanks in advance for the advice