So unfortunately I continue to be plagued with driver/version inconsistency issues. Same application code base and client as in below 2 links and similar situations. It seems every time I need to touch these reports I struggle to get them deployed on and older set of ancillary software.
http://scn.sap.com/message/14433540#14433540
http://scn.sap.com/thread/3342435
Situation:
Existing reports writing in Crytsal XI, run from and ASP.NET app against SQL Server 2005 SP3. All were upgraded about 1 year ago to .NET framework 4.0 for ASP.NET app code, Reports all upgraded with CR for Visual Studio (much struggles with that but eventually everything worked).
Now I have a single report I need to apply and additional filter to via a parameter and I can get it working locally in various development environments Inlcuding the two listed below:
- Visual Studio 2013, CR for VS SP 9, SQL Server 2014 Express
- Crystal Reports 2013 Trial against SQL Server 2005 SP3 inside a vm
No matter what I do in development I get the parameters prompted in the ASP.NET app, but the report fails with the error listed above when I try to deploy. If I used SQL OLEDB, I get error 17 above and Error Code 53 if I use the native SQL Client. I have even tried creating a brand new report using CR 2013 Trial with both drivers on the dev machine where I have the exact same DB (SQL Server 2005 SP 3) as in the client test and production environments and as soon as I add a single parameter the report fails.
So what I continue to not understand (and wish the SAP team would address) is why does the actual report not use the same connection method as the parameters prompting? The parameter prompting hits the same DB, (many times the same tables) and never fails, it is always the report that fails.
As I mentioned any help is appreciated.
Thanks
Tom