Skip to Content
Former Member
Aug 30, 2006 at 10:48 PM

CR XI server install sp2 breaks report redirection in code


I'm having problems redirecting reports opened in an app written with Visual Studio 2003 using Crystal Reports XI.

Until recently the application was able to redirect reports to whatever database our application was pointed to. In the code I change the connection info for each of the tables and then apply the changes before opening the report. It's the same code that appears in a number of places on the web.

However, once we update any of our clients to the most recent version of the server install that functionality stops working. We're not installing release 2, it's just the most recent version of the server install. I think it corresponds to CR sp2, but it's not really labeled properly so it's hard to tell.

When I try to open the report from within our app using sp2, it pops up with an error message saying:

Failed to open the connection
Details: [Database Venfore Code: 17]
Failed to open the connection
C:\DOCUME......(path to report)
Details: [Database Vendor Code: 17]

When designing the report we're using CR XI sp1 with an OLEDB connection to a SQL server. In addition, if the database that the report was originally pointed to is available to the client, the report will point to that database and ignore the new connection settings without popping an error message. That made it difficult to detect in the first place.

Has anyone else run into similar issues? This is one of 3 Crystal Reports issues I'm trying to troubleshoot right now. I'm in the middle of a very long and very frustrating email correspondence with Business Objects' email support, which I'm starting to realize is completely useless.

Chris" alt="Crystal Reports connection error" width="536" height="159" />