Outlook Web Access - HTTP/1.1 503 Service Unavailable

Hi, we are running Exchange Server 2003 SP2 in a FE/BE configuration over 
SSL. The OS is Windows Server 2003 Std SP2 on both.

Last week a power outage at this particular site resulted in dirty shutdowns 
for both the FE and BE servers. Since then OWA has not worked. I am getting 
the logon prompt but when logged on "HTTP/1.1 503 Service Unavailable" is 
being displayed. I can use the FE server to connect to a mailbox running on a 
different BE server at another site, leading me to believe the issue is with 
the Mailbox server. I get the error if I try and connect via it's DNS name 
over the internet and also by locally using 
 http://www.**--****.com/ 

The following DCOM and EXCDO errors are being displayed in the System Log 
and Application log every 2 mins respectively (they only started appearing 
since the power outage): -

Event Type:	Error
Event Source:	DCOM
Event Category:	None
Event ID:	10016
Date:		09.06.2008
Time:		15:37:29
User:		NT AUTHORITY\SYSTEM
Computer:	BE Server
Description:
The application-specific permission settings do not grant Local Activation 
permission for the COM Server application with CLSID 
{9DA0E106-86CE-11D1-8699-00C04FB98036}
 to the user NT AUTHORITY\SYSTEM SID (S-1-5-18).  This security permission 
can be modified using the Component Services administrative tool.

Event Type:	Error
Event Source:	EXCDO
Event Category:	General 
Event ID:	8206
Date:		09.06.2008
Time:		15:39:23
User:		N/A
Computer: BE Server
Description:
Calendaring agent failed with error code 0x8000ffff while saving appointment. 

I have followed all of the relevant MS articles including and applied the 
fixes: -

 http://www.**--****.com/ 
 http://www.**--****.com/ 
 http://www.**--****.com/ 


I have also gone through the How to Troubleshoot "503 Service Unavailable 
error message in Outlook Web Access in Exchange Server 2003. What I haven't 
done so far is contact PSS for the HKCRScan tool to ensure that no registry 
keys exceed 259 chars.

I have also re-applied the OS and Exchange SP's to both servers. In addition 
I have checked the IIS security settings (Default Web Site, Application Pool, 
Exchange Virtual Sites etc) against a working BE Server and all seems to be 
fine.

None of the above has so far resolved the problem.

I am now running out of ideas so any assistance would be appreciated.

Many thanks in advanced.

Did you compare your settings on this CLSID
{9DA0E103-86CE-11D1-8699-00C04FB98036 from a working exchange BE to
the non working one using dcomcnfg? Try backing up this registry key;
deleting and importing the key from a working Exchange BE.



James Chong (MVP)
MCITP | EMA; MCSE | M+, S+,
Security+, Project+, ITIL
msexchangetips.blogspot.com


On Jun 9, 10:14燼m, Matthew Barclay


> Event Type: ??Error>
> Event Source: ?DCO>
> Event Category: Non>
> Event ID: ???1>016
> Date: ?????0>.06.2008
> Time: ??> ??15:37:29
> User: ?????>T AUTHORITY\SYSTEM
> Com>uter: ???BE >erver
> Description:
> The application-specific permission settings do not >rant Local Activation
> permission for the COM Server >pplication with CLSID
> {9DA0E106-86CE-1>D1-8699-00C04FB98036}
> 爐o the user NT AUTHORITY\SYSTEM SID (S-1-5-18). 燭h>s security permission
> can be modified using the Component Service> a>ministrative tool.
>
>> Event Type: ??Error>
> Event Source: ?EXCDO
> Event ID: ???8>06
> Date: ?????>9.06.2008
> Time> ?????15:39:23
>>User: ?????gt;N/A
> Computer: BE Server
> Description:
> Calendaring agent failed with erro> c>de 0x8000ffff while saving appointment.
>
> I have followed all of the rel>vant MS art>cl>s including and applied the
> fixes: -
>
>  http://www.**--****.com/ ://support.microsoft.com/kb/943721- For EXCDO http://www.**--****.com/ ;88>380- Reset Exchange Virtual Directories
>
> I have also gone through the H>w to Troubleshoot "503 Service Unavailable
> error message in Outlook Web Acc>ss in Exchange Server 2003. What I haven't
> done so far is contact PSS for t>e HKCRScan tool to ensure>th>t no registry
> keys exceed 259 chars.
>
> I have also re-applied the OS and>Exchange SP's to both servers. In addition
> I have checked the IIS security se>tings (Default Web Site, Application Pool,
> Exchange Virtual Sites etc) agai>st a wor>in> BE Server and all seems to be
> fine.
>
> None of>th> above has so far resolved the problem.
>
> I am now running out of id>as>so any assistance would be appreciated.