Thank you for your reponse. As far as I know, yes, the report worked before the server changed. All other reports are running successfully in Desktop (I tested out a large sample and when one goes down, we hear within minutes). This is running from the Generate Reports menu (Billing > Crystal > Dues Receipt). The report parameters references one of our network drives, so it is a custom Crystal report out on the network. I thought about the permissions issue, and I'll double check that, but the same user has access to all other reports. And since the server moved but the report didn't, the permissions changing on the report didn't make sense to me. But stranger things have happened, as they say. Thank you again!

I think it is a permission issue. Is it possible you can login to this pc as an domian administrator and run the crystal. If it works may be this user don't have permission to access crystal reports temprory folder.

Thank you for your response. If it is a permission issue, then it's specific to that 1 report, because users seem able to access other reports in the same category. Plus, I have full access to the report (and am logging in with Manager access) and I also get the error through iMIS. But I can run the Crystal outside of iMIS.

You might want to check the following:

1.First and foremost I would recommend to remove the network location parameter (for temporary testing) and run the report to see whether it runs properly inside iMIS. If it does then the network location is the problem and your server/iMIS might require security permissions to access that location (file server).  You may want to move which ever file in the Network location the report is trying to access to some other location in the Application server itself so that it is local and no external outbound access if required. If it still doesn't pass then I would recommend to look into your selection criteria and other places to see any thing related to the location of the file or path.

2. When you say other reports run fine do they have the Specific Network Path related parameters in any of those reports as well? If not it is not a true test.

3. When you say it runs fine in native Crystal directly it is not a true test either. Since the direct run from Crystal uses the ODBC connection to the database server and the file server access may be based on how you logged on to your windows operating system and your user permissions in Active Directory or LDAP or what ever system your organization uses. iMIS accesses the database server and other places by

4. Is the Rpt.File/Format name is hardcoded with dedicated path? For example c:\\....\Custrpts etc. If so remove the path and keep only the file name with the .rpt extension or change the path if needed to correspond to your new setup.

5. Is the file with the same name of the report in the reportspec  in the StdRpts or CustRpts folder under the iMIS installed location (application server from where the iMIS desktop is running)? If not copy and paste your custom report in the CustRpts folder.

6. When you say Server moved last week which server do you refer to - Application Server or Database Server or the file server? Change of Database server shouldn't matter as long as iMIS and/or iMIS Reporting (something like that - check with ASI Tech Support) has the user permissions for the database (looks like you have already checked the permissions for the views). The only time it would matter would be that your report (rpt file) is in Crystal version 8.x and your datasource location property is populated with fully qualified path. If so, Strip the prefixes. If your rpt file is in CR 9 or above it shouldn't matter because the location would be automatically  universal path with out any prefixes.

7. When you have a network location as a hard coded parameter you might need a login permission to access that location (file server or other). Did you have any trusted relationship between your old iMIS Application server and the network location file server and are you missing that trusted relationship between your current iMIS Application Server and your network location. You might want to check your old server and create the same relationship with the current server.

8. Did you contact ASI Tech Support? They may be able to look at your setup and provide solutions.

Hope this helps to point you in the right direction(s) to solve your problem.

Hi

May be you can check the following settings from your crystal report.

 -  Make sure your report is not saved with 'Save data with report' option ticked

-  Do not use ' integrated security' to access the database from crystal,

Thanks

I've encountered this error message in custom crystal reports after we upgraded to 15. I found that the there were tables listed twice in the Detail Report Parameters in Report Specs. I suggest you check the Main Tables and Search Files fields in the Detail Report Parameters.

Thank you for your suggestion. Unfortunately, when I look at the detailed report specs in iMIS for the report in question, the fields you mentioned are blank (as they seem to be for other of our reports).

Thank you for your input. "Save data with report" was not checked. I'm not sure if we're using integrated security, but would this cause all reports to not work? 99% of our reports are working. Or is this a setting in the report itself? Thank you!

Thank you everyone for your input (especially dramadas for the volume of information). Unfortunately, the report still gives the error. I have contacted ASI support but they suggested something else that had no effect. I will likely re-contact them about this issue. Please keep any thoughts coming. Thank you!