I have the same problem as outlined below. CrystalReport11_5_NET.msi will not install. It gives the error message "This software package can only be installed on systems that has installed .Net 1.0 or 1.1. Needless to say, 1.1 is installed. Does any one have a simpler solution than below?
Thanks,
Robert T
http://forums.msdn.microsoft.com/es-ES/vscrystalreports/thread/598537d5-03dd-460c-9696-60717c2dc2f4/
We currently have a case where we are supporting multiple versions of our product on the same web server (a windows 2003 server). However, we have 2 versions of our application on the same server, but one is in ASP.nET 1.1 and the other is in ASP.nET 2.0. Our applications are fine and can co-exist ok on the server. They both use Crystal REports XI, Relesae 2, which supports both 1.1 and 2.0.
Our developer machines run just fine wtih both products and crystal reports, but the problem we are having is deployment. When we install the runtime redistrubutale for ASP.nET 2.0 on the machine a file(CrystalReports11_5_NET_2005.msi) then our ASP.NET 2.0 application works fine. However, when we install the crystal runtime redistributable fro ASP.nET 1.1 a file (CrystalReports11_5_NET.msi) windows 2003 server will not let us install it, it gives us an error saying that "This software package can only be installed on systems that has .NET 1.0 or 1.1". Which of course this server has, because our application in 1.1 runs jsut fine.
2 questions.
1. Can Crystal Reports XI Relesae 2 co-exist on a windows 2003 server for BOTH the asp.net 1.1 and asp.net 2.0 version?
2. Has anyone encountered this and resolved this?
Thanks
-
I believe the only way to get this to work is to uninstall the 2.0 framework, install the XIr2 for 1.1 framework msi file, install the 2.0 framework, then install XIr2 for the 2.0 framework.
-
Can't do the uninstall stuff because I got SQL Server 2005 and other .NET 2.0 apps running on the server. I got it to work by copying the .NET 1.1 versions of the Crystal DLL files (e.g. CrystalDecisions.CrystalReports.Engine.dll) from my PC to the server in the corresponding directory and then adding them to the assembly cache with the 1.1 Configuration tool. Don't forget the xxx.resources.dll files in the "en" directory also. In my case, I just needed to get the 1.1 stuff working. This is really bad and just adds another Crystal Reports horror story to my already very long list (I've been using Crystal for almost 15 years).