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 ...Http Error 404: file not found when trying to access Child PortalHttp Error 404: file not found when trying to access Child Portal
Previous
 
Next
New Post
5/23/2007 8:41 PM
 
gkgrun

Joined: 4/9/2007
Posts: 9

I have DNN 4.5.1 installed (Starter Kit) and created my website using the "file system" option.  I have no problem accessing my main page at "http://localhost:1696/DNNWeb1/".  

I created a child portal named "testportal".  When I try to access the child portal, I receive: "The page cannot be found" and "http - 404 file not found, Internet Information Services".  I've tried "//localhost:1696/DNNWeb1/testportal".  The "testportal" directory and default.aspx are in the C:DNNWeb1 directory and there is a "1" directory in the DNNWeb1/Portals/ directory.

Any Ideas?
 
New Post
5/24/2007 3:29 AM
 
Guy Jascht

Joined: 7/26/2006
Posts: 262

I think the portal alias directs to a place that not exists. 
Open the database and look/send me the entries and the virtual directory entry from the IIS.   
 
New Post
5/24/2007 3:31 PM
 
gkgrun

Joined: 4/9/2007
Posts: 9

Thank you for replying.  Here's the information from the database . . .

From PortalAlias Table:

PortalAliasID  PortalID  HTTPAlias
1         0             localhost/dnnweb1
2         1             localhost:1696/dnnweb1/testportal

From Portals Table:

PortalID   PortalName   HomeTabId   AdminTabID   HomeDirectory
0                My Website     37                 39                   Portals/0
1                New Portal      54                 56                   Portals/1

There is no virtual directory entry in IIS.  Did I need to create one?  I did not create one when creating the website. 

I am working out of the "Beginning DotNetNuke 4.0 Web Site Creation in VB2005 with Visual Web Developer 2005 Express" book by Symmonds

Thank you in advance
 
New Post
5/24/2007 5:37 PM
 
Guy Jascht

Joined: 7/26/2006
Posts: 262

I assume your using XP than is the (only) web site from the IIS is the 'Default Web Site'. The virtual directory is 'dnnweb1'.

The first portal uses the standard http port from the IIS and should work fine without a start from the vs2005. The second is coming from the integrate webserver from the vs2005 who assigns an arbitrary port and is only valid within a start inside the vs2005. Easy spoken: within the default IIS web site on a XP system there can only be one port. 
On a W2K3 you can create two localhost with different ports and the problem is solved. On XP you can solve your problem with the following recipe (ignores the 'built-in' vs2005 server running everything over IIS):

Change the project file (*.sln file) and 'tell' vs2005 to start your sessions over the IIS
Example:
Microsoft Visual Studio Solution File, Format Version 9.00
# Visual Studio 2005
Project("{E24C65DC-7377-472B-9ABA-BC803B73C61A}") = "http://localhost/dnnweb1/", "http://localhost/dnnweb1", "{79D3BA0F-F76F-4A84-AE7F-C6A01EC247F9}"
 ProjectSection(WebsiteProperties) = preProject
  ProjectReferences = "{4912F062-F8A8-4F9D-8F8E-244EBEE1ACBD}|DotNetNuke.WebUtility.dll;{D391550C-7107-49B2-A6AC-8627C8B06ADC}|DotNetNuke.dll;{89093FD0-076F-48CD-9232-B665226CDBF0}|CountryListBox.dll;{F336D16D-E512-42CC-876A-9E0118F87514}|DotNetNuke.HttpModules.UrlRewrite.dll;"
  Debug.AspNetCompiler.VirtualPath = "/PreCompiled"
  Debug.AspNetCompiler.PhysicalPath = "Website\"
snip...
and create two virtual directories (dnnweb1 and testportal where is a child from dnnweb1). To finish all you delete the port of the second portal alias (-> localhost/dnnweb1/testportal). That's it - I prefer such configuration because I can easily migrate the portal from the development machine to the production server in 20 seconds.

Tell me if this was successful
 
New Post
5/24/2007 7:48 PM
 
gkgrun

Joined: 4/9/2007
Posts: 9

Thanks for the reply.  I am using XP and I understand the explanation you provided.  I just am not quite sure how to go about making the changes.  Below is part  of the dnnweb1 project file (*.sln).  I'm not sure what I am changing and I don't want to make the wrong changes.

 Microsoft Visual Studio Solution File, Format Version 9.00
# Visual Web Developer Express 2005
Project("{E24C65DC-7377-472B-9ABA-BC803B73C61A}") = "C:\DNNWeb1\", "..\..\..\..\..\..\DNNWeb1\", "{9230F867-0226-439D-93F1-AB8E38393F1F}"
 ProjectSection(WebsiteProperties) = preProject
  Debug.AspNetCompiler.VirtualPath = "/DNNWeb1"
  Debug.AspNetCompiler.PhysicalPath = "..\..\..\..\..\..\DNNWeb1\"
  Debug.AspNetCompiler.TargetPath = "PrecompiledWeb\DNNWeb1\"
  Debug.AspNetCompiler.Updateable = "true"
  Debug.AspNetCompiler.ForceOverwrite = "true"
  Debug.AspNetCompiler.FixedNames = "false"
  Debug.AspNetCompiler.Debug = "True"
  Release.AspNetCompiler.VirtualPath = "/DNNWeb1"
  Release.AspNetCompiler.PhysicalPath = "..\..\..\..\..\..\DNNWeb1\"
  Release.AspNetCompiler.TargetPath = "PrecompiledWeb\DNNWeb1\"
  Release.AspNetCompiler.Updateable = "true"
  Release.AspNetCompiler.ForceOverwrite = "true"
  Release.AspNetCompiler.FixedNames = "false"
  Release.AspNetCompiler.Debug = "False"
  VWDPort = "2189"
  DefaultWebSiteLanguage = "Visual Basic"
 EndProjectSection
EndProject

Also, you mentioned creating 2 virtual directories.  Can I assume you mean to do this through the IIS Manager?

Lastly, you say to delete the port of the second portal alias.  Where am I deleting this port from?

I apologize in advance for all of the questions.  Thanks again.
 
 Page 1 of 3
123Next 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...Http Error 404: file not found when trying to access Child PortalHttp Error 404: file not found when trying to access Child Portal


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