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

HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...Child Web Apps Child Web Apps
Previous
 
Next
New Post
3/13/2007 10:36 AM
 
Hassan,

Configuring your child web application to use DNN for its authentication and authorization cannot work out of the box.  I have created a module AuthIntegrator (see links in my sig) that does this for DNN 4.3.5+.  It will work for .NET 1.1 apps also.  If you are able to upgrade your DNN install to 4.3.5+ my module should do the trick.
 
New Post
3/13/2007 10:55 AM
 

Dear Shawn,

My child Apps deasn't use DNN DB, login in this Apps separate with DNN login

when I run this Apps alone it worked well and I can logged in it and open all pages normally BUT when I open it under DNN home page opened and when I logged in it this error appeared to me in my local machone

Server Error in '/dnn3/test' Application.
Session state can only be used when enableSessionState is set to true, either in a configuration file or in the Page directive 
 
But in my web site

DNN Site http://www.qubaaschool.com

Child Apps http://www.qubaaschool.com/exams/default.aspx

and this error appeared to me

Server Error in '/Exams' 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".

please help me

 


Regards, Hassan Ali
 
New Post
3/13/2007 1:14 PM
 
The error you are encountering is due to the nested nature of web.config files.  You should first turn custom errors off in the external app's web.config in order to see the true error.  As indicated by the various errors you will probably get, you likely will need to copy some entries from the parent to the child config file and hopefully the errors will go away.  Good luck.
 
New Post
3/21/2007 9:20 AM
 

Dear Shawn

I turned custom errors of in DNN's web.config but the same error appeared to me

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".

please help me


Regards, Hassan Ali
 
Previous
 
Next
HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...Child Web Apps Child Web Apps


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