OWA has stopped working :(

OWA with SSL was working perfect up until yesterday. Now whenever I
try logging in it gives me the cert then comes up with this page:

The page cannot be displayed
There is a problem with the page you are trying to reach and it cannot
be displayed.

--------------------------------------------------------------------------------

Please try the following:

Click the Refresh button, or try again later.

Open the Web site home page, and then look for links to the
information you want.
If you believe you should be able to view this directory or page,
please contact the Web site administrator by using the e-mail address
or phone number listed on the Web site home page.
500 Internal Server Error - The target principal name is incorrect.
(-2146893022)
Internet Security and Acceleration Server


I have gone into IIS and it looks like PUBLIC, EXCHANGE, & EXADMIN are
not working? They all have red Error icons next to them. I am also
getting these errors in the log which may or may not be related:


Event Type: Warning
Event Source: RemoteAccess
Event Category: None
Event ID: 20171
Date: 2/09/2003
Time: 7:26:48 p.m.
User: N/A
Computer: PARENT
Description:
Failed to apply IP Security on port VPN2-0 because of error: The RPC
server is unavailable.
. No calls will be accepted to this port.
Data:
0000: ba 06 00 00 º...

And lastly this error:

Event Type: Error
Event Source: Microsoft Web Proxy
Event Category: None
Event ID: 14200
Date: 2/09/2003
Time: 7:30:51 p.m.
User: N/A
Computer: PARENT
Description:
ISA Server failed to establish an SSL connection with 192.168.16.2.
The target principal name is incorrect.

Data:
0000: 22 03 09 80 "..?


Any help would be greatly appreciated :).

David
Tue Sep 02 04:36:39 CDT 2003

Have you had any viruses recently? Have you made any=20
changes to ISA server, removed or changed any user=20
permissions?

>-----Original Message-----
>OWA with SSL was working perfect up until yesterday. Now=20
whenever I
>try logging in it gives me the cert then comes up with=20
this page:
>
>The page cannot be displayed=20
>There is a problem with the page you are trying to reach=20
and it cannot
>be displayed.=20
>
>----------------------------------------------------------
----------------------
>
>Please try the following:
>
>Click the Refresh button, or try again later.
>
>Open the Web site home page, and then look for links to=20
the
>information you want.=20
>If you believe you should be able to view this directory=20
or page,
>please contact the Web site administrator by using the e-
mail address
>or phone number listed on the Web site home page.=20
>500 Internal Server Error - The target principal name is=20
incorrect.
>(-2146893022)
>Internet Security and Acceleration Server=20
>
>
>I have gone into IIS and it looks like PUBLIC, EXCHANGE,=20
& EXADMIN are
>not working? They all have red Error icons next to=20
them. I am also
>getting these errors in the log which may or may not be=20
related:
>
>
>Event Type: Warning
>Event Source: RemoteAccess
>Event Category: None
>Event ID: 20171
>Date: 2/09/2003
>Time: 7:26:48 p.m.
>User: N/A
>Computer: PARENT
>Description:
>Failed to apply IP Security on port VPN2-0 because of=20
error: The RPC
>server is unavailable.
>.. No calls will be accepted to this port.=20
>Data:
>0000: ba 06 00 00 =BA... =20
>
>And lastly this error:
>
>Event Type: Error
>Event Source: Microsoft Web Proxy
>Event Category: None
>Event ID: 14200
>Date: 2/09/2003
>Time: 7:30:51 p.m.
>User: N/A
>Computer: PARENT
>Description:
>ISA Server failed to establish an SSL connection with=20
192.168.16.2.
>The target principal name is incorrect.
>=20
>Data:
>0000: 22 03 09 80 "..? =20
>
>
>Any help would be greatly appreciated :). =20
>.
>

Chad
Tue Sep 02 13:42:48 CDT 2003

Hi Ben -

I've seen this happen before - and in my experience it seems to be in some
way related to the M: drive, although I haven't had the opportunity to
investigate further what the underlying cause is. Open IIS Administration
and expand the Default Web Site. I'll bet that you have stop signs next to
your Exchange, Exchweb & Public subwebs - yet they indicate that they are
running ok. Open the Properties for one of these subwebs, and on the
Virtual Directory tab, click Browse next to the Local Path field. Change
the path from the original directory to its parent, then change it back to
the original. Click OK on the subweb properties and the subweb should be
back to normal. Do this for each of the stopped Exchange subwebs and you
should be good to go. If OWA doesn't work after doing this, you may need to
restart your Exchange services . . .

--
Chad A Gross

Lerman's Law of Technology: Any technical problem can be overcome
given enough time and money. Corollary: You are never given enough
time or money.



Benjamin Hamilton wrote:
> OWA with SSL was working perfect up until yesterday. Now whenever I
> try logging in it gives me the cert then comes up with this page:
>
> The page cannot be displayed
> There is a problem with the page you are trying to reach and it cannot
> be displayed.
>
> --------------------------------------------------------------------------
------
>
> Please try the following:
>
> Click the Refresh button, or try again later.
>
> Open the Web site home page, and then look for links to the
> information you want.
> If you believe you should be able to view this directory or page,
> please contact the Web site administrator by using the e-mail address
> or phone number listed on the Web site home page.
> 500 Internal Server Error - The target principal name is incorrect.
> (-2146893022)
> Internet Security and Acceleration Server
>
>
> I have gone into IIS and it looks like PUBLIC, EXCHANGE, & EXADMIN are
> not working? They all have red Error icons next to them. I am also
> getting these errors in the log which may or may not be related:
>
>
> Event Type: Warning
> Event Source: RemoteAccess
> Event Category: None
> Event ID: 20171
> Date: 2/09/2003
> Time: 7:26:48 p.m.
> User: N/A
> Computer: PARENT
> Description:
> Failed to apply IP Security on port VPN2-0 because of error: The RPC
> server is unavailable.
> . No calls will be accepted to this port.
> Data:
> 0000: ba 06 00 00 º...
>
> And lastly this error:
>
> Event Type: Error
> Event Source: Microsoft Web Proxy
> Event Category: None
> Event ID: 14200
> Date: 2/09/2003
> Time: 7:30:51 p.m.
> User: N/A
> Computer: PARENT
> Description:
> ISA Server failed to establish an SSL connection with 192.168.16.2.
> The target principal name is incorrect.
>
> Data:
> 0000: 22 03 09 80 "..?
>
>
> Any help would be greatly appreciated :).

Benjamin
Tue Sep 02 16:03:35 CDT 2003

On Tue, 2 Sep 2003 13:42:48 -0500, "Chad A Gross"
<chad.gross@laytonflower.nospam.com> wrote:

>Hi Ben -
>
>I've seen this happen before - and in my experience it seems to be in some
>way related to the M: drive, although I haven't had the opportunity to
>investigate further what the underlying cause is. Open IIS Administration
>and expand the Default Web Site. I'll bet that you have stop signs next to
>your Exchange, Exchweb & Public subwebs - yet they indicate that they are
>running ok. Open the Properties for one of these subwebs, and on the
>Virtual Directory tab, click Browse next to the Local Path field. Change
>the path from the original directory to its parent, then change it back to
>the original. Click OK on the subweb properties and the subweb should be
>back to normal. Do this for each of the stopped Exchange subwebs and you
>should be good to go. If OWA doesn't work after doing this, you may need to
>restart your Exchange services . . .


I really do appreciate the support this group gives :). I did as you
suggested and I could get it going for about 30 seconds (it would go
thru the SSL stuff, the login then load some emails onto the screen
before giving up the ghost) so I decided what have I done this time
;). Only 2 things I had changed in the last couple of days was
setting up VPN and installing a new antivirus program (the system was
running after I installed it - well Im pretty sure it was!). Wasnt
going to go thru the hassles of removing the VPN stuff as I'd proberly
be shot so I decided to give removing the antivirus program a shot.
Just rebooted and bingo! Its absolutely perfect now!

For the record I was using NOD32 for Exchange. I had it on a 1 month
trial so its not a biggie if I cant use it. Im going to contact the
distro's here and see what they have to say about it. The weird thing
is the system worked perfect if you just went
https://server/exchange..