Broke IIS and OWA

josh...@gmail.com

unread,

Sep 20, 2006, 11:10:36 AM9/20/06

to

I accidentally deleted the default web site in IIS6 and thus Outlook
Web Access no longer functions. Is there anyway I can easily restore
the default site and default settings for outlook web access to get it
functioning again?

Thanks!

Andy David - MVP

unread,

Sep 20, 2006, 11:14:52 AM9/20/06

to

http://support.microsoft.com/kb/883380
"How to reset the default virtual directories that are required to
provide Outlook Web Access, Exchange ActiveSync, and Outlook Mobile
Access services in Exchange Server 2003"

josh...@gmail.com

unread,

Sep 20, 2006, 11:23:00 AM9/20/06

to

The only problem is that it says to right click the Default Web Site,
and that is the site I accidentally deleted. How can I restore the
defualt web site that was deleted?

Thanks Josh

a@tleederbyshired.0.tc.0.m Lee Derbyshire [MVP]

unread,

Sep 20, 2006, 11:38:43 AM9/20/06

to

<josh...@gmail.com> wrote in message
news:1158765036.2...@d34g2000cwd.googlegroups.com...

Do you have a backup copy of your Metabase that you can restore? Have
a look in C:\Windows\System32\Inetsrv\Metaback.

Or, just use ESM to create a new Exchange Virtual Server? Right-click
Servers/<servername>/Protocols/HTTP , and create a new VS.

Actually there's nothing special about the Default Web Site, apart
from it's ID, which is always 1. The MS procedure to restore the OWA
folders in IIS might rely on it still being 1.

Lee.

--
_______________________________________

Outlook Web Access For PDA , OWA For WAP
www.owapda.com
email a@t leederbyshire d.0.t c.0.m
_______________________________________

Ben Winzenz [Exchange MVP]

unread,

Sep 20, 2006, 12:42:35 PM9/20/06

to

Uninstall IIS, then reinstall IIS. That should get the default web site
back.

Following this,you will then need to perform a reinstall of Exchange and
Exchange Service pack plus any Exchange hotfixes you have applied. So, the
steps would be:

1. Uninstall IIS
2. Install IIS
3. Re-run Exchange Setup and choose Reinstall from drop-down menu
4. Reinstall Exchange Service Pack
5. Re-apply any specific Exchange hotfixes that are applied.

This should get you fixed up.

--
Ben Winzenz
Exchange MVP
MessageOne
Read my blog!
http://winzenz.blogspot.com
http://feeds.feedburner.com/winzenz (RSS Feed)

<josh...@gmail.com> wrote in message
news:1158765780.1...@m73g2000cwd.googlegroups.com...

josh...@gmail.com

unread,

Sep 20, 2006, 1:03:41 PM9/20/06

to

Would it be easier to just recreate a new web site, edit the metabase
to give it a site id of 1 and then follow the Knowledge base article
previously supplied?

Josh

Ben Winzenz [Exchange MVP]

unread,

Sep 20, 2006, 1:27:52 PM9/20/06

to

It's up to you. The good thing about IIS here is that if creating a new
website doesn't fix it, you can always fall back to the steps I outlined
below, and it will fix it.

--
Ben Winzenz
Exchange MVP
MessageOne
Read my blog!
http://winzenz.blogspot.com
http://feeds.feedburner.com/winzenz (RSS Feed)

<josh...@gmail.com> wrote in message
news:1158771821.8...@i3g2000cwc.googlegroups.com...

a@tleederbyshired.0.tc.0.m Lee Derbyshire [MVP]

unread,

Sep 21, 2006, 9:45:42 AM9/21/06

to

<josh...@gmail.com> wrote in message
news:1158771821.8...@i3g2000cwc.googlegroups.com...

> Would it be easier to just recreate a new web site, edit the
metabase
> to give it a site id of 1 and then follow the Knowledge base article
> previously supplied?
>
> Josh

If you are comfortable doing that, I think that would definitely be
worth a try. Remember to enable Direct Metabase Edit in IIS Manager.
You will need to make sure that the first IIsWebServer is located at
/LM/W3SVC/1 , so you will need to search and replace any references to
the old location. Should be easily done in Notepad.