An Update: I added read permissions for the (limited) group that my test user is in to field '1'. I still encountered the 9021 error. I then remove the group's permissions to field '1' and added the user to a group that has access to all fields on the form but is still restricted to records by row level permissions. I did not get the error.
I am thinking there is a field in the report that my test user does not have permissions to when in the limited group even though they have permissions to the record. I am checking the permission on the fields being pulled by the Report, I'll update if that fixes the issue. Jason On Wed, Sep 16, 2009 at 10:55 AM, Jason Miller <[email protected]>wrote: > I am actually running into the same thing this morning. I have an old > Crystal Report that I am reusing behind a new button and Active Link. If I > run the report from WUT I get the same message. I am checking the ODBC > settings, reports settings and AL settings now. > > The report does run from Mid-Tier but I am seeing a different issue (the > reason I tried it in the User Tool). From the MT the row level permissions > are not being enforced. I open the form as a test user and query for all > records, I get two results. I run the report from the button and I see all > records in the data range that I select. > > I suspect these issue may be related to row level permissions being used on > this form. I'll let you know what I find about the 9021 error. > > ARS 7.5 p2 > MT 7.1 p5 > WUT 7.5 p2 > > Jason > > > On Wed, Sep 16, 2009 at 7:00 AM, <[email protected]> wrote: > >> ** >> >> We’re getting an error condition but I don’t know where to go to look to >> resolve it. Briefly, we bring up an >> >> incident in Incident Management, then click on the “print” button. It >> then brings up a screen that shows an >> >> error box that is titled “Crystal Report Viewer” and contains “Failed to >> retrieve data from the database. >> >> Details: [Database Vendor Code: 9021] and an “OK” button. This is on our >> production server that is just >> >> getting it’s final checkout before going live. This happens in the user >> tool as an admin. It’s >> >> reproducible. >> >> >> >> The Development sever has the options set up the same but it works as it >> should. We thought that >> >> they were set up identically as far as options/choices/ etc. go. Comparing >> the two setups doesn’t >> >> seem to show much, but we’re not sure what we should be looking at/for >> for this one. >> >> >> >> We’re on 7.5, patch 1. >> >> >> >> Any suggestions as to what to check/read/etc. are welcomed. Thanks!! >> >> >> >> >> >> Portions of this message may be confidential under an exemption to Ohio's >> public records law or under a legal privilege. If you have received this >> message in error or due to an unauthorized transmission or interception, >> please delete all copies from your system without disclosing, copying, or >> transmitting this message. >> _Platinum Sponsor: [email protected] ARSlist: "Where the Answers >> Are"_ > > > _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor:[email protected] ARSlist: "Where the Answers Are"
