RE: Update: OMA Woes!

  • From: Chris Maciejewski <cmaciejewski@xxxxxxxxxxxxxxxxxxxxxxxxx>
  • To: "[ExchangeList]" <exchangelist@xxxxxxxxxxxxx>
  • Date: Tue, 13 Jan 2004 08:30:47 +1100

I Changed the VS thinking that I had screwed up permissions somewhere. Creating another VS seems to set up with the original defaults. Its with the new VS that I'm getting the 405 error.
 
I still have the Old VS. If I enable that one, and disable my new VS, I do still get the 500 error.
 
I really don't know why all these problems started at the original VS. We had the ActiveSync working with the PDAs, but it suddenly stopped!
 
Chris


From: Mulnick, Al
Sent: Tue 13/01/2004 1:57 AM
To: [ExchangeList]
Subject: [exchangelist] RE: Update: OMA Woes!

http://www.MSExchange.org/
Your original issue was a 500 error.  Now you're getting lower numerically to 405.  Perhaps that's progress? :)
 
Seriously, why did you change the VS?  What was the logic path that led you down that path as part of the troubleshooting? Maybe that will help bring us up to speed and help out a little more.
 
 
 
 


From: Chris Maciejewski [mailto:cmaciejewski@xxxxxxxxxxxxxxxxxxxxxxxxx]
Sent: Monday, January 12, 2004 5:44 AM
To: [ExchangeList]
Subject: [exchangelist] Update: OMA Woes!

http://www.MSExchange.org/
Ok,
 
Disabled the Exchange Virtual Server in the system manager, and created a new one, with same settings. Now the PDA gives me HTTP_405, which according to Microsoft is "Verb not allowed"
 
Am i gettIng any better?
 


From: Chris Maciejewski
Sent: Mon 12/01/2004 8:37 PM
To: [ExchangeList]
Subject: [exchangelist] RE: OMA Woes!

http://www.MSExchange.org/
I turned on verbose logging to see what's going on, this is what I get; in case anyone is interested!
 
 
=-= Build 13100 =-=
=-= No XIP Information Available =-=
naomi
=-=- [12/1/2004 9:29:34.0] -=-=
=-=-=-= Client Request =-=-=-=
OPTIONS Microsoft-Server-ActiveSync?User=lburn&DeviceId=73040F051407036178000050BF1977E0&DeviceType=PocketPC
Accept-Language: en-us
-=-=-=- Start of Body -=-=-=-

=-=- [12/1/2004 9:29:34.0] -=-=
=-=-=-= Server Response =-=-=-
HTTP/1.1 200 OK
Date: Mon, 12 Jan 2004 09:32:03 GMT
Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NET
Pragma: no-cache
Content-Length: 0
Public: OPTIONS, POST
Allow: OPTIONS
MS-Server-ActiveSync: 2.0.3274.0
MS-ASProtocolVersions: 1.0,2.0
 
=-=- [12/1/2004 9:29:34.0] -=-=
=-=-=-= Client Request =-=-=-=
POST Microsoft-Server-ActiveSync?User=lburn&DeviceId=73040F051407036178000050BF1977E0&DeviceType=PocketPC&Cmd=GetHierarchy
Accept-Language: en-us
-=-=-=- Start of Body -=-=-=-

=-=- [12/1/2004 9:29:34.0] -=-=
=-=-=-= Server Response =-=-=-
HTTP/1.1 500 Internal Server Error
Connection: close
Date: Mon, 12 Jan 2004 09:32:03 GMT
Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NET
Pragma: no-cache
Content-Length: 0
MS-Server-ActiveSync: 2.0.3274.0
 


From: Chris Maciejewski
Sent: Mon 12/01/2004 8:34 PM
To: [ExchangeList]
Subject: [exchangelist] OMA Woes!

http://www.MSExchange.org/
Hi all,
 
Got a PDA running Pocket PC 2003. Trying to ActiveSync directly to our Exchange 2003 Server.
I get a HTTP_500 Synchronisation failed because of a server error.
 
I have tried the Microsoft Articles that suggest;
 
Re-enabled Kerberos or Windows Integrated Authentication
(Kerberos using cscript adsutil.vbs set w3svc/NTAuthenticationProviders)
 
Ensuring SSL is disabled
 
I cant try Disabling DevTools because we aren't running Mobile Info Server. Just Exchange 2003
 
 
Can anyone shed any light? One minute it was working, the next minute it wasn't. I don't recall actually making any substantial changes, if any changes at all, to our Exchange server.
 
Thanks,
Chris
 
--------------------------------------------------------------------------
 
Chris Maciejewski
Computer Technician
 
Catholic Education Office
Diocese of Ballarat, Victoria, Australia
 
 
--------------------------------------------------------------------------
 
This email message (and attachments) may contain information that is confidential to the Catholic Education Office, Diocese of Ballarat. If you are not the intended recipient you cannot use, distribute or copy the message or attachments. In such a case, please notify the sender by return email immediately and erase all copies of the message and attachments. Opinions, conclusions and other information in this message and attachments that do not relate to the official business of the Catholic Education Office are neither given nor endorsed by it.
------------------------------------------------------

Other related posts: