RDLC Native Error 255 - asp.net

I have an ASP.Net site running on 4.5.2, using the report viewer control. All of a sudden on our server, we are getting
An unexpected error occurred while compiling expressions. Native
compiler return value: ‘255’.
This is occurring for all of our reports (Most of which haven't been modified in over a year). I am trying to identify what potentially changed and is causing this and am coming up short.
We are on Windows Server 2012.
I have found some articles pointing to an issue that occurs with some security patches. We had 4.6 installed on the server so I updated to 4.6.1 and still same issue occurs

So turns out that if you had installed some security patches then installed .net 4.6, it breaks the VB compiler.
I had to remove those two patches as indicated here.

Related

Is Possible to Run Multiple Versions of Crystal Reports Runtime on the Same Server?

I am using Visual Studio 2017 to develop an ASP.NET Core application which uses the version of Crystal Reports that's on SP22. I will be deploying this application onto a Windows 2008 Server which already has another ASP.NET application which uses the version of Crystal Reports that's on SP17.
If I install the SP22 runtime on that server, will my existing application break or will they be able to run side by side without issues?
This article talks about installing multiple versions of Crystal Reports for development purposes, but that's not that what I'm asking here. I'm talking about runtime only, not development.
This question says we can install multiple Crystal Reports runtimes without issues, but it's too old and I'm wondering if things have changed since then. Especially since my existing application targerts .NET framework 2.0 and the new one will target .NET Framework 4.7.1
This question, asked here about 4 years ago, still leaves me in the dark.
As I understand, the .NET CLR 2.0 is no longer supported by Crystal Reports (see this document, page 9). My existing application uses that runtime and I can not update it right now, thus I need to make sure that installing the new Crystal Reports runtime (the one on SP22) will not break that application.
Is it safe for me to install the latest Crystal Reports runtime on the Windows Server without fear of breaking my existing application?
Note: I asked this question in the Crystal Reports community last week and have gotten no response. I was hoping someone here would have some experience in the matter and would shed some light.
Thank you
The article from SAP supports you pointed out https://apps.support.sap.com/sap/support/knowledge/public/en/1216278
applies not only for development purposes; it clearly explains which version can be installed on the same computer without issue :
Basically : each major can be installed on the same machine , but only one version of each major , since Crystal Reports 9.
So, if this is correct, you should not face any issue. I recommand nevertheless that you try before (test server, VM...) modifying your production server

Pages won't load - only on my computer

Created a asp.net 5 project with another team member and works on everyone's computer but mine. I get "Failed to load resource: the server responded with a status of 500 (Internal Server Error and the web page is blank.
I thought maybe I was missing a .net version but when downloading .NET Framework 4.6 it says ".NET Framework 4.6 or a later update is already installed on this computer."
If someone could point me in the right direction it would be a lot of help! Thanks!
The error code is very general in that some error happened in your code that stopped the execution of the webpage.
If you are running the webpage in debug mode from Visual Studio on your computer, VS should have stopped on the line of code containing the error.
If, for some reason, Visual Studio does not stop on the error, you can also look in Windows Logs -> Application. It should appear as an Asp.Net Warning with details regarding the error.
See Log #3:
http://blog.leansentry.com/the-server-logs-you-need-to-know-to-fix-any-iis-aspnet-error/
I figured out my problem! I had a dependency issue in my project.json file.
"Oracle.ManagedDataAccess": "12.1.2400"
"FluentNHibernate": "2.0.3"
"NHibernate.Caches.SysCache": "4.0.0.4000"
These packages didn't support dnx 5.0 so they couldn't be in the default dependencies section. They needed to go under dnx451 -> dependencies.

Error while running asp.net apps in Visual Studio 2015

In my company I'm running Visual Studio 2015 Enterprise and just recently upgraded to Windows 10. Unfortunately, now I can't run any web project using versions of asp.net earlier than 5 (owin/katana) - always getting error :
"Could not load file1or assembly 'XXX' or one of its dependencies.
The process cannot access the file because it is being used by another
process. (Exception from HRESULT: 0x80070020) ".
Now, I've found a few posts like this and the answer is mostly that some other application is running on port 80, 8080 etc blocking visual studio's iis express. The problem is that I get this error regardless of port I'm using (even on some random 34535 etc).
The interesting part is that when I run kestrel (app on asp.net 5) it works and runs fine without any error.
Anyone has any ideas ?
Okay, so I had this issue and resolved it by uninstalling Panda antivirus, which presumably was locking the assemblies for just long enough to interfere with loading them some of the time.
If anyone else is having this issue, and there is definitely an assembly that won't load (as opposed to a port that's already been bound to) then try checking your antivirus!

Crystal Reports and Visual Studio 2010 Error: Unsupported Operation

I Googled for this error, and found many links on SAP as well as StackOverflow, but none of these seem to answer my specific problem.
I have developed a web application using VS 2010, ASP.NET 4.0 and Crystal Reports. I have deployed this application on Windows 2003 R2, Enterprise Edition, SP 2, 32-bit, on IIS 6. I have installed Crystal Report Distributable 32-bit, Version - 13.0.8.1216, on the server. The data source is Oracle 11g XE, on a separate server
When I browse the report from the browser (IE, FF), the reports are visible in the viewer for some time. The problem is after some time, I start getting the following error:
Unsupported Operation. A document processed by the JRC engine cannot be opened in the C++ stack
As suggested in many solutions, i have checked the availability of the report files(.rpt) and they are available on \Reports folder. The aspnet_client folder is also available which has a crystalreportviewer13 folder inside aspnet_client\system_web\4_0_30319
I have no clue, why it will work perfectly fine initially, but later it will start giving this error. I thinks it is probably when I try to access the application concurrently from 3-4 different machines. I replicated this behaviour once.
Now if restart the server machine, it again works fine. Restarting just IIS does not help
Would appreciate any help, as I am at my wits end to find a solution. I will readily provide any other information if required.

Asp.net published web site: The specified module could not be found. Exception from HRESULT: 0x8007007E

I'm having a problem when browsing a published site on local iis7 (on windows 7).
When browsing the asp.net site through VS2008 with F5 (dev iis) it works fine. When publishing it and browsing, I get a:
Server Error in '/MySite' Application.
The specified module could not be found. (Exception from HRESULT: 0x8007007E)
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: System.IO.FileNotFoundException: The specified module could not be found. (Exception from HRESULT: 0x8007007E)
Stack trace offers no clue on the problematic dll either. I copied the same published folder to a different machine (also with windows 7 32bit and iis 7) and it works.
Since this is a fresh install of iis on my machine, I verified the matching selected items in "Turn Windows Features on/off". After noticing the issue I also ran the "aspnet_regiis" util, but the problem remains.
The web site includes several external dlls (native and managed) and they all appear in the published bin folder (which is identical to the development bin folder)
Any insights?
Cheers,
Shay
As gleaned from this thread: http://social.msdn.microsoft.com/forums/en-US/netfx64bit/thread/f609f52e-00f6-4ada-9d6e-7129b85d3d4d/, as mentioned toward the bottom of the thread (second to last post as of right now), our problem was a "rogue" dll, Microsoft.SqlServer.Replication.dll. We simply removed the dll and no more error. Additionally, as no project in the solution referenced this dll, I simply removed it from the bin file and subsequent builds/publishes do not add the dll. I have no idea how the dll got in the bin file in the first place. A college prank, maybe.
Native dlls are supposed to be locatable in the PATH. Problem was they were under the User PATH and not the System PATH, so it worked fine through the VS but not through the IIS. I added the dll folder to the system PATH and everything worked...
A long shot in most cases but check you have good .NET Framework libraries. Was getting nothing from old Framework 2.0 website maintained with VS 2005 running on IIS 6 except plain text in browser window stating the error. Fiddler and Firebug reveled nothing. Started checking this, that and the other thing. Perhaps when wondering about using aspnet_iisreg that the C:\Windows\Microsoft.NET\Framework\v4.0.30319 folder was discovered to have only a handful of files. Doesn't make a lot of sense, the applications were 2.0 but there is some cross application communication and several libraries so maybe some are run as 4.0 or it might be that IIS will try to use some things from the highest version of .NET Framework available.
A co-worker more knowledgeable about servers repaired the 4.0 Framework with the stand alone installer from here.
Runs well now.
This error occurred for me when the .Net Framework on the target server was only 4.5.2 and a recently upgraded Nuget package required 4.7.2. To temporarily solve it, we downgraded the Nuget library to a previous version that did not require 4.7.2 until we can upgrade the server library.
This was in spite of our project properties having .NET Framework 4.5.2 selected as a target framework.

Resources