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
HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...Web config Error after uploading moduleWeb config Error after uploading module
Previous
 
Next
New Post
6/27/2010 3:53 AM
 
Jeff


Joined: 5/31/2007
Posts: 297
I uploaded the Chat Module from the links here on DNN, and my site AND another DNN site which is the primary on my hosting both show the same error code. Prior to uploading the Chat Module, I did the Gallery and the Blog modules with no problem. The site I am working with is aliased under the primary site on my Godaddy hosting. The URL for the troubled sites are http://greenbrierband.net and the primary domain which has the same problem is www.1800skyrideripoff.com The following is the code just as it shows.

 Thanks, Jeff...

Server Error in '/greenbrierband.net' 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>
 
New Post
6/27/2010 6:50 AM
 
William Severance


www.wesnetdesigns.com
Joined: 2/18/2005
Posts: 3253
The Chat module has a namespace conflict when installed in DotNetNuke versions 5.3.1 and later. If you were to set <customErrors mode="Off" /> in your site's web.config file you would likely see the following error:

Compiler Error Message: BC30002: Type 'Web.HttpContext' is not defined.

In App_Code\Chat\DnnChatCodeHelper.vb

Line 308: Try

Line 309: Dim ctx As Web.HttpContext = Web.HttpContext.Current

Line 310: Dim lvstrImageRoot As String = String.Empty

Line 311: oCache = ctx.Cache.Get(key)

Detailed compiler output says:

App_Code\Chat\DnnChatCodeHelper.vb(309) : error BC30002: Type 'Web.HttpContext' is not defined.

The following modification to line 309 of the file \App_Code\Chat\DNNChatCodeHelper.vb should eliminate the application error:

Current Line 309:  Dim ctx As Web.HttpContext = Web.HttpContext.Current
Modified Line 309: Dim ctx As System.Web.HttpContext = Sytem.Web.HttpContext.Current

Note the prefix System. which has been inserted in two places in Line 309.

Since the Chat module is dynamically compiles when the site starts, you can make the change and save the file without any manual build/compile necessary.

Note also that the Chat module may have other issues in DNN 5.4.x and above that this simple fix will not address.

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
6/27/2010 12:45 PM
 
Jeff


Joined: 5/31/2007
Posts: 297
Will removing all associate files for the Chat module reverse this issue? I have removed all that I could find from the FTP, and I am currently going through the File manager in my Godaddy hosting and looking for files to remove..
 
New Post
6/27/2010 1:18 PM
 
Jeff


Joined: 5/31/2007
Posts: 297

Update;
 I found an attribute in the Web.config file for Greenbrierband.net that was showing where the module had been added, I removed the attribute, and Greenbrierband.net came back online and all appears to be fixed. The problem is that the other DNN site, which is an very old version, (2007) still is down. The other DNN site is the primary domain, 1800skyrideripoff.com/skydiving/skyride, That is in the folder path Skydiving/skyride, The root or base file in the hosting and all the other domains aliased in the hosting appears to be working fine, http://www.1800skyrideripoff.com.
 Is there something I should have changed that I have not found yet?
 Thanks, Jeff...
 
New Post
6/27/2010 1:36 PM
 
Jeff


Joined: 5/31/2007
Posts: 297
Resolved!  I went back in and uploaded the original Web.config for the primary domain and all is well!


 Thanks, Jeff....
 
 Page 1 of 3
123Next 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...Web config Error after uploading moduleWeb config Error after uploading module


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