"failed to save document" error when changing data-source

[Former Member]

I have searched and found many different suggested solutions to this problem, including in this forum (http://scn.sap.com/thread/1522368) but none give a definitive answer or solution, and I am now faced with a significant problem:

A user has developed a number of reports against a test database with a data-source name of Systest4. These have now all passed testing and are ready to be put live against the production data-source, an identical database called Production.

I have checked the reports for sub-reports, formulas and verified the database on each move, but EVERY time you try to save the .rpt (with the same name or a different name) it comes back with:

failed to save document

failed to save database information

database connector error the specified object was not saved

Curiously, if I point the Systest4 data-source to the live (Production) database, so there is no change to the .rpt file, the report will connect and run normally, and will save. This, however, is not an option as there will ultimately be a large number of reports and they need to be managed by all the live reports pointing to the Production data-source.

This has been a reported issue since 2008 and I cannot find a solution.

Can anyone help?

Thanks

Martin

[former_member11696]

Hi Martin,

First thing to do is, and we've noticed this with Oracle only, is when you use the Set Location function do so for each table, not just the connection. Click on each table, old and new, and then the update button. Do so for all subreports also. For some reason Oracle does not allow CR to update globally.

If that doesn't then...

Use a program tool called Process Monitor, from Microsoft, and filter on crw32.exe. Then go through the steps and when you try to save it the look at the logs to determine why you are not allowed to save the report. It could simply be a permission issue on the folder you are trying to save to.

As for the DB issue it could simply be the user account you are using does not have full permissions to access the database. CR fully supports database security, if the tables do  not have read/write permissions CR will not let you run the report.

Don

[Former Member]

Crystal Reports 2011

Version 14.0.2.364

mySQL ODBC Data source 3.51.30