But if we have only one instance then no problems, crystal reports works fine. What happens is sometimes when it doesn’t work we see cross image indicating image not found. But we have noticed that the moment we have more than one instance, sometimes crystal reports work and sometimes it doesn’t. The biggest advantage of web roles is that we can have multiple instances.
After that our web application works fine.Ģ. The way we fix this problem is by logging remotely into the instance and manually installing crystal reports. The error we get is: : Could not load file or assembly ', Version=.0, Culture=neutral, PublicKeyToken=692fbea5521e1304' or one of its dependencies. We have noticed that whenever the web roles cloud service restarts(for any unknown reason), the crystal reports installation doesn’t work and the cloud service just goes into loop of starting and restarting, and our web application doesn’t work at all. We have deployed crystal reports on azure web roles. Good luck - it's very satisfying when you get it going.
#Crystal reports runtime 13.0.2 download#
Here are the steps you will need to take:įirst of all you will need to download the SAP Crystal Reports runtime engine for.
#Crystal reports runtime 13.0.2 how to#
How to install Crystal Reports on your Azure web roleįortunately it is still easy with Azure. With Azure, though, if you remote into the machine and install it, it will work fine until your deployment is redistributed to another machine which it will do at some point due to the nature of cloud computing. This isn't a problem with regular hosting since you can just install Crystal Reports on each of your servers and off you go. The problem is that you need to install the Crystal Reports runtime. If you try to run a Crystal Report in your ASP.NET site without the Crystal Reports runtime installed you will receive a "" with description "The Report Application Server failed". Here is a step by step guide on how to make an ASP.NET project that uses Crystal Reports run successfully on Azure.