Products

Evoq Content Overview Content Creation Workflow Asset Management Mobile Responsive Personalization Content Analytics SEO Integrations Security Website PerformanceEvoq Engage Overview Community Management  Dashboard  Analytics  Member Profile Gamification Advocate Marketing Community Engagement  Ideas  Answers  Discussions  Groups  Wikis  Events Mobile ReadyDNN Support PackagesEvoq: CMS FeaturesEvoq OnDemandCompare DNN's CMS Products

Solutions

Content Management SystemMulti-Channel PublishingDigital MarketingOnline Community ManagementIntranet Software SolutionOur CustomersPrime

Resources

Test DrivesSchedule A DemoDocumentation CenterWebinarsWhite PapersProduct ManualsRequest PricingData SheetsCase StudiesEvoq Preferred Products Content Management Ecommerce Forms Identity Management and Authentication Site Management Social Themes

Partners

DNN Partners Partner Directory Become a DNN Partner Partner Program Overview  Hosting  Implementation  ISV  Training  Competencies

Community

Participate Ask a Question Forums Community Showcase DNN MVP  Program Overview  Lifetime MVPs  Honorary MVPs Subscribe to DNN Digest Advisory Groups  Awareness Advisory Group  Developer Advisory Group  Partner Advisory Group  Technology Advisory GroupLearn Documentation Wiki Community Blog Video Library Project History Development RoadmapDownload DNN Store Language Packs Manuals Nightly BuildsSecurity Policies Security Center

Blog

About

News Press Releases News Coverage Press KitCareersContact DNN

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...SQL Server error 15369SQL Server error 15369
Previous
 
Next
New Post
10/27/2010 10:33 PM
 
Boris


Joined: 9/3/2010
Posts: 10
Hi, I am a realtively new user and I hit this error for several days now. Think that I tried everything...
I had working site on the localhost. Then I upgraded version to 5.5.1, hit an error, made many other changes and eventually came to this SQL Server error 15369.
It means "Failed to generate a user instance of SQL Server due to a failure in impersonating the client."

I configured my system using all the recommendations from this forum. I have IIS 7.5. DNN running in its own website. Windows authentication is enabled. Anonymous authentication is enabled and uses ApplicationPoolIdentity. App pool is called DotNetNukePool. It uses .NET v4.0, Integrated pipeline, and ApplicationPoolIdentity.

DNN folder, App_Data folder, DotNetNuke.mdf and DotNetNuke.ldf all give IIS AppPool\DotNetNukePool full access.

SQL Server Express 2008 has login and user IIS AppPool\DotNetNukePool. The user has db owner rights. My Windows account also has full rights. DotNetNuke.mdf is attached in Management Studio.

But when I go to my Home.aspx page which used to work before all my system changes, the wizard starts and it ends with this 15369 error. What am I missing?! Can anybody help?

Thank you,

Boris.
Boris
 
New Post
10/27/2010 10:55 PM
 
Matthias Schlomann


Joined: 8/10/2003
Posts: 3594
I hope you did use the upgrade package and not the install or source package to upgrade your instance.  If you do not have used the upgrade package you have to modified the web.config file manuelly.  Transfering the 2 Connection Strings, MaschineKey, databaseOwner and ObjectQualifier and perhaps some of the WSP module paths fron the old web.config to the new web.config file.

If not I hope you still have a backup of your previous web.config file!  The MaschineKey is the encryption for your Database!
Regards
Matthias
DNN MVP
www.aarsys.de
Metro7 Skin
ShoutCastStats Module for DNN
 
New Post
10/27/2010 11:01 PM
 
Boris


Joined: 9/3/2010
Posts: 10
Thanks,

Yes, I used upgrade package.

I have the same connection strings I had before: "Data Source=HOME\SQLEXPRESS;AttachDbFilename=|DataDirectory|DotNetNuke.mdf;Integrated Security=True;User Instance=False"

And I cannot go back. I have to either figure what I am doing wrong or just recreate the whole thing. But I don't want to do that because I have .mdf with all data which opens in SQL.
Boris
 
New Post
10/27/2010 11:13 PM
 
Boris


Joined: 9/3/2010
Posts: 10
Mathias,

I checked and 2 Connection Strings, MaschineKey, databaseOwner and ObjectQualifier are all the same. I changed folder and .mdf file permissions, application pool and some other IIS settings according to the best advise from the forum experts.

Boris
 
New Post
10/28/2010 8:33 AM
 
William Severance


www.wesnetdesigns.com
Joined: 2/18/2005
Posts: 3253
Although the following blog entry is four years old, I believe that you are seeing this same issue after attaching to DotNetNuke.mdf using SQL Server Management Studio:

http://www.dotnetnuke.com/Community/B...

The basic point to be gained from the blog and comments is that once you have attached to DotNetNuke.mdf outside of DotNetNuke, you should modify your connection strings (2) to follow the format used when connecting to a non-Express SQL Server 2005 or 2008 database. It is for this same reason especially when developing extensions that I never use the included DotNetNuke.mdf but always create a new Express database using SSMS and connect to that as if it were a non-Express SQL Server database.
Bill, WESNet Designs
Team Lead - DotNetNuke Gallery Module Project (Not Actively Being Developed)
Extensions Forge Projects . . .
Current: UserExport, ContentDeJour, ePrayer, DNN NewsTicker, By Invitation
Coming Soon: FRBO-For Rent By Owner
 
 Page 1 of 2
12Next 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...SQL Server error 15369SQL Server error 15369


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out