• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 319
  • Last Modified:

IIS - Default Website and Exchange Server email problem

Microsoft 2011 server and IIS 7.
Implementing a local asp.net website on server in wwwroot.
Website has a web.config file.
The presence of the config file in the wwwroot folder is causing remote email to stop working. for example... "https://remote.xxxxx.com/OWA"
Once the file is removed, the remote email works fine.
Have tried several things but nothing has worked.
Need help! Thanks!
0
Cubbybulin
Asked:
Cubbybulin
3 Solutions
 
Jeff PerryWindows AdministratorCommented:
Is this the only IIS/web server you have?  

Do you get an error for the remote email stoppage? Is it a port in use error?

If so just change the TCP port assignment and the SSL port assignment on the properties page of the new website.  You may have to edit the web.config file directly and look for what ports it is setting the new site up on.

If it is not a port in use error then we will need more information to help you further.
0
 
R. Andrew KoffronCommented:
here's an article on how to install OWA outside of the default website, so the config might not cascade to the exchange app.

Not positive it'd work, but it's the second(or 20th) thing I'd try.  First thing I'd try is leaving the default web the heck alone, and installing the new application in a different site(different server even better, I also wouldn't try installing the Hyper-V service on my exchange server to run a 2008web system, but it might be an option, just opens a slew of complexity issues if tracking down future issues or network changes).  either the company selling the new application, or the In-house developers can make their product work in a different spot, I just personally wouldn't mess with my exchange server.

http://forums.msexchange.org/m_170142600/tm.htm
0
 
hecgomrecCommented:
Unless you are closing the ports in that file or using them for other services your OWA site should work.

Now, when you say its stops, you get to the IIS and the website has the stop status or just users from outside are not able to load the website?

If you are changing settings or folder permissions on the file then you should definitely should move your OWA site out of there if permissions can't be managed.

Finally, you can't have both sites using the same ports (80, 443, etc)
0
 
CubbybulinAuthor Commented:
Thanks for all your replies. It turned out to be something simple for me but allot of time spent researching.
I simply put the below statement in the New local website (default) web.config file and it worked great.

<location inheritInChildApplications="false">
...other config parameters within
</location>

I found this in the web.config of the OWA and tried it.

Thanks again for your help and quick responses!
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Cloud Class® Course: SQL Server Core 2016

This course will introduce you to SQL Server Core 2016, as well as teach you about SSMS, data tools, installation, server configuration, using Management Studio, and writing and executing queries.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now