![]() See what data access errors occurred and make note of any additional details provided. What follows are a few suggestions to help you deal with errors you may encounter.įind and save the specific error First examine the Queries & Connections pane (Select Data > Queries & Connections, select the connection, and then display the flyout). It may have been removed or is temporarily unavailable. The server is not responding and may be undergoing maintenance. The file you're trying to access could not be found. ![]() Common remote errors include:Ĭouldn't connect to a service or resource. Check your connection. These types of errors require a different approach. Something has happened in a system that might be across the street, half-way around the world, or in the cloud. Remote However, an error that comes from a remote external data source is another matter entirely. Excel also has improved error handling with clearer messages and context-sensitive links to targeted help topics to help you figure out and fix the problem. These errors are bothersome, but fairly easy to track down, identify, and fix. Perhaps refreshed data caused an error with a function, or the data created an invalid condition in a drop-down list. Local If an error occurs in your Excel workbook, then at least your troubleshooting efforts are limited and more manageable. ![]() Uninstall the application that includes MyDll.dllĬhanging the AssemblyVersion was good enough for me.There are two types of errors that might occur when you refresh data.How to Uninstall an Assembly from the GAC.If the above failed: You can uninstall the old MyDll.dll from GAC.If needed, specify the fully qualified assembly name (for example, "MyDll.dll, Version=1.0.0.1, Culture=neutral, PublicKeyToken=1234567890abcdef") when you reference it in your other projects.// Assuming the old DLL file was versioned 1.0.0.0.Make sure the following attributes are correct: When compiling your project make sure you use a different version number than you used in the previous version located in the GAC.Preferred way: Make sure you use the correct version of MyDll.dll.The MyDll.dll in the GAC was registered by the installer of the same product (obviously an earlier version, with /slightly/ different content). ![]() In my case the root cause 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. (Though I am responsible for the confusion of 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. The whole solution compiles and the error is thrown when the package is being created by CreatePkgDef. I had the same error message reported when compiling a Visual Studio package (VSPackage). Stack trace: at ._GetTypesInternal(StackCrawlMark& stackMark)Īt .ObjectItemCollection.Assembl圜acheEntry.LoadTypesFromAssembly(LoadingContext context)Īt .ObjectItemCollection.Assembl圜acheEntry.InternalLoadAssemblyFromCache(LoadingContext context)Īt .ObjectItemCollection.Assembl圜acheEntry.LoadAssemblyFromCache(Assembly assembly, Boolean loadReferencedAssemblies, Dictionary 2 knownAssemblies, Dictionary2& typesInLoading, List`1& errors)Īt .ObjectItemCollection.LoadAssemblyFromCache(ObjectItemCollection objectItemCollection, Assembly assembly, Boolean loadReferencedAssemblies)Īt .ObjectItemCollection.LoadAssemblyForType(Type type)Īt .MetadataWorkspace.LoadAssemblyForType(Type type, Assembly callingAssembly)Īt .CreateQuery(String queryString, ObjectParameter parameters)Įntity Framework seems to have issue, any clue how to fix it? Retrieve the LoaderExceptions property for more information Unable to load one or more of the requested types. It works absolutely fine locally, but when I deploy the project to our test environment, I am getting the following error: I have developed an application using Entity Framework, SQL Server 2000, Visual Studio 2008 and Enterprise Library.
0 Comments
Leave a Reply. |