Re: Need correct way to create virtual dir under SharePoint

So we can access files on file shares via http:// on port 80 of SharePoint
server -- this is not SharePoint content we need the vd for.

To do that, we need to create a vd under SharePoint - 80. According to MS,
it will (should) be automatically excluded from managed paths (unlike where
in version 2.0, you then needed to go into Central Admin, add path and check
Exclude).

We actually did this a year ago successfully after several tries (which at
first did not work because we kept creating a web application in the vd
settings; once we removed the web app the vd worked pointing to file share).
We do not know why now doing the same thing blows up SharePoint.

"Amir Mehrani" wrote:

Correct way of creating virtual directory under sharepoint is to create or
extend web application throuhg application management in central
administration.
They way you try to create virtual directory have two problems:
1- You're going to create VD outside sharepoint which is not extended by
sharepoint and breaking access is normal.
2- You're going to create a VD point to a file share which is not meaningful
for sharepoint.

In fact the scenario you're looking for is not clear.Why you want to create
a VD point to file share and extend it?


--
Amir Mehrani
Sharepoint Consultant
http://sharepointroad.wordpress.com

"jremmc" <jremmc@xxxxxxxxxxxxxx> wrote in message
news:C84127E6-6372-43F3-8E0E-55D05208EE61@xxxxxxxxxxxxxxxx
WSS 3.0 and IIS 6.0 -- I need to create a virtual directory under
SharePoint
- 80 that points to a file server share (not another web application). I
went
thru new vd wizard, then reset IIS, and that broke access to SharePoint
sites
on port 80. I got the typical fatal error, contact administrator, go back
to
site. (Central Admin, which is on another port, opened fine.) I deleted
the
vd, reset IIS, and access was restored (thankfully).

When I went thru the wizard in IIS, I named the vd project, pointed it to
\\server\share, checked Read and Directory Browse permissions, set the
user
name and password to a specific domain account used for that purpose,
authentication was Integrated Windows Authentication only. When the wizard
finished, the vd showed in IIS (globe icon, not gear\application icon,
since
I did not create the vd as a web app) and I was able to browse the file
share
just fine in IIS. Only a blank page came up in Internet Explorer though,
and
I read I had to reset IIS, and after I did that, SharePoint access broke.

What did I not do or what went wrong?

Thanks,
jremmc



.

Relevant Pages

  • Re: Need correct way to create virtual dir under SharePoint
    ... They way you try to create virtual directory have two problems: ... 1- You're going to create VD outside sharepoint which is not extended by ... a VD point to file share and extend it? ... thru new vd wizard, then reset IIS, and that broke access to SharePoint ...
    (microsoft.public.sharepoint.windowsservices)
  • Re: WSS 2.0 and 3.0
    ... SharePoint Central Adminstration v3 ... Central Administration and one for the Magiglo Intranet. ... Default Web Site (Port 80) ...
    (microsoft.public.windows.server.sbs)
  • Re: WSS 2.0 and 3.0
    ... SharePoint Central Adminstration v3 ... In the window that opens up you should have two entries: One for the Central Administration and one for the Magiglo Intranet. ... What we do is delete the old site you created and create it again under port 80. ... Under Port type 80 and under 'Host header' type: ...
    (microsoft.public.windows.server.sbs)
  • Re: WSS 2.0 and 3.0
    ... Select 'Remove SharePoint from IIS Web Site'. ... Administration and one for the Magiglo Intranet. ... Default Web Site (Port 80) ...
    (microsoft.public.windows.server.sbs)
  • Re: WSS 2.0 and 3.0
    ... SharePoint Central Adminstration v3 ... One for the Central Administration and one for the Magiglo Intranet. ... Default Web Site (Port 80) ...
    (microsoft.public.windows.server.sbs)