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/25/2007 4:19 AM
 

OK, a lot of things to explain - I'll answer this in three parts because here are three completely differnent aspects.
I'll starting with the .sln file. You know .sln files are the project files for vs2005. Beyond the settings you're managing from the IDE there are a lot things that can be set manually. Before you start make a copy of your sln file!
One is the VWDPort for the port from the built-in webserver. Delete this line
I think your .PhysicalPath is wrong - it's dependent from your .sln file (the path to the DNN directory)
Insert the following line before the EndProjectSection
SlnRelativePath = "the path from sln to the DNN directory "
Change the Line: Project("{...}")= "http://localhost/DNNWeb1/", "http://localhost/DNNWeb1", "{...}"

try this and tell if it worked.
The rest will I write on the afternoon.

 
New Post
5/25/2007 6:31 PM
 

I deleted the VWDPort line from the *.sln file. 

I added the "SlnRelativePath" line to the .sln file.  The path was correct for the .PhysicalPath.  I had installed Visual Studio Express in "C:/Documents and Settings/Gayle/My Documents/Visual Studio 2005".  Because of this, the "Projects" directory was in the .../Visual Studio 2005/Websites/Projects/DNNWeb1 directory, but the DNNWeb1 website resided at the root directory, "C:".  I have since recreated the DNNWeb1 website so that it now resides in the .../Visual Studio 2005/Websites directory.  So, the line I added reads SlnRelativePath = "..\..\WebSites\DNNWeb1".

I also changed the "Project("{...}") line to have the "http" entries mentioned in your last post instead of the "C:\...\DNNWeb1\" entries. 

But, when I use notepad to change the .sln file, then start VWD, it starts a "DNNWeb1 (2)", creates a corresponding directory under Projects, and the Solutions Explorer has "C:\...\DNNWeb1" for it's title.    How can I change this?

In order to use the new .sln file, I have to open the new .sln file in the Projects/DNNWeb1 directory, then start the website.  Now the Solutions Explorer will have http://localhost/DNNWeb1" for it's title.  When I compile the default.aspx file, I get "The resource cannot be found.  Server Error in "/" Application, The resource cannot be found".  It also does NOT start asp.net. 

I then created a virtual IIS directory through the IIS Manager and called it DNNWeb1 and pointed it to the WebSites/DNNWeb1 directory.  Now when I open the .sln file, then compile the default.aspx file, I get "Server Application Not Available.  The web application you are attempting to access on this web server is curretnly unavailable. . . ."  The Event Viewer has the error message for asp.net as:

Failed to execute the request because the ASP.NET process identity does not have read permissions to the global assembly cache. Error: 0x80070005 Access is denied.

Here's my current .sln file:

Microsoft Visual Studio Solution File, Format Version 9.00
# Visual Web Developer Express 2005
Project("{E24C65DC-7377-472B-9ABA-BC803B73C61A}") = "http://localhost/DNNWeb1/", "http://localhost/DNNWeb1/", "{4BCBE674-8E65-4C70-87E9-D33E8285B416}"
 ProjectSection(WebsiteProperties) = preProject
  Debug.AspNetCompiler.VirtualPath = "/DNNWeb1"
  Debug.AspNetCompiler.PhysicalPath = "..\..\WebSites\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 = "..\..\WebSites\DNNWeb1\"
  Release.AspNetCompiler.TargetPath = "PrecompiledWeb\DNNWeb1\"
  Release.AspNetCompiler.Updateable = "true"
  Release.AspNetCompiler.ForceOverwrite = "true"
  Release.AspNetCompiler.FixedNames = "false"
  Release.AspNetCompiler.Debug = "False"
  DefaultWebSiteLanguage = "Visual Basic"
  SlnRelativePath = "..\..\WebSites\DNNWeb1\"
 EndProjectSection
EndProject

 

 
New Post
5/26/2007 6:34 AM
 

Ok, the project file looks good for me. Note for my environment: I only use the system on C: all other activcities are on other partitions.

Now the new errors: 
1. Have you added the ASPNET user to the DNN directory and granted him all permissions?
When you don't have a ASPNET user, reinstall .NET 2.0.

2. You said :
But, when I use notepad to change the .sln file, then start VWD, it starts a "DNNWeb1 (2)", creates a corresponding directory under Projects, and the Solutions Explorer has "C:\...\DNNWeb1" for it's title.    How can I change this?
Have you updated the directories (popup menu: VS2005 -> Solution Explorer -> Project "http:\\local ..." -> right click )?
Have you cleared the cache (.NET2.0 framework)?
!!! Have you a second section in the .sln file !!! 

 
New Post
5/29/2007 2:30 PM
 

1.  I do have an ASPNET user and did grant full permissions to him on the DNNWeb1 directory.  It did help.  I then checked the IIS "DNNWeb1" virtual directory.  The "Anonymous" user was "ISUSR", so I changed it to "ASPNET".  That resolved the permissions issues, allowing me to open the main portal home page.  I can also now access the child portal, so it seems that this resolved the permissions all the way around.

2.  I found that when I change the .sln file, I have to have VWD running with the DNNWeb1 website open.  Then when I save the .sln file in notepad, VWD asks me if I want to "reload" the new .sln file.  This resolved the "DNNWeb1(2)" issue.

3.  The only thing I didn't do was "delete a port", which is something you mention in an earlier post.  I believe it was because XP doesn't support multiple ports.  Do I still need to do this?  and if so, where am I deleting the port from? 

thank you for your patience.

 
New Post
5/29/2007 5:22 PM
 

Using the built-in webserver in the vs2005 or not actually it depends what you want. On both sides is a great advantage as well a disadvantage. 
When you're  using the built-in webserver you must brood over the configuration of IIS. When you start the DNN for the first time the vs2005 takes an arbitrary  / random port ( VWDPort = "..." ) . The really disadvantage is when your finished the development / web design phase and you want to transfer the prototype to the production server. It will take some effort and sometimes quite tricky (I only say multilanguage solution and the problems with the application paths).
I don't use the built-in webserver so I don't have these problems. The advantage is in 5 minutes can you copy the complete solution (with it's database if you want) and the only thing to do is to change the entries in the PortalAlias table. Very comfortable and stable! The disadvantage is you must configure the vs2005 and the IIS for each solutuion. After the fifth it's then an easy.
I think you know now how to handle this things - try both solutions and decide what's the best for you.

Please feel free to ask me again when you've some problems again

 
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.

Copyright 2014 by DNN Corp | Terms of Use | Privacy | Design by Parker Moore Design