ASP.NET 3.5 and KB2533623, KB2507938

If I install KB2533623 or KB2507938 on Win 7 or Win 2008, it kills my ASP.NET 3.5 application. Actual error that I get when loading the project:

Invalid memory access. (Exception from HRESULT: 0x800703E6).

I don't have a full stack trace, but the error comes from calling LoadAllAssembliesFromAppDomainBinDirectory() . Now MS updates have made changes to the way "unsafe libraries" are loaded. I guess this is causing me a problem. Removing these 2 updates will solve the problem. This is not a machine-related problem because it happened on a total of 6 machines in two operating systems and is managed by three different groups (so this is not just a bad image or something else).

Assuming I need to protect my libraries, are we talking about signing them? And if the third-party library is not signed, then what? Is there a way to tell ASP.NET to accept libraries?

The MSDN article http://msdn.microsoft.com/en-us/library/ff919712(VS.85).aspx talks about setting up directories for download. If this solves the problem, can I implement it before ASP.NET tries to load all the libraries from the bin folder?

+4
source share
1 answer

Tony, I'm not sure the next solution is for you, but I don't have enough reps to add a comment.

So, some questions and suggestions:
1. Are you getting an HTTP 500 error on the front?
2. Are these dlls in the bin folder of the web application?
If the answer to any of the above questions is yes, try hacking → right-click on the bin folder in Explorer and give [System] \ Users access to the folder (where system is the name of the machine). First try using readonly, then try reading the record.

Typically, your administrator will do this at the production site. Therefore, someone will have to tell us how to "really" solve the problem. You can also try the solution for the user running AppPool.

I had 500 errors with Ajaxcontroltoolkit.dll in the bin folder, and that is how I resolved it.

Hope this helps.

0
source

All Articles