shanna1017
asked on
Page could not be displayed after logging into OWA 2007
I was trying to fix the following error that kept showing up in our Exchange 2007 server
Source: MSExchangeTransport
Category: TransportService
Event ID: 12014
Microsoft Exchange couldn't find a certificate that contains the domain name mail.mydomain.net in the personal store on the local computer. Therefore, it is unable to offer the STARTTLS SMTP verb for any connector with a FQDN parameter of mail.fcc-inc.net. Verify the connector configuration and the installed certificates to make sure that there is a certificate with a domain name for every connector FQDN.
so i followed these instructions to try and fix it
__________________________ __________ __________ __________ __________ __________ _
I solved the problem today like this;
1. On the "Exchange Management Shell" I wrote "Get-ExchangeCertificate" command..
there are many thumbprints of cretificates (Wrongly I created many certificates before)
I looked to correct thumbprint from OWA certicate from Internet explorer...
2. After that on the shelll I wrote "Enable-ExchangeCertificat e -Thumbprint 3afd24627925332cd096f45eb5 b4473c7252 6112 -Services "SMTP" *(These thumbprint numbers ar sample)
After that all errors are cancelled... I'm getting correct information from TLS
__________________________ __________ __________ __________ __________ __________
and now when i log into OWA i get the login screen but when after I enter the credential it takes me to a page could not be displayed. The GoDaddy certificate is installed in IIS and SSL is enabled.
Any ideas what could be causing this?
Source: MSExchangeTransport
Category: TransportService
Event ID: 12014
Microsoft Exchange couldn't find a certificate that contains the domain name mail.mydomain.net in the personal store on the local computer. Therefore, it is unable to offer the STARTTLS SMTP verb for any connector with a FQDN parameter of mail.fcc-inc.net. Verify the connector configuration and the installed certificates to make sure that there is a certificate with a domain name for every connector FQDN.
so i followed these instructions to try and fix it
__________________________
I solved the problem today like this;
1. On the "Exchange Management Shell" I wrote "Get-ExchangeCertificate" command..
there are many thumbprints of cretificates (Wrongly I created many certificates before)
I looked to correct thumbprint from OWA certicate from Internet explorer...
2. After that on the shelll I wrote "Enable-ExchangeCertificat
After that all errors are cancelled... I'm getting correct information from TLS
__________________________
and now when i log into OWA i get the login screen but when after I enter the credential it takes me to a page could not be displayed. The GoDaddy certificate is installed in IIS and SSL is enabled.
Any ideas what could be causing this?
ASKER
i tried restarting WWW and clearing my client's SSL cashe and I still receive an HTTP 400 page could not be displayed after I enter my credentials at the OWA page.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I'm an idiot...i should've tried this on multiple machines before i assumed it was an issue. It works on other machines so it must just be my machine.
It was just odd that it worked on my machine before i made the change and then it stopped working immediately afterwards.
Sorry to waste your time. have some points for your effort.
It was just odd that it worked on my machine before i made the change and then it stopped working immediately afterwards.
Sorry to waste your time. have some points for your effort.
Thanks for the points. Glad things are working better for you - that's the main thing. Maybe a reboot of the problem client might help? Otherwise take a look at your browser settings.
1) Restart WWW service on OWA. Many times this helps when messing around with the certs.
2) Clear client SSL cache - in Internet Options - Content tab - Clear SSL State button. Close all browsers and try again.
Beyond that, could you be more descriptive of the error you are receiving?