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 ...Can Not Logon as Admin of DotNetNuke 4.0.2 as IIS Web Site (Works fine as a virtual directory)Can Not Logon as Admin of DotNetNuke 4.0.2 as IIS Web Site (Works fine as a virtual directory)
Previous
 
Next
New Post
3/16/2006 9:51 AM
 
Craig Holdheide

Joined: 1/12/2006
Posts: 12

Ok, this problem has really stumped me!

I created two instances of DotNetNuke 4.0.2 on my hard drive.  (C:\DotNetNuke_vd and C:\DotNetNuke_ws)  After extracting the files to there respective folders I set the file permissions for each folder to allow the ASPNET full access to each folder.  I am using the Microsoft Windows 2000 Advanced Server operating system, IIS 5.1, and Microsoft SQL Server 2000.

Next, I went into IIS and created a virtual directory to the C:\DotNetNuke_vd\Website\ folder (http://localhost/dotnetnuke_vd).  I also created a new web site to the C:\DotNetNuke_ws\Website\ folder (http://DotNetNuke_TST:81).  I also set the default document for each site to Default.aspx.  I then ensured that each site was set to use .NET v2.0 under the ASP.NET tab in IIS.

Next, I created two separate databases for each site instance respectively (DotNetNuke_vd and DotNetNuke_ws).  After creating both databases I then created two separate users to access the databases respectively (dnnadmin_vd and dnnadmin_ws).  After both usernames were created I then set the default database to the user names respectively.  I then sent access to there respective databases and granted each user db_owner access to there respective databases.

Next, I went into each websites directory and renamed the Release.config to web.config.  I then set the following settings for the virtual directory DotNetNuke web site:

<connectionStrings>
<!-- Connection String for SQL Server 2005 Express -->
<!-- <add
name="SiteSqlServer"
connectionString="Data Source=.\SQLExpress;Integrated Security=True;User Instance=True;AttachDBFilename=|DataDirectory|Database.mdf;"
providerName="System.Data.SqlClient" />-->
<!-- Connection String for SQL Server 2000/2005-->
<add name="SiteSqlServer" connectionString="Server=DotNetNuke_TST;Database=DotNetNuke_vd;uid=dnnadmin_vd;pwd=mypassword;" providerName="System.Data.SqlClient" />
</connectionStrings>
<appSettings>
<!-- Connection String for SQL Server 2005 Express - kept for backwards compatability - legacy modules -->
<!-- <add key="SiteSqlServer" value="Data Source=.\SQLExpress;Integrated Security=True;User Instance=True;AttachDBFilename=|DataDirectory|Database.mdf;"/>-->
<!-- Connection String for SQL Server 2000/2005 - kept for backwards compatability - legacy modules-->
<add key="SiteSqlServer" value="Server=DotNetNuke_TST;Database=DotNetNuke_vd;uid=dnnadmin_vd;pwd=mypassword;" />
<add key="InstallTemplate" value="DotNetNuke.install.config" />
<!-- Alternative Install Templates (included in package)
<add key="InstallTemplate" value="Club.install.config" />
<add key="InstallTemplate" value="Personal.install.config" />
<add key="InstallTemplate" value="SmallBusiness.install.config" />
-->
<add key="AutoUpgrade" value="true" />
<add key="InstallMemberRole" value="true" />
<add key="ShowMissingKeys" value="false" />
<add key="EnableWebFarmSupport" value="false" />
<add key="EnableCachePersistence" value="false" />
<add key="InstallationDate" value="3/14/2006" />
</appSettings>

 

Next, I did the same thing for the website version.

<connectionStrings>
<!-- Connection String for SQL Server 2005 Express -->
<!--<add
name="SiteSqlServer"
connectionString="Data Source=.\SQLExpress;Integrated Security=True;User Instance=True;AttachDBFilename=|DataDirectory|Database.mdf;"
providerName="System.Data.SqlClient" />-->
<!-- Connection String for SQL Server 2000/2005-->
<add name="SiteSqlServer" connectionString="Server=DotNetNuke_TST;Database=DotNetNuke_ws;uid=dnnadmin_ws;pwd=mypassword;" providerName="System.Data.SqlClient" />
</connectionStrings>
<appSettings>
<!-- Connection String for SQL Server 2005 Express - kept for backwards compatability - legacy modules -->
<!-- <add key="SiteSqlServer" value="Data Source=.\SQLExpress;Integrated Security=True;User Instance=True;AttachDBFilename=|DataDirectory|Database.mdf;"/>-->
<!-- Connection String for SQL Server 2000/2005 - kept for backwards compatability - legacy modules-->
<add key="SiteSqlServer" value="Server=DotNetNuke_TST;Database=DotNetNuke_ws;uid=dnnadmin_ws;pwd=mypassword;" />
<add key="InstallTemplate" value="DotNetNuke.install.config" />
<!-- Alternative Install Templates (included in package)
<add key="InstallTemplate" value="Club.install.config" />
<add key="InstallTemplate" value="Personal.install.config" />
<add key="InstallTemplate" value="SmallBusiness.install.config" />
-->
<add key="AutoUpgrade" value="true" />
<add key="InstallMemberRole" value="true" />
<add key="ShowMissingKeys" value="false" />
<add key="EnableWebFarmSupport" value="false" />
<add key="EnableCachePersistence" value="false" />
<add key="InstallationDate" value="3/14/2006" />
</appSettings>

After setting all of this up I then navigated to http://DotNetNuke_TST:81 to install DotNetNuke.  After that was installed I then installed the virtual directory version by navigating to http://localhost/DotNetNuke_vd/.  Both versions installed just fine.

Now, since I had both versions installed I then navigated to both installations of DotNetNuke.  Both displayed without any problems.  I then went to logon as admin to each of the DotNetNuke sites.  After logging on to http://localhost/DotNetNuke_vd/ I was able to see the admin toolbar at the top of the web page and I was also allowed access to the admin menu which allowed me to make site changes.  Next, I logged on to http://DotNetNuke:81.  After logging on the site I did not see the admin toolbar at the top of the web page and I did NOT see the admin menu.

For the life of me I can not understand why I was not given the admin menus in both cases after logging on as admin.  To check into this problem even further I did a Beyond Compare on both directories only to find that the only real difference was the usernames, directory locations, and databases in the web.config file.  I then ensured that the directory permissions were correct and the same.  I then did a database comparison on DotNetNuke_vd and DotNetNuke_ws with my Red Gate SQL Data Compare and found that the only differences were GUIDs and dates.  Can anyone explain to me why I am having this problem?  I would really like to get this working but unfortunately I have been unable to go any further because of this problem.  Please help me.  I am sure other users are also having this problem as well.  Any help would be appreciated.

Craig Holdheide

 
 
 Page 1 of 1
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Can Not Logon as Admin of DotNetNuke 4.0.2 as IIS Web Site (Works fine as a virtual directory)Can Not Logon as Admin of DotNetNuke 4.0.2 as IIS Web Site (Works fine as a virtual directory)


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