I have a feature that I upgraded from SharePoint 2010 to 2013. This feature uses a connection string from Web.Config for the web application to talk to a Membership database for FBA, to do Entity Framework operations on it. The feature worked in 2010. Now
that I have upgraded the feature, the database connection no longer works. Other parts of the feature I haven't mentioned, including the actual FBA functionality, do work. All the entity framework jazz is in a separate project in the solution and the web application
pool account has more than enough permissions on the actual database in question.
When I attempt to use the feature that is broken I get an error message:
The underlying provider failed on Open
Which is about as helpful as a hole in a boat. Seeing it, though, I tried changing the connection string a few different ways and finally thought to use Debug mode to see if there was an inner exception. There was! This exception told me that "anonymous user" was trying to access the database and that was the no-go point. Much more useful to me than the original error message. My problem, now, though, is that my code hasn't changed between versions and overall I only did things to update the solution to VS2012 and SharePoint 2013. This particular library didn't get changed at all. Why is it running as anonymous, when the App pool is running as UserX? How can I fix this? Did something change between 2010 and 2013?
Matt Olson, MS Content Development Specialist MCITP, MCTS