Last post May 24, 2011 03:14 AM by necro_mancer
Apr 14, 2011 07:52 AM|VinceArcher23|LINK
Its been awhile when I last log in to this forum. Not until now that I really need help badly.
Our application was migrated from windows server 2003 to windows server 2008 and also upgraded IIS to 7.0. Though the base code still remain under framework 2.0.
Since it was a 64bit machine we installed a 64bit redistributable package for crystal report.
Now when we test the application, it was wierd that some of the report pops up the logon information from crystal report and some opens as expected.
This is working perfectly on the old environment under windows 2003 and we have been using this for three years already. So if you will answer to use ApplyLogOnInfo to all tables by iteration I have done that already with this old base code.
there is no change done on the code, we just want to make this application work on the new environment.
Do someone encountered this wierd error? Is their any issue with 64 bit redistributable package? Or is there a special procedure in installing crystal report engine in IIS 7.
ANy help would be very much appreciated.
May 23, 2011 03:56 PM|microsoftee|LINK
Use a ReportSource control and set CrystalReportSource control's report file .rpt and set DataSources to SQLDataSource control, set SQLDataSource control commandText to your query.
This is how I deal with it, more details about ReportSource control at MSDN
May 24, 2011 03:14 AM|necro_mancer|LINK
I am not surprised if you have problems migrating CR to Windows Server 2008 environment. Windows 2008 has different policies in permission and if you do not properly configure your CR, you can get this kind of problem
Please follow the guidelines below:
1. Please make sure that the CR version installed on the server MATCHES exactly with the CR version you use on your code.
2. Please make sure the CR assemblies used on your web.config MATCHES with the CR assemblies "recognised" by the server
3. Please make sure LOCAL SERVICE permission is enabled on your application pool
4. HttpHandler is set to "Revert to Inherited"
5. aspnet_client and crsytalreportviewer folders are copied properly to your working folder.
If you follows all the settings above, your CR will certainly load fine on Windows 2008 server. Please mark this response as an "answer" if it helps you. Thank you.