Menu
I have developed an application using Entity Framework, SQL Server 2000, Visual Studio 2008 and Enterprise Library.
It works absolutely fine locally, but when I deploy the project to our test environment, I am getting the following error: Friends season 1 720p english subtitles download sites.
Unable to load one or more of the requested types. Retrieve the LoaderExceptions property for more information
Stack trace: at System.Reflection.Module._GetTypesInternal(StackCrawlMark& stackMark)
at System.Reflection.Assembly.GetTypes()
at System.Data.Metadata.Edm.ObjectItemCollection.AssemblyCacheEntry.LoadTypesFromAssembly(LoadingContext context)
at System.Data.Metadata.Edm.ObjectItemCollection.AssemblyCacheEntry.InternalLoadAssemblyFromCache(LoadingContext context)
at System.Data.Metadata.Edm.ObjectItemCollection.AssemblyCacheEntry.LoadAssemblyFromCache(Assembly assembly, Boolean loadReferencedAssemblies, Dictionary
2 knownAssemblies, Dictionary 2& typesInLoading, List`1& errors)
at System.Data.Metadata.Edm.ObjectItemCollection.LoadAssemblyFromCache(ObjectItemCollection objectItemCollection, Assembly assembly, Boolean loadReferencedAssemblies)
at System.Data.Metadata.Edm.ObjectItemCollection.LoadAssemblyForType(Type type)
at System.Data.Metadata.Edm.MetadataWorkspace.LoadAssemblyForType(Type type, Assembly callingAssembly)
at System.Data.Objects.ObjectContext.CreateQuery[T](String queryString, ObjectParameter[] parameters)
Entity Framework seems to have issue, any clue how to fix it?
Peter Mortensen
14.2k1919 gold badges8888 silver badges115115 bronze badges
The LightThe Light
12.4k5757 gold badges153153 silver badges246246 bronze badges
34 Answers
12 next
I solved this issue by setting the Copy Local attribute of my project's references to true.
40.6k1818 gold badges105105 silver badges154154 bronze badges
MentoliptusMentoliptus
2,36522 gold badges2121 silver badges3333 bronze badges
This error has no true magic bullet answer. The key is to have all the information to understand the problem. Most likely a dynamically loaded assembly is missing a referenced assembly. That assembly needs to be in the bin directory of your application.
Use this code to determine what is missing.
Ben GripkaBen Gripka
12.1k55 gold badges3535 silver badges3535 bronze badges
One solution that worked for me was to delete the bin/ and obj/ folders and rebuild the solution.
Kenny EliassonKenny Eliasson
Two possible solutions:
14.2k1919 gold badges8888 silver badges115115 bronze badges
William EdmondsonWilliam Edmondson
2,56333 gold badges2525 silver badges3838 bronze badges
As it has been mentioned before, it's usually the case of an assembly not being there.
To know exactly what assembly you're missing, attach your debugger, set a breakpoint and when you see the exception object, drill down to the 'LoaderExceptions' property. The missing assembly should be there.
Hope it helps!
mkormanmkorman
The solution was to check the LoaderException: In my case, some of the DLL files were missing.
Peter Mortensen
14.2k1919 gold badges8888 silver badges115115 bronze badges
DevDev
I encountered this error with an ASP.NET 4 + SQL Server 2008 R2 + Entity Framework 4 application.
It would work fine on my development machine (Windows Vista 64-bit). Then when deployed to the server (Windows Server 2008 R2 SP1), it would work until the session timed out. So we'd deploy the application and everything looked fine and then leave it for more than the 20 minute session timeout and then this error would be thrown.
To solve it, I used this code on Ken Cox's blog to retrieve the LoaderExceptions property.
For my situation the missing DLL was Peter Mortensen
Microsoft.ReportViewer.ProcessingObjectModel (version 10). This DLL needs to be installed in the GAC of the machine the application runs on. You can find it in the Microsoft Report Viewer 2010 Redistributable Package available on the Microsoft download site.
14.2k1919 gold badges8888 silver badges115115 bronze badges
DeanDean
Make sure you allow 32 bits applications on IIS if you did deploy to IIS. You can define this on the settings of your current Application Pool.
Peter Mortensen
14.2k1919 gold badges8888 silver badges115115 bronze badges
MrKhalMrKhal
If you're using the EntityDataSource in your project, the solution is in Fix: 'Unable to load one or more of the requested types' Errors. You should set the ContextTypeName='ProjectNameNameSpace.EntityContainerName' '
This solved my problems..
Peter Mortensen
14.2k1919 gold badges8888 silver badges115115 bronze badges
Luiz Frederico JrLuiz Frederico Jr
Initially I tried the Fusion log viewer, but that didn't helpso I ended up using WinDbg with the SOS extension.
!dumpheap -stat -type Exception /D
Endeavor is a research-based reading series designed specifically for adult learners. This easy-to-use program. Endeavor Student Book 3. Endeavor digital version books free. Endeavor: Cultivate Excellence While Making a Difference - Kindle edition by Scott Perry. Want to know our Editors' picks for the best books of the month? Publication Date: November 17, 2018; Sold by: Amazon Digital Services LLC. Amazon.com: A Fool's Endeavor (901): Janetje Amabilis: Books. If you buy a new print edition of this book (or purchased one in the past), you can. About Us Why Digital? Discounts Contact Request Quote File Upload Booklets Hardcover Books Spiral Bound Books Brochures Perfect Bound Books.
Then I examined the FileNotFoundExceptions. The message in the exception contained the name of the DLL that wasn't loading.
N.B., the /D give you hyperlinked results, so click on the link in the summary for FileNotFoundException. That will bring up a list of the exceptions. Then click on the link for one of the exceptions. That will !dumpobject that exceptions. Then you should just be able to click on the link for Message in the exception object, and you'll see the text.
mikomiko
My instance of this problem ended up being a missing reference. An assembly was referred to in the app.config but didn't have a reference in the project.
SteveCavSteveCav
Another solution to know why exactly nothing works (from Microsoft connect):
14.2k1919 gold badges8888 silver badges115115 bronze badges
Siarhei KuchukSiarhei Kuchuk
3,60311 gold badge2323 silver badges2828 bronze badges
Adding my specific problem/solution to this as this is the first result for this error message. In my case, the error was received when I deployed a second application within the folder of my first application in IIS. Both were defining connection string with the same name resulting in the child application having a conflict and in turn generating this (to me) non-obvious error message. It was solved by adding:
in the connection string block of the child web application which prevented it from inheriting the connection strings of web.config files higher in the hierarchy, so it looks like:
A reference Stack Overflow question which helped once I determined what was going on was Will a child application inherit from its parent web.config?.
Community♦
MatthewMatthew
8,90144 gold badges3535 silver badges6969 bronze badges
Rahul NikateRahul Nikate
5,02344 gold badges2626 silver badges4747 bronze badges
My issue has been resolved after I deleted the redundant assembly files from the Peter Mortensen
bin folder.
14.2k1919 gold badges8888 silver badges115115 bronze badges
user2814851user2814851
In case none of the other answers help you:
When I had this problem, it turned out my Windows service was built for an x64 platform, and I was inadvertently running the 32-bit version of InstallUtil.exe. So make sure you're using the right version of InstallUtil for the platform you built for.
Peter Mortensen
14.2k1919 gold badges8888 silver badges115115 bronze badges
jkindwalljkindwall
2,42111 gold badge1111 silver badges1212 bronze badges
I had a .NET 4.0, ASP.NET MVC 2.0, Entity Framework 4.0 web application developed in Visual Studio 2010. I had the same problem, that it worked on one Windows Server 2008 R2 server but not on another Windows Server 2008 R2 server, even though the versions of .NET and ASP.NET MVC were the same, throwing this same error as yours.
I went to follow miko's suggestion, so I installed Windows SDK v7.1 (x64) on the failing server, so I could run !dumpheap.
Well, it turns out that installing Windows SDK v7.1 (x64) resolved the issue. Whatever dependency was missing must have been included in the SDK. It can be downloaded from Microsoft Windows SDK for Windows 7 and .NET Framework 4.
Peter Mortensen
14.2k1919 gold badges8888 silver badges115115 bronze badges
Mafi OsoriMafi Osori
If you are using Entity Framework, try copying the following references locally.
Change the property 'Copy Local' to 'True' for these references and publish.
Peter Mortensen
14.2k1919 gold badges8888 silver badges115115 bronze badges
SameerPcSameerPc
Other suggestions are all good. In my case, the problem was that the developer box was a 64-bit machine using the x86 location of various APIs, including Silverlight.
By changing the target platform to match the 32-bit server where the web application was being deployed removed the majority of the errors related to not being able to load one or more of the requested types.
Peter Mortensen
14.2k1919 gold badges8888 silver badges115115 bronze badges
rclopezrclopez
I changed the Specific Version Property of the Refrences to false and that helped.
Dov MillerDov Miller
1,03444 gold badges2525 silver badges4141 bronze badges
I had the same issue (but on my local) when I was trying to add Entity Framework migration with Package Manager Console.
The way I solved it was by creating a console application where Main() had the following code:
Make sure the Configuration class is the migration Configuration of your failing project. You will need System.Data.Entity.Migrations to use DbMigrator.
Set a breakpoint in your application, and run it. The exception should be caught by Visual Studio (unless you have that exception type set to not break the debug session), and you should be able to find the info you are looking for.
The missing reference in my case was EFProviderWrapperToolkit.
Peter Mortensen
14.2k1919 gold badges8888 silver badges115115 bronze badges
Peter NagyPeter Nagy
I got this problem when I installed a NuGet package on one of the projects and forgot to update the other project.
I solved this by just making both projects having the same reference assembly.
Peter Mortensen
14.2k1919 gold badges8888 silver badges115115 bronze badges
jayson.centenojayson.centeno
It happened for me also. I solved the problem as follows:Right click Solution, Manage NuGet Packages for Solution.. Consolidate packages and upgraded the packages to be in the same version.
user1760527user1760527
Set 32 bit IIS mode to true, debug mode to true in the configuration file, deleting the Peter Mortensen
temp directory and resetting IIS fixes the issue temporally and it comes back after some time.
14.2k1919 gold badges8888 silver badges115115 bronze badges
johnnyjohnny
Verify that each of your projects is setup correctly in the Configuration Manager.
Similar to William Edmondson's reason for this issue, I switched my Configuration Manager setting from 'Debug' 'Any CPU' to 'Debug' '.NET'. The problem was that the '.NET' version was NOT configured to build ALL of the projects, so some of my DLLs were out of date (while others were current). This caused numerous problems with starting the application.
The temporary fix was to do Kenny Eliasson's suggestion to clean out the bin and obj directories. However, as soon as I made more changes to the non-compiling projects, everything would fail again.
Community♦
cat5devcat5dev
I also got this issue when create new Microsoft Word add-in with Visual Studio 2015. The issue is about I have 2 versions of MS Office, 2013 and 2016. I uninstall MS Office 2013 and then it works.
amzdmtamzdmt
I build a few projects for SharePoint and, of course, deployed them. One time it happened.
I found an old assembly in C:Windowsassemblytempxxx (with FarManager), removed it after reboot, and all projects built.
I have question for MSBuild, because in project assemblies linked like projects and every assembly is marked 'Copy local', but not from the GAC.
Peter Mortensen
14.2k1919 gold badges8888 silver badges115115 bronze badges
IlyaIlya
I had the same error message reported when compiling a Visual Studio package (VSPackage). The whole solution compiles and the error is thrown when the package is being created by CreatePkgDef. Having said that, it is clear that I cannot catch the LoaderExceptions as it is not my application that throws it, but Microsoft's own tool. (Though I am responsible for the confusion of CreatePkgDef.)
In my case the root cause Mgq paradox part 2 save. was that my solution creates a MyDll.dll that has already been registered to the GAC (and they are different), so the CreatePgkDef got confused which one to use and it decided just to throw an error which isn't really helpful. The MyDll.dll in the GAC was registered by the installer of the same product (obviously an earlier version, with /slightly/ different content).
How to fix it
Changing the AssemblyVersion was good enough for me. :)
I hope this was helpful.
Peter Mortensen
14.2k1919 gold badges8888 silver badges115115 bronze badges
ShakaronShakaron
I am able to fix this issue by marking 'Copy Local=True' on all referenced DLL files in the project, rebuilding and deploying on a testing server.
Peter Mortensen
14.2k1919 gold badges8888 silver badges115115 bronze badges
Srinivasa RaoSrinivasa Rao
I had an issue with automap. In the Peter Mortensen
bin folder, the file automap.4net.dll was there, but for some reason the automap.xml and automap.dll weren't. Copying them to the bin directory solved the issue.
14.2k1919 gold badges8888 silver badges115115 bronze badges
alex440alex440
97911 gold badge1212 silver badges3030 bronze badges
12 next
protected by i3arnonNov 23 '14 at 22:41
Thank you for your interest in this question. Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).
Would you like to answer one of these unanswered questions instead? Not the answer you're looking for? Browse other questions tagged c#entity-framework or ask your own question.
After the May 2018 update to Windows 10, most of the users who use Remote Desktop function are facing RDP authentication error, function requested is not supported issue where they get the following error while logging in to a remote computer via RDP.
An authentication error has occurred.
The function requested is not supported
Remove computer: [computername] This could be due to CredSSP encryption oracle remediation.
For more information, see https://go.microsoft.com/fwlink/?linkid=866660
RDP Authentication Error Function Requested Is Not Supported
This is due to a recent vulnerability fixed in Windows 10 and Windows 7. After installing the latest update KB4103727 for Windows 10 Version 1709 and KB4103718 for Windows 7, you will start getting this error.
Quick Summary
4 solutions to RDP Authentication Error Function Requested Is Not SupportedEtabs 2016.2.1 Error Occurred During Showing Of Information Free
Let’s go through some resolutions to this problem.
Solution 1: Install updates on the target computer
The first and the most recommended solution to this issue is to update the target computer on which you are trying to connect remotely. Go to Windows Update and check for updates. Install all the updates specifically related to CVE-2018-0886.
Specifically, if the target computer is running Windows Server 2016, you should install KB4103723 and if you are using Windows Server 2012 R2, then you should install KB4103725.
A server reboot will be required after installing these updates.
If you do not want to update the computer or it’s not in your access then you can try the other solutions listed below.
Solution 2: Using Group Policy
This will apply the group policy immediately and you will be able to use Remote Desktop without restarting the computer.
Solution 3: Using Registry Editor
The same thing can be achieved through Windows Registry. Here are the steps:
Solution 4: Uninstall updates from your computer
Another workaround is to uninstall the updates from your computer. If you are using Windows 10 Version 1709, you should uninstall the update KB4103727 and KB4103718 if you’re running Windows 7. Uninstalling these updates requires the computer to be restarted.
Final words
Although you can use any of the above mentioned methods to resolve this issue of RDP Authentication Error Function Requested Is Not Supported but I recommend that you should either use Solution 1 or Solution 2 for the resolution. What are your thoughts about this?
Must Read Articles:Comments are closed.
|
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |