Products

Solutions

Resources

Partners

Community

Blog

About

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 ...Install Error - Possible XP Pro IssueInstall Error - Possible XP Pro Issue
Previous
 
Next
New Post
6/11/2006 10:07 PM
 

Hi folks, I am trying to install DNN3.x on a Win XP Pro SP2 PC at home. This is for a work project. I went through the install document and found that when it comes time to provide .net access to my dotnetnuke folder, I do not see a security tab. Here is a cut out of the doc where it says I should confiure .net access:

4. Set File Permissions

The next step in preparation for installing DotNetNuke is to set the NTFS file

permissions for the Asp.NET worker process. This step is required as DotNetNuke needs

to be able to create directories and files. The User Account that needs to be given

permissions is different depending on which version of Windows you are using.

􀂗 In Windows 2000/IIS5 the account to use is the {Server}\ASPNET User Account,

􀂗 in Windows 2003/IIS6 the account is the NT AUTHORITY\NETWORK SERVICE

User Account.

So in between Sharing and Web Sharing I am missing the security tab in my directory properties. So I cant configur this. I think this is causing the error below. Help is appreciated... Thanks.

 

Server Error in '/DotNetNuke' Application.

Configuration Error

Description: An error occurred during the processing of a configuration file required to service this request. Please review the specific error details below and modify your configuration file appropriately.

Parser Error Message: Access is denied: 'DotNetNuke.XMLLoggingProvider'.

Source Error:

Line 196:				<add assembly="System.EnterpriseServices, Version=1.0.5000.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a"/>
Line 197:				<add assembly="System.Web.Mobile, Version=1.0.5000.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a"/>
Line 198:				<add assembly="*"/>
Line 199:			</assemblies>
Line 200:		</compilation>

Source File: c:\windows\microsoft.net\framework\v1.1.4322\Config\machine.config    Line: 198

Assembly Load Trace: The following information can be helpful to determine why the assembly 'DotNetNuke.XMLLoggingProvider' could not be loaded.

=== Pre-bind state information ===
LOG: DisplayName = DotNetNuke.XMLLoggingProvider
 (Partial)
LOG: Appbase = file:///C:/DotnetNuke
LOG: Initial PrivatePath = bin
Calling assembly : (Unknown).
===

LOG: Policy not being applied to reference at this time (private, custom, partial, or location-based assembly bind).
LOG: Post-policy reference: DotNetNuke.XMLLoggingProvider
LOG: Attempting download of new URL file:///C:/WINDOWS/Microsoft.NET/Framework/v1.1.4322/Temporary ASP.NET Files/dotnetnuke/be580ab2/9ffb9ac7/DotNetNuke.XMLLoggingProvider.DLL.
LOG: Attempting download of new URL file:///C:/WINDOWS/Microsoft.NET/Framework/v1.1.4322/Temporary ASP.NET Files/dotnetnuke/be580ab2/9ffb9ac7/DotNetNuke.XMLLoggingProvider/DotNetNuke.XMLLoggingProvider.DLL.
LOG: Attempting download of new URL file:///C:/DotnetNuke/bin/DotNetNuke.XMLLoggingProvider.DLL.
LOG: Policy not being applied to reference at this time (private, custom, partial, or location-based assembly bind).
LOG: Post-policy reference: DotNetNuke.XMLLoggingProvider, Version=2.0.1.30184, Culture=neutral, PublicKeyToken=null

 

 
New Post
6/12/2006 1:02 AM
 
Turn of Simple File-sharing witch is the default for XP.

1) Browse to any directory.
2) Right click for sub-menu and click on properties.
3) Click on view tab
4) Scroll to bottom and uncheck Simple File-sharing.

This will make the secuirty tab appear when you look at a folder properties and set who has what permissions.
 
New Post
6/12/2006 2:17 AM
 

smehaffie, thanks for the help! That fixed it.

smehaffie wrote
Turn of Simple File-sharing witch is the default for XP.

1) Browse to any directory.
2) Right click for sub-menu and click on properties.
3) Click on view tab
4) Scroll to bottom and uncheck Simple File-sharing.

This will make the secuirty tab appear when you look at a folder properties and set who has what permissions.

 
New Post
6/30/2006 12:44 AM
 

I get this exact same erorr (although it looks for a different dll) while i'm building my custom module. It seemed to only happen when i would modify my SqlDataProvider.vb (in a different project than my module files), but now i'm seeing it more and more.

my current workaround is to stop IIS, kill all locks on the 'C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\Temporary ASP.NET Files' folder, then delete the dnn folder. this works, but is a pain in the butt since it happens every 3 or 4 builds or so.

Oh, the one difference for me is that i am on win 2k3, not XP. I looked for the simple file sharing but it must be somewhere else, or named differently in 2k3.

 
New Post
7/4/2006 1:10 AM
 
Win2K does not have the Simple File Sharing, this is a new feature of XP and is on by default.  By turning simple files sharing off the permissions work the same as Win2k
 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Install Error - Possible XP Pro IssueInstall Error - Possible XP Pro Issue


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