Related
Ok I have wrestled with this for 2 days straight.
I had issues with this with my CFO's windows mobile device but at least his was giving me a specific error message.
My Tilt has the latest Dutty ROM upgrade (Dual Touch), I haven't been able to get my exchange server synced OTA.
I run a Exchange 2007 Enterprise environment. Everything on the server side is fine. My OWA url is https://webmail.firethornmobile.net. All I get is waiting on network after 2-15 minutes.
I have soft reset, deleted the PC partnership, taken my connection off of auto and tried both my work connection and isp.
I'm starting to suspect it maybe the ROM upgrade but it was doing the same thing when I first started the phone.
Please help.
OMA enabled?
Do you have the OMA enabled? Do you have the server root CA installed in the tilt (I am assuming you are using secure method for OMA)?
I have flashed Dutty's dual touch v2 and I don't have problem to get emails through OMA services.
Do you ever get the other PDA sync with email before? From the error message, it seems the Activesync in the Tilt can't talk to the exchange (front end) server at all.
Yes on Exchange 2007 OMA is enabled natively. In the middle of seperating data centres from our sister company.
We just got bought by Qualcomm so we never bought a cert from Verisign. I am using a self sign cert from our exchange server ( I have to turn SSL off on the pda side.
This has never worked, I already called Cingular and they said if I can get webmail from gmail and hotmail then it isn't their problem.
I have installed the self signed cert on the handset.
OK, you don't need to install the self-signing cert in the PDA, but you need to install the root cert of the self-signing cert in the PDA.
Usually, a server cert or user cert has a root authority (CA), you need to install the CA cert in the PDA, not the server cert.
If you can install a window server (2000 or 2003), you can enable the certificate authority server and issue your exchange server a server certificate. In this case, you will have your own root certificate. I don't suggest you to use Verisign's certificate because everyone has Verisign's root certificate can try to "play" with your OMA server.
However, the error message is still showing that the Activesync in PDA can't reach to the OMA at all.
BTW, the push email doens't work if it's not on the SSL connection.
I apologize that I wasn't clear. Its is the root cert from the CA (Which is our DNS server).
I realize the message means that it isn't getting to OMA. I have been on the phone with AT&T and HTC aboutthis and no one can tell me why it can't connect. I have been given tons of different network settings by AT&T and HTC and nothing changes. I get different error messages but when i put everything back to the way it should be it still gives me this generic message.
I have configured my CFO's handset to get email (Its Palm Treo with WM 6.0) and even though that was a pain in ass it still works (just as good as his Blackberry) and he has SSL unchecked as well.
In that case, you can try to see if you can reach to the OWA from your PDA, if it can, you shall not have network issue.
BTW: the connon name of the server cert must be the same as your public domain name, otherwise, the Activesync will still reject the connection.
Apex i ITR said:
I apologize that I wasn't clear. Its is the root cert from the CA (Which is our DNS server).
I realize the message means that it isn't getting to OMA. I have been on the phone with AT&T and HTC aboutthis and no one can tell me why it can't connect. I have been given tons of different network settings by AT&T and HTC and nothing changes. I get different error messages but when i put everything back to the way it should be it still gives me this generic message.
I have configured my CFO's handset to get email (Its Palm Treo with WM 6.0) and even though that was a pain in ass it still works (just as good as his Blackberry) and he has SSL unchecked as well.
Click to expand...
Click to collapse
I agree with the poster above. I have this exact same set up at my company and it does work. The certificate has to be the external name of the exchange server. If this does not match the PDA will never sync. Check your certificate and make sure the FQDN is correct.
I just check your exchange server from the URL you posted above, your OMA and OWA are working, but the certificate's common name is not the same as the public domain name.
Try to re-issue the certificate, it may just work.
Thanks guys. I'll try that.
Webmail does work from the handset. I don't know how I got my CFo's working to be honest if its flaking on the name of the cert but I'll try that and let you know. I was about to hard reset this thing and leave the cooked ROM's alone for a while. Hopefully this resolves it.
From my experience dealing with Acticesync in the PDA, it's very picky of the name of the certificate. I think that's security reason. The Activesync doens't accept certificate that common name doesn't match the public domain name.
When I use the IP address for test, I have to get a certifiate with the IP address as its common. So I believe that's the certificate's problem, not the cooked rom.
I still suggest you to get your own CA and certificate, in that way, you have more control even debugging this problem.
I feel like a moron asking but how the hell do I change the common name.
You can't change an existing certificate, you have to re-issue a new certificate.
I guest you can't do it by the self-siging certificate, but I am not fimiliar with the self-signing certificate. Get a WIN server machine and install the CA server, after that, you can issue a certificate.
Assumeing you have a CA server ready:
1. Request the certificate from exchange server: you will have a chance to enter the common name of this certificate.
2. Generate a certificate from this certificate request from CA server
3. Import the certificate back to the exchange server.
If you can't get a WIN server as CA server, I will need to ask my colleagues about the free CA server he used from the Internet.
My DNS box is a CA server (started the service on that).
I'll try that then (I hard reset and I now I have an error stating I'm not authorized).
I'll let you know if it works. Thanks.
Ok I believe I did it right but I still get tha error (When connect via usb cable) and I still get the waiting for network message.
When you connect to the USB cable, you have to "allow" the Internet access pass through from the Activesync in the PC, otherwise, it won't reach out to the Internet at all.
Try to connect to other web site to see if you have a good internet connection or not.
Some updates. I made sure the cert is the right common name. I noticed that after I install it on the handset it doesn't put the cert in the root tab...only intermediate. I installed the ca server's cert as well (That went into the root tab).
Im leaving ssl checked and now I get 0X80072F17.
incorrect common name
Your common name is still not correct, it shall be "webmail.firethornmobile.net" only, but you put "http://" at the begining and "/owa" at the end, it not correct.
You have to issue the server certificate one more time with "webmail.firethornmobile.net" (without quotes) as the common name.
Also, when I check the Certification path of your certificate, I don't see this certificate is under any root certificate. Properly you need to check your CA (DNS) to see if it's setup properly.
Hey,
Use this site to figure out the errors you are getting on your phone. http://www.pocketpcfaq.com/faqs/activesync/exchange_errors.php
Also are you the Exchange Admin? If so enable verbose logging so that you can see what is going on with exchange as the connection comes in.
Also if you want to make sure it is not the cert you can "Enable" SSL on the phone and then reg hack it so that it doesn't check for the cert. this will allow you to see if it is a cert problem.
Let me know if you need any help with that. I"m an Exchange Admin and i work with Active Sync day in and day out.
Tried Fix Suggested on Pocket PC FAQ Site
I think this is ON TOPIC. If not, please advise and I will repost elsewhere.
I flashed my phone with the Dutty Beta 2 Touchflow ROM for Tilt. I am getting the following error and have tried the matched solution from Pocket PC FAQ:
0x80830003 N/A Synchronization failed. If the problem continues, contact your network administrator.
1. The Exchange server is configured to require client certificates.
1. On the Exchange server, launch Internet Services Manager. Right click on the Microsoft-Server-ActiveSync virtual directory and choose Properties. Select the Directory Security tab. Click the Edit button in the Secure Communications section and select the option to “Ignore client certificates.”
I continue to get the same error even after dumping the device through the exchange server.
My System Admin thinks that there is something wrong with the version of ACTIVE SYNC provided in the ROM used to flash the device.
Any thoughts/direction you could point me in or is there any other info you need?? Is th
Hi all,
Impossible to synchronize with my exchange server using a latop or 3G or Wifi
always got an 0x85010015 error reverting to wm6 no more error
some idea
poussin69 said:
Hi all,
Impossible to synchronize with my exchange server using a latop or 3G or Wifi
always got an 0x85010015 error reverting to wm6 no more error
some idea
Click to expand...
Click to collapse
I saw in you other post that you are running : 8.1.122...strange version ...
Exchange 2007 SP1 is : 8.1.240.0
And Exchnage 2007 is : 8.0.685.0
What's your exchange ?
SP1 beta 2
rollup package 3 for exchange 2007 is needed
http://support.microsoft.com/kb/934402
Certificate?
I also BELIEVE that you need a CA Security Certificate. Self Signed doesn't work. Don't have direct proof of this statement only from reading documentation and the fact that in other arenas (including Sharepoint integration) you have to use a CA Cert.
anyone tried this with getztek ?
0x85010015 - 1
Also have you tried the disable TASKS in Activesynch, soft reset, enable TASKS in sync trick?
0x85010015 - 2
For testing just yourself with a qualititively different phone in terms of either hardware or ROM on the phone - this is a long shot because you don't have others at the Enterprise to test this idea before deciding it is only happening to you or everyone
It is a long PIA to do but actually worked for me the other day. Remember in this case - the clue was that it was only one person in the Enterprise having the problem. All others (with identical phones) were not.
Somewhere DEEP in Google Groups is a discussion (sorry I lost the link) of this error code which saved me the other day when it was only happening to ONE person in the Enterprise.
In essence there is a corrupt entry in their Exchange Storage somewhere. The fix is to:
Back their mailbox up to a PST by ExMerge or Export tool in Outlook
Run the PST repair tool on the PST file
Delete their Mailbox in Exchange.
Run Exchange Cleanup
Create a new empty mailbox
Import their data from the PST file.
Like I say - long shot but worked for me.
I was able to test on a SP1 Exchange 2K7 a real one and it works
Cheers
poussin69 said:
Hi all,
Impossible to synchronize with my exchange server using a latop or 3G or Wifi
always got an 0x85010015 error reverting to wm6 no more error
some idea
Click to expand...
Click to collapse
I use a hosted exchange mailbox, syncing & push email work perfect for me, even with WM6.1, never tried it with the original roms but my cooked one has no issue with exchange for sure!
Hi, I just upgraded to the official Dutch WM 6.1 ROM. Everything is working great... except Exchange sync! I get the error 0x85010015 too. The system administrator says he is already running Exchange 2007 SP1 which would contain the mensioned update.
Does anyone have an idea on what I can try to get Exchange sync working?
Exchange 2007 SP1 here, and works fine with every WM6.1 ROM i have tested (including official ones by HTC)...
Cheers.
I this a production E2K7 environment? Why not install RTM bits???
I'm on HTC's "official" WinMo 6.1 Rom on my Tilt and have no issues with email sync ... as for certs to the listener in the ISA server, you can use self signed (not recommender), but unified certs with multiple alternate names are problematic on ISA Server 2006.
I downloaded the new WLM beta for my PC, mainly because I liked the sound of the MPOP (multiple points of presence) feature, allowing me to sign into my Windows Mobile device at the same time as my PC (i.e. it doesnt sign out of the PC, and i get the messages on both).
This would mean, I could use WLM on the PC, step away with my phone, answer some IMs, and come back to the PC without signing in and out, and losing track of a conversation, as well as my chat logs being complete.
Or so i thought, as signing into my mobile device still signs me out of WLM 2009 on the pc. Apparently both devices need to support MPOP.
According to WLM 2009 support page "If you sign in to a version of Messenger that doesn't support the multiple sign-in feature, you will automatically be signed out from the other devices."
But it also says "For example, if you're already signed in to Messenger on a computer, you can sign in on a mobile device or on another computer without having to sign out on the first computer"
So why do they say mobile device? Where do I get a version for my mobile device that supports this? Is my WLM mobile out of date?
Thanks
It´s the same for me, I don´t know if there is a version for Mobile devices that support this ultiple places
Hope someone can give us a clue
I hope Messenger for WinMo is updates soon to take advantage of this feature
>>"But it also says "For example, if you're already signed in to Messenger on a computer, you can sign in on a mobile device or on another computer without having to sign out on the first computer""
So, it basically says that you don`t have to sign out from computer (if you`re signed in) when you want to signing in from ppc. It doesn`t say anything about MPOP :/ Just that signing in is possible even if you are signed in on another computer when you sign in with ppc. lul, complicated. I hope wlm on winmo gets updated soon.
Yes, Microsoft will be releasing a new WL Messenger for Mobiles in next year... It will happen, just give it time as they need everything else in place first.
Hopefully the new WLM doesn't get treated like the new Pocket Internet Explorer (new WM6.5 ROMs only).
I sign into WLM on my mobile fine now without it signing out on my computer?
According to Paul Thurrott's site about windows:
The native Windows Live Messenger client on Windows Mobile supports the new Multiple Points of Presence (MPOP) functionality that allows you to be signed in to Messenger from multiple PCs, mobile devices, and Web sites.
Click to expand...
Click to collapse
Since i don't remember if it's possible to link other sites, just google the statement to find the full article (part 4).
I'm wondering which version he has of WLM... i'm really thinking of sending him a message to ask clarifications.
I have a version of WLM that is newer than the one posted in the big WLM thread on here. And I get signed out of WLM on the PC. I'd love to know what version he has, or why he said that.
The version of Windows Live messenger I am using is 10.6.0034.0800
On my desktop, I use the Windows Live messenger beta (can't tell you the number as I am not at home).
Signing into one does not sign me out of the other....
Joezhang said:
The version of Windows Live messenger I am using is 10.6.0034.0800
On my desktop, I use the Windows Live messenger beta (can't tell you the number as I am not at home).
Signing into one does not sign me out of the other....
Click to expand...
Click to collapse
Wow r u kiddin? trying gettin 34.800 somewhere to check it out.
EDIT:
Installed 34.800. No way. Signs me out. Using latest RC on pc.
What I'm reading here is that you guys have logged in to Live on your PC with the new 2009 client and you can STILL log in on your mobiles - is that right? All I'm getting after having logged in once to the new client on my PC is the "problem with the server" message on my phone. I change the account back to an old one that has never logged in to the new PC client and I'm OK.
Is there a workaround or particular version that is working now on the phone?
Thanks
The only version of the desktop Windows Live Messenger that supports MPOP is the version that downloads to the Windows 7 beta. Version 16.something IIRC
dontpannic said:
The only version of the desktop Windows Live Messenger that supports MPOP is the version that downloads to the Windows 7 beta. Version 16.something IIRC
Click to expand...
Click to collapse
Not true.. WL Messenger 2009 (version 14.0.x) does support MPOP.
The problems come with WL for Windows Mobile, which seems not to support MPOP Signing at all. It disconnects from everywhere when sign in on the phone.
EDIT: AFAIK there's no 16.x version specific for windows 7.
I have asked to Paul Thurott about WLM for mobile supporting MPOP and he has told me that new mobile phone will get the WLM with MPOP support.. but there will be nothing for old phones. We should find a cab of a version supporting MPOP.
It's the same about WebMessenger... which does not support MPOP .. but the new Windows Live WebMessenger should comes out soon !
i am sure a CAB version will appear shortly after relase. one good thing with so many carriers using winmo is that one is bound to leak it.
they also need to update Xbox NXE to support MPOP too
koala996 said:
We should find a cab of a version supporting MPOP.
Click to expand...
Click to collapse
What about WL for mobile from WM6.5?
playerkiller said:
What about WL for mobile from WM6.5?
Click to expand...
Click to collapse
still nothing ... even with 10.7 version of WL ... umbelievable ! I don't know what Microsoft is doing about MPOP support for WLM !
Hello,
currently, my mobile network provider (giffgaff) do not support BIS/BES, so no bbm for me, so, would it be possible, to install windows server 2003 on my old pc connected to the internet, then install and exchange server, then install BES onto that, and get bbm that way?, would that actually work, or do i have to pay BB to use it, or anything, thanks for you help
Bump......
Hello,
I recently got a Lumia 800 - had i iPhone 3GS before.
And there you can sync your calender with ActiveSync.
But for some reason it doesnt work on Windows Phone 7.5
Any of you got it working or have some idea how to get it working?
Everytime i try - it just keeps asking for user and password, like it doesnt send it correctly to the server. Even got my username changed to [email protected] cuz I had an idea that it used <username>@<domain> you type in the account info. But didnt work either.
What server are you trying to connect to? I've used ActiveSync with several versions of Exchange, plus Google's implementation, and they've all worked just fine (including calendar sync). The most trouble I had was my office's Exchange server, which required that I provide a certificate on the phone... but the error message told me that, so it wasn't hard.
Note that username, domain, and server are all different fields and my have nothing to do with each other at all. Use the same settings you used on your iPhone and it should work, though.
GoodDayToDie said:
What server are you trying to connect to? I've used ActiveSync with several versions of Exchange, plus Google's implementation, and they've all worked just fine (including calendar sync). The most trouble I had was my office's Exchange server, which required that I provide a certificate on the phone... but the error message told me that, so it wasn't hard.
Note that username, domain, and server are all different fields and my have nothing to do with each other at all. Use the same settings you used on your iPhone and it should work, though.
Click to expand...
Click to collapse
Its a FirstClass mail server - that has a ActiveSync feature. I dont know much about the server part. Mostly schools and similar that use it as mailserver
There is no SSL support - so a certificate error it can't be?
I've been using ActiveSync for years with Google on iOS/Android. But I guess its the service that provides ActiveSync on our server that is the problem.