Could not load file or assembly System.Data.Entity

  • Thread starter Thread starter Steve Wofford
  • Start date Start date
S

Steve Wofford

I am recieving the following. This happens when I moved it from my
development system to our production SBS 2003 w/ latest .net frameworks and
service packs . I developed under XPSP2 and VS2008.

The error is pointing to the Web.Config of my application.

System.Data.Entity was missing from the server, but was on the dev system.
I tried to add, but didnt help:

C:\Program Files\Reference Assemblies\Microsoft\Framework\v3.5

Server Error in '/' Application.
--------------------------------------------------------------------------------

Configuration Error Description: An error occurred during the processing of
a configuration file required to service this request. Please review the
specific error details below and modify your configuration file
appropriately.

Parser Error Message: Could not load file or assembly 'System.Data.Entity,
Version=3.5.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' or one of
its dependencies. The system cannot find the file specified.

Source Error:

Line 47: <add assembly="System.Xml.Linq, Version=3.5.0.0,
Culture=neutral, PublicKeyToken=B77A5C561934E089"/>
Line 48: <add assembly="System.Security, Version=2.0.0.0,
Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A"/>
Line 49: <add assembly="System.Data.Entity, Version=3.5.0.0,
Culture=neutral, PublicKeyToken=B77A5C561934E089"/>
Line 50: <add assembly="System.Data.Entity.Design, Version=3.5.0.0,
Culture=neutral, PublicKeyToken=B77A5C561934E089"/>
Line 51: <add assembly="System.Data.Linq, Version=3.5.0.0,
Culture=neutral, PublicKeyToken=b77a5c561934e089"/>

Source File: D:\Inetpub\wwwroot\GoldmineIntegration\web.config Line: 49

Assembly Load Trace: The following information can be helpful to determine
why the assembly 'System.Data.Entity, Version=3.5.0.0, Culture=neutral,
PublicKeyToken=b77a5c561934e089' could not be loaded.

WRN: Assembly binding logging is turned OFF.
To enable assembly bind failure logging, set the registry value
[HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
Note: There is some performance penalty associated with assembly bind
failure logging.
To turn this feature off, remove the registry value
[HKLM\Software\Microsoft\Fusion!EnableLog].
 
Steve said:
I am recieving the following. This happens when I moved it from my
development system to our production SBS 2003 w/ latest .net

There was no way for you to know it (except maybe by browsing through some
of the previous questions in this newsgroup before posting yours - always a
recommended practice) , but this is a classic asp newsgroup. ASP.Net bears
very little resemblance to classic ASP so, while you may be lucky enough to
find a dotnet-knowledgeable person here who can answer your question, you
can eliminate the luck factor by posting your question to a group where
those dotnet-knowledgeable people hang out. I suggest
microsoft.public.dotnet.framework.aspnet or the forums at www.asp.net.

Oh, wait ... you crossposted ... how many groups? A little beit of everkill
there. Anyways, I'm responding from the inetserver.asp.db group, so if
respondents to this thread could remove that group from the crosspost, it
would be appreciated.
 
Back
Top