cancel
Showing results for 
Search instead for 
Did you mean: 

error trying to set database location

crazycrystal
Explorer
0 Kudos

I developed a report design using SAP Crystal Reports 2013 at my local office and it runs fine. The report connects to an ODBC data source name created based on an ODBC driver provided by the software company. Everything works fine at my office. But, when I copied the report design to the remote office where the same software/database/ODBC driver/data source name are installed (all same versions). The report errors out when I try to use the menu option "Set Database Location" to point the Data Source to the once on the remote office server at the remote site (all of this is through RDP, so it isn't like a WAN or a remotely connected database/cloud database). The errors messages show in the following sequence:

Data Object cannot be opened/accesses. [ OK ]

Database Connector Error: 'Cannot obtain error message from server." [ OK ]

So it doesn't make any changes to the location of the data source and leaves it as the same from the original server. When I look at the table properties, it shows the "Owner" value as the server name I created the report design on, not the server I moved the report too. The interesting thing is, I can create new reports on the remote server using the same data source I'm trying to change my existing report with no errors and the report runs fine. The report took me multiple hours to create as there are a lot of groupings and sub reports and tons of formulas. I don't want to have to recreate the report from scratch etc. Any ideas on a work around would be apricated.

crazycrystal
Explorer
0 Kudos

I ended up recreated the entire report and all subreports.

Accepted Solutions (1)

Accepted Solutions (1)

crazycrystal
Explorer
0 Kudos

I re-keyed the report, tool about 2 days but it's all good now. So weird how it wouldn't allow the change of the DSN with the folder the data is stored in had a "." and a "," in the name.

Answers (5)

Answers (5)

crazycrystal
Explorer
0 Kudos

Don here is something interesting: I can create a new report using the DSN that's linked to the data in the folder with a comma and a period in the folder name. I can then use set database location and change the DSN to a different DSN without a comma and period in the folder name. But, if I then try and set database location back to the original DSN that I used to create the report, the DSN linked to a folder with a comma and a period, it errors out and gives me the same error messages.

crazycrystal
Explorer
0 Kudos

Don, Thanks again for the suggestion for resolving this weird issue. It still gives me the error : "Data object can't be opened or accessed" I'm not sure but one thing I noticed is the folder name that the data is stored in has a "comma" and a "period" in the naming. If I try to update the ODB Data Source name I get the error but on the same data copied to a folder with out those characters in the name, it works, same data same software same ODBC driver version etc., just a data source name with out the comma or period in the name ? I guess I'll see what is involved with IT staff renaming the folder to no use the comma and period. I fear it's a bigger issue and will cause other things to break. So I might be stuck re-keying the report and copy / paste as much of the old report as I can !

.

DonWilliams
Active Contributor
0 Kudos

Hi Scott,

On the Set Location... screen in the lower box select ODBC and it should prompt for the DSN to use, fill in the info and then click on Table by table and click the update button.

If that fails to log in it's your DSN causing the problem, could be permissions on the new DB, CR does respect all DB Permissions, if you don't have access to the Database/Tables you won't be able to update the report.

Then when you click on ODBC the ODBC UI pops up:

Select your DSN and possibly you can then click the update button, or you may have to select each table.

Note this report is using Access as the data source so it's flat file, your report may have a server name or database or table.

If that fails check with your DBA to verify you do have permissions, try the DB's Admin account to see if that works.

See if that helps

Don

crazycrystal
Explorer
0 Kudos

Don, Thanks for responding! So I'm a bit lost, sorry. When I click menu options: [Database] / [Set Database Location] it shows at the top the Data Source Name used to originally create the report back at my local office. So I don't see any option to "Connect to Database" on that screen. I can select from the blow [Replace With:] and I can click either [My Connections] which shows existing ODBC Data Source names (that work fine for creating new reports, same exact database as at my local office) from the list. If I select one from the list, it asks for my my login credentials! Or, I can select [Create New Connection] and created a new connecting to the database and log in to the data base there. But that doesn't change the "Current Data Source" the report has at the top. For that, I would need to click [Update] once I establish the connection to either an existing "My Connections" or after I create a "New Connection". But that is also where the errors occur. However, if I create a new report from scratch and use either an existing "My Connections" and create a new report, all works fine with no errors. I only get the errors when I try and change the location of the database the existing report has to one that is on the remote office server. It's so strange. The only thing that is different is the folder name the database is in is a different name and it for some reason has a " , " in the folder name (I didn't do that!) I whish I go to a report hack and change the location of where the report saves the server name for where the database! Such as Local office is : \\Main-Acct2 vs the remote location: \\STL-Acct The Data Source names are the same: Production-Accounting Thanks!

DonWilliams
Active Contributor
0 Kudos

HI Scott,

On the remote PC open the report and select Set Data Source.... and then connect to the DB.

Once connected then click on Database, Verify.

CR does keep the connection info in the RPT file, since you see your original connection info it's not updating to the new one.

Don