Hi there,
We are facing the following issue,
This issue arise when running the order types report in SL 2011 FP1 SP2 after upgrade. Can you help us with the steps to resolve this?
Thanks,
Karthik
*This post is locked for comments
Hi there,
We are facing the following issue,
This issue arise when running the order types report in SL 2011 FP1 SP2 after upgrade. Can you help us with the steps to resolve this?
Thanks,
Karthik
*This post is locked for comments
You can do the following steps to resolve this issue.
1. Open the report in the CR 2008 designer.
2. Select Database -> Set Datasource Location.
3. Set Datasource Location window will appear and in the replace with section connect to the database and replace these tables with the tables in the current datasource by clicking the update button.
4. After updating close the Set Datasource Location window.
5. Go to 'Database menu' and Click 'Verify Database' and click on ’OK’.
Place the report in Usr_Rpts folder of Solomon Root folder. Hope this will work for this issue.
Thanks
Hi
If the DSN settings configured properly, then try with the following steps.
1) Close the Solomon application
2) Delete the Application and System DSN from control pannel-> ODBC settings
3) Open SL again and try to execute any working report and check with ur report
4) Also check, If any user table/views persists in that report then provide the select / execute access to that custom table / views
Ex:
GRANT SELECT ON CUSTOM-VIEW's-NAME TO PUBLC
Hope this helps
Thanks & Regards
Hi Rick,
Only order types report shown this error message. The ODBC connection seems good. I checked with few other SL 2011 environment there also getting this same message.
Thanks,
Karthik
While this is a pretty general message, I have found that it can be caused by any of the following:
The ODBC definition to the application database is bad. If this were the case, many other reports would give the same error. You can try to delete the ODBC definition and let Crystal Reports recreate it when you launch the report.
You have run out of SQL seats such that Crystal Reports cannot gain access to SQL to open the database tables. Get some users out of SL and see if the problem persists.
A DLL (in memory) has become corrupt. Try rebooting the workstation and see if the issue resolves itself.
André Arnaud de Cal...
292,494
Super User 2025 Season 1
Martin Dráb
231,307
Most Valuable Professional
nmaenpaa
101,156