We are in the middle of a back-end upgrade on our SQL server. We are moving 200 Crystal Reports reports (9.2) from our old SQL database (SQL Server 2005) on Windows Server 2003 R2 x64 to our new SQL database (SQL Server 2008 R2) on Windows Server 2008 R2 Enterprise. Our migration is finished and everything looks good as far as the tables go. We are using the same ODBC connection for all the reports and just switching the database names and manually refreshing the tables and saving for our external users.
I am a domain admin and have refreshed and updated all the reports to the new backend.
They refresh fine and everything is good.
The problem arises when a regular domain user goes to refresh the reports. The report won't refresh and there is a mapping issue that pops up. The majority of reports are looking for tables that aren't showing up in the table list in the reports for the regular user. The SQL permissions are clear giving the regular user the rights to pull and read the report. If I give the regular user domain admin rights, the problem goes away. When I remove them. Table mismatches. It's like a different set of tables gets pulled through the same ODBC configuration that is dictated by domain rights.
I'm at a loss and our go live is on Monday. Any ideas would be appreciated.