We recently re-located a DNN site from shared hosting to a dedicated server and we are having problems getting the blog module to work.   Currently running DNN 4.3.5

Error Message

Error: test is currently unavailable.
DotNetNuke.Services.Exceptions.ModuleLoadException: Failed to generate a user instance of SQL Server due to failure in retrieving the user's local application data path. Please make sure the user has a local user profile on the computer. The connection will be closed.

Senario

The module seems to be trying to access the app_data folder which we are not using.   The site is using a local instance of SQL Server express(machinename\sqlexpress) and that is where the blog data has always been stored.  I ran query profiler and can tell that it is not even touching the SQL Server instance for anything blog related prior to throwing this error.

All connection strings in web.config point to our local SQL Server instance and the rest of the site works just fine. 

I am assuming this is a simple fix but having not a lot of experience with DNN I have been unable to resolve this.

Tips, Suggestions and Troubleshooting ideas are welcomed. 

Chris Farrell

That resolved the problem.  I feel stupid now.  I was aware of this and did actually update both connection strings before realizing the config file I had but then we had a different problem and I ended up reverting the config file to a version prior to making that change.

Thanks for the quick response

Chris Farrell

I had the exact same issue as Chris... i though about that "other" legacy connection string... and then happily dug in to the Bin folder to see of the Blog dll was present.. thought about the SQL users i had on the server... - Doh! I now feel as silly as Chris for not checking the legacy connecection string first. Ho Hum! All is well and good now.

An excellent diagnosis and cure ! - Nice one Antonio !