Crystal Report v10.5 toolbar not visible on Firefox but visible on IE and Chrome

Question

I am using crystal report v10.5 with visual studio 2008 to develop crystal reports.The problem I am facing is with the toolbar which is not visible on Firefox but it is visible on IE and Chrome. I have installed same version on both development machine and on production server which is Crystal report v10.5. My development machine is Windows 7 32bit and production is Windows 2008 64bit.

I have tried solutions mentioned on numerous forums such as

1. Copy the 'aspnet_client' folder from 'C:\Inetpub\wwwroot' to 'C:\Inetpub\wwwroot\your-website-name'.
2. create a new virtual directory in your web site and point it to "C:/Inetpub/wwwroot/aspnet_client".
3. Application pool is to be changed to "Classic" instead of "Integrated".
4. Set the application pool of your application to operate under LOCAL SERVICE permission.

But still I am not able to show toolbar on Firefox.

Configurations:

• Visual Studio 2008
• .Net Framework 3.5
• Crystal Report for runtime 10.5
• Windows Server 2008 64bit

Can anyone point me to the right direction?

Edit- I recently upgraded from Windows 2003 to Windows 2008 and the same version for CR 10.5 was working as expected without any mentioned solutions above.

Thank you

Answer 1

You need to add ClientTarget="uplevel" to the page directive of the aspx file.

<%@ Page ClientTarget="uplevel" ... %>

Answer 2

It seems that there are compatibility issues between CR and certain browsers depending on the version of CR. There is a very helpful post here that has links to a compatibility table. I suggest to check that out and then see if you can maybe upgrade to a different version of CR. Hope that helps.

Answer 3

My application use last Crystal Runtime on x64 server and work on firefox too.

1) If the toolbar is not visible there should be a reason (press F12 in firefox.. what do you see? 404 error? 500 error? Please post it!)

2) Crystal Reports Runtime 13.x IS available for X64 servers too.. There is no reason to use an old runtime containing many bugs resolved in other releases.
You can get it here (get MSI 64 bit - Support Pack 8)

After updating runtime you have to copy the 'aspnet_client' folder again fi you did (new virtual directory in your web site is a better approach)

After updating runtime you could need a little hack to let an application developed with older dll work with new dll. There are few rows you have to put into web.config described here.