![]() You should use the latest version as it contains bug fixes, security updates, etc. Crystal Report Runtime (Crystal Reports redistributable) has function and libraries which need to exist on the target PC without which reports won’t show up. If you create an application using crystal report, then to run your Crystal Reports application you need to install the crystal report runtime engine on the target machine (Client machine). How to Create Crystal Report using ASP.NET MVC.How to Create Crystal Reports in ASP.NET Webforms.How to Create Crystal Report using Visual Studio.We have a few how-to tutorials which take you through step by step process of creating the report using C#, ASP.NET, and ASP.NET MVC. How to Include Runtime into your application setup.If I run into any in the future I’ll let you know. I’m not sure of any negative side-effects at this point. The scripts are located under Internet Information Services – Web Management Tools – IIS 6 Management Compatibility – IIS 6 Scripting Tools. If you do not have the admin scripts installed, install the from the ‘Turn Windows features on or off’ option in your Control Panel. Open a command prompt and execute: cscript.exe %SystemDrive%inetpubAdminScriptsadsutil.vbs set W3SVC/AppPools/Enable32BitAppOnWin64 true Open a command prompt, go to the non 圆4 framework folder of your choice (for instance C:WindowsMicrosoft.NETFrameworkv9) and execute “aspnet_regiis –enable –i” Enable 32 bit apps for 64 bit IIS Things that did not help to get this problem fixed included removing log4net from the assemblies section of the web.config, kicking my machine around the office and trying to recompile log4net for the 圆4 architecture.Īs far as I have been able to find out, these two steps will get it working: Enable 32 bit ASP.NET IIS integration I tried several things to get my (圆4) IIS, Crystal Reports and log4net to get to play together nicely. ![]() That means it can’t be loaded by IIS, which is 圆4 on this machine. ![]() The Processor Architecture for the log4net assembly is set to x86. Or could it…? Having a second (and closer) look at the log4net assembly in the GAC one thing stood out. Log4net was available in the GAC, with the exact version and PublicKeyToken stated in the error message.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |