SBS2011 Remote Access/OWA Troubleshooting

Hello.

We have a server running SBS 2011.

Today some of our Exchange services have become unreachable from outside the network. OWA doesn't load and users emails have stopped working on their phones/tablets.

Everyone inside the building (ie. on the local network) can send/recieve emails just fine. VPN and RDP still work fine also.

I have tried restarting IIS and Exchange services with no success.

I am also receiving this error when trying to access Exchange Management Console or Shell.

Connecting to remote server failed with the following error message: The WinRM client received an HTTP server error status (500), but the remote service did not include any other information about the cause of the failure.


Any suggestions on troubleshooting this issue are much appreciated.
KTBerwickAsked:
Who is Participating?
 
KTBerwickAuthor Commented:
I followed this guide to restore the metabase.xml + mbsschema.xml files.http://fix.lazyjeff.com/2009/09/sbs-2003-iis-won-start-try-metabase.html

IIS Admin Service now starts and I can get into Exchange Management Console & Shell.

Now when going to /owa it beings to load... gets redirected to
/owa/auth/logon.aspx?url=https://remote.DOMAIN.co.uk/OWA/&reason=0
Then hangs on a white page.

Feel like I have made some progress though!
0
 
RAdministratorCommented:
If iisreset doesn't solve the problem, you might have to reset the individual web applications. In the IIS manager menu, in the application tree, I recall that you just right-click the offending application and reset/reinitialize it. Sorry for being imprecise, but I'm rusty on IIS management...
0
 
KTBerwickAuthor Commented:
Have just tried this with no success.

Just noticed I can't access the Companyweb or SharePoint page either. We don't really use these, but the issue is likely related.
0
Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

 
RAdministratorCommented:
You said OWA and ActiveSync don't work from the outside. What about on your local network? If you try to browse to OWA, does it work? If it does, then the inbound firewall is blocking requests.
0
 
Simon Butler (Sembee)ConsultantCommented:
The error you have posted indicates a problem with IIS.
Run the fix my network wizard to begin with, it is in the SBS management console.

Simon.
0
 
KTBerwickAuthor Commented:
No I cant access OWA from anywhere. Even directly from the server using localhost.

Have just rebooted the server and nothing has changed. Still can't get into Exchange Management Console or Shell due to the error above. If I could get in there, I would probably find what the issue is.
0
 
KTBerwickAuthor Commented:
Will try running that wizard now, thanks.
0
 
KTBerwickAuthor Commented:
Wizard came up with 3 potential errors.

#1 - the dns server is not listening to the ip address of the primary network adapter

#2 - DNS is using a DNS forwarder

#3 - An error occurred while trying to connect to the Exchange Management Shell


The Wizard automatically "resolved" #1
For #2, the only DNS forwarders in place are to Googles DNS Servers (8.8.8.8; 8.8.4.4)
#3 is the same error I get when trying to connect to Exchange Management Shell myself.

Connecting to remote server failed with the following error message: The WinRM client received an HTTP server error status (500), but the remote service did not include any other information about the cause of the failure.
0
 
KTBerwickAuthor Commented:
I have noticed the IIS Admin services is not running and when started manually it fails with the following error in event viewer:

The IIS Admin Service service terminated with service-specific error %%-2145318902.
Event ID 7024


Could this be why OWA isn't working etc? Does it rely on this service.
0
 
RAdministratorCommented:
What is your Exchange patch level? I vaguely recall that in unpatched versions (basically before SP1) some EMC issues are related to IPv6 being activated. You could try disabling IPv6 in the network stack (NOTE: DO NOT uncheck the box, disable via the registry key) and see if the console begins to load correctly.
0
 
Simon Butler (Sembee)ConsultantCommented:
If the server isn't on Exchange 2010 SP3, then installing SP3 would be a better option. That effectively reinstalls the product and will resolve a lot of issues.

Although if IISADMIN isn't starting, that will break everything else Exchange wise as the web service has a dependency on it.

However that does sound like your IIS installation may well be corrupt. If that is the case then you are looking at some hefty work to correct it.

The steps on this page apply to Exchange 2007, same steps work on Exchange 2010:
http://support.microsoft.com/kb/320202

Simon.
0
 
KTBerwickAuthor Commented:
Currently on SP1 version 14.01.0438.000

Assuming you mean this key. I have changed the value to 0xffffffff

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip6\Parameters\DisabledComponents

Afraid it made no difference.


Currently downloading Exchange SP3.


I understand you can backup IIS with a copy of the %SystemRoot%\system32\inetsrv\config folder
I have copies of this folder dating back to when everything was working. If I was to re-install IIS then replace the config folder with one of my backups, would this restore the settings?
0
 
Simon Butler (Sembee)ConsultantCommented:
I don't think this is related to IPv6, and I would encourage you to undo whatever changes you made to try and disable IPv6. Do you have anything other than SBS apps in the web server? If IIS has got corrupt this is going to be very painful to repair, the Exchange integration is easy, but I haven't had to do the SBS bits myself before.

Simon.
0
 
KTBerwickAuthor Commented:
I reverted the IPV6 change already.

IIS is pretty much default Exchange/SBS sites. Here is a screenshot - - http://puu.sh/88Qwy.jpg

We have full Windows Server Backups from last week when everything was working. Would restoring the System State resolve this? Not sure if IIS is included in that.
0
 
KTBerwickAuthor Commented:
Ran the following PowerShell script which has finally got OWA working again!

C:\Program Files\Microsoft\Exchange Server\V14\Bin\UpdateCas.ps1


Huge relief. Thanks for all the help. Will leave this thread open for a while until I can fully verify the issue is resolved (will soon find out when staff return to work tomorrow).
1
 
KTBerwickAuthor Commented:
The steps described are what fixed the issue
1
 
george_397aCommented:
Saved my day!

Many thanks!
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.