Restarted IIS then the server and can't open up the exchange web admin or owa

I restated IIS and couldn't get OWA to come up, restarted the server.

Checked the IIS services which are all running. Nothing will come up.
Who is Participating?
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.

I am assuming this is Exchange 2013?  Have you checked the Event Logs to see if there are any events that can point you to the culprit?

cnl83Author Commented:
Inbound authentication failed with error LogonDenied for Receive connector Client Frontend BHA02. The authentication mechanism is Login. The source IP address of the client who tried to authenticate to Microsoft Exchange is [].

An error occurred while using SSL configuration for endpoint  The error status code is contained within the returned data.

Performance counter updating error. Counter name is Process ID, category name is MSExchangeRemotePowershell. Optional code: 2. Exception: The exception thrown is : System.InvalidOperationException: The requested Performance Counter is not a custom counter, it has to be initialized as ReadOnly.
   at System.Diagnostics.PerformanceCounter.InitializeImpl()
   at System.Diagnostics.PerformanceCounter.get_RawValue()
   at Microsoft.Exchange.Diagnostics.ExPerformanceCounter.get_RawValue()
Last worker process info : System.ArgumentException: Process with an Id of 9236 is not running.
   at System.Diagnostics.Process.GetProcessById(Int32 processId)
   at Microsoft.Exchange.Diagnostics.ExPerformanceCounter.GetLastWorkerProcessInfo()
Processes running while Performance counter failed to update:
984 svchost
6296 Microsoft.Exchange.Store.Service
2044 rundll32
580 lsass
380 svchost
11476 InetMgr
572 services
3132 conhost
12784 w3wp
9856 iexplore
10220 igfxtray
2140 sftracing
5880 EdgeTransport
4896 LogMeIn
1152 spoolsv
3120 MSExchangeHMWorker
8136 svchost
6072 MSExchangeDelivery
6840 Microsoft.Exchange.Store.Worker
11776 LogMeInRC
3304 scanningprocess
6848 MSExchangeMailboxReplication
11812 iexplore
1328 svchost
6168 MSExchangeFrontendTransport
4672 TmListen
5656 UMWorkerProcess
7024 svchost
7820 msdtc
1800 hkcmd
528 winlogon
920 svchost
1116 mqsvc
7812 TmProxy
3280 MSExchangeSubmission
2884 noderunner
10972 pccntupd
9776 WmiPrvSE
3668 MSExchangeThrottling
3076 Microsoft.Exchange.RpcClientAccess.Service
5916 CNTAoSMgr
10836 igfxsrvc
3064 msexchangerepl
1744 Ntrtscan
1288 hostcontrollerservice
4636 MSExchangeTransport
300 smss
5224 iexplore
5420 Microsoft.Exchange.Search.Service
13124 inetinfo
11112 w3wp
5020 Microsoft.Exchange.UM.CallRouter
5556 w3wp
684 svchost
2456 noderunner
484 wininit
876 svchost
5996 MSExchangeDagMgmt
5516 Microsoft.Exchange.AntispamUpdateSvc
476 csrss
5596 conhost
1456 ramaint
3228 Microsoft.Exchange.ServiceHost
2252 Microsoft.Exchange.Directory.TopologyService
10316 w3wp
11056 ServerManager
1644 SMSvcHost
12920 svchost
7572 LogMeInSystray
10760 mmc
652 svchost
9680 taskhostex
2620 WmiPrvSE
5264 SMSvcHost
2224 WMSvc
3204 umservice
4188 scanningprocess
4076 w3wp
3004 noderunner
5760 igfxpers
13044 w3wp
828 svchost
2796 noderunner
9700 w3wp
6140 conhost
2396 MSExchangeMigrationWorkflow
1212 fms
4164 scanningprocess
1380 MSExchangeHMHost
6560 MSExchangeMailboxAssistants
1992 updateservice
1428 LMIGuardianSvc
412 csrss
10852 svchost
10260 explorer
788 dwm
1192 w3wp
4540 Microsoft.Exchange.EdgeSyncSvc
1584 Microsoft.Exchange.Diagnostics.Service
1976 rundll32
10840 PccNTMon
4 System
1776 ForefrontActiveDirectoryConnector
1184 svchost
3744 MSExchangeTransportLogSearch
0 Idle
Performance Counters Layout information: FileMappingNotFoundException for category MSExchangeRemotePowershell : Microsoft.Exchange.Diagnostics.FileMappingNotFoundException: Cound not open File mapping for name Global\netfxcustomperfcounters.1.0msexchangeremotepowershell. Error Details: 2
   at Microsoft.Exchange.Diagnostics.FileMapping.OpenFileMapping(String name, Boolean writable)
   at Microsoft.Exchange.Diagnostics.PerformanceCounterMemoryMappedFile.Initialize(String fileMappingName, Boolean writable)
   at Microsoft.Exchange.Diagnostics.ExPerformanceCounter.GetAllInstancesLayout(String categoryName)
cnl83Author Commented:
Ping of mdb 'cc501ddf-f810-46e1-ac63-8015de3e017f' timed out after '00:00:00' minutes.  Last successful ping was at '10/8/2014 3:03:14 PM' UTC.
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.

cnl83Author Commented:
Got a bunch of errors like this under iis

A process serving application pool 'MSExchangePowerShellAppPool' suffered a fatal communication error with the Windows Process Activation Service. The process id was '21704'. The data field contains the error number.
Lets validate your Exchange Certificates really quick.

On your Exchange Server, run the Get-ExchangeCertificate cmdlet from the Exchange Console.

Example Output:Capture.JPG
Then open a command prompt and ensure that the certificate used for IIS is bound to ports 444 and 443:

Example Output:Capture.JPG
You can verify the certificate that should be used by opening IIS and checking the bindings on your Default Web Site:

Open IIS Manager:
Start -> type iis and select Information Services ManagerCapture.JPGExpand the tree till you get to your sites list and select the Default Web SiteCapture.JPGSelect Bindings from the Actions on the rightCapture.JPGSelect the https Type for port 443 (there may be multiple entries) and click EditCapture.JPGSelect View and then the Details tabCapture.JPGGo down to the Thumbprint field and select itCapture.JPG
This value should match in both the ssl certificate for port 443 on the Default Web Site and the ssl certificate for port 444 on the Exchange Back End site.


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
cnl83Author Commented:
They do not match. In fact there was no certificate selected for the bindings. I had to select my godaddy certificate from the drop down then select view.
Did you select the certificate for both the 443 and 444 bindings?

Try restarting both IIS and your Exchange Transport service.  See if this resolves your issue.

cnl83Author Commented:
I selected the Godaddy certificate for both and restarted IIS. OWA and Backend pulled up.
Is your issue resolved then?  If so, don't forget to accept the comment that solved the problem for you.

Hello Saige,

This solved my problem in a minute!!!

Best regards
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

From novice to tech pro — start learning today.