Comments on: Troubleshooting the “Unable to Complete Request” Error When Synching a Blackberry with Groupwise via Blackberry Desktop Manager http://thebackroomtech.com/2008/04/23/troubleshooting-the-%e2%80%9cunable-to-complete-request%e2%80%9d-error-when-synching-a-blackberry-with-groupwise-via-blackberry-desktop-manager/ serving up the info back room techs everywhere find interesting Sun, 07 Nov 2010 18:59:34 +0000 hourly 1 http://wordpress.org/?v=3.2.1 By: JP http://thebackroomtech.com/2008/04/23/troubleshooting-the-%e2%80%9cunable-to-complete-request%e2%80%9d-error-when-synching-a-blackberry-with-groupwise-via-blackberry-desktop-manager/#comment-837 JP Thu, 01 Oct 2009 03:00:13 +0000 http://thebackroomtech.wordpress.com/?p=328#comment-837 Interesting. I really appreciate Julie's posting this helpful note. While my five years' experience is with multiple Blackberry models and Outlook, Julie's intuition reinforces what I hear from vendor and RIM techs, which is that the calendar sync is imperfect. Their RIM-recommended resolutions include deleting the Intellisync folder, then reconfiguring the BDM sync; and using advanced logging to locate the "bad" Outlook record(s), which is/are then deleted. Either of these two methods work equally well - until the next error. Here is what's REALLY interesting: All this time, vendors and RIM have been saying that the calendar sync problem stems from some Outlook calendar (or, early on, contact list) issue. This very thread is not about Outlook but Groupwise. The indication, then, is that the Blackberry software, not the Microsoft or Novelle application, is the weak link (pun unavoidable). Taking at face value Julie's discovery that repairing field mapping resolves the issue ad infinitum: Might RIM be wise to publicize this true resolution? Further, might RIM be wise to write a little applet that, with a single button, automates the field-mapping process? Even better, why not put a flag and the script into BDM, so that, whenever this error occurs (and it, along with associated errors, always requires the same resolution), BDM simply displays "Errors found, please wait a moment while we repair them" and resolves the known issue with the known resolution? This thread changes my image of RIM, and of Microsoft (I have no opinion on Novelle). Lastly, Julie's comment about the most "likely suspect" fields is right on the mark. In this regard, perhaps Groupwise is like Outlook: In Outlook, free/busy, alarm and recurring appointment flags appear to cause the vast majority of BDM sync failures; in fact, notice of recurring appointments occasionally becomes corrupted in Outlook. So Microsoft is not perfect; but we already know that. Now, it's RIM's turn to begin addressing sync issues with active resolutions for issues that erase the productivity promised by these devices. Interesting. I really appreciate Julie’s posting this helpful note. While my five years’ experience is with multiple Blackberry models and Outlook, Julie’s intuition reinforces what I hear from vendor and RIM techs, which is that the calendar sync is imperfect. Their RIM-recommended resolutions include deleting the Intellisync folder, then reconfiguring the BDM sync; and using advanced logging to locate the “bad” Outlook record(s), which is/are then deleted. Either of these two methods work equally well – until the next error.

Here is what’s REALLY interesting: All this time, vendors and RIM have been saying that the calendar sync problem stems from some Outlook calendar (or, early on, contact list) issue. This very thread is not about Outlook but Groupwise. The indication, then, is that the Blackberry software, not the Microsoft or Novelle application, is the weak link (pun unavoidable).

Taking at face value Julie’s discovery that repairing field mapping resolves the issue ad infinitum: Might RIM be wise to publicize this true resolution? Further, might RIM be wise to write a little applet that, with a single button, automates the field-mapping process? Even better, why not put a flag and the script into BDM, so that, whenever this error occurs (and it, along with associated errors, always requires the same resolution), BDM simply displays “Errors found, please wait a moment while we repair them” and resolves the known issue with the known resolution?

This thread changes my image of RIM, and of Microsoft (I have no opinion on Novelle).

Lastly, Julie’s comment about the most “likely suspect” fields is right on the mark. In this regard, perhaps Groupwise is like Outlook: In Outlook, free/busy, alarm and recurring appointment flags appear to cause the vast majority of BDM sync failures; in fact, notice of recurring appointments occasionally becomes corrupted in Outlook.

So Microsoft is not perfect; but we already know that. Now, it’s RIM’s turn to begin addressing sync issues with active resolutions for issues that erase the productivity promised by these devices.

]]> By: Luke http://thebackroomtech.com/2008/04/23/troubleshooting-the-%e2%80%9cunable-to-complete-request%e2%80%9d-error-when-synching-a-blackberry-with-groupwise-via-blackberry-desktop-manager/#comment-836 Luke Mon, 21 Sep 2009 14:35:11 +0000 http://thebackroomtech.wordpress.com/?p=328#comment-836 Resolved a user's sync issue today with the help of this article. Thanks! Resolved a user’s sync issue today with the help of this article. Thanks!

]]> By: Bob Scrofani http://thebackroomtech.com/2008/04/23/troubleshooting-the-%e2%80%9cunable-to-complete-request%e2%80%9d-error-when-synching-a-blackberry-with-groupwise-via-blackberry-desktop-manager/#comment-835 Bob Scrofani Fri, 10 Jul 2009 00:38:33 +0000 http://thebackroomtech.wordpress.com/?p=328#comment-835 I had the exact same problem, and a similar setup, and your solution worked like a charm. Thank you so much! I had the exact same problem, and a similar setup, and your solution worked like a charm. Thank you so much!

]]> By: Douglas http://thebackroomtech.com/2008/04/23/troubleshooting-the-%e2%80%9cunable-to-complete-request%e2%80%9d-error-when-synching-a-blackberry-with-groupwise-via-blackberry-desktop-manager/#comment-834 Douglas Tue, 24 Feb 2009 13:44:42 +0000 http://thebackroomtech.wordpress.com/?p=328#comment-834 This also solved my problem - thank you. I using an E-ten Glofiish M800 and Nokia Intellisync Handheld 6.0 with Groupwise. This also solved my problem – thank you. I using an E-ten Glofiish M800 and Nokia Intellisync Handheld 6.0 with Groupwise.

]]> By: Jay http://thebackroomtech.com/2008/04/23/troubleshooting-the-%e2%80%9cunable-to-complete-request%e2%80%9d-error-when-synching-a-blackberry-with-groupwise-via-blackberry-desktop-manager/#comment-833 Jay Mon, 05 Jan 2009 18:18:33 +0000 http://thebackroomtech.wordpress.com/?p=328#comment-833 Thank you so much. I just fixed my issue following your steps. My configuration included the following: Windows XP professional SP3 MS Outlook 2007 client Blackberry Desktop Manager 4.2.2.12 Thank you so much. I just fixed my issue following your steps.

My configuration included the following:

Windows XP professional SP3
MS Outlook 2007 client
Blackberry Desktop Manager 4.2.2.12

]]> By: Jgould http://thebackroomtech.com/2008/04/23/troubleshooting-the-%e2%80%9cunable-to-complete-request%e2%80%9d-error-when-synching-a-blackberry-with-groupwise-via-blackberry-desktop-manager/#comment-832 Jgould Tue, 07 Oct 2008 14:22:34 +0000 http://thebackroomtech.wordpress.com/?p=328#comment-832 Thank you!!! This was driving me crazy and your simple solution worked. Thank you!!! This was driving me crazy and your simple solution worked.

]]>