I am getting the following error after deploying my web application to a 2008 server...
Parser Error Message: Could not load file or assembly 'CrystalDecisions.Web, Version=10.5.3700.0, Culture=neutral, PublicKeyToken=692fbea5521e1304' or one of its dependencies. The system cannot find the file specified.
Crystal is not installed on the server but the .dll files are deployed. It works on my local. What file do I need to install on the server to get this to work?
If you installed the merge module with you web application look in the GAC (C:\windows\assembly) to see which version of Crystal is installed then change the crystal reference tags in both your web.config and apsx files (bear in mind if it's a different version some features may not work)
Or if you have a spare license install 10.5 on the server using the server install utility:
https://websmp230.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/bobj_download/main.htm
Related
Could not load file or assembly 'CrystalDecisions.Shared, Version=10.2.3600.0, Culture=neutral, PublicKeyToken=692fbea5521e1304' or one of its dependencies. The system cannot find the file specified.
Crystal can be, touchy to deploy and run if it's not your server (e.g. you don't have access to deploy there and possibly make tweaks). If it's your server, not a problem. Go get the Crystal merge modules from sap.com and install them on your server, then you will just need to reference them in your web.config. You may run into other issues with permissions (Crystal in some circumstances uses the C:\Windows\Temp directory to export files which hosted servers will at lot of times prevent you from using, I assume this is a throw back to the fact their codebase dates back to the Windows 3.x era).
I'm going to provide the links to the downloads page at SAP:
http://wiki.scn.sap.com/wiki/pages/viewpage.action?original_fqdn=wiki.sdn.sap.com&pageId=56787567
You're using version 10.2 (which is pretty old, Crystal is pretty good about backwards compatibility so if you're in a pinch you can use newer Crystal DLL's and they should export your reports fine).
I've go an ASP.net sites that connect to Oracle 11. That works.
Now I'm trying to have a site that should connect to Oracle 10.2, but I can't find the necessary ODP.Net libraries.
I've downloaded the ODAC components for Oracle 10 from Oracle, but it crashes when I try to install it (Maybe it's because of the previous files I have for 11g).
When I try to use the Oracle 11 libs, I get:
Could not load file or assembly 'Oracle.DataAccess, Version=4.121.1.0, Culture=neutral, PublicKeyToken=89b483f429c47342' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)
I can't find another place to download the necessary libs. Any pointers?
You don't need ODAC 10.2 to connect to a 10.2 Database. Any ODAC up to the current 12.1 will work.
What may be happening is:
1) The application has a dependency on ODP.NET 12.1. The error message suggest this. Try installing ODP.NET 12.1.
2) You aren't installing the correct bitness (eg IIS is 64 bit so you need ODAC 64 bit)
3) You aren't doing a proper install and are just copying files and are either missing some of them, or missing a configuration step. Try running the installer (OUI or XCopy) if you are not.
You can get 64 bit ODAC from here:
http://www.oracle.com/technetwork/topics/dotnet/downloads/index.html
I hosted my application on vertual dedicated server.(windows 2008 r2)
All the crystal reports are running on the local host.but after hosting application, reports are not working.I installed "CRRuntime_64bit_13_0_1" on the server.error message as below.
Could not load file or assembly 'log4net, Version=1.2.10.0, Culture=neutral,
PublicKeyToken=692fbea5521e1304' or one of its dependencies. The system cannot find the
file specified.
Please help me to solve this.
Log4net is an error reporting tool and is independent of Crystal Reports.
So, at risk of asking the obvious here but do you have the correct version of the log4net DLL in the Bin folder of your installed app?
I have a few web applications running on the same server. Recently I added crystal reports for VS 2010. I thought to use new reports for several of projects but not all. Other projects uses the older version of crystal reports
So I modified the web.config of the required projects. I downloaded runtime on both my development machine and server. So now I have both versions of asseblies (v 10 and v 13) in GAC. I have .NET 4.0 on both macines as well.
It has worked on development machine
However, when I run the same projects on server it raises an error.
CS0433: The type 'CrystalDecisions.CrystalReports.Engine.ReportClass' exists in both 'c:\WINDOWS\assembly\GAC_MSIL\CrystalDecisions.CrystalReports.Engine\10.5.3700.0__692fbea5521e1304\CrystalDecisions.CrystalReports.Engine.dll' and 'c:\WINDOWS\assembly\GAC_MSIL\CrystalDecisions.CrystalReports.Engine\13.0.2000.0__692fbea5521e1304\CrystalDecisions.CrystalReports.Engine.dll'
I am wondering why it works on my development machine and does not on server ? Do I have to configure something on server to make it happen ? Or do I need to add in someting in web.config file ?
If someknow knows it, please let me know.
Thanks in advance for your help.
I had the same problem and fixed it by commenting/deleting assembly references which refer to version 10.5.... in web.config. In addition I had to change manually correct version to register assembly="CrystalDecision.... in the .aspx file where I use Crystal report components.
I get following error when deploying on test server with II6 and Framework 3.5 SP1 installed.
The located assembly's manifest
definition does not match the assembly
reference
My development machine is a 64bit pc with Visual Studio 2008.
Any suggestions?
Looks as though the .net assembly is unable to find the correct version that you are after. Make sure you put the assembly definition in the GAC. You may need to look at the GAC and remove the old version and then rebuild.
In other words, go to your production server and look for any assemblies (.dll files) that are currently loaded on that server. The version on your production server may not match the reference of your local machine's project.
Once you find it remove it and replace it with what your application is using.