We are getting numerous printing issues after our upgrade from SL 7 to SL 2011. Datasource location issues, error kind errors, database errors etc.
Is there a way to fix these issues without going report by report?
Thanks
Chuck
*This post is locked for comments
Chuck,
Anytime SL runs a Crystal Report, it uses a ODBC connection to connect back to the database. For it to work correctly, that ODBC connection needs pointed at the right server/database and be set for "SQL authentication" regardless of the authentication method you use to login to SL. When in doubt, you can delete the ODBC connections and SL will recreate them automatically.
Ok. Thanks.
Why are ODBCs causing issues with SL?
I thought that was an FRx issue.
Chuck
Chuck,
Well, that is one way to fix it! :)
If it does come back though or if you (or anyone else) runs into something similar, I'd try the ODBC connection thing first and then try the SQL profiler trace.
Thanks,
-Mark
Mark
Thanks for your troubleshooting.
They resolved the issue by giving the user a new laptop.
Chuck
Hello Chuck,
Thanks for the screenshot. The 229 error indicates a SQL permissions issue. The question is "why".
If you are using SQL authentication, the process should be using the master80 login to connect to the database and run the report. That user should be the owner of the DB and there should be no permissions issue.
If you are using Windows authentication, the process should be using the E8...... user to connect to the database and run the report. That user should have READ access to all the tables/views in the database and there shouldn't be an issue.
BUT... occasionaly we see it actually using the windows user account (Domain\username) to run the report. That user (unless they are an admin) would not normally have access rights to the database and would lead to the 229 error. The more common way for this to occur is if there is something messed up with the ODBC connections on that machine. That could be machine and user specific so worth checking.
If the machine is a 64bit OS, we want to make sure to look at the 32bit ODBC connections. The best way to tell is to open C:\Windows\SysWOW64\odbcad32.exe. From here, remove any mention of the SL databases under the User and System DSN tabs. Then try the process again.
If that doesn't work:
1 - Run the "sync ownership and security" process in Sl database maintenance. Make sure it runs without error.
2 - Run a SQL trace of the user getting the error. See if you can tell if it's using the E8 user or the windows user to run the report.
-Mark
Mark
Thanks for the feedback.
User and workstation specific. It only happens for one user on one workstation.
For that report, does it appear to be user specific or workstation specific? Also, can you paste in the exact error you are seeing?
Standard report = 01acctdi.rpt for just one user.
Hi
Is it happened only for customized reports or for Standard reports too?
Thanks & Regards
We did run the hot fix. Thanks. Tons of report issues. I got a suggestion to open each report and save it again on new server. Seems like a lot of work.
Share
Report
All responses (
Answers (
