I agree with your last comment in that I should not need to restart IIS.
I discovered this scenario after a couple of users could not start OWA.
Exchange and and IIS servers were restarted. When I checked the IIS folder structure I noticed the icon change. I changed the path apply, all is ok, OWA Users still cannot connect, I restart Exchange & IIS, look in the IIS manager and the icons have changed to error. A little strange.
Gary
"David Wang [Msft]" wrote:
> When you stop and start IIS, do you restart Exchange and OWA as well?
>
> Since Exchange has a dependency on IIS, stopping IIS causes Exchange to
> stop, but starting IIS does NOT cause Exchange to start. You will have to
> explicitly restart such services that stopped due to you stopping a critical
> dependency like IIS. This is how dependencies work.
>
> Also, when do you stop/start IIS when you set the path to the folder
> location? That change should propagate automatically -- no restart of IIS
> required.
>
> --
> //David
> IIS
> This posting is provided "AS IS" with no warranties, and confers no rights.
> //
> "Gary Boulter" <GaryBoulter DeleteThis @discussions.microsoft.com> wrote in message
> news:287B8EA7-7E67-4649-BC46-272E201521D4@microsoft.com...
> I have some strange IIS behaviour with OWA exchange 2k folders. Each time I
> set the path to the folder location, stop and start IIS. The public,
> Exchange and Exadmin virtual folders display an error icon. users are unable
> to connect to OWA.
>
> Any ideas welcome
>
> Many thanks
> Gary
>
>
>
><!-- ~MESSAGE_AFTER~ -->
>> Stay informed about: Virtual Directory Path error with OWA 
FAQ
Profile
Private Messages
Log in
