[stuwhite]

Originally Posted by DarienA

stu I've kinda noted this but never really got it clarified... updating the BES CDO is as simple as just running the KB926666 on the BES or do I need to manually copy over the Exchange cdo.dll and register it?

No it is that easy mate, the pain is all the sendas crap later (which hopefuly I have avoided). As long as you run the patch on all Exch boxes before BES, you are cool. Doing all mine tomorrow morning (Sat GMT). Use this doc to check that the right cdo is in use after.

[stuwhite]

Originally Posted by tibbymstie

Has anyone gotten the 0x8D error yet?? The patch went through great on the Pearl, but this is a 7150T
I tried calling RIM, but there were 87 calls ahead of me!!
We're installing this wirelessly (which means there's VERY little documentation for errors) via the BES..
On the device itself, it does have a listing for "2007DST Patch", but in there all it says "Error installing 2007 DST patch."
I have tried re-downloading it from the device, but no luck.

EDIT: Forgot to mention, I'm on Lotus Notes 6.5.5 if that matters..

All the error codes are here. HTH.

[DarienA]

Originally Posted by stuwhite

No it is that easy mate, the pain is all the sendas crap later (which hopefuly I have avoided). As long as you run the patch on all Exch boxes before BES, you are cool. Doing all mine tomorrow morning (Sat GMT). Use this doc to check that the right cdo is in use after.

Cool, we're a very small org so it's only one Exch, one BES thank goodness, and yeah due to problems that were going on when I first got here last year I quickly learned about verifying that the version of the cdo on the BES is the same one as the Exch... so looks like I'm all set...

After talking it over with the help desk tech I'm just gonna run the Outlook update tool(that's all the exchange tool does anyway is run the outlook tool). We're small enough that it'll take longer, but less stress for me.

[tibbymstie]

Originally Posted by stuwhite

All the error codes are here URL. HTH.

Yes, I looked at the error code message before coming on here, it says "EVENT_ERROR_INSTALLING_PATCH_TX_ERROR"

Now could someone tell me what that means?? What is a TX error and how do I resolve it??
: s

[DarthBBerry]

Originally Posted by stuwhite

Ah shuddup. You don't even run Exchange, your life is bliss :-> I thought a Filter-bot would be nothing to a Telecom Sith Lord

You will all bow down before my über 1337-ness!

[DarthBBerry is now smited by Filter-bot for 10,000 damage.]
[Alas, DarthBBerry has died from pain and suffering.]

Oh woe as me.

But true, I don't know Exchange as well as I would like. Domino here, but not by my choice.

[stuwhite]

Originally Posted by tibbymstie

Yes, I looked at the error code message before coming on here, it says "EVENT_ERROR_INSTALLING_PATCH_TX_ERROR"

Now could someone tell me what that means?? What is a TX error and how do I resolve it??
: s

Total guess but looks like the BB can't communicate with the site correctly. Assuming they can browse to the site properly (if not, there you go), must be a weird error (shock horror). Can you ask the user to use the USB method?

[DarienA]

Originally Posted by tibbymstie

Yes, I looked at the error code message before coming on here, it says "EVENT_ERROR_INSTALLING_PATCH_TX_ERROR"

Now could someone tell me what that means?? What is a TX error and how do I resolve it??
: s

This is a shot in the dark, do you have in the software configuration policy did you remember to set External Network Connections to Allowed, and Disposition to Required?

[tibbymstie]

Originally Posted by stuwhite

Total guess but looks like the BB can't communicate with the site correctly. Assuming they can browse to the site properly (if not, there you go), must be a weird error (shock horror). Can you ask the user to use the USB method?

Unfortunately, I can't.. Right now I'm just testing before I send this out to all our users, but quite a few of them have the older (7100 and 7105) devices.. If it couldn't find the site, though, why would the Pearl device I tested work??

Guess I was just hoping someone had already seen this error and knew what to do..

[tibbymstie]

Originally Posted by DarienA

This is a shot in the dark, do you have in the software configuration policy did you remember to set External Network Connections to Allowed, and Disposition to Required?

Yup, did that..
And we didn't have any existing policies or security in place, so I know it's not something else in there..

[totalstu]

Originally Posted by DarienA

Cool, we're a very small org so it's only one Exch, one BES thank goodness, and yeah due to problems that were going on when I first got here last year I quickly learned about verifying that the version of the cdo on the BES is the same one as the Exch... so looks like I'm all set...

After talking it over with the help desk tech I'm just gonna run the Outlook update tool(that's all the exchange tool does anyway is run the outlook tool). We're small enough that it'll take longer, but less stress for me.

So, you're going to run 926666 on your exchange server, then run it on the BES server. Then, instead of the exchange calendar tool your going to run the outlook tool zmove.exe? We have a smallish organization. One Exch with approx 250 mailboxes, one Bes with 49 users. Is this outlook tool going to be easier to run than the exchange tool. I haven't looked at the outlook tool.

Thanks

[BirdmanSTX]

I was getting the same 0x8D error. You'll notice you're probably only getting that with older versions of device software. The disposition needs to be Optional. If you look in the release notes for the 2.2 version of PatchManager you see this...

----------
For BlackBerry® Device Software versions earlier than 4.1.0.344, including 4.1.0.347, the DST Query tool might have listed a BlackBerry device in the xxx8220;Awaiting Patchxxx8221; state even though the patch could not be applied to the BlackBerry device.
DST 2007 patch manager version 1.5 downloaded the DST 2007 patch and attempted to install it. The installation failed because the specified application control policy did not permit the DST 2007 patch to be installed on the BlackBerry device. The event logs for the BlackBerry device incorrectly reported xxx8220;EVENT_PATCH_INSTALLED_NO_RESET_REQUIRED (0x15)xxx8221;. In the DST Query tool, the BlackBerry device was listed in the xxx8220;Awaiting Patchxxx8221; state.
When used with DST 2007 patch manager version 2.2, the DST Query tool now sends the xxx8220;EVENT_ERROR_INSTALLING_PATCH_TX_ERROR (0x8D)xxx8221; error message to the BlackBerry Enterprise Server if this error occurs. On the BlackBerry device, the xxx8220;Error installing 2007 DST patchxxx8221; message appears.
Workaround:
For BlackBerry Device Software versions earlier than 4.1.0.344, including 4.1.0.347, administrators must use a BlackBerry Enterprise Server software configuration to set the default application control policy to xxx8220;optional.xxx8221;
After an administrator sets the default application control policy to optional, users can attempt to download the DST 2007 patch again.
KB12424
----------

Once I changed the disposition to Optional, I stopped getting the 0x8D error.

[DarienA]

Originally Posted by totalstu

So, you're going to run 926666 on your exchange server, then run it on the BES server. Then, instead of the exchange calendar tool your going to run the outlook tool zmove.exe? We have a smallish organization. One Exch with approx 250 mailboxes, one Bes with 49 users. Is this outlook tool going to be easier to run than the exchange tool. I haven't looked at the outlook tool.

Thanks

Yeah only about 100 employees, between 2 of us that should take no time. All the Exchange tool really is doing is running the outlook tool with on all mailboxes in a silent-like mode thats why the outlook tool needs to be run on the machine that you run the Exchange tool on.

Unlike the exchange tool the outlook tool is blazingly easy to use. Open it on the users desktop you see that it has their profile selected(their name will show up), click ok and its off and running.

[totalstu]

Originally Posted by DarienA

Yeah only about 100 employees, between 2 of us that should take no time. All the Exchange tool really is doing is running the outlook tool with on all mailboxes in a silent-like mode thats why the outlook tool needs to be run on the machine that you run the Exchange tool on.

Unlike the exchange tool the outlook tool is blazingly easy to use. Open it on the users desktop you see that it has their profile selected(their name will show up), click ok and its off and running.

So you have to log on as each user seperately and/or onto each of their workstations? Our organization is mainly running on Citrix, unless your an executive with a laptop.

[DarienA]

Originally Posted by totalstu

So you have to log on as each user seperately and/or onto each of their workstations? Our organization is mainly running on Citrix, unless your an executive with a laptop.

Yes, but probably could also do it just at one PC. Configure that pc to have access to the mail account for the user you want to prep, run the outlook tool, configure a new mail account, run the tool again, etc.

[BirdmanSTX]

RIM DST site now shows v2.3 of PatchManager and 4.1.2.8 of DST2007Query, just FYI.

[silver_2000]

I did the dstquery with the resync command that was posted somewhere here and suddenly 2 hours later the dst query results went from less than 10% applied to 80% applied - No need to upgrade from 1.5 to 2.3 or 2.4 or 2.5 whatever the current version is ..

Also installed the boxtone web version of the query - I installed it on my pc - which is the right move since it wants to install php and apache - I also had to set the apache2 serviec to logon as me before it would work

The boxtone app makes for some pretty pictures but is over kill for my one server with 130 users - Im sure my manager will love it though. Trouble is Boxtone will be hounding me to spend money with them now...

edit add links to details of what worked for me .....

http://www.blackberryforums.com/bes-...ync#post468579

High level steps to diagnose and address this scenario are:
(1) Run the DST2007Query tool and check for devices in the 'awaiting patch' state;
(2) If there are then run the new tool with a command line switch "-invokesync" during off hours;
(3) Reboot the SYNC server;
(4) Wait to let the data sycnhronize; and
(5) Then re-run the tool again (Step #1) hours later, or ideally the next morning.

[ts937km]

Anyone know if the new dstquery tool should be run from the actual blackberry server or another box. I'm assuming it doesn't matter.

Right now I ran it from my test blackberry server (pointing to the production database). Once run with the -invokesync parameter I reset the synch services on my 2 production bes servers. I guess I will wait and see what happens to my 188 that are showing awaiting patch. I'm up to 674 upgraded (after have the user do manual patching of the last 400+)

[Gotrek]

Originally Posted by ts937km

Anyone know if the new dstquery tool should be run from the actual blackberry server or another box. I'm assuming it doesn't matter.

Right now I ran it from my test blackberry server (pointing to the production database). Once run with the -invokesync parameter I reset the synch services on my 2 production bes servers. I guess I will wait and see what happens to my 188 that are showing awaiting patch. I'm up to 674 upgraded (after have the user do manual patching of the last 400+)

I've been running it from my workstation at home and it's working fine.

[stuwhite]

All Exch and BES boxes are now CDO-patched. I did have to manually move and reg the CDO files on the BESs as the registered ones (c:\winnt\system32) were still the old ones after the patch. But i have to assume that mannually registering the new ones in the same location is fine. If not, tough Now to try and have some weekend.

[stuwhite]

BTW, grabbed the new dstquery after I did the CDO and ran the invokesync on both BESs. Will see on Monday if it has made a difference.