January 24, 2007 at 4:24 pm
I am having some sort of permission issue with an OEM version of Crystal Reports, ver 7 (I know, gonna have to dust off a few brain cells) and SQL 2000.
We are moving to new W2K3 Terminal Servers on a new domain but the current SQL will remain on W2K on the old domain which is NT based. Domain trusts are in place and the accounting program has no issue working from the new servers to the SQL databases. Nor do Excel queries.
The users all have a short cut on their desktop that takes them to a directory of shortcuts to the various reports. Both of these reside on the same W2K server. Some of the reports work just fine until the user needs to switch printers. When they try that, they are booted out of CR with no message or error log entry. As Admin, I can change the printer for them and then they can print. This is the same set up that is on the old domain and still works. All I did was point to the same directory.
Other reports appear to run okay and records are returned. But, those that are just fields are printed in the report as expected. The formulas all return zeros. Again, as Admin, I can run the report without issue and see all that the same number of records are returned and the formula data is printed.
I realized that I had been running those from my logon on the old domain. When I ran it from one of the new terminal servers, I also got the zeros in the formula problem.
I have checked the ODBC settings between the two domains and they are the same except that the SQL drivers are different versions on the newer servers.
I have checked the ODBC registry settings and all users have full control. They have all been given full control on the directory permissions to see if that made any difference. It did not.
I suspect it has to do with something to do with permissions in W2K3 and the SQL 2000 but can't figure it out. Again, the SQL server has not been changed, its only be accessed differently. With the new system and domain, comes AD. I have not found anything suspect in there and have loosened it up more than I would like.
Looking for any suggestions at this point. My other resources for Macola (the CR OEM provider) and TS are also shaking their heads in a non positive way.
January 24, 2007 at 4:56 pm
1. Make sure all systems have the same version of MDAC.
2. Are the users using SQL Server authentication logins? Or Windows Authentication logins?
3. If Windows Authentication logins, are the two domains 'trusting' of each other? In other words, do they authenticate users from each other's domain (common domain controller)?
-SQLBill
January 24, 2007 at 5:44 pm
1. MDAC's are different versions. 2.6 on the older domain and SQL and 2.8 on the W2K3. A quick read indicates some incompatibilities.
2. Users authenticate with Windows logons
3. Yes, both domains are trusting
Sounds like I need to work on the MDAC issue.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply