Clever_Bob
asked on
Error: Unable to find the requested .Net Framework Data Provider. It may not be installed.
Receiving this error once published to Webyhost4life server (see here http://www.bribie.soccerclubstats.com/)
I guess the problem is with my connection string? Not really sure. I'm also not sure why the error references the physical location of my application on my local PC (where it works fine with an alternative connection string)
Here is the connection string section from my config...
<connectionStrings>
<add name="SQLiteEntities" connectionString="metadata =res://*/M odel1.csdl |res://*/M odel1.ssdl |res://*/M odel1.msl; provider=S ystem.Data .SQLite;pr ovider connection string="data source=~/App_Data/1.080000 .iKeepScor e;"" providerName="System.Data. EntityClie nt" />
</connectionStrings
I guess the problem is with my connection string? Not really sure. I'm also not sure why the error references the physical location of my application on my local PC (where it works fine with an alternative connection string)
Here is the connection string section from my config...
<connectionStrings>
<add name="SQLiteEntities" connectionString="metadata
</connectionStrings
ASKER
thanks for the input.
Do you mean the framework on the server? Its hosted by Webhost4life
I'm using the 'Publish' feature in Visual Studio 2010, so presumably the publishing mechanism is sound
Do you mean the framework on the server? Its hosted by Webhost4life
I'm using the 'Publish' feature in Visual Studio 2010, so presumably the publishing mechanism is sound
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks David - how can they unsupport it though? Can they specifically disable it somehow? Its just a file sitting in the application directory.
One, if it is referencing your local PC, can you make sure that you are uploading the correct files?
Second, this might be an instance where your .net framework is corrupt.
This link explains how you can repair that if it were the problem.
http://support.microsoft.com/kb/306160/en-us