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

HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...web.config errorweb.config error
Previous
 
Next
New Post
5/9/2006 11:15 AM
 
I am bit rusty at .net and totally green at DNN, so go easy on me as I inherited the portal administration with the new job.

I am getting the common error message:    

Server Error in '/Myfpcn' Application.

Runtime Error

Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). It could, however, be viewed by browsers running on the local server machine.

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 I did before recieving this error is this:

I tried to add a sub tab under my contacts tab, but something funky happened when I finished.  There was an error message at the top of my central column - pretty non-descript

To solve this I tried resetting the server that hosts the portal.  Upon being restarted I got the error you see above when tring to view the portal.

I appreciate any help on this.

Matt Fanning
 
New Post
5/9/2006 11:25 AM
 
Here's my web.config file for reference

 
New Post
5/9/2006 12:04 PM
 
Lets try that again:


<configuration>

    <!-- register local configuration handlers -->
    <configSections>
        <sectionGroup name="dotnetnuke">
            <section name="data" type="DotNetNuke.ProviderConfigurationHandler, DotNetNuke" />
            <section name="logging" type="DotNetNuke.ProviderConfigurationHandler, DotNetNuke" />
            <section name="scheduling" type="DotNetNuke.ProviderConfigurationHandler, DotNetNuke" />
            <section name="htmlEditor" type="DotNetNuke.ProviderConfigurationHandler, DotNetNuke" />
        <section name="yafnet" type="yaf.SectionHandler,yaf" />

       
        </sectionGroup>



    </configSections>




    <!-- Sql Server connection string for support of pre DNN 2.0 Private Assemblies
         The new connection string (for DNN 2.0) is in the section dotnetnuke (providers) -->
    <appSettings>
        <add key="connectionString" value="Server=*server;Database=*database;uid=*username;pwd=*password;" />
    </appSettings>

    <system.web>

        <!-- set debugmode to false for running application -->
        <compilation debug="false" />

        <!-- permits errors to be displayed for remote clients -->
        <customErrors mode="off" />

        <!-- Forms or Windows authentication -->
        <authentication mode="Forms">
        <forms name=".DOTNETNUKE" protection="All" timeout="60" />
       
        </authentication>
        <!--
            <identity impersonate="true"/>
            <authentication mode="Windows">
            </authentication>
        -->

        <!-- allow large file uploads -->
        <httpRuntime useFullyQualifiedRedirectUrl="true" maxRequestLength="8192" />
       
        <!--  GLOBALIZATION
        This section sets the globalization settings of the application.
        Utf-8 is not supported on Netscape 4.x
        If you need netscape compatiblity leave iso-8859-1.
        UTF-8 is recommended for complex languages
        -->
        <globalization culture="en-US" uiCulture="en" requestEncoding="UTF-8" responseEncoding="UTF-8" fileEncoding="UTF-8" />
        <!--<globalization culture="en-US" uiCulture="en"  fileEncoding="iso-8859-1" requestEncoding="iso-8859-1" responseEncoding="iso-8859-1"/>-->

        <!-- page level options -->
        <pages validateRequest="false" enableViewStateMac="true" />

    </system.web>

    <dotnetnuke>
        <htmlEditor defaultProvider="FtbHtmlEditorProvider" >
            <providers>
                <clear/>
                <add name = "FtbHtmlEditorProvider"
                        type = "DotNetNuke.HtmlEditor.FtbHtmlEditorProvider, DotNetNuke.FtbHtmlEditorProvider"                   
                        providerPath = "~\Providers\HtmlEditorProviders\FtbHtmlEditorProvider\"
                />
            </providers>
        </htmlEditor>
        <data defaultProvider="SqlDataProvider" >
            <providers>
                <clear/>
                <add name = "SqlDataProvider"
                        type = "DotNetNuke.Data.SqlDataProvider, DotNetNuke.SqlDataProvider"
                        connectionString = "Server=*server;Database=*database;uid=*username;pwd=*password;"
                        providerPath = "~\Providers\DataProviders\SqlDataProvider\"
                        objectQualifier = ""
                        databaseOwner = "dbo"
                        upgradeConnectionString = ""
                />
                <add name = "AccessDataProvider"
                        type = "DotNetNuke.Data.AccessDataProvider, DotNetNuke.AccessDataProvider"
                        connectionString = "PROVIDER=Microsoft.Jet.OLEDB.4.0;"
                        providerPath = "~\Providers\DataProviders\AccessDataProvider\"
                        objectQualifier = "DotNetNuke"
                        databaseFilename = "DotNetNuke.mdb.resources"
        />
            </providers>
        </data>
        <logging defaultProvider="XMLLoggingProvider" >
            <providers>
                <clear/>
                <add name = "XMLLoggingProvider"
                        type = "DotNetNuke.Logging.XMLLoggingProvider, DotNetNuke.XMLLoggingProvider"
                        configfilename="LogConfig.xml.resources"
                        providerPath = "~\Providers\LoggingProviders\XMLLoggingProvider\"
                />
            </providers>
        </logging>
        <scheduling defaultProvider="DNNScheduler" >
            <providers>
                <clear/>
                <add name = "DNNScheduler"
                        type = "DotNetNuke.Scheduling.DNNScheduler, DotNetNuke.DNNScheduler"
                        providerPath = "~\Providers\SchedulingProviders\DNNScheduler\"
                        debug="false"
                        maxThreads="-1"
                        enabled="true"
                />
            </providers>
        </scheduling>

    </dotnetnuke>
</configuration>
 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...web.config errorweb.config 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