Report with two ODBC MS Access subreports won't run

[davidlpd]

I have a report whose primary data is from MS SQL Server 2000. I also have two subreports on this report that pull data from MS Access via ODBC. This reprort runs fine in Crystal Reports Developer 10. When I publish this report to Crystal Enterprise Professional version 10.0 the report won't run. Attempting to run the published report "normally" I get the error "There was an error retrieving data from the server: Failed to open a rowset." When I run the report via the Crystal Report Viewer I get the error "Failed to open a rowset..." and the subreports show a status of Loading. I would appreciate any suggestions any can provide.

 

[synapsevampire]

Sounds like you don't have the ODBC connectivity properly set up for the Access databases, or the accounts under which the Crystal Services execute do NOT have access to the folders where the Access database(s) reside, the latter being fairly common.

-k

 

[davidlpd]

Thanks for the reply. I verified this by using the tool Microsoft ODBC Test and running it as the user running the service. I wasn't able to get the syntax correct so I didn't get any records returned via the tool but I was getting syntax errors from the jet database. Any other suggestions?

 

[synapsevampire]

As a rule I always put Crystal Reports on the server as it gives more verbose error messages.

Also the ODBC connection should be using a UNC pathing, as in \\machine\path, not <drive letter>\path.

Your problem is common, and in my memory for one of the aforementioned reasons.

-k

 

[mgpeters]

In my experience, I have always had to have the Access db stored locally on the CE server. I could not get an ODBC connection to work via CE even when using the UNC path.

Once I put the Access db on the CE server I was able to get it to work.

Good luck.

 

[synapsevampire]

I've used Access via ODBC to remote drives many times on CE, the key is that the user for the services have access to it, and you use UNC.

-k

 

[Turkbear]

Hi,
Same here, for the few times we have needed to use Access DB data, using a UNC specification in the DSN and insuring that the account the CE servers run under have access rights to that physical location/file system has always worked..





To Paraphrase:"The Help you get is proportional to the Help you give.."