Exchange ActiveSync / Server HTTP_500 error
Aaron Gitlin
We have recently implemented OMA and have been unable to get it to
successfully work. I have done two other installations for OMA and have not
had a single problem. So far, I am not able to tell what I have done wrong
this time around :) If anyone has any ideas, please let me know.
Thanks in advance!
Things I have tried / setup (hopefully I didn't leave anything out):
ESM:
1) Under "Mobile Services" all of the "Exchange Active Sync" and "OMA" boxes
are checked.
2) The appropriate SMS domain is listed under the "Mobile Services" tree
IIS:
1) We are NOT using HTTPS at this time.
2) ExAdmin, Exchange, ExchWeb and Public virtual directories all have Basic
and Integrated security marked
3) None of the virtual directories in the site have "Require SSL" marked
4) The appropriate NetBIOS name is listed under "Default Domain" in the
virtual directories
5) Microsoft-Server-ActiveSync and OMA virtual directories have Basic
authentication marked only
6) The IP address for the site itself is set to "All Unassigned"
PDA:
1) Samsung i700 with Verizon Wireless - it has worked in the past with
another OMA setup
2) Have warm and cold rebooted the device
3) Disabled the CERTCHK for the device
4) "This server uses an SSL..." is not marked
5) Neither the FQDN or WAN IP of the server will allow connection
6) The credentials are correct for authentication
MISC:
1) Followed the procedures for SMTPProxy per Microsoft (we have two domains
listed in the AD - the xxxxxxxx.local domain and the WAN IP)
2) The user can access their mailbox via OWA or Outlook itself
3) We have CRM 1.2 installed / configured on this server
Server Log on the PDA:
-------------------------------------------------------------------------------------
=-= Build 13252 =-=
=-= No XIP Information Available =-=
<domain here>
=-=- [13/7/2005 17:24:40.0] -=-=
=-=-=-= Client Request =-=-=-=
OPTIONS
Microsoft-Server-ActiveSync?User=administrator&DeviceId=32000A009D3F3F71280000022AC6713F&DeviceType=PocketPC
Accept-Language: en-us
MS-ASProtocolVersion: 2.0
-=-=-=- Start of Body -=-=-=-
=-=- [13/7/2005 17:24:40.0] -=-=
=-=-=-= Server Response =-=-=-
HTTP/1.1 401 Unauthorized
Content-Length: 83
Content-Type: text/html
Server: Microsoft-IIS/6.0
WWW-Authenticate: Basic realm="<domain here>"
X-Powered-By: ASP.NET
Date: Wed, 13 Jul 2005 17:23:00 GMT
-=-=-=- Start of Body -=-=-=-
=-=- [13/7/2005 17:24:40.0] -=-=
=-=-=-= Server Response =-=-=-
HTTP/1.1 200 OK
Date: Wed, 13 Jul 2005 17:23:00 GMT
Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NET
Pragma: no-cache
Content-Length: 0
Public: OPTIONS, POST
Allow: OPTIONS, POST
MS-Server-ActiveSync: 3.0.4215.0
MS-ASProtocolVersions: 1.0,2.0,2.1
MS-ASProtocolCommands:
Sync,SendMail,SmartForward,SmartReply,GetAttachment,GetHierarchy,CreateCollection,DeleteCollection,MoveCollection,FolderSync,FolderCreate,FolderDelete,FolderUpdate,MoveItems,GetItemEstimate,MeetingResponse,Notify
=-=- [13/7/2005 17:24:40.0] -=-=
=-=-=-= Client Request =-=-=-=
POST
Microsoft-Server-ActiveSync?User=administrator&DeviceId=32000A009D3F3F71280000022AC6713F&DeviceType=PocketPC&Cmd=FolderSync
Accept-Language: en-us
MS-ASProtocolVersion: 2.0
Content-Type: application/vnd.ms-sync.wbxml
-=-=-=- Start of Body -=-=-=-
<?xml version="1.0" encoding="utf-8"?><FolderSync
xmlns="FolderHierarchy:"><SyncKey>0</SyncKey></FolderSync>
=-=- [13/7/2005 17:24:40.0] -=-=
=-=-=-= Server Response =-=-=-
HTTP/1.1 500 Internal Server Error
Date: Wed, 13 Jul 2005 17:23:00 GMT
Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NET
Pragma: no-cache
Content-Type: text/html
Content-Length: 56
MS-Server-ActiveSync: 3.0.4215.0
Rehm@discussions.microsoft.com Matthew Rehm
Rehm@discussions.microsoft.com Matthew Rehm
I was getting the same error message and getting ready to "pull my hair out"
when I stubled across your post. My configuration is the same as yours, so I
thought I would double
check all the settings you listed in your post. I had a one check boxe
uncheck and that was all it took to solve the problem. The key for me was
checking Integrated Authentication
under exchange virtual directory. I did some more testing and for me I did
not have to change an other authentication types.
Thank you for you help.
Matthew