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 ...GoDaddy DNN install issueGoDaddy DNN install issue
Previous
 
Next
New Post
4/19/2008 3:20 PM
 

I installed DNN 4.8.0 in GoDaddy using their install method and get the following error when I acces the directory that DNN is located (phgcoesct.org/portal), how can I fix the issue? I have no clue where to begin.


Server Error in '/portal' Application.
--------------------------------------------------------------------------------

Access to the path 'd:\hosting\phgcct\portal\\DotNetNuke.config' is denied.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.UnauthorizedAccessException: Access to the path 'd:\hosting\phgcct\portal\\DotNetNuke.config' is denied.

ASP.NET is not authorized to access the requested resource. Consider granting access rights to the resource to the ASP.NET request identity. ASP.NET has a base process identity (typically {MACHINE}\ASPNET on IIS 5 or Network Service on IIS 6) that is used if the application is not impersonating. If the application is impersonating via <identity impersonate="true"/>, the identity will be the anonymous user (typically IUSR_MACHINENAME) or the authenticated request user.

To grant ASP.NET access to a file, right-click the file in Explorer, choose "Properties" and select the Security tab. Click "Add" to add the appropriate user or group. Highlight the ASP.NET account, and check the boxes for the desired access.

Source Error:

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below. 

Stack Trace:


[UnauthorizedAccessException: Access to the path 'd:\hosting\phgcct\portal\\DotNetNuke.config' is denied.]
   System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath) +651
   System.IO.File.InternalCopy(String sourceFileName, String destFileName, Boolean overwrite) +432
   DotNetNuke.HttpModules.RequestFilter.RequestFilterSettings.GetSettings() +236
   DotNetNuke.HttpModules.RequestFilter.RequestFilterModule.FilterRequest(Object sender, EventArgs e) +286
   System.Web.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +92
   System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +64

 

 
New Post
4/19/2008 4:25 PM
 

It looks like file permissions for the DotNetNuke.config file are incorrect. I don't know if the GoDaddy interface allows you to set permissions or if it's something only they can do.

 
New Post
4/19/2008 5:00 PM
 

I found where in the their interface how to fix it, I had to make the directory web visible and writable. When I did that and went back to the site, I then get the following error....

 

Data at the root level is invalid. Line 1, position 1.

Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.Xml.XmlException: Data at the root level is invalid. Line 1, position 1.

Source Error:

The source code that generated this unhandled exception can only be shown when compiled in debug mode. To enable this, please follow one of the below steps, then request the URL:

1. Add a "Debug=true" directive at the top of the file that generated the error. Example:

  <%@ Page Language="C#" Debug="true" %>

or:

2) Add the following section to the configuration file of your application:

<configuration>
   <system.web>
       <compilation debug="true"/>
   </system.web>
</configuration>

Note that this second technique will cause all files within a given application to be compiled in debug mode. The first technique will cause only that particular file to be compiled in debug mode.

Important: Running applications in debug mode does incur a memory/performance overhead. You should make sure that an application has debugging disabled before deploying into production scenario.

Stack Trace:

[XmlException: Data at the root level is invalid. Line 1, position 1.]
   System.Xml.XmlTextReaderImpl.Throw(Exception e) +90
   System.Xml.XmlTextReaderImpl.Throw(String res, String arg) +127
   System.Xml.XmlTextReaderImpl.ParseRootLevelWhitespace() +1953906
   System.Xml.XmlTextReaderImpl.ParseDocumentContent() +503
   System.Xml.XmlTextReaderImpl.Read() +41
   System.Xml.XmlLoader.Load(XmlDocument doc, XmlReader reader, Boolean preserveWhitespace) +145
   System.Xml.XmlDocument.Load(XmlReader reader) +96
   System.Xml.XmlDocument.Load(String filename) +160
   DotNetNuke.Modules.Admin.ResourceInstaller.ResourceInstaller.InstallPortal(String strFile, Boolean writeFeedback, Int32 indent) +291
   DotNetNuke.Modules.Admin.ResourceInstaller.ResourceInstaller.Install(Boolean writeFeedback, Int32 indent, String type) +961
   DotNetNuke.Services.Upgrade.Upgrade.InstallDNN(String strProviderPath) +747
   DotNetNuke.Services.Install.Install.InstallApplication() +391
   DotNetNuke.Services.Install.Install.Page_Load(Object sender, EventArgs e) +274
   System.Web.UI.Control.OnLoad(EventArgs e) +99
   System.Web.UI.Control.LoadRecursive() +47
   System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +1436

 
New Post
4/20/2008 12:21 PM
 

DNNSkinner,

I've recently been messing around with a GoDaddy hosting account and had a few observations:

1. The FTP Upload process is un-reliable -> make sure that all your files got  uploaded to the site. The exception you are getting is usually when the LoadXml method cannot find the path for the file specified to load. It might be that some files didn't get uploaded. Use an FTP client like FileZilla so that you can see failures and retry until all files are uploaded.

2. If you signed up for their new IIS7 hosting, you will need to change the Pipeline mode to support DNN's current version. In the GoDaddy control panel, you will find this under Content->IIS Settings. Click the toolbar button for Advanced options and you can change the Pipeline mode to classic.

codemunki9 (http://codemunki9.blogspot.com)

 
New Post
4/24/2008 11:44 AM
 

Guys, instead of spending time with GoDaddy you'd better go with a good hoster.

 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...GoDaddy DNN install issueGoDaddy DNN install 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