Database Info

Activesync and Office 2007

After installing Office 2007 I was not able to synchronize. Here's the fix that I found.
1) Connect your phone.
2) Open Outlook 2007.
3) Help > Office Diagnostics.
Run the diagnostics, and it will likely tell you that there’s one setup thing wrong. Close and reopen Outlook, and you should see your device synchronize from scratch, just as it should be.

Helped me!
Excellent! I was having problems syncing after upgrading to Eqinoxe's ReTOUCHed rom, did your fix (1 error detected and fixed) and now syncs fine. Funny, I had no problems with an older Fario WM6 rom, just this recent Touch ROM. Anyway, thanks again

No Exchange 2007 sync with New official WM 6.1 Rom

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.

Can sync OTA with a 6.0 rom - but not the 6.1 rom - error 8503001c

It does not work for me when I try to sync to an exchange server with a 6.1 rom. With a 6.0 rom I can always sync with both the Outlook on the PC and the exchange server. But when I upgrade, I can only sync with the Outlook on the PC - sync with the exchange server fails to work. It fails when I try OTA, and it fails when I try with USB. I have tried 3 different 6.1 rom for kaiser, and also tried on a 6.1 rom ELF I have - with the same result. But when I go back to a 6.0 rom - everything works again. I have tried setting up the phone manually - to make sure it is identical with the 6.0 rom - but still no luck. I can sync with mails, calendar etc on the Outlook on the pc, but when I change it to sync with the server - it wont.
Does anyone have a solution?

Is there not at single person that can help me with my problem??
I really want to upgrade to 6.1 rom - but can't, since I have to be able to sync with the exchange server for work reasons.....

Mine just works. Sorry I wish I could help but I wanted to let you know mine has worked on every rom I have tried. Sleuth right now.

finch said:
Mine just works. Sorry I wish I could help but I wanted to let you know mine has worked on every rom I have tried. Sleuth right now.
Click to expand...
Click to collapse
I wish I could say the same....
And you did nothing different when setting up the phone with the 6.1 rom compaired to the 6.0 rom? Have you noticed any differences in the settings?

How do you upgrade to 6.1 currently?

bull3001 said:
How do you upgrade to 6.1 currently?
Click to expand...
Click to collapse
LOL
WIKI...WIKI....WIKI...Sticky....Sticky...Sticky!!! (Chanting)

bull3001 said:
How do you upgrade to 6.1 currently?
Click to expand...
Click to collapse
Hmm..... - I don't quite understand your question? Everything else works fine after the upgrade....

verify that the exchange server is 2007 SP1 or 2007 RTM with rollup 3

poussin69 said:
verify that the exchange server is 2007 SP1 or 2007 RTM with rollup 3
Click to expand...
Click to collapse
I am using the exchange server at the company where I work - and dont have much knowledge of that - but I am pretty sure they still rund 2003 exchange server. Do you need to have exchange cerver 2007 for using 6.1 rom?.

Are there not anybody that have a solution to my problem? Or do I really have to stay with a 6.0 rom?

I think you need to hard reset again
00s of people use OTA with Exchange with 6.1 without any problems
Odds are it is something you did wrong or a bad flash.
Re-flash, hard reset, try to re-load your radio, rinse, lather repeat

Nobody has a solution because nobody else is having this problem. I just upgraded to 6.1 yesterday and have no issue with OTA sync with our exchange server (2007 w/SP1).
What error are you getting when you try to sync? There is a lot of troubleshooting that can be done, but it may be difficult for you to do so without help of the Exchange server admin. If you're actually hitting the Exchange server, there are various logs that can be accessed, but for starters, we'd need more info on what exactly the problem is other than 'I cant sync'. I assume you're getting some sort of 0x00000000 type error?

Exchange 03
""My First Post""
I flashed with Duttys 6.1 a couple of days ago and am in Tennessee using At&t and used the 1.64.06.04 radio. I'm the Network Admin at my company and use Exchange 03 and everything works great for pushing email, calendar, etc. Basically im just saying that 07 isn't required. Perhaps you should try a different radio? Just throwing in my two cents worth as this is my first Phone ROM flash I've done since my MPX200.

bzowk said:
""My First Post""
I flashed with Duttys 6.1 a couple of days ago and am in Tennessee using At&t and used the 1.64.06.04 radio. I'm the Network Admin at my company and use Exchange 03 and everything works great for pushing email, calendar, etc. Basically im just saying that 07 isn't required. Perhaps you should try a different radio? Just throwing in my two cents worth as this is my first Phone ROM flash I've done since my MPX200.
Click to expand...
Click to collapse
As long as he has data connectivity, it's likely not the radio. He just hasn't given us enough info to go on. One thing you might check is to try with both SSL enabled and disabled but I only bring that up because someone here recently upgraded their phone and forgot about that checkbox, but of course they were getting a specific error that helped me to solve the problem.

Error code
The errror code I get is:
8503001c
I thought I had already written that - but my mistake. I have googled, and I have not found one solution that could help in my case. Often it is an errorcode you get related to Vista - and I am running XP.

PPCBANDIT said:
The errror code I get is:
8503001c
I thought I had already written that - but my mistake. I have googled, and I have not found one solution that could help in my case. Often it is an errorcode you get related to Vista - and I am running XP.
Click to expand...
Click to collapse
Read some of this. From what I've read here and elsewhere, it seems to me like that error is caused by some sort of corruption in the data that's trying to sync. Try to sync just mail, if that works, add tasks, etc until you encounter the error. See here for more info:
http://forums.microsoft.com/windowsmobile/ShowPost.aspx?PostID=2769442&SiteID=65

Cool - thanks for the different advices. I will try during the weekend to reflash - and check for some corrupted files. Hopefully it will work out at the end.

Same problem here HTC TYTNII
After upgrading to a WM 6.1 rom no sync with the Exchange-server
Error 8503001c.
Trying to downgrade to WM6.0 rom at the moment.
If anybody find a real solution please let me know

I tried a whole weekend - and finally I managed to be able to syncronize my mails with the exchange server. I dont know why it suddently accepted the mails - and I left it there, and i settled for that.
I normally also syncronized contacts, calendar and tasks with the server with my WM6.0.
I tested for corrupted files - found nothing. Even when I deleted all the contacts in the contact folder, it still would not syncronize with the exchange server.
I did not go any further with the issue - since apparently I was the only one. So please let me know if you find any logical explanation - because I would prefer being able to syncronize with the Server instead - expecially for my calender.

And what has changed??
PPCBANDIT said:
I tried a whole weekend - and finally I managed to be able to syncronize my mails with the exchange server. I dont know why it suddently accepted the mails - and I left it there, and i settled for that.
I normally also syncronized contacts, calendar and tasks with the server with my WM6.0.
I tested for corrupted files - found nothing. Even when I deleted all the contacts in the contact folder, it still would not syncronize with the exchange server.
I did not go any further with the issue - since apparently I was the only one. So please let me know if you find any logical explanation - because I would prefer being able to syncronize with the Server instead - expecially for my calender.
Click to expand...
Click to collapse
Please can you tell me what has changed?? Do you still use a Rom with WM6.1??
I just returned to a 6.0 Rom and Atcive Sync works like a train. No problems at all. So can somebody figure out what is happening here??
Is it a WM6.1 and Exchangeserver 2003 issue?? There must be more companies using still the Exchange 2003 ?? (Maybe we even stll have it running on a Win 2000 server )

Windows Mobile 6.1 SMTP issues (MS acknowledged)

Thought you guys might be interested in this - credit to the author Matt
Windows Mobile 6.1 SMTP issues
18/09/08 10:37:37 am by Matt - 718 words
Categories: News
Do you have a Windows Mobile 6.1 powered device and use either POP3 or IMAP4 with SMTP? Have you encountered problems sending email or seen the error message below?
If the answer to either of the questions above is yes then read on as what you are seeing is actually a bug that affects all WM 6.1 powered handsets!
Background
I first discovered this problem a few months ago while using my HTC TyTN II. I have access to two Exchange servers but, as you'll probably know, you can only set up one Exchange activesync partnership per device. So for the other account I have to use IMAP4 and send over SMTP.
I've been using the setup for about 18 months and it works perfectly well for me, well until HTC released the WM 6.1 update for the TyTN II it did.
I installed the 6.1 update on the TyTN II and set up my Exchange and IMAP4 accounts. Was able to receive email with both accounts, no problem. All was well until I tried to send an email from my IMAP4 account (through SMTP). Upon trying to send mail I simply got presented with the error message above. I checked the account settings, they were all correct, but still unable to send mail.
I then restored the original WM 6.0 ROM to the TyTN II and the problem went away! This lead me to think that there was a problem with HTC's implementation of the 6.1 ROM. However later test revealed this to not be the case.
I set up my IMAP4 email on my new HTC Touch Diamond and was able to send one email, but subsequent emails then failed with the same error message. Deleting and recreating the account allowed me to send one or two more emails before it then failed again. One sending failed the account never works again!
So I contacted one of our friends at Microsoft to try and work through the problem.
Having worked with the guys at Microsoft for the past 6 weeks or so (including the top Outlook Mobile chap in the US) and having sent them my TyTN II to test we have discovered the following bug affecting ALL Windows Mobile 6.1 devices.
You can see more in the email excerpt from Microsoft below:
We are done with it and just checked in a bug fix last week to address what turned out to be a severe product bug that will affect all WM 6.1.x devices until they receive a fix or upgrade to WM 6.1.4. Your help both made us aware of the issue before it bubbled up through the forums and your device actually did help us debug the issue.
We are driving the issue with our response team and pushing to make a fix more broadly available independent of a device update.
More details on this bug:
Symptoms:
At some point sending e-mail stops working for a given e-mail account.
This will happen if the there is *any* failure to connect to the SMTP server – ever. After that point the user cannot send mail with that account again.
Recovery:
The user must delete their e-mail account and recreate it each time this happens.
There is no way to prevent this from reoccurring.
So as you can see, the problem is pretty severe and affects all devices with WM 6.1. The work around, if you can call it that, is to delete the affected account and recreate it.
I also suspect that this bug is related to the problem that many people report with GMail on their mobile and the reason why you must delete and recreate an email account if any of the account credentials change.
Microsoft are working on the problem at the moment and are hoping to make an independent update available. Let's hope that it will be available in that format rather than part of a full ROM update as I suspect that it will take time to filter through the manufacturers and the operator supply channels.
If you are affected by this issue then do drop me a line and I'll endeavour to keep you updated with the progress of the fix.
EDIT: Please see this post for a potential fix to the problem!
Posted by: Matt
[ Post Tags: smartphone news, windows mobile news, WM 6.1, SMTP Error, bugs, tracyandmatt.co.uk ]

lui2001 said:
EDIT: Please see this post for a potential fix to the problem!
Click to expand...
Click to collapse
Could you please provide the actual link?!

This rocks!!! I have been playing with other solutions (from MS, Tmobile, XDA, etc) for months, nothing worked more than a few days. So far so good!! ken

I have tried all patches and fixes suggested
as sais i tried all patches and fixes suggested still no result on my xperia x1 . upto now i noticed one time that my kpnplanet dutch account has sent my outbox. after a reboot/ system hang
is microsoft having a future update coming? i have spent many houjrs getting it to work..unfortunately without result yet...
tx for any advice

Are there any updates relating to this issue? I too was recently affected by this bug and it is very annoying.

Bug in Windows Mobile 6.1?

Hi,
I have a problem with my touch pro with every ROM I have testet yet (didn't test a wm 6.5 ROM) and a co-worker has the same problem with his samsung omnia i900:
When I create a appointment on the pda with yearly occurance and sync with the pc (testet with xp and vista64 with office 2007) it occurs every 12 years on the pc. It seems someone mixed up months with years..
Is this a known bug? Is there a fix?
Greetings
Eddie73

Update
Sorry to bother you all, but I still have no solution.
As an Update: The same happens with a 6.5 Rom (latest Energy 3.0). A Friend with a Touch Hd seems not to have this problem (he is running Duttys V3.4 XT System 21048). The newest 6.1 ROM I could find for the touch pro was 21046 which had the same Problem.
Could anybody please check this with his phone, please?
Greetings
Eddie73

It's not WM 6.1 but Office 2007 Servicepack2
Seems I'm only talking to myself.. Another update:
Today I did a lot of tests: I installed a fresh outlook 2007 German in a virtual machine: syncing works. Installed SP1(for office): syncing works. Installed SP2(for office): New yearly appointments created on the phone occur only every 12 years on the PC... (Before SP2 there isn't even the option to make a appointment every x years..)
So Service Pack 2 for Office is the fault.... (I should get paid for this...)
Could anybody try this with SP2 (it can be uninstalled (seperate download))?
Greetings
Eddie73

Wow good find, yes I can confirm that occurence in Outlook Professional 2007 SP2 says 12 years.
Steps to reproduce.
1) On my HTC Touch Pro, create New Appointment;
Subject: Dummy
Location: Nowhere
Occurs: Every 4 June (for today's date)
2) Press Ok, and then Sync with Active Sync and Outlook SP2.
3) Go to Calendar in Outlook, double-click on the Dummy Appointment (select Series not single occurence and it shows Occurs every 12 years on June 4 effective 04/06/2009 from 12:00 to 13:00.
Confirmed!
a) My HTC Touch Pro is using Latest Stock ROM from HTC - WM 6.1 Pro.
b) PC O/s is Windows XP 64 bit and latest patches.
I think your assumption is right, it's an issue with Office 2007 and Active Sync. Not sure whether this was introduced in SP2 though!

Same problem here.
I sync my Touch HD on two computers:
Home - Vista 32/ WMDC 6.1/ Outlook 2007 SP2
Work - Win 2003 server/ ActiveSync 4.5/ Outlook 2007 SP1
Touch HD - Duttys 3.7XT (win 6.1 - build 21051) with Manila 2.1
Whenever I sync calendar on either machine alternately all yearly appointments (birthdays) occurs every 12 years.
It is only when I sync with "the other" computer it happens.
ie.
- I sync home computer
- I fix the appointments
- I later re-sync home computer
and all is ok.
if I then later sync to work computer, we're back to 12 years again.
This is also vice-versa, so if I fix the appointments on my work computer, I can sync that computer however many times I want. When I then later sync at home, 12 years...
I suspected an issue with WMDC 6.1, so I downgraded it to WMDC 6.0. But it didn't help...
I upgraded work computer's Outlook 2007 from SP1 to SP2 hoping that would help, but no.
I'm not sure when this error first occured. So I can't be sure whether the problem is with WMDC, Activesync, Outlook 2007, WinMo or Manila 2.0/2.1.
I think I'm starting to look into syncing with google OTA instead...
brgds
Royan

Exactly the same problem on my Omnia (latest original ROM).
I sync to two computers (both XP, Outlook 2007 SP2). Syncing works in the meantime (at least sometimes; Support Code 86000107 ).
Try changing the items from yearly appointment to "every twelve months".
It might work.
I experienced some funny things after changing to "every twelve months" and sync. Here's an example:
Computer 1: "every 12 months" beginning on June 6 ....
Computer 2: "every 12 years" beginning on June 6 ....
Omnia: "Every June 6"
Ain't it funny?
Andreas
PS: Sometimes I long for my old Prophet.

FYI: Uninstalling SP2 for Office solved this problem on both Computers I sync with (it happened to both of them).
I assume not all people with this problem use the German version of Office 2007?
This is such a basic function for an pda.. and it doesn't work correctly with a fully patched current version of office..
Greetings Eddie73

Same problem here
I have the same problem when synchronizing my Touch HD with two computers using Office SP2.

The problem is also being discussed in this Microsoft thread:
http://social.microsoft.com/Forums/...p/thread/8dbfde6c-9788-4ff9-a4b8-6b5751b765da

As a heavy user of the Outlook calendar, this bug is by far my biggest gripe. I really hope they get this resolved. I am seriously starting to consider other platforms that seem more reliable.

I'm also having this issue. I have two computers, one has Windows XP SP3, Outlook 2007 SP2, ActiveSync 4.5; the other has Windows 7 64 bits, Outlook 2007 SP2 and WMDC.
Do I have to uninstall SP2 from both computers or just one? I'm going to try uninstalling it on the Windows XP computer and see how it goes. I'll keep you updated.
Update: On the XP computer I have been able to uninstall SP2, but not SP1. SP1 cannot be uninstalled. And my install disc has SP1 included. If I must get rid of SP2 and SP1 on both computers to get around this, I'm out of luck, it seems.
Someone tried Outlook 2010 yet?

I have spent a couple of hours doing some tests, and unfortunately I have bad news. This bug is most like caused by a change in Outlook 2007 after installing SP1 or SP2 (I can't tell at this moment), which breaks Calendar synchronization with ActiveSync or Windows Mobile Device Center 6.1 (and 6.0). Moving to Outlook 2010 beta won't help either.
The test consisted on setting up two different computers with the following configuration:
Computer 1: Windows 7 32 bits Ultimate Release Candidate (that's the "spare" computer I can use for tests), with Office 2010 Home and Office beta and Windows Mobile Device Center 6.1.
Computer 2: Windows XP Professional SP3 32 bits, with Office 2007 SP2 and ActiveSync 4.5.
PocketPC: FS Loox N560 in which I used PIM Backup to transfer appointments, contacts and tasks from my main PDA. The FS had no previous association, and no PIM data, almost like hard-reseted.
I proceeded as follows:
I restored appointments, contacts and tasks into the PocketPC. Checked that data was there and seemed correct (some 205 contacts, 143 appointments, 7 tasks).
Then plugged the PocketPC to Computer 1 in order to load my PIM data into this clean install of Outlook (there was no previous data, I just set up one email to get it started).
First surprise, after WMDC completed synchronization most yearly appointments where changed to occur every 12 years instead. The weirdest thing was that not all of them where changed, but I didn't look exactly which were untouched, so I can't comment on that (I may do some additional testing here).
I spent some time correcting them all. Then I unplugged my PocketPC and plugged it back to check that repetitions were still every year.
Then I plugged my PocketPC to Computer 2. I set up ActiveSync to sync calendar, contacts and task. After synchronization was completed I was back to square one, all yearly appointments where now 12 years.
I changed a few back to every year, and went back to Computer 1. Again all appointments where changed to 12 years .
Then I tried limiting repetitions to 10 for some appointments (as suggested elsewhere), corrected again to happen every year. No luck, those were also changed to 12 years after moving from Computer 1 to Computer 2 or the other way around.
So, the conclusion is that after Outlook 2007 SP1, ActiveSync 4.5 and Windows Mobile Device Center 6.1 calendar synchronization is broken. If you have one single computer it's not that much problem, since once you manually correct everything, it will stay. The bad news is for those of us that have two computers and have to use ActiveSync or Windows Mobile Device Center instead of Microsoft Exchange to keep everything synchronized.
I have no work around to offer. Only maybe moving to Google Calendar and synchronizing desktops and PocketPCs with it. Or giving up with Windows Mobile. I find increasingly frustrating this bug and that no one at Microsoft seems to care about it .

As Eddie73 explained early in the thread, the problem was introduced with Office 2007 SP2, if you have SP1 you don't have the option to repeat an event every X years, so ActiveSync/WMDC don't mess up your yearly events.
Fortunately SP2 can be uninstalled using this tool from Microsoft. After that reboot and you're ready to go again.
This means that I have been able to fix the problem simply by uninstalling SP2 . Nice. I hope Microsoft fixes the problem sooner rather than later, because being stuck at Office 2007 SP1 isn't ideal.

Here is a macro that will remove the 12-year reoccurance. I cannot take credit here is the source: ttp://social.microsoft.com/Forums/en-US/windowsmobilehelp/thread/8dbfde6c-9788-4ff9-a4b8-6b5751b765da
add an h to the http can't post links
Code:
Sub SetRecurrenceType()
Dim olApp As Outlook.Application
Dim objAppointment, objRecurring As Object
Dim objAppointments As Outlook.Items
Dim objNameSpace As Outlook.NameSpace
Dim objProperty As Outlook.UserProperty
Dim s As String
Dim i As Integer
Dim changed, recurring As Boolean
Set olApp = CreateObject("Outlook.Application")
Set objNameSpace = olApp.GetNamespace("MAPI")
Set objAppointments = objNameSpace.GetDefaultFolder(olFolderCalendar).Items
i = 0
For Each objAppointment In objAppointments
i = i + 1
If objAppointment.Class = olAppointment Then
If objAppointment.IsRecurring Then
changed = False
Set objRecurring = objAppointment.GetRecurrencePattern
If objRecurring.RecurrenceType = olRecursYearly Then
objRecurring.RecurrenceType = olRecursYearly
objAppointment.Save
End If
End If
End If
Next
MsgBox Str(i) & " Entries rewritten"
End Sub

If someone is still using Windows Mobile for whatever reason, there seems to be a fix for this bug:
http://support.microsoft.com/?kbid=981048