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 StartedNew to DNN Plat...New to DNN Plat...DataProvider ErrorDataProvider Error
Previous
 
Next
New Post
12/1/2010 8:43 AM
 
William Severance


www.wesnetdesigns.com
Joined: 2/18/2005
Posts: 3253
If you are installing DotNetNuke for the first time to learn how it will work for you, I recommend that you use the Install or Web Platform Installer packages, not the  Source package. The Upgrade package is for upgrading an already installed site.

In regards to your error, note that the Source package does not include a web.config file. The included release.config or development.config file must first be copied or renamed as web.config. Also, after doing that step, the Source package's VS 2010 solution must be loaded into VS 2010 and built before you can continue with the installation.
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
 
New Post
12/6/2010 1:05 AM
 
Maithree Duggirala


Joined: 11/29/2010
Posts: 15
Building it in VS2010 sloved most of the errors, but i am left with one
The Error Description is below.

Unable to copy file "bin\DotNetNuke.Services.Syndication.xml" to "..\..\..\Website\bin\DotNetNuke.Services.Syndication.xml". Could not find file 'bin\DotNetNuke.Services.Syndication.xml'.

in file DotNetNuke.Syndication.csproj
at Line 113 ,column 5 ,Project DotNetNuke.Syndication

I included the Components\Syndication folder in DotNetNuke.Library project and build it ..which was successful, but the building the web site still throws this error

When i run the site I get a Unauthorised access error saying

\Website\Portals\_default\Logs\LogFailures.xml.resources' is denied. The Windows User Account listed below must have Read/Write Privileges to this path.

I checked the Integrated windows authentication in the directory security tab of the vrtual directory.Write permission is also given.
 
New Post
12/6/2010 10:12 PM
 
William Severance


www.wesnetdesigns.com
Joined: 2/18/2005
Posts: 3253
I have received the same Unable to copy file "bin\DotNetNuke.Services.Syndication.xml" error when building DotNetNuke 05.06.00 solution but not having time to track down the issue have found that I can ignore the error.

Note that the website is a dynamicly compiled website project and should not be checked to be built in the build configuration. It will be just-in-time compiled. DotNetNuke does not as of 5.06.00 support pre-compilation of the website itself - just of the library and other dependent projects in the VS solution.

The unauthorized access error for the LogFailures.xmlo.resources indicates insufficient filesystem permissions for the ASP.Net worker process account (IIS AppPool identity account) on the \Website folder and all child filders (at least on Portals\_default\Logs\ folder). Depending on the web server/IIS version this account may be either Network Services or IIS AppPool\DefaultAppPool. The attempt to write the error to the LogFailures.xml.resources file rather than the database EventLog table also indicates that the DotNetNuke application cannot connect to the 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 2 of 2
Previous12 
Previous
 
Next
HomeHomeGetting StartedGetting StartedNew to DNN Plat...New to DNN Plat...DataProvider ErrorDataProvider Error


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