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 ... Version 05.02.00...FAILURE 400 Version 05.02.00...FAILURE 400
Previous
 
Next
New Post
12/2/2009 7:39 AM
 

Hello,

 

when i start to install database , it well show me this error!!

 

 Installing Database - Version 05.00.00...Success

Upgrading Database to Version 05.00.01...Success
Upgrading Database to Version 05.01.00...Success
Upgrading Database to Version 05.01.01...Success
Upgrading Database to Version 05.01.02...Success
Upgrading Database to Version 05.01.03...Success
Upgrading Database to Version 05.01.04...Success
Upgrading Database to Version 05.02.00...FAILURE 400 - Access to the path 'c:\websites\176727nn7\Install\Cleanup\03.00.08.txt' is denied.
 
 
I am using Ms sql 2008
on my  hosting.
 
New Post
12/2/2009 8:03 AM
 

did you make sure having .Net Framework 3.5 SP1 installed?


Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
12/3/2009 10:51 PM
 

I sent this qustion to my hosting support :

When the servers were switched to medium trust we also added .NET 3.5 SP1 so this is installed. I would check back with the forums as they will be your best bet for help since we do not often work with DotNetNuke. As a side note, DotNetNuke is installed with Full trust permissions set in the web.config file for ASP. This must be changed or the site will not load due to the permissions that are enforced on our shared servers. Do this this, please change the following lines:> > Change this: <trust level="Full" originUrl="http://some_site_or_ip/.*"/>> > To this: <trust level="Full" originUrl="http://some_site_or_ip/.*"/> --> > > This will clear the .NET errors that are displayed. Please be aware that after making this change, it can take up to 15 minutes for the site to load properly as it will recompile all the DLLs required for the website. Please be patient and not close the window until this has completed. This will probably not impact your the site until the install has completed, but just as a heads up.

 

after that a new erorr is coming when I typing my domin in a home page :

 

Domain Name Windows Server 2003 Does Not Exist In The Database

DotNetNuke supports multiple portals from a single database/codebase. It accomplishes this by converting the URL of the client browser Request to a valid PortalID in the Portals database table. The following steps describe the process:

 

  1. Web Server Processing
    • When a web server receives a Request from a client browser, it compares the file name extension on the target URL resource to its Application Extension Mappings defined in IIS.
    • Based on the corresponding match, IIS then sends the Request to the defined Executable Path ( aspnet_asapi.dll in the case of ASP.NET Requests ).
    • The aspnet_isapi.dll engine processes the Request in an ordered series of events beginning with Application_BeginRequest.


     
  2. HttpModule.URLRewrite OnBeginRequest ( UrlRewriteModule.vb )
    • The Request URL is parsed based on the "/" character
    • A Domain Name is constructed using each of the relevant parsed URL segments.

      Examples:

      URL: http://www.domain.com/default.aspx = Domain Name: www.domain.com
      URL: http://209.75.24.131/default.aspx = Domain Name: 209.75.24.131
      URL: http://localhost/DotNetNuke/default.aspx = Domain Name: localhost/DotNetNuke
      URL: http://www.domain.com/virtualdirectory/default.aspx = Domain Name: www.domain.com/virtualdirectory
      URL: http://www.domain.com/directory/default.aspx = Domain Name: www.domain.com/directory

       
    • Using the Domain Name, the application queries the database ( Portals table - PortalAlias field ) to locate a matching record.

      Note: If there are multiple URLs which correspond to the same portal then the PortalAlias field must contain each valid Domain Name in a comma seperated list.

      Example:

      URL: http://localhost/DotNetNuke/default.aspx
      URL: http://MACHINENAME/DotNetNuke/default.aspx
      URL: http://209.32.134.65/DotNetNuke/default.aspx
      PortalAlias: localhost/DotNetNuke,MACHINENAME/DotNetNuke,209.32.134.65/DotNetNuke

      Note: If you are installing the application to a remote server you must modify the PortalAlias field value for the default record in the Portals table according to the rules defined above.

 

What Can I do?

 
New Post
12/4/2009 3:05 AM
 

Hello,,

the site is work but the same erorr stil when install database script!!

I change this code section in web.config:

<!-- set code access security trust level - this is generally set in the machine.config
    <trust level="Medium" originUrl=".*" />
    -->

TO

<!-- set code access security trust level - this is generally set in the machine.config
    <trust level="Full" originUrl=".*" />
    -->


may be should i change OriginUrl=".*" to my domain name?

Thank You

 
New Post
12/4/2009 4:32 AM
 

no, enabling full trust should be sufficient, but it must be allowed in machine.config, otherwise it will not take any effect.


Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ... Version 05.02.00...FAILURE 400 Version 05.02.00...FAILURE 400


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