SBS 2008 - Server Freezing when using RPC/HTTPS (Outlook Anywhere)

Hi,

Givern that there are a number of different services involved in the delivery of OutlookAnywhere it would be worthwhile examining each component, I would start with with IIS.

Does IIS respond normally in all other aspects? for example can you access OWA, Remote Web Workplace, etc without the server crashing

Are there any third party application with sites in IIS? examples would include some AV Servers or accounting applications

Andy

Hi Andy

Fair point, however OWA, OMA etc all fine...
Fairly clean server to be honest...and runs fine normally

Thanks for the suggestion

G

Hi,
I take it that this means that there are no third party applications using IIS? the reason I ask is that I have seen a similar situation where a 32bit aplication was trying to share an application pool with one of the inbult SBS Web Application pools, and any time the third party application was accessed the server hung.

You mention it crashes the server from the Microsoft test site. does it crash if you use OutlookAnywhere from a client on the LAN as well as from the internet?

Hi Sunny

Tried to run the commands you gave me but they failed (looks like syntax issue)

Tried Test-Outlookwebservices and got the following.   (changed domain name)


Id      : 1003
Type    : Information
Message : About to test AutoDiscover with the e-mail address ServerAdmin@mydomain.com.

Id      : 1007
Type    : Information
Message : Testing server SERVER2008.DOMAIN2008.local with the published name https://mail.mydomain.com/EWS/Exchange.asmx & https://mail.mydomain.com/EWS/Exchange.asmx.

Id      : 1019
Type    : Information
Message : Found a valid AutoDiscover service connection point. The AutoDiscover URL on this object is https://mail.mydomain.com/Autodiscover/Autodi
          scover.xml.

Id      : 1006
Type    : Information
Message : The Autodiscover service was contacted at https://mail.mydomain.com/Autodiscover/Autodiscover.xml.

Id      : 1016
Type    : Success
Message : [EXCH]-Successfully contacted the AS service at https://mail.mydomain.com/EWS/Exchange.asmx. The elapsed time was 203 milliseconds.

Id      : 1015
Type    : Success
Message : [EXCH]-Successfully contacted the OAB service at https://mail.mydomain.com/EWS/Exchange.asmx. The elapsed time was 0 milliseconds.

Id      : 1014
Type    : Success
Message : [EXCH]-Successfully contacted the UM service at https://mail.mydomain.com/UnifiedMessaging/Service.asmx. The elapsed time was 177 millise
          conds.

Id      : 1016
Type    : Success
Message : [EXPR]-Successfully contacted the AS service at https://mail.mydomain.com/EWS/Exchange.asmx. The elapsed time was 31 milliseconds.

Id      : 1015
Type    : Success
Message : [EXPR]-Successfully contacted the OAB service at https://mail.mydomain.com/EWS/Exchange.asmx. The elapsed time was 0 milliseconds.

Id      : 1014
Type    : Success
Message : [EXPR]-Successfully contacted the UM service at https://mail.mydomain.com/UnifiedMessaging/Service.asmx. The elapsed time was 176 millise
          conds.

Id      : 1013
Type    : Error
Message : When contacting https://mail.mydomain.com/Rpc received the error The server committed a protocol violation. Section=ResponseStatusLine

Id      : 1017
Type    : Error
Message : [EXPR]-Error when contacting the RPC/HTTP service at https://mail.mydomain.com/Rpc. The elapsed time was 13 milliseconds.

Id      : 1006
Type    : Success
Message : The Autodiscover service was tested successfully.

Id      : 1021
Type    : Information
Message : The following web services generated errors.
              Contacting server in EXPR
          Please use the prior output to diagnose and correct the errors.

start > run > services.msc

Remote Procedure Call
Has the service started
Can you restart it ?

Tks, Ok the results came back with both populated however bith are the same, both external FQDN

Identity    : SERVER2008\EWS (SBS Web Applications)
InternalUrl : https://mail.mydomain.com/EWS/Exchange.asmx
ExternalUrl : https://mail.mydomain.com/EWS/Exchange.asmx

Perhaps I should alter the internalurl or is that not an issue for the current issue?

Thanks again.

did you change mail.mydomain.com - to your local FQDN nad external FQDN

if your exchange server is SERVER2008.DOMAIN2008.local

your external FQDN is
mail.mycompany.com

you have to make the changes in the script and run it again

Get-WebServicesVirtualDirectory | Set-WebservicesVirtualDirectory -internalurl https://SERVER2008.DOMAIN2008.local/EWS/Exchange.asmx 

Get-WebServicesVirtualDirectory | Set-WebservicesVirtualDirectory -externalurl https://mail.mycompany.com/EWS/Exchange.asmx 

did it work ? let me know

OK Good,

I ran both of those commands with the appropiate internal and external urls and got no response for the command (which in my book means they took effect successfully)

I then re-ran the the query command Get-webservicesvirtualdirectory | fl identity,internalurl,externalurl

and got the updated results as applied

Identity    : SERVER2008\EWS (SBS Web Applications)
InternalUrl : https://server2008."mycompany"2008.local/EWS/Exchange.asmx
ExternalUrl : https://mail."mycompany".com/EWS/Exchange.asmx

where "mycompany" is replaced with my actual companyname (hidden for security reasons)

Perhaps this will help?

If your internal FQDN is server208.mycompany.local > then you're good
if your external FQDN is mail.mycompany.com > then you're good

Now try to access OWA

On
test-outlookwebservices

Still getting
Id      : 1013
Type    : Error
Message : When contacting https://mail.mycompany.com/Rpc received the error The server committed a protocol violation. Section=ResponseStatusLine

Id      : 1017
Type    : Error
Message : [EXPR]-Error when contacting the RPC/HTTP service at https://mail.mycompany.com/Rpc. The elapsed time was 8 milliseconds.

OWA was Ok, however it was RPC which was crashing the server, from home user access using rpc over https.

Can the above errors be ignored or do I need to get them cleared.
Tks

Can you tell me your webserver name.
We can do much better testing that way.

nslookup exchangeserver.domain.local

what happens ?

Hi Sunny

We were getting the following (noticed IPV6 turned on so we turned it off)

C:\Users\ServerAdmin>nslookup server2008.MyCompany2008.local
Server:  UnKnown
Address:  fe80::4c6d:b4cb:3e82:6406

Name:    server2008.MyCompany2008.local
Address:  192.168.80.10



Now getting the following after turning off IPV6


C:\Users\MyCompanyAdmin>nslookup server2008.MyCompany2008.local
Server:  server2008.MyCompany2008.local
Address:  192.168.80.10

Name:    server2008.MyCompany2008.local
Address:  192.168.80.10

Perhaps this will help

Thanks
G

IPv6 has to be turned on on SBS @ please turn it back on.

Lets check your DNS

dcdiag /v /e /TEST:DNS > c:\dcdiagdns.txt

Upload the file here please.

Sunny please see attached
dcdnsdiag.txt

I'm going to take a completely different approach and say that *no* IIS or Outlook Anywhere issue should *crash* a server. I've *never* see it on SBS or standalone boxes unless core OS components were corrupt. No amount of reconfiguring networking, running IIS commands, etc will fix that.
Windows simply separates the various OS layers so this type of thing *shouldn't* happen.
So, for what it's worth, I see four possible causes, in order of severity:
1) Bad NIC driver. Download the latest driver and re-install it. Wouldn't hurt to disable RSS and TCP checksum offloading while you are doing this.
2) Bad NIC. It throws garbage data to the RPC services and causes the entire system to freeze. Solution: Replace the NIC (and update the new NICs driver while you are at it)
3) Corruption in the core OS. Reinstall the OS and migrate the data to the new installation.
4) Phisical hardware failure (CPU overheating, etc). Replace the failing hardware.
It really is that simple. Windows doesn't just "freeze" anymore, or bluescreen, or any "halt" behavior, without some significant underlying cause.
-Cliff
 

Cliff
DNS Test's Failed.

What do you think ?

Thanks


                                            Auth Basc Forw Del  Dyn  RReg Ext
            _________________________________________________________________
            Domain: MyCompany2008.local

               SERVER2008                   PASS FAIL FAIL PASS PASS FAIL n/a  

DNS servers:

                        192.168.80.10 (server2008.MyCompany2008.local.) [Valid]
                        Warning:
                        208.67.222.222 (<name unavailable>) [Invalid]
                     


 DC: SERVER2008.MyCompany2008.local
            Domain: MyCompany2008.local
               TEST: Authentication (Auth)
                  Authentication test: Successfully completed
                 
               TEST: Basic (Basc)
                  Error: No LDAP connectivity

No Forwarders configured
>> Please enter your ISP's DNS as forwarders and remove root hints
start > programs > admin tools > DNS > Right click server > properties > Forwarders
ISP's DNS > enter here - 208.67.222.222

Hi guys

The NIC card looks fine and no issue with hardware.... is it not an RPC related issue ?
OMA and OWA all work fine...

Not sure what to do next....

G

did you turn ip6 back on?

> OWA was Ok, however it was RPC which was crashing the server, from home user access using rpc over https.

Does RPC over HTTPS crach the server when accesses over the LAN?

ggntt
Your DNS tests are failing

Please check my post above.

>> Please enter your ISP's DNS as forwarders and remove root hints

start > programs > admin tools > DNS > Right click server > properties > Forwarders

ISP's DNS > enter here - 208.67.222.222

Hi guys

I went off and searched for the following errors (displayed after running this commandTest-Outlookwebservices)


Id      : 1013
Type    : Error
Message : When contacting https://mail.mydomain.com/Rpc received the error The server committed a protocol violation. Section=ResponseStatusLine

Id      : 1017
Type    : Error
Message : [EXPR]-Error when contacting the RPC/HTTP service at https://mail.mydomain.com/Rpc. The elapsed time was 13 milliseconds.

Someone mentioned that it could be related to settings in IIS

expaned the ISS tree to RPC > Security and checked on "require SSL"

Tried RPC over the weekend and it worked fine.... (the client did get a certificate notifcation (snakeoil) but accepted that and it worked ok....(not sure if this was the original cause of the problem or not)

Thanks all for your help, sunny i know you put a lot of time into this (I did not change hte DNS server settings yet by the way)

Thanks again
GGNTT

Hi all

Just wanted to add this to this thread.
Have not tried it yet but the exact same problem on a second server that is also running NOD32

http://forums.msexchange.org/Outlook_anywhere_will_freeze_my_server!/m_1800512973/tm.htm

GGNTT