Hello

I am trying to install a site on a remote host. After confirming that asp.net.1.1 is enabled and that the start page should be default.aspx.

I changed the config file to the appropriate settings for the remote server and remote newly created database etc.,

Altered the DotNetNuke.vbproj.webinfo and the DotNetNuke.sln file from:

    <Web URLPath = "http://localhost/DdotNetNuke/DotNetNuke.vbproj" />

To:

     "http://www.mysite.com/a2zdom/DotNetNuke.vbproj" 

I uploaded the files and after I keyed in the site URL in the address bar I got this error message:

Details: To enable the details of this specific error message to be viewable on remote machines, please create a <customErrors> tag within a "web.config" configuration file located in the root directory of the current web application. This <customErrors> tag should then have its "mode" attribute set to "Off".

<!-- Web.Config Configuration File -->

<configuration>
    <system.web>
        <customErrors mode="Off"/>
    </system.web>
</configuration>
 

Notes: The current error page you are seeing can be replaced by a custom error page by modifying the "defaultRedirect" attribute of the application's <customErrors> configuration tag to point to a custom error page URL.

<!-- Web.Config Configuration File -->

<configuration>
    <system.web>
        <customErrors mode="RemoteOnly" defaultRedirect="mycustompage.htm"/>
    </system.web>
</configuration>

What does this mean and how should I rectify it, when I have installed on a local machine I have not been required to alter a page default. 

 I thought that it would automatically open with default.aspx on a remote installation if the iis has been adjusted accordingly as I was assured that this is the case.

I would appreciate any suggestions.

Thanks

Lynn

I managed to get rid of this error by  inserting Off

<configuration>
    <system.web>
        <customErrors mode="Off"/>
    </system.web>
</configuration>

But now I have a new error:  I am trying to install a new source version of DNN 3.2.2 with asp.net version 1.1

 

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

Server cannot append header after HTTP headers have been sent.
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.Web.HttpException: Server cannot append header after HTTP headers have been sent.

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:

[HttpException (0x80004005): Server cannot append header after HTTP headers have been sent.]
   System.Web.HttpResponse.AppendHeader(String name, String value) +415
   blowery.Web.HttpCompress.CompressingFilter.WriteHeaders() +40
   blowery.Web.HttpCompress.DeflateFilter.Write(Byte[] buffer, Int32 offset, Int32 count) +28
   System.Web.HttpWriter.Filter(Boolean finalFiltering) +282
   System.Web.HttpResponse.Flush(Boolean finalFlush) +505
   System.Web.HttpWriter.Write(String s) +206
   System.Web.HttpResponse.Write(String s) +10
   DotNetNuke.Common.Utilities.HtmlUtils.WriteHeader(HttpResponse response, String mode) +287
   DotNetNuke.Framework.Install.InstallApplication() +1176
   DotNetNuke.Framework.Install.Page_Load(Object sender, EventArgs e) +265
   System.Web.UI.Control.OnLoad(EventArgs e) +67
   System.Web.UI.Control.LoadRecursive() +35
   System.Web.UI.Page.ProcessRequestMain() +744

 

--------------------------------------------------------------------------------
Version Information: Microsoft .NET Framework Version:1.1.4322.2032; ASP.NET Version:1.1.4322.2032

 

Any suggestions?

Thanks

 

Lynn

Hi Lynn

Been a while - have you still got ptoblems?
Out of interest - are you using the Blowery HTTP compression module?

Hello rodneyjoyce

Thanks for your post and interest.

I have had quite a lot of problems with the site, too many to list here.  It seems that my hosting provider had made errors when the site was installed. Which has only come to light of late.

It was necessary to reinstall a fresh DNN, this was only a few days ago. The site is now up and running up to now it seems to be working ok apart from* it is too early to say if everything else is working as it should.

Yes I am using Blowery HTTP compression and so far it seems fine.

*I have installed HumanFriendly URL's which are look good. But I found that  when using the Host features the links are not available "this page cannot be displayed". (perhaps it's my hosting provider) I solved that by switching back to SearchFriendly URL's. Not quite as friendly, but at least they work.  I have not yet had time to to locate source of error.   

Thanks.

Lynn

Hmmm - the reason I asked about the Compression dll is that when I upgraded my site I had the cookie append error, so I disabled compression in the web config and it worked fine. After it upgraded I re-enabled it and it worked fine - worth bearing in mind for future upgrades.

Do you have a local staging server to test everything on first? May be a good idea to narrow down problems to host-specific or not.