Hi,
This is most likely an issue relating to CRL checking. If the server the Client Access component is installed on does not have direct Internet Access, for example, access to crl.microsoft.com, it is common for .NET Framework when loading the digitially signed
binaries to validate the certificates on the package. After a period of time, the certificate validation checks timeout and the modules load in IIS.
This can be reproduced by disabling access to the internet from the CAS server, performing an IISRESET /NOFORCE, then opening a user's mailbox via the CAS server. The time out could take anywhere from 15s to 120s, in my experience. Common scenarios include
building Exchange an isolated test environment.
Note: a similar problem is experience when installing Exchange without direct internet access. The installation may take a long time. This article may help
http://technet.microsoft.com/en-us/library/ee221147(EXCHG.80).aspx
To resolve this issue (if this is the issue), modify the following files and add the indicated line to the <runtime> section.
C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Aspnet.Config
C:\WINDOWS\Microsoft.NET\Framework64\v2.0.50727\Aspnet.Config
Add the line between the <runtime> and </runtime> lines:
<generatePublisherEvidence enabled="false" />
The contents of Aspnet.Config should look similar to:
<?xml version="1.0" encoding="UTF-8"?>
<configuration>
<runtime>
<generatePublisherEvidence enabled="false" />
<legacyUnhandledExceptionPolicy enabled="false" />
<legacyImpersonationPolicy enabled="false" />
<alwaysFlowImpersonationPolicy enabled="false" />
<SymbolReadingPolicy enabled="1" />
</runtime>
</configuration>
Restart the IIS components (IISRESET /NOFORCE) and attempt to access the OWA site. This should take much less time than before
An article which touches on similar CRL certificate validation issues :
http://msexchangeteam.com/archive/2008/07/08/449159.aspx
Hope this helps
Colin
