MOSS Forum

Ask Question   UnAnswered
Home » Forum » MOSS       RSS Feeds

Need help on Managed Path

  Date: Sep 17    Category: MOSS    Views: 1530

I was trying to setup a virtual directory to our MOSS site
but ran into difficulties.
1. From the IIS Manager, I created a virtual
directory name “virtualpath”, linked to the physical path: “C:\inetpub\wwwroot\wss\VirtualDirectories\80\virtualpath”.
2. As suggested by the post www.knowsharepoint.com/.../...de-managed-path.html,
I added “Network Service” with read & execute permission.
3. I added read and execute permission to the
folder as well for “Network Service”.
4. I copied a very simple index.htm to the directory
5. In Central Administration page, I added “virtualpath”
as a wildcard inclusion Managed Path.
6. When I try the URL https://mysite/virtualpath/index.htm,
nothing shows up.
Are the above procedures right? What did I miss?



5 Answers Found

Answer #1    Answered On: Sep 17    

so, I am confused as to what you are trying to do. Are you trying to create a managed path for one of your current web apps?

Answer #2    Answered On: Sep 17    

Yes, I am trying to create a managed path so that I can place my aspx pages with VB code behind to the path, e.g.,

Answer #3    Answered On: Sep 17    

Just skip step 5 and it should work. The blog mentions that creating a Wildcard EXCLUSION Managed path was required in SharePoint 2003 but is no longer needed in 2007. You wouldn’t use a Wildcard inclusion managed path in either version for this.

Answer #4    Answered On: Sep 17    

I removed the Managed Path from the Central Adminstration, and refresh the web site from the IIS.

One super simple html file test1.htm was created with this content

Then in this URL https://mysite/virtualpath/test1.htm, nothing shows up. (Note that it I try a non-existence path such as mysite/none, HTTP 404 is shown - this somehow proves that "virtualpath" was indeed available). Right-click to View Source, I saw:

HTML 4.0 Transitional//EN">
<METAcontent="text/html; charset=windows-1252" http-equiv=Content-Type></HEAD>
Looks like generated code, not the above simple htm file I typed.

Any idea?

Answer #5    Answered On: Sep 17    

The problem is resolved. The culprit was an incorrect web.config

Didn't find what you were looking for? Find more on Need help on Managed Path Or get search suggestion and latest updates.