Sharepoint Forum

Ask Question   UnAnswered
Home » Forum » Sharepoint       RSS Feeds

Non-Sharepoint Application on Sharepoint IIS Server

  Asked By: Alyssa    Date: May 20    Category: Sharepoint    Views: 6147

I was wondering if it's possible to run a non-sharepoint web
application on a sharepoint IIS server. It seems that WSS 3.0 takes
over port 80 so any request for a web page that isn't sharepoint seems
be denied. I saw some articles that said to use "managed paths" to fix
this issue but it's confusing because it looks like you need a
sharepoint application in order to use "managed paths". So, if anyone
can share a solution to using IIS for both sharepoint and non-
sharepoint web applictions on IIS, I'd appreciate it.



5 Answers Found

Answer #1    Answered By: William Odom     Answered On: May 20

you just create a new web  site in iis

set it to use a host header for a URL thats not in use by sharepoint

et voila

i.e. users usually go to http://moss.mycompany.com" target="_blank" rel="nofollow">http://moss.mycompany.com to access sharepoint  - for
your new non-sharepoint  site they can use the URL

if you absolutely have to use the same URL then you can use a different port

e.g. http://moss.mycompany.com" target="_blank" rel="nofollow">http://moss.mycompany.com:81

if you have to use the same URL and port  number then you are, I am afraid, going
to have to go the managed  paths route.

Answer #2    Answered By: Mia Scott     Answered On: May 20

I thought that should work too. But, it doesn't! Unless I completely
uninstall wss  3.0, the new site just returns a page  not found error.

Answer #3    Answered By: Kristian Chaney     Answered On: May 20

Actually, the ASP.NET application  goes in an unmanaged path. These used to
be referred to as excluded paths.

In 2007, you create a Virtual Directory in IIS and put your ASP.NET
application there. You can set these up with a separate URL, as Phillip
described previously. I believe you can also install the custome app in a
"subdirectory" under the sharepoint  URL if you wish.

There are some gotcha's concerning web.config files, however, so be sure to
read the article below.


Answer #4    Answered By: Alicia Scott     Answered On: May 20

First, Are you using a Host Header for your sharepoint  site? To use Host
Headers on any site in IIS all sites using the same port  need to use Host

Second, after adding the new IIS site with the Host header did you define the
host header in your DNS server  as an alias? Otherwise you won't be able to
resolve the name to an IP address.

Third, make sure you are addressing the new site by the host header. For
example, If you are in Domain.com and create a site with a host header of
Intranet, then Http://Intranet will respond, but Http://Intranet.Domain.com
won't. Even though the DNS server will resolve both to the same IP address,
only one of them actually matches the host header. To use the FQDN name you
would need to add that as a second Host Header by adding it through IIS manager.

Another option is to use IIS manager to create a unique Virtual Directory inside
one of the SharePoint web  Applications. This will be a location where you can
host standard ASP.NET 2.0 web pages, without needing SharePoint.

Answer #5    Answered By: Mike Lamb     Answered On: May 20

Just place your custom application  into a physical (or virtual) directory under
the SharePoint website in IIS on each WFE. In WSS v3, you no longer need to
specify an excluded managed  path for your file system based applications because
ASP.NET the initial handler, rather than SharePoint.

Didn't find what you were looking for? Find more on Non-Sharepoint Application on Sharepoint IIS Server Or get search suggestion and latest updates.