Exchange 2010 OWA Not working

We are having problems with an Exchange 2010 SP3 server running on Small Business Server 2011 (Server 2008 R2 essentially).  All of a sudden users are not able to login using OWA.  Users get the message below.  We have tried reinstalling SP3, and update roll-up 10.  I have also run sfc /scannow and .Net Framework Setup Verification Tool which found no errors.  There are a few random Exchange errors that seem unrelated but I will post those as well.

Request
Url: https://remote.DOMAIN.org:443/owa/
User: Administrator
EX Address: /o=DOMAIN/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=Administrator8f3
SMTP Address: administrator@DOMAIN.org
OWA version: 14.3.248.2

Exception
Exception type: System.MissingMethodException
Exception message: Method not found: 'System.String Microsoft.Exchange.Clients.Strings.get_SetDefaultLanguage()'.

Call stack
Microsoft.Exchange.Clients.Owa.Core.RequestDispatcher.ValidateAndSetThreadCulture(OwaContext owaContext)
Microsoft.Exchange.Clients.Owa.Core.RequestDispatcher.PrepareRequestWithoutSession(OwaContext owaContext, UserContextCookie userContextCookie)
Microsoft.Exchange.Clients.Owa.Core.RequestDispatcher.AcquireAndPreprocessUserContext(OwaContext owaContext, HttpRequest request)
Microsoft.Exchange.Clients.Owa.Core.RequestDispatcher.InternalDispatchRequest(OwaContext owaContext)
Microsoft.Exchange.Clients.Owa.Core.RequestDispatcher.DispatchRequest(OwaContext owaContext)
Microsoft.Exchange.Clients.Owa.Core.OwaRequestEventInspector.OnPostAuthorizeRequest(Object sender, EventArgs e)
System.Web.HttpApplication.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)

Open in new window



Source: MSExchange Common
Event ID: 4999
Watson report about to be sent for process id: 7316, with parameters: E12, c-RTL-AMD64, 14.03.0227.000, OWA, M.E.Clients.Owa, M.E.C.O.C.RequestDispatcher.ValidateAndSetThreadCulture, System.MissingMethodException, e235, 14.03.0248.002.
ErrorReportingEnabled: False


Source: MSExchange ADAccess
Event ID: 2102
Process MSEXCHANGEADTOPOLOGYSERVICE.EXE (PID=2128). All Domain Controller Servers in use are not responding:
NUMBERS.DOMAINChurch.local


Source: MSExchangeTransport
Event ID: 5016
The Active Directory topology service could not discover any route to connector CN=Windows SBS Company Web Connector GENESIS,CN=Connections,CN=Exchange Routing Group (DWBGZMFD01QNBJR),CN=Routing Groups,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=DOMAIN,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=DOMAINChurch,DC=local in the routing tables with the timestamp 8/17/2015 9:24:34 PM. This connector will not be used.

Source: MSExchangeTransport
Event ID: 5015
Microsoft Exchange cannot find a route to the source transport server or home MTA server CN=Microsoft MTA\0ADEL:5ed8de14-3ff3-43c3-bfa8-f7ede4db3c1a,CN=Deleted Objects,CN=Configuration,DC=DOMAINChurch,DC=local for connector CN=Windows SBS Company Web Connector GENESIS,CN=Connections,CN=Exchange Routing Group (DWBGZMFD01QNBJR),CN=Routing Groups,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=DOMAIN,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=DOMAINChurch,DC=local in routing tables with timestamp 8/17/2015 9:24:34 PM. Microsoft Exchange is ignoring the source transport server.

Source: MSExchangeTransport
Event ID: 12014
Microsoft Exchange could not find a certificate that contains the domain name exchange.DOMAIN.org in the personal store on the local computer. Therefore, it is unable to support the STARTTLS SMTP verb for the connector Windows SBS Internet Send NUMBERS with a FQDN parameter of exchange.DOMAIN.org. If the connector's FQDN is not specified, the computer's FQDN is used. Verify the connector configuration and the installed certificates to make sure that there is a certificate with a domain name for that FQDN. If this certificate exists, run Enable-ExchangeCertificate -Services SMTP to make sure that the Microsoft Exchange Transport service has access to the certificate key.
LVL 1
bdhtechnologyAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Casey WeaverManaged Services Windows Engineer IIICommented:
This almost seems like a DNS or IP issue. Did the server's IP change? Has IPV6 been accidentally disabled? Is DNS set to use itself then use the proper root servers to access the internet?
systechadminConsultantCommented:
Please check the if all the Exchange services are in started mode or not?
bdhtechnologyAuthor Commented:
The server IP address has not changed and DNS resolution is working fine.  All Exchange and other automatic processes are started and running fine as well.

I did correct the last 3 errors, 2 by removing an invalid routing group connector through ADSIEdit.msc and the last one by specifying a FQDN for the send connector that matched a FQDN that there was a certificate for.  Neither of those seemed to help either though.
Big Business Goals? Which KPIs Will Help You

The most successful MSPs rely on metrics – known as key performance indicators (KPIs) – for making informed decisions that help their businesses thrive, rather than just survive. This eBook provides an overview of the most important KPIs used by top MSPs.

bdhtechnologyAuthor Commented:
I ended up removing the Exchange Client Access Server Role by downloading and extract Exchange 2010 SP3 and running:
setup.com /m:uninstall /r:c

When I went to re-install the role it would not run so I had to do that by using the add/remove programs control panel and then pointed the installer at the sp3 installation files.  After doing that I re-ran the Update Rollup 10 setup and all is well!

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
David AtkinTechnical DirectorCommented:
Great, thanks for posting your solution. Hopefully it will help others.
bdhtechnologyAuthor Commented:
Found the answer on my own
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Exchange

From novice to tech pro — start learning today.