• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1736
  • Last Modified:

Outlook Anywhere HTTP 500 error

I am receiving HTTP 500 errors when running tests from testexchangeconnectivity.com/
I have already uninstalled and re-installed the RPC proxy twice. When I go to https://webmail.mydomain.org/rpc/rpcproxy.dll I get page cannot be displayed. I have checked and verified that my SSL settings are correct in IIS and I have checked the authentication settings are correct as according to http://technet.microsoft.com/en-us/library/gg263433(v=exchg.80).aspx. Please help. Webmail is working as an interim workaround but this has been happening since last week and users are getting restless.
0
danmiller81
Asked:
danmiller81
  • 3
  • 2
1 Solution
 
danmiller81Author Commented:
Testing RPC/HTTP connectivity.
The RPC/HTTP test failed.
Test Steps
Attempting to resolve the host name webmail.mydomain.org in DNS.
The host name resolved successfully.
Additional Details
IP addresses returned: MY IP
Testing TCP port 443 on host webmail.mydomain.org to ensure it's listening and open.
The port was opened successfully.
Testing the SSL certificate to make sure it's valid.
The certificate passed all validation requirements.
Test Steps
ExRCA is attempting to obtain the SSL certificate from remote server webmail.mydomain.org on port 443.
ExRCA successfully obtained the remote SSL certificate.
Additional Details
Remote Certificate Subject: CN=webmail.mydomain.org, OU=Domain Control Validated, O=webmail.mydomain.org, Issuer: SERIALNUMBER=xxxxxxx, CN=Go Daddy Secure Certification Authority, OU=http://certificates.godaddy.com/repository, O="GoDaddy.com, Inc.", L=Scottsdale, S=Arizona, C=US.
Validating the certificate name.
The certificate name was validated successfully.
Additional Details
Host name webmail.mydomain.org was found in the Certificate Subject Common name.
Certificate trust is being validated.
The certificate is trusted and all certificates are present in the chain.
Test Steps
ExRCA is attempting to build certificate chains for certificate CN=webmail.mydomain.org, OU=Domain Control Validated, O=webmail.mydomain.org.
One or more certificate chains were constructed successfully.
Additional Details
A total of 2 chains were built. The highest quality chain ends in root certificate OU=Go Daddy Class 2 Certification Authority, O="The Go Daddy Group, Inc.", C=US.
Analyzing the certificate chains for compatibility problems with versions of Windows.
No Windows compatibility problems were identified.
Additional Details
The certificate chain has been validated up to a trusted root. Root = E=info@valicert.com, CN=http://www.valicert.com/, OU=ValiCert Class 2 Policy Validation Authority, O="ValiCert, Inc.", L=ValiCert Validation Network.
Testing the certificate date to confirm the certificate is valid.
Date validation passed. The certificate hasn't expired.
Additional Details
The certificate is valid. NotBefore = 3/20/2012 7:10:03 PM, NotAfter = 3/20/2013 7:10:03 PM
Checking the IIS configuration for client certificate authentication.
Client certificate authentication wasn't detected.
Additional Details
Accept/Require Client Certificates isn't configured.
Testing HTTP Authentication Methods for URL https://webmail.mydomain.org/rpc/rpcproxy.dll.
The HTTP authentication test failed.
Additional Details
An HTTP 500 response was returned from Unknown.
0
 
PadamdeepCommented:
Looking at the above output, it looks like you are not even able to authenticate against IIS RPC virtual directory.

Could you go to Exchange CAS server and try browsing https://localhost/rpc/rpcproxy.dll?

It may throw the certificate warning but don't worry about it.

Put in your credential if it prompts and see if you are getting Blank Page.

Lets do the above steps and I'll tell you what to do next.

~ Singh
0
 
danmiller81Author Commented:
Here is the result after clicking through the certificate error
HTTP500.24Error
0
 
PadamdeepCommented:
There is something messed up in configuration of IIS/ASP.net.

Try changing the Default App Pool to classic. Reset IIS and try browsing the same url again.

I addition to this, look into App and Sys logs for relevant events.

Please let me know the results.

~ Singh
0
 
danmiller81Author Commented:
Worked like a charm and its back up and running thank you so much
0

Featured Post

Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now