We had BES on Domino 7.01FP1 however there were some serious issues (non DST) with that so upgraded to 7.02 and it is OK now. You could probably stay on 7.01 w/o issues though.

The bug for losing pending messages was on Domino, may not exist in other 4.06 platforms. Also, it did not lose messages on upgrade, it lost them every time you stopped and re-started the BES task. This was fixed in 4.06 HF3.

Told the boss we are buying Exchange 2007 and a new 64-bit server.

Found a document on the net at MSEXchange.org showing step by step how to transition to it. I too was whinning and sweating over nothing as I perceive it.

Guess I will be kicking all my BB users off-line till I can readd them to the new server. Sounds like the Judge's and Sheriff are getting pagers and no mobile calendars for a few hours to a day.

I ran into the the same error and in my case I hadn't given myself rights to the database. DOH! try running the query from the server and see if it works there.

Too clarify.

My 7290's, 8700's and 8100's already have the latest firmware....so if I roll out this update, it should not be necessary?

The server you are running this from does not have internet access, sorry if this has been resolved already.

petim123, mind if I pick your brain re: Groupwise calendars, email me if you have the time. Just wondering what you may be doing, since Novell basically gave me a one finger salute re: a tool to change users meeting times.

Does anyone have instructions on how to run the DST2007Query.exe? I am having one of those days!!

Does it have to run on the BES server? Or can it run from a client. I get "access denied" error running it from my client.

http://www.blackberry.com/DST2007/pa...007_Update.pdf

HA! I had one of those days yesterday! On page 38, you will find instructions on using the utility. I am not running it from the BES, but am running at my workstation.

I have been trying to update our first Blackberry 8703e with the Blackberry DST 2007 Update Installer for the past day. I have been unable to complete the update using either the over the air procedure or the USB cable process from the Blackberry web site as well. The USB process provides the error "Blackberry DST 2007 Update site is currently too busy to service my your download.Please try again later." Has anyone else been able to update their device successfully this way?

We have a limited number of users running on a 3.6 Bes. I spoke with RIM and they said that I would have to wait on hold for two hours to speak to a Technical Support person. They said that they plan to have a team dedicated to DST set up by tomorrow.

ok seems i'm having one of those days today as well. Can someone point me in the direction of hotfix 1 for sp6.

ok seems i'm having one of those days today as well. Can someone point me in the direction of hotfix 1 for sp6.

Hey,

I read those, but still getting the message. I am not sure what <-dbauth> should be.

I am upgrading my server to 4.1.3 tomorrow, today is reading the docs day. I was looking over this to see how it worked before we rolled out the patches to everyone.

You will love this.

Background info: 8700c device version 4.1.0.194; platform OS 2.0.0.90

On my BB, I went to Internet Browser and onto BlackBerry. I downloaded the patch, it asked for a reboot, which I did. Afterwards, I went into Options - 2007 DST Patch. Stuck at Patch not found: Trying again at...

Opened a ticket with T-Support. The tech I spoke with's solution, upgrade the handheld OS to the latest version. Sounds easy huh? How about trying to locate 300+ other devices worldwide to upgrade. I don't think so buddy.

How is this done? How long do you have to leave it configured like this?

Exchange 2000
BES 4.1

When I go in to CMD and go to c:\program files\common files\research in motion\apploader and then type "loader.exe /index" and then hit enter, nothing happens. When I type "loader.exe" it brings up the application loader. wtf? what am I doing wrong?

When you type loader.exe /index it indexes the files in the directory.
From pg 41 of Deploying_DST_2007_Update

So essentially, you won't see anything happen, but check the directory for your DST files. You should have a new Specification.pkg & PkgDBCache.xml

This is likely going to sound stupid, but I have 415 users (BES 4.1.0.38/Exchange 2003), all in California, and after reading about all of the trauma everyone seems to be experiencing with pushing this from the BES, I am tempted to leave it to my users to download the patch themselves using the BB browser... A pain in the rear to be sure, but it has worked on a handful of devices so far.

I do have the files, but when I try to set that folder to the "handheld software location" it greys out the OK button.

You have to share the C:\Program Files\Common Files\Research In Motion directory out first. Share it to everybody
Then the path would be \\YOUR SERVER NAME\C$\Program Files\Common Files\Research In Motion

MUCH appreciated, everyone! Thanks for all the help!

Can someone spread some light on these Error log entries for me? I've been getting them whenever i assign a new device to a user. Platform is BES 4.0.1 and Exchange 2000


(EFFF2710) -> {<username>} PromotePendingAttributes: Promote pending service name failed

(EFFF2710) -> {<username>} PromotePendingAttributes: Promote pending routing info failed


(EFFF2710) -> {<username>} PromotePendingAttributes: Promote pending HRT failed

RacerGregg,

Would it be possible for you to give me these screenshots in french?

I would really appreciate that! thanks!

Mon Blackberry ne parle pas français. Désolé.

All-

I currently have a ticket open w/ T-support because a number of guinea pigs (err..devices) in both my test and prod environments are only reporting back to the BES that they have received the patcher application OTA but not that they have actually been patched. The devices themselves report having successfully been patched but that data apparently isn't being written back to the SQL DB.

RIM says they have had many other reports of this and that they are investigating. I'm am not rolling the patch out in production until I'm convinced that they're not going to roll out an updated patch.

Can you help me? How would I go about taking snapshots of a french device??

On those users "clear wireless backup data" wait a couple hours, re-run the dstquery tool.

"I currently have a ticket open w/ T-support because a number of guinea pigs (err..devices) in both my test and prod environments are only reporting back to the BES that they have received the patcher application OTA but not that they have actually been patched. The devices themselves report having successfully been patched but that data apparently isn't being written back to the SQL DB.

RIM says they have had many other reports of this and that they are investigating. I'm am not rolling the patch out in production until I'm convinced that "

Well, from some of the other threads here it appears that that is not a guraranteed fix. Besides that, my testing has shown over 95% of the devices have had this issue. I'm not sure I'm read to do this across many servers and thousands of users when I roll this out corporate wide. I'm not exactly ready to see what happens when the servers try to rebuild this info in a decent-sized environment.

I'll wait for RIM. We pay for T-Support for cases just like this.

I hear you.. I have a couple thousand myself.. well see..

Just got off the phone with RIM support, they told me a new patchmanager will be released today or tomorrow morning...

This is SOOOOO SAD!

It's released. I will start testing again this morning.... uggh!

Anyone have an idea what are the differences between DSt patches?

Never mind found it....

What different patches?

And,
We updated our fleet and only two of our 8700's are giving us problems. For some reason every appointment after April 1st is off by an hour. What do yall think?

My bad. I meant "Patch Manager", and the differences are idicated in a pdf doc included in the .zip download.

Sounds like all the pther patches aren't done yet (server OS, desktop OS, Exch CDO, BES CDO, cal re-base) but I wouldn't have thought you would have done them all yet anyway. Once all the other patches are done, you shouldn't see the 1 hour dif on the BB. If you have done them all, I guess you have found a new feature :->