none
Error 80004005-501-4B9-560

    Question

  • Hi all,

            im migrating from Exch 2007 to Exch 2010, i moved all users to Exc2010, and Exc2010 its generating the OAB. When i start Outlook 2007 (on all clients) i get the following synchronization error:

    15:46:28 Synchronizer Version 12.0.6423
    15:46:28 Synchronizing Mailbox 'User Name'
    15:46:28 Synchronizing Hierarchy
    15:46:28 Synchronizing server changes in folder 'Inbox'
    15:46:28 Downloading from server 'Exch2010_CAS'
    15:46:28 2 view(s)/form(s) added to offline folder
    15:46:28 Downloading from server 'Exch2010_CAS'
    15:46:28 3 view(s)/form(s) added to offline folder
    15:46:28 1 view(s)/form(s) updated in offline folder
    15:46:29 Uploading to server 'Exch2010_CAS'
    15:46:29 1 item(s) deleted in online folder
    15:46:29 Synchronizing Forms
    15:46:29 Downloading from server 'Exch2010_MBX'
    15:46:29 Error synchronizing folder
    15:46:29 [80004005-501-4B9-560]
    15:46:29 The client operation failed.
    15:46:29 Microsoft Exchange Information Store
    15:46:29 For more information on this failure, click the URL below:
    15:46:29 http://www.microsoft.com/support/prodredirect/outlook2000_us.asp?err=80004005-501-4b9-560
    15:46:29 Done
    15:46:33 Microsoft Exchange offline address book
    15:46:33 Download successful

    Looking for information, i found in the following link:

    http://busbar.blogspot.com/2010/04/exchange-2010-bug-sync-issues-with.html

    that Microsoft has confirmed that it is a bug, ETA to be SP1

    Is this information correct?.

    Regards

    Leonardo

     

    Friday, April 16, 2010 4:23 PM

All replies

  • Hi,

    It is looks like the local client issue.

    Kindly do the following:

    Turn off offline files and folders, make sure the client is not in cached mode, delete any ost files (*.ost) one the machine. Make sure you search hidden files and folders are revealed when doing this search. Then put the client back in cached mode or offline files/folders, whichever you have configured and allow it to resync.

    If this works, find a way to automate the remaining clients.

    I trust that this would resolve this issue


    With Best Regards Anbu
    Friday, April 16, 2010 5:39 PM
  • Hi,

       I did that test and didn´t work, but if i move one mailbox to the Exch 2007, when i start outlook the error doesn´t appear. But that mailbox on Exch 2010, it gives me the error on Outlook when starts it. This error appears on all Outlook Clients, is not an .OST problem.

     

    Regards,

    Leonardo

    Friday, April 16, 2010 8:36 PM
  • Hi,

    Have you set up the RPC CAS on the mailbox database holding your problematic mailbox on Exch 2010 server.

    set-mailboxDatabase "Your Mailbox Database" -RpcClientAccessServer  "Exch2010_CAS"

    Regards,


    Laeeq Qazi|Team Lead(Exchange + Sharepoint + BES + DynamicsCRM) www.HostingController.com
    Friday, April 16, 2010 9:02 PM
  • Hi Laeeq,

                 yes, i set the RPC CAS on the mailbox database, on all databases, an example:

    [PS] C:\Windows\System32>Set-MailboxDatabase “TEST”  -RpcClientAccessServer “CAS2010”

    WARNING:The command completed successfully but no settings of “TEST” have been modified

    If i move a mailbox to Exch 2007, the error not appear, but when the mailbox is on Exch 2010 i get the error. Another test that i made is that if i set (in Exch 2010) on the properties of each database the PF of Exch 2007, when i start Outlook 2007, the syncronization error  (80004005-501-4B9-560) doesn´t appear.

     

    Regards,

    Leonardo

    Friday, April 16, 2010 10:47 PM
  • Hi,

    So the error persists if you set the Exch 2010 PF Database on the mailbox database? Also does the MBX Database have an OAB selected? get-mailboxdatabase "DB" |FL OfflineAddressBook

    Also what happens with a new mailbox on Exch 2010 mailbox server? Does he also get the same error?

    Regards,


    Laeeq Qazi|Team Lead(Exchange + Sharepoint + BES + DynamicsCRM) www.HostingController.com
    Friday, April 16, 2010 10:56 PM
  • Laeeq, hi,

                  yes, the mbx db have an OAB selected, if i run get-mailboxdatabase "DBname" |fl OfflineAddressBook, the result:

    OfflineAddressBoob : \DefaultOfflineAddressList

    And if i add a new mailbox, i get the error too.

    Regards

    Leonardo

    Saturday, April 17, 2010 3:24 AM
  • Hi,

    Please try to remove the PF replica for the Org Forms Library public folder from the Exchange 2010 server, then add it back.


    Frank Wang
    Wednesday, April 21, 2010 2:24 AM
  • Hi,

        if i remove the PF replica for the Organization Forms public folder from Exchange 2010, the error (80004005-501-4B9-560) dissapear. If i add it back, the error back again on outlook clients.

    Regards

    Leonardo.

    Wednesday, April 21, 2010 12:41 PM
  • I'm in exactly the same situation and get the same error... did you manage to solve this problem yet?

    Tuesday, April 27, 2010 10:08 AM
  • Hi Marcel, no i still having this error.
    Tuesday, April 27, 2010 1:25 PM
  • Hi Frank, i did what you told me, but i still have the error. Its possible that this error be a bug?

    Regards

    Tuesday, April 27, 2010 1:28 PM
  • same error here, DAG with two servers, migrating from 2003.

    Tuesday, April 27, 2010 1:51 PM
  • Hi Leonardo,

    I don't find any official document listed this is an bug. I will update if I find something.

    By the way, after you remove the PF replica and add it back, did you try to create a new outlook profile to test?


    Frank Wang
    Wednesday, April 28, 2010 2:40 AM
  • Hi Mark,

               the problem with this error is with all users, and if i create a new profile, i get the same error.

    Regards

    Leonardo Artese

    Wednesday, April 28, 2010 6:56 PM
  • Hi Leo, Hi frank.

    Since My post was involved, I am trying to contact my customer and know if they got an SRQ number or case ID.

    Hi Leo,

    this error was in E12 as well, have you tried to delete the OST and then try to re-create the profile


    Regards, Mahmoud Magdy http://busbar.blogspot.com http://ingazat.wordpress.com
    Wednesday, April 28, 2010 7:03 PM
  • migrating from 2003 to 2010 we get same error after I move a user's mailbox to E2010.
    Wednesday, May 12, 2010 12:56 PM
  • We also have this exact same problem after migrating from 2003 to 2010. Accept our archiving solution replies on replication of the Forms folder and this is a major problem for me!

     

    Although I get a different error code:

     

    13:49:52 Error synchronizing folder

    13:49:52 [80070057-501-80070057-560]

    13:49:52 The client operation failed.

    13:49:52 Microsoft Exchange Server Information Store



    Wednesday, May 12, 2010 1:05 PM
  • Hi Mahmoud,

                      the deletion of the ost file is not a solution in this case, all user have this error.

     

    Regards

    Wednesday, May 12, 2010 2:56 PM
  • Hi Leo,

    Have you seen this article:

    http://social.microsoft.com/Forums/en-US/partnermsgexchange/thread/cf6fc702-cfed-4818-8b51-47b6042f8329


    Regards, Mahmoud Magdy Watch Arabic Level 300 Videos about Exchange 2010 here: http://vimeo.com/user3271816 Read pretty advanced Exchange stuff I and other MVPs post here: http://www.enowconsulting.com/ese/blog.asp Or follow my blog: http://busbar.blogspot.com or our corp blog: http://ingazat.wordpress.com and if you Liked my post please mark it as helpful and accept it as an asnwer
    Wednesday, May 12, 2010 3:05 PM
  • Hi Mahmoud,

                      yes, i sow. But i don´t see a Microsoft Report about this issue.

    Regards.

    Leonardo Artese

     

    Wednesday, May 12, 2010 3:53 PM
  • We got the same issue, migrating from 2003 to 2010.

    Error applies to all users that are on the Exchange 2010 Server.

    Wednesday, May 12, 2010 4:30 PM
  • So is this a bug in Exchange 2010? The link that busbar posted seems to conclude with this being a bug, or at least an error that can be ignored, however the MSFT support technician seemed to want to wrap up the issue rather than spend anymore time trying to resolve it...

    For the record, we are experiencing this same issue on our Exchange 2010 server after migration from Exchange 2003.

    Wednesday, May 19, 2010 6:06 PM
  • We are experiencing this same issue from our migration to 2010 exchange from 2003.
    Monday, May 24, 2010 12:34 PM
  • We had the same issue - changing the client settings on the mailbox database back to the Exchange 2007 public folder database seems to have cured it. This then seems to break again when you change this setting back to the Exchange 2010 public folder database. I'm hopping this will be an SP1 fix.
    • Proposed as answer by Laeeq Qazi Saturday, July 10, 2010 9:50 AM
    • Unproposed as answer by Leonardo Artese Sunday, July 11, 2010 5:42 PM
    Friday, July 09, 2010 8:27 PM
  • RabbidWombat,

                           yes, if you change the client settings of the mailbox database pointing to the E2k7 PF database the error dissappear, but this is not a solution, because the Exchange 2007 should be eliminated in some point to conclude the migration. So, yes i hope too tha this problem will be fixed with SP1.

    Regards,

    Leonardo Artese.

    Sunday, July 11, 2010 5:47 PM
  • Hi Leonardo,

    yes I realise this is a temporary measure, but it will resolve the problem in the interim as I'm sure a lot of transitions to 2010 will take a while to complete. From the link above from Busbar http://social.microsoft.com/Forums/en-US/partnermsgexchange/thread/cf6fc702-cfed-4818-8b51-47b6042f8329 it looks like this will be fixed in RU5 for 2010 so I'm guessing it will also be in SP1 which is good news.

    And congratulations to Spain - a well deserved win :)

    Cheers

    Sunday, July 11, 2010 9:27 PM
  • Hi all

     

    any update on this issue as we are also experiencing this issue and I am unable to find documentation on Microsoft outlining this as a Bug.

    Thanks

     

    Ash

    Monday, September 20, 2010 11:24 PM
  • Hi,

    I too am getting these messages on all our users. We have upgraded our exchange servers to SP1 and it hasnt fixed the issue. Is someone albe to shed some light on this?

     

    Cheers

    Daniel

    Tuesday, September 21, 2010 12:17 AM
  • Hi Daniel.r:

                    the resolution for this issue it was posponed and won´t be fixed at the moment. You can check here:

    http://social.microsoft.com/Forums/en-US/partnermsgexchange/thread/cf6fc702-cfed-4818-8b51-47b6042f8329

    Regards.

    Leonardo Artese

    Tuesday, September 21, 2010 9:17 PM
  • Thanks Leonardo, unfortunately i don't have access to that thread. is there any ETA on when it will be fixed?

     

    Cheers

    Daniel

    Tuesday, September 21, 2010 9:51 PM
  • Hi all,

     

    As this error specificaly shows up during a migration, I would like to know if your organization uses public folders.

    If yes, how was the replication initiated and if its complete.

    If its complete then try dismounting the PF database on the source and then verify if the user connected to exchange 2010 can access all the public folders and also if this error throws up.

    This error will show up only in cache mode and not in online mode.

     

    Check and update.

    Thanks

    Wednesday, September 22, 2010 1:33 AM
  • Hi daniel.r, no, there are no plan to fix this at the moment.

    Regards,

    Leonardo Artese

    Wednesday, September 22, 2010 12:02 PM
  • Hi all,

    i do have the same problem since Migrating Mailboxes from Exchange 2007 to 2010(SP1!).

    I can confirm that the error disappears when disabling cache-modus.

    Hopefully there will be a fix for that because i already removed exchange 2007 from active directory.

     

    Regards,

    Kai-Olaf Pieth

    Monday, September 27, 2010 2:54 PM
  • Hi,

     

    In our case customer also reports that he seems to miss e-mail, when i disable the OST cq. Cached Exchange, the mail is there, so it seems that this issue is getting more of an urgency this way?

     

    Regards,

    Michel Dijkgraaf

    Thursday, October 21, 2010 9:41 AM
  • Hi,

    Did you find a solution ? I have the same problem (but in a new Exchange 2010 organisation, no migration)...

    Regards

    Boris

    Saturday, December 11, 2010 10:45 PM
  • We still have this error ourselves with cache mode users... ugh...

    Exchange 2010 SP1 with Rollup1

    Monday, December 13, 2010 8:06 PM
  • Same issue. Migrated from Exchange 2003 to 2010 SP1. All updates applied.

    10:21:48 Synchronizer Version 14.0.4760

    10:21:48 Synchronizing Mailbox 'Earl Marinus'

    10:21:48 Synchronizing Hierarchy

    10:21:48 Synchronizing server changes in folder 'Calendar'

    10:21:48 Downloading from server 'TF-EXCHANGE.rbvh.local'

    10:21:48 Synchronizing local changes in folder 'Inbox'

    10:21:48 Uploading to server 'TF-EXCHANGE.rbvh.local'

    10:21:48                   1 view(s)/form(s) updated in online folder

    10:21:48 Downloading from server 'TF-EXCHANGE.rbvh.local'

    10:21:48                   1 item(s) changed read-state in offline folder

    10:21:48 Synchronizing server changes in folder 'Drafts'

    10:21:48 Downloading from server 'TF-EXCHANGE.rbvh.local'

    10:21:48 Synchronizing server changes in folder 'Deleted Items'

    10:21:48 Downloading from server 'TF-EXCHANGE.rbvh.local'

    10:21:48                   1 item(s) changed read-state in offline folder

    10:21:48 Synchronizing Views

    10:21:48 Downloading from server 'TF-EXCHANGE.rbvh.local'

    10:21:48 Synchronizing Forms

    10:21:48 Downloading from server 'TF-EXCHANGE.rbvh.local'

    10:21:48 Error synchronizing folder

    10:21:48                                 [80004005-501-4B9-560]

    10:21:48                                 The client operation failed.

    10:21:48                                 Microsoft Exchange Information Store

    10:21:48                                 For more information on this failure, click the URL below:

    10:21:48                                 http://www.microsoft.com/support/prodredirect/outlook2000_us.asp?err=80004005-501-4b9-560

    10:21:48 Done

    10:21:48 Microsoft Exchange offline address book

    10:21:48 Download successful

     

    Wednesday, December 15, 2010 3:38 PM
  • Hi all,

    i have Exchange 2010 SP1 with Rollup 2. Error is still the same.

    Kind Regards

    Udo

    Saturday, December 18, 2010 1:38 AM
  • Having the same issue, even tried another articled about a missed attribute in the E2010 Org Forms Library (http://nilleb.wordpress.com/2010/02/26/exchange-2010-and-organizational-forms-libraries/) without any luck.  Definatelly seems to be a issue/bug/problem in the E2010 System Public Folders Org Forms type folder causing the 80004005 access denied type error code.  Even my account which is an owner of the Org forms, and I'm able to publish, just can't pull down apparently.

    Exchange 2010 SP1 with Outlook 2010 and Outlook 2007 SP2, getting the identical error codes, no issue on our E2007 side.

    K.

    Monday, December 20, 2010 4:43 PM
  • IS there anyone over at MS that we can contact regarding this. It has been 8months now and no fix. I have SP1 UR2 and problem is here as well. 
    Thursday, December 30, 2010 9:25 PM
  • Got the same problem here. Exchange 2010 SP1 RO2 and still the problem exists. :(

     

    Monday, January 03, 2011 4:00 PM
  • Frank 

    I see you last post on this was 4/28/2010 - Since then MS has released SP1 and Update-Rollup 2 - but the problem still exists. Can you give me any insight towards resolution? Or do you know where I can check to see if this is being addressed at all?

     

    THanks - SJMP

    Monday, January 03, 2011 4:03 PM
  • We're running 2010 SP1 RU 2 as well and were still experiencing the problem after we recently decommissioned our 2007 servers.  Using the Public Folder Management Console to delete the Organizational Forms folder resolved our issue.  Note:  We verified there was no data in this folder before deleting it and chose "Web-Based" as the Distribution Mechanism for our Default Offline Address Book.
    Thursday, January 13, 2011 4:57 PM
  • Just in the middle of migrating another environment, still have this issue with Syncing Forms from an Exchange 2010 Public Folder database, and running Exchange 2010 SP1 HFRU2 installed.  80004005-501-4B9-560

    Do'h!

    Friday, January 21, 2011 5:25 PM
  • This problem is causing me serious grief. Please update with a solution.
    Friday, January 28, 2011 12:06 PM
  • We also had the Problem and opend a MS Call last Year:

     

    1. Its seems to be a in/official Bug without any KB-Article, the MSsupport know the problem...

    2. When the Exchange 2003 PF-DB still exit then delete the Replica on Ex 2010 and readd. I dont know if that works because we had, at this time last year, deleted the old Exchange 2003 PF-DBs so:

    3. Our Solution because we deleted our ex2003 PF-DB bevor and so cant readd the Replica: Delete the Formsfolder in Systemfolders and renew the Mailprofile of any client (at least these Users that are nerved from the syncerror ;)). Check first if you use organziationalwide Forms! -> That was our Solution, not very fine because of renewing the mailprofiles but... so what...

    Friday, January 28, 2011 1:36 PM
  • Going to try and delete the forms folder from the systemfolder on out test environment and have a look if it works.
    Will let you know what comes up.

    But to renew 400 mail client profiles!? not a great id. :(

    thanks for the update.

    Saturday, January 29, 2011 5:55 PM
  • zagaz

    Did you delete the complete system folder EFORMS REGISTRY including the subfolder PublicForms? No need to recreate it after deletion?
    We are at the beginning of a Computer replacement project. So if this is a solution we should do it now. Please keep me updated…

    Monday, January 31, 2011 7:24 AM
  • We use the organizational forms library, which is why this is such a problem. 

    Exactly what do I need to delete and recreate please?

    Cheers.

    Monday, January 31, 2011 11:08 AM
  • The Exchange 2010 Replica from the Formsfolder in the Systemfolders you should readd
    Monday, January 31, 2011 12:07 PM
  • I have no Replica, the old 2003 server/PF is gone. This was a new PF DB created on the ex2010 box, it is the only server which holds the PF DB.

    So I should delete "EFORMS REGISTRY" if so how is it re-added?

    Or should I just delete "Organizational Forms" from the "EFORMS REGISTRY"?

    Sorry for the confusion.

     

    Monday, January 31, 2011 2:10 PM
  • I have the same problem. Any solution???
    Tuesday, February 01, 2011 5:38 PM
  • I to am having the same issue. went from Exchange 2007 to 2010. everything works fine just this sync error on everyones computer. it looks like it only happens when outlook is opened.
    Wednesday, February 02, 2011 6:17 PM
  • I too have this problem for anyone that migrated from Exchange 2003 to Exchange 2010.  Thousands of users get this since the migration.  No issues have been reported as far as mailflow or connecting to Exchange 2010, it just shows up in the Sync Issues folder.  I gave this folder a retention tag/policy to hopefully keep it somewhat clean, but not yet mask the issue.

    d
    Wednesday, February 02, 2011 7:32 PM
  • Removing the folders from the EFORMS REGISTERY folder and renewing the outlook profile is working. No sync messages anymore. But to renew 500 outlook client profiles is to much :(

    Anyone an other sugestion?

    T

    Thursday, February 03, 2011 11:13 AM
  • Agreed, also I need to use the EFORMS REGISTRY so if someone could confirm it can be recreated and that the problem does then not return that would be handy.

     

    Still recreating 500 outlook profiles over 30+ sites, is not an answer.

     

    Thursday, February 03, 2011 12:07 PM
  • I'm having the same issue also.  Exchange 2010 SP1 with all latest updates and OL 2010 with all latest udpates.
    Wednesday, February 23, 2011 9:47 PM
  • Same issues here and we use Organisation Forms within our product!

    Any news please Microsoft?

     

    Friday, February 25, 2011 5:21 PM
  • here's a pretty questionable response from MS:

    A Synchronization error is logged in OL2003 with error code: 80070057-501-80070057-560, and this is by design. More outlined in Case 110122247397062 “OL2K3/E2010/PRE/Outlook 2003 clients connecting to Exchange 2010 having synchronization error logs in the Sync Issues folder.”

    We log these errors when we get a partial completion for syncs to Outlook in cached mode from the server. Partial Sync is a new feature in Exchange 2010. The server returns a ecPartialCompletionto Outlook in the following cases:

     

    - When an item has already been deleted or when a request is made to delete an item that doesn’t exist

    - When the server actually fails to delete the requested item

     

    Unfortunately at the moment we don’t have a way of distinguishing a false positive from a deletion request that actually fails.

     

    The jist of the above: since the server sends only one code for two different possible outcomes under its new design, the Outlook team feels that putting a log item into the sync issues folder when the partial sync fails is better than logging nothing at all. Since you aren't actually seeing problems with items being deleted, the best thing to do is to instruct your users to periodically clear out their sync issues folders.

    So, we are to ignore these very annoying messages, unless of course there is an issue which we're all ignoring...  so ms might as well turn it off.

     

    Wednesday, March 02, 2011 3:01 AM
  • But i can not still download oab
    Monday, March 07, 2011 9:21 PM
  • Sorry, I thought this forum question was about the Forms sync failures, not OAB.  OAB issues, I don't think I've hit an issue that wasn't resolvable via Mr. Goldman's site.   http://blogs.msdn.com/b/dgoldman/ 

    This conversation thread is about Org Forms sync:

    15:46:29 Synchronizing Forms
    15:46:29 Downloading from server 'Exch2010_MBX'
    15:46:29 Error synchronizing folder
    15:46:29 [80004005-501-4B9-560]
    15:46:29 The client operation failed.

    Monday, March 14, 2011 7:10 PM
  • But i can not still download oab

    Have you checked to ensure the DB is linked to an OAB as suggested earlier? I had several DB's not linked to an OAB so that fixed my issue. I still however got the sync errors. Personally, I'm going to create a Retention tag for the Sync Issues folder and have it auto delete after a certain amount of time.

    get-mailboxdatabase "%DBNAME%" |FL OfflineAddressBook
    Friday, March 25, 2011 6:14 PM
  • Has anyone heard of any fixes for this, we are seeing the same issue and it only started happening when I added the 2010 server to the replication of the Org Forms.

     

    Thanks

    Tuesday, March 29, 2011 8:46 PM
  • We too are starting to see this error.  All user mailboxes are on Exch 2010 SP1 RU1.  I did not start seeing the error until after I decommed the last Exch 2003 Public Folder and move over the PF tree to the Exch 2010 Admin group.

    11:22:48 Synchronizing Forms

    11:22:48 Downloading from server 'Exch2010_PF_Server'

    11:22:48 Error synchronizing folder

    11:22:48                                 [80004005-501-4B9-560]

    11:22:48                                 The client operation failed.

    11:22:48                                 Microsoft Exchange Information Store

    11:22:48                                 For more information on this failure, click the URL below:

    11:22:48                                 http://www.microsoft.com/support/prodredirect/outlook2000_us.asp?err=80004005-501-4b9-560

    I would remove the "EFORMS REGISTRY" folder, as descibled in in this article, but we have a archve app that has a organization form that uses.

    http://blogs.technet.com/b/agobbi/archive/2010/08/04/troubleshooting-error-synchronizing-folder-synchronizing-forms-80004005-501-4b9-560.aspx

    I hop MS will come back with some kind of fix becuase users are complaining about the message in thier Sync Issues folder.

    Friday, April 29, 2011 5:07 PM
  • Any update on this ? Having same issue
    Monday, June 06, 2011 7:43 AM
  • I'd like to update my current "findings" about this issue.

    The sync issues were showing up in migration projects we've done, I've noticed two things:

    1) If you do not add a replica to your Exchange 2010 server to the Organizational Forms folder - the issue will not happen.

    2) If your client does have organizational forms items meaning they actually use it - from what I've seen - the issue will not happen.

     

    For the safe side, i just exclude adding a replica to the organizational forms until we actually need to DE-commission the last 2003 server.which workaround this issue all together

    Hope this helps anyone,

    Ilantz

    Monday, June 06, 2011 9:09 AM
  • So is the only workaround to remove the repliacted org. forms? If so can someone please provide a link with the correct way to do this.

    thanks,

    SJMP

    Monday, June 06, 2011 12:13 PM
  • Take this for what it's worth: I had an Exchange 2003 server with org forms (that I didn't know existed). We replicated what we thought were all the PF's only to find that when we decommissioned the 2003 box, the org forms were gone. We were able to re-create the forms, but now get the error you receive on every 2007 client. Here was MS's response to my particular issue:

    http://social.microsoft.com/Forums/en-US/partnermsgexchange/thread/4ed7d01e-1d4c-4d38-bfeb-668aa8af2d28

    Monday, June 06, 2011 1:48 PM
  • TBone - Can you paste the reply from the link. I am not authorized - partner only? - to view it. 

    Thanks - SJMP

    Monday, June 06, 2011 2:07 PM
  • The short of it is, after calling pay-per-incident support, they said I would have to ignore the error and upgrade to Exchange 2015.  I laughed.

    Monday, June 06, 2011 2:10 PM
  • so lets wait for Exchange 2015 :) lol

     


    Zahir Hussain Shah Infrastructure Practice Consultant My blog: http://zahirshahblog.com
    Wednesday, June 08, 2011 7:36 AM
  • Have you tried the steps in the following article?

    http://blogs.technet.com/b/eileenor/archive/2011/05/04/outlook-synchronization-error-80004005-501-4b9-560-with-a-microsoft-exchange-server-2010-mailbox.aspx

    It did not work on my setup though...

    Friday, June 10, 2011 10:44 AM
  • Have you tried the steps in the following article?

    http://blogs.technet.com/b/eileenor/archive/2011/05/04/outlook-synchronization-error-80004005-501-4b9-560-with-a-microsoft-exchange-server-2010-mailbox.aspx

    It did not work on my setup though...


    I tried the steps in the article, but didnt see an Orginzational Forms Library within in the system folders.  Has anyone else run into this?
    Friday, June 10, 2011 9:07 PM
  • It's been lost in the long thread, so a refresher might help.  There isn't actually a problem, the Org Forms come over, and they do infact, or aleast in my cases, come to the Outlook client. 

    The problem is in how Outlook and Exchange are talking with each other.  If memory serves, Exchange 2010 has a new code for successful partial syncs, but Outlook isn't distinguishing, or is unable to differntiate between success of a partial or of a full sync, so the programers "erred on the side of caution" and listed the partial sync as a failure.  I don't know if theres an enhancement to Outlook that needs to come out, or a change to Exchange that needs to happen.  Or maybe it was Outlook that's reporting a different success code for partial syncs...

    In summary, I've found that the org forms are working (assuming you migrated them or set them up correctly) its just that you now get an "error" on the client, when there is in fact no error.

    Friday, June 10, 2011 9:55 PM
  • Hi,

    I have been searching for a solution for this and finally came up with the solution that might help.

    My issue was to do with the OAB web.config file not having authenticated users in it by default for the OAB.

    The location of my file was on the CAS server:

    C:\Program Files\Microsoft\Exchange Server\V14\ClientAccess\OAB\web.config

    Add authenticated users to it with read and execute permissions.

    Log off the client PC and log back in again, after this I was able to download my OAB.

    I hope this helps people out there.

    Thanks,

    Roger
    Monday, July 25, 2011 5:18 PM
  • It looks like it is a client problem, not a server one. Whats worked for me: deinstall Office, delete HKCU\Software\Microsoft\Office and HKLM\Software\Microsoft\Office, reboot, reinstall Office. The problem is gone (the one with Forms sync error).

     

    Monday, August 08, 2011 4:10 PM
  • Hope that's not the only answer.  I have over 400 machines.
    Monday, August 08, 2011 8:13 PM
  • Is it possible it's caused by synchronisation with a Blackberry server ?

    I have this error from the moment I'm using a company Blackberry.


    Monday, August 29, 2011 9:07 AM
  • I do have a BES server.  Not certain that's the culprit.  If you hear otherwise, please let us know.
    Monday, August 29, 2011 4:29 PM
  • I'm also having these sync isues on Exchange 2010.

     

    Thursday, September 08, 2011 6:33 AM
  • From the horses mouth!

     

    http://support.microsoft.com/kb/2614647

     

    We can ignore it.

    • Proposed as answer by TBone1985 Tuesday, September 13, 2011 3:23 PM
    Tuesday, September 13, 2011 2:39 PM
  • How convenient. Ignore the hundreds of sync errors on all clients. I *really* miss Exchange 2003/Outlook 2003, and we're regretting the migration to 2010. That setup worked perfectly.
    no
    Wednesday, September 14, 2011 6:41 PM
  • Our Exchange PFE looked into this issue and determined that there is no scheduled fix until the next version of Exchange... So essentially everyone using public folders and Org Forms can expect to get these synchronization errors every time they fire up Outlook in cache mode.

    Not sure what the sync issue is because Outlook in cache mode can access and use the forms just fine. Apparently this only affects offline usage which I don't think much anyone does. 

    The position of the Exchange team, while understandable given their focus on the next version of Exchange, doesn't help us in the field upgrading to the latest version of their product.

    Telling our users to ignore it isn't going to stop the countless number of questions coming into our help desk from now until the next version of Exchange is released and eventually deployed. The number one problem with a suggestion like this is it is coming from a company of mostly IT people to companies with very few IT people. Non-IT people simply don't remember that 6 months ago they were told to ignore Sync Isses with just the Forms library folder, especially when they see 1 entry in the folder for every time the fired up Outlook.

    Wednesday, September 21, 2011 6:55 PM
  • This "Solution" is only suitable if you don't actually have forms published.  Making the change you suggest actually breaks it from being a Org form library.

    re:  HotFix, MS response on this is crap.  It's been a known issue since the beta days, and "fixing" in in the next release is a lousy answer.  Great, you're working on the next release, meanwhile the rest of us are trying to get people off of E2003 still (and 2007) and no one needs this grief.  They certainly went out of their way to "fix" some hidden attachment mac issue which screwed a lot of people.

    I'm getting to old for this kind of crap.

    Wednesday, September 21, 2011 8:56 PM
  • HotFix and Korbyn, I must add to the above that in a few migration projects I've handled Org Forms were widely used, and are already native Exchange 2010 with 2003 servers long gone... one customer by the way, has couple of dozens forms - all working flawlessly.

    Our main issue was indeed with the majority customers that are not using Org Forms and receive the sync error.

    To work around the issue when Org Forms are indeed in place and being used, I kept the replicas only on the Exchange 2003 public folders during migration. only when we moved to remove the legacy servers I've completely moved all replicas including the Org Forms folder to the 2010 servers.

    Hope this works for you.

    ilantz

    • Proposed as answer by InDellHell Tuesday, September 27, 2011 3:25 PM
    Friday, September 23, 2011 7:48 PM
  • So once you "flipped" the Org forms library from 2003 to 2010 the error stopped occuring on the clients? Specifically you aren't getting the sync issue alert on any of your clients?
    Thursday, September 29, 2011 8:29 PM
  • I still get the error and ALL non 2010 Exchange servers have been decommissioned. How do I get rid of it then?
    Thursday, September 29, 2011 8:54 PM
  • I still get the error and ALL non 2010 Exchange servers have been decommissioned. How do I get rid of it then?

    Same here.
    Friday, September 30, 2011 1:57 AM
  • So once you "flipped" the Org forms library from 2003 to 2010 the error stopped occuring on the clients? Specifically you aren't getting the sync issue alert on any of your clients?


    Hi hotfix,

    sorry for the late response , been in a long vacation :)

    actually what i've written is the other way around. when "flipping" the forms from 2003 to 2010 the error started. when flipping back to 2003, that is removing the replica from 2010 and leaving a single replica on the 2003 the error stopped.

    try my blog thread it has a better written step by step of the procedure:

    http://ilantz.wordpress.com/2011/09/20/solving-sync-issues-error-80004005-501-4b9-560-in-exchange-2010-rtm-and-sp1/

    ilantz

     

    Monday, October 24, 2011 3:14 PM
  • So once you "flipped" the Org forms library from 2003 to 2010 the error stopped occuring on the clients? Specifically you aren't getting the sync issue alert on any of your clients?


    Hi hotfix,

    sorry for the late response , been in a long vacation :)

    actually what i've written is the other way around. when "flipping" the forms from 2003 to 2010 the error started. when flipping back to 2003, that is removing the replica from 2010 and leaving a single replica on the 2003 the error stopped.

    try my blog thread it has a better written step by step of the procedure:

    http://ilantz.wordpress.com/2011/09/20/solving-sync-issues-error-80004005-501-4b9-560-in-exchange-2010-rtm-and-sp1/

    ilantz

     

    How do I verify that my company isn't using forms?
    Monday, October 24, 2011 3:49 PM
  • Hi,

    So the error persists if you set the Exch 2010 PF Database on the mailbox database? Also does the MBX Database have an OAB selected? get-mailboxdatabase "DB" |FL OfflineAddressBook

    Also what happens with a new mailbox on Exch 2010 mailbox server? Does he also get the same error?

    Regards,


    Laeeq Qazi|Team Lead(Exchange + Sharepoint + BES + DynamicsCRM) www.HostingController.com

     

     

    Sorry for a silly question as I am new to this.  But what "PF" that people keep mentioning?

    Monday, October 24, 2011 9:05 PM
  • Hi,

    So the error persists if you set the Exch 2010 PF Database on the mailbox database? Also does the MBX Database have an OAB selected? get-mailboxdatabase "DB" |FL OfflineAddressBook

    Also what happens with a new mailbox on Exch 2010 mailbox server? Does he also get the same error?

    Regards,


    Laeeq Qazi|Team Lead(Exchange + Sharepoint + BES + DynamicsCRM) www.HostingController.com

     

     

    Sorry for a silly question as I am new to this.  But what "PF" that people keep mentioning?

    Public Folder.
    Monday, October 24, 2011 9:09 PM
  • Hi,

     

    same question here.

    How can I check, if my company´s using forms?

     

    Thx!

     

    Mirjam

    Tuesday, October 25, 2011 10:30 AM
  • So once you "flipped" the Org forms library from 2003 to 2010 the error stopped occuring on the clients? Specifically you aren't getting the sync issue alert on any of your clients?


    Hi hotfix,

    sorry for the late response , been in a long vacation :)

    actually what i've written is the other way around. when "flipping" the forms from 2003 to 2010 the error started. when flipping back to 2003, that is removing the replica from 2010 and leaving a single replica on the 2003 the error stopped.

    try my blog thread it has a better written step by step of the procedure:

    http://ilantz.wordpress.com/2011/09/20/solving-sync-issues-error-80004005-501-4b9-560-in-exchange-2010-rtm-and-sp1/

    ilantz

     

    Sorry Ilantz, it´s not that I don´t believe in your solution :)

    But does anybody had proceed it?
    What is the result?

    Thx Mirjam

    Tuesday, October 25, 2011 10:32 AM
  • Hi,

     

    same question here.

    How can I check, if my company´s using forms?

     

    Thx!

     

    Mirjam

    Hi Mirjam,

    I guess that the easiest way is to actually see if you have any forms showing up within outlook.

    (Outlook 2010) Within outlook click on "New Items", then "More Items", then "Choose form".

    within the window, locate the "Look in" drop down, locate the Organizational Forms directory you have in public folders and see if anything is there.. well if the list is empty (most chance...) no forms.. The standard forms; message, appointment etc.. is not what you are looking for.


    Forms are commonly used within Public Folders, users click a public folder and then "see a page" or a "program" forms is actually VB code with easy access from Outlook. although it is really practical it is rarely used.

    Another good way to check is some human engineering, just ask your DEV guys / department if anyone ever coded for Outlook and using the Forms in the Exchange server.

     

    Good luck !

    ilantz


    • Edited by Ilantz Tuesday, October 25, 2011 5:30 PM typo
    Tuesday, October 25, 2011 5:27 PM
  • Hi ilantz,

     

    thank you for your reply and sorry for my late response.
      had to occupy myself with other problems.

    I´m confused about the forms.
    If I check in Outlook, I have only the Standardforms like Appointment, Contact, Message, Note and so on...

    But when I look at our Exchange/Public Folder Toolbox in Public System Folder/EFORMS REGISTRY there is an "XPR Formular"


    So I think your workaround will not work for us, which is unfortunate, because we get a lot of issues at the Help Desk.

     

    I fell left alone...

     

    Thanks
    Mirjam

     

    There are any news from MS, maybe... ?
    We´ve already migratet from EXchange 2003 to Exchange 2010, we will not migrate to Exchange 2015 for the next 3 Years.

     


    • Proposed as answer by Paul Gazzara Tuesday, February 21, 2012 1:57 PM
    • Unproposed as answer by Paul Gazzara Tuesday, February 21, 2012 1:57 PM
    Tuesday, January 31, 2012 8:40 AM
  • Has anyone installed Exchange 2010 SP2 yet to see if it fixed this problem?
    Tuesday, February 21, 2012 1:58 PM
  • Hi Mirjam,

    A folder under the EFORM REGISTRY in the public folder doesn't really mean it has anything in it :) if using an outlook client you cannot see any items to choose (forms) then you don't have any...

    Worst case you can always backup your public folder, and restore it..

    ilantz
    Tuesday, February 21, 2012 2:00 PM
  • Again, just because this thread is so long and people just scroll to the bottom looking for the answer...

    There is no actual issue to be concerned about when you get this particular error in the sync log.  If you are using Organizational Forms in Exchange 2010, and nothing had been updated or changed, the system is uses the same packet to report back that there are no changes as it would if there was an error.  It's stupid, its annoying, MS says they'll fix it in the next version, but in the mean time, you might be so annoyed as to get rid of the Org Forms library, and public folders all together...

    Monday, February 27, 2012 4:28 PM
  • Hi All,

    It seems like this is already a known issue as per Microsoft's article that I found on their support site. You may want to check the post I made about this. I have also encountered this, just recently.

    http://curly-live.hubpages.com/t/2e636f

    Regards,

    Miscarey

    Monday, March 12, 2012 3:48 AM
  • I did the migration from Exch2003 to Exch 2010 w/SP2 directly, when I removed Exch2003 from the organization, the outlook2003 users also got Sync error: [80070057-501-80070057-560], so SP2 doesn't fix this problem.

    but not all users have this error, waiting for the solution.


    gary li

    Thursday, March 15, 2012 6:42 PM
  • @Everyone - if this sync issue is specific to synchronizing your Public Folder based Org Forms library, this is a known issue with Exchange 2010, and will not be fixed until (maybe) the next product version.

    You know if you have the issue with the Org Forms library if you see this and only this error in your Sync Issues entry:

    9:28:51 Synchronizing Forms
    9:28:51 Downloading from server 'whateveryourservernameis.company.com'
    9:28:51 Error synchronizing folder
    9:28:51    [80004005-501-4B9-560]
    9:28:51    The client operation failed.
    9:28:51    Microsoft Exchange Information Store
    9:28:51    For more information on this failure, click the URL below:
    9:28:51    http://www.microsoft.com/support/prodredirect/outlook2000_us.asp?err=80004005-501-4b9-560
    9:28:51 Done
    9:28:51 Microsoft Exchange offline address book
    9:28:51 Download successful

    Friday, March 16, 2012 8:50 PM
  • Apparently the information my Exchange PFE was given and handed to me was incorrect because this appears to be fixed in Exchange 2010 SP2 RU3:

    http://support.microsoft.com/kb/2572029

    I haven't tried it yet in production to verify, but we are very optimistic based upon this long standing issue Microsoft has been aware of and the focus of the KB article.

    • Proposed as answer by Lavelle IT Monday, June 04, 2012 1:20 PM
    Wednesday, May 30, 2012 12:25 AM
  • Great news HotFix !! anyone can report RU3 solves this issue ??
    Saturday, June 02, 2012 7:44 AM
  • It fixes that problem and if you go back to the link I posted, it points to the same solution.

    http://support.microsoft.com/kb/2614647

    Monday, June 04, 2012 1:23 PM
  • I can confirm that after we applied Exchange 2003 SP2 RU3, the issue of generating a Sync Error about the Org Forms library every time you start Outlook is gone.

    Thank you Exchange team for not waiting until the next product release to fix this VERY annoying bug.

    Monday, July 02, 2012 3:42 PM