jollyreaper
Technical User
Using Crystal Reports and Server XI, accessing a topspeed database via SoftVelocity ODBC driver 4.0. Server is on one machine, Faxsrv, the database is on another, Mainfs. I have an ongoing issue I'm trying to debug and I'm positive it has something to do with the permissions. I have Crystal support working on it, too, but it's a knotty problem.
From all the tech support I've read, most problems in Server/Enterprise boil down to misconfigured permissions. We've already worked through the common permission misconfigurations so I'm now looking at goofball odd ones. We already had some odd errors with the kinds of registry keys required to get inner/outer joins working properly. I wouldn't have believed the solution if I hadn't seen it work myself, it seemed like voodoo -- put registry keys in for Lotus and Microsoft (neither of which I am using) and that will get a completely unrelated driver working properly. At this point, if they suggested sprinking the server with the blood of a freshly killed chicken I'd consider it!
So, running down all the bases, here's what I've confirmed:
1. I can run the same report properly in Developer on both my desktop and server. This tells me:
A) The DSN for ODBC has been setup successfully on both machines
B) The registry keys are succesfully added on both
C) There's no inherent permissions issue for Crystal talking to the other machine
2. I can save reports to Enterprise and run them from those folders with one caveat: static parameters work fine but if I use dynamic parameters, I get errors. It's like I don't have permission to view the List of Values stored on Enterprise, even though said list is updated when I check it in business views. Nevermind that, the report just pukes on me.
3. When logging in as admin, I should have few restrictions in running reports, assuming I haven't dicked around with the admin permissions in the first place. Most genuine "you screwed up the permissions" errors come when dealing with created users and in situations where the admin can view the report but users can't. (True/False? It seems like there are always exceptions.)
3. We tried explicitly putting in the admin account username and password for database connections on the report object. A simple test report I created (dump a couple fields from one table in the database, no joins or fancy stuff) will return the header and footer but no content within the report. That's better than a flat out error but not by much.
4. Fancier reports will give me a table not found error. Looking up that error in the different crystal forums usually returns "check your permissions" suggestions.
5. Page reporting service has also been updated to run with the admin username and password rather than the defaults Cystal shipped with.
So, have I overlooked anything obvious here? My gut instinct tells me that this problem will be in "unusual crazy solution" territory but maybe we've overlooked something embarassingly simple.
Thanks for any and all replies!
From all the tech support I've read, most problems in Server/Enterprise boil down to misconfigured permissions. We've already worked through the common permission misconfigurations so I'm now looking at goofball odd ones. We already had some odd errors with the kinds of registry keys required to get inner/outer joins working properly. I wouldn't have believed the solution if I hadn't seen it work myself, it seemed like voodoo -- put registry keys in for Lotus and Microsoft (neither of which I am using) and that will get a completely unrelated driver working properly. At this point, if they suggested sprinking the server with the blood of a freshly killed chicken I'd consider it!
So, running down all the bases, here's what I've confirmed:
1. I can run the same report properly in Developer on both my desktop and server. This tells me:
A) The DSN for ODBC has been setup successfully on both machines
B) The registry keys are succesfully added on both
C) There's no inherent permissions issue for Crystal talking to the other machine
2. I can save reports to Enterprise and run them from those folders with one caveat: static parameters work fine but if I use dynamic parameters, I get errors. It's like I don't have permission to view the List of Values stored on Enterprise, even though said list is updated when I check it in business views. Nevermind that, the report just pukes on me.
3. When logging in as admin, I should have few restrictions in running reports, assuming I haven't dicked around with the admin permissions in the first place. Most genuine "you screwed up the permissions" errors come when dealing with created users and in situations where the admin can view the report but users can't. (True/False? It seems like there are always exceptions.)
3. We tried explicitly putting in the admin account username and password for database connections on the report object. A simple test report I created (dump a couple fields from one table in the database, no joins or fancy stuff) will return the header and footer but no content within the report. That's better than a flat out error but not by much.
4. Fancier reports will give me a table not found error. Looking up that error in the different crystal forums usually returns "check your permissions" suggestions.
5. Page reporting service has also been updated to run with the admin username and password rather than the defaults Cystal shipped with.
So, have I overlooked anything obvious here? My gut instinct tells me that this problem will be in "unusual crazy solution" territory but maybe we've overlooked something embarassingly simple.
Thanks for any and all replies!