So I am generally unhappy with my BES experience. The only major technical problem I had was getting it set-up with it's own SQL database. Once I finally dug out my SBS 2003 installation disk and got a new database for besmgmt I got the success dialog box and my hopes were promptly squashed by the whole installation window vanishing after clicking ok. No error message, just gone. The next step should be CAL and license info. Now what? Can I resume the install somehow?

Set-up:
SBS2003
Exchange2003
MSDE SQL

check the install logs located near here

C:\Program Files\Research In Motion\BlackBerry Enterprise Server\Logs

It you do resume the install search on here for threads about what happens when you stop the install halfway through. IIRC some tinkering will be required to get MDS_CS working, happened to me once and wasn't fun but also wasn't hard

thank you for the quick reply. I was able to resume the install and it went smoothly. I was afraid something terrible has occurred. Now I am getting "Unable to open default message store of the MAPI profile used to initiate MAPI"
when using the BB manager. HMPF. I hope it will let me set-up the device now.

If it was setup wrong then

View Document

wow, that sucks. I haven't fixed the MAPI profile yet. Is this required to get a device up and running? I am at the activating step, the device is unresponsive and I got an activation e-mail on the exchange account but nothing is happening. It still says initializing.

did you get teh right data plan for the -phone. BES knot BIS. And carriers do make many mistakes when setting it up and causes endless posts/calls/frustration.

If mapi was wrong then how did you get BBM to open?

It just did. I got the error and then it continued to load. It said I wouldn't be able to send e-mails from the manager but I don't care about that right now unless it is critical. BES installation has filled me with intense hatred for RIM. There are many other solutions I could have implemented by now. This whole set-up is needlessly complex. Too many points of failure. I would not recommend this solution to others.

wouldn't the phone tell me if it didn't have the plan? Shouldn't there be some error code somewhere? I got the activation e-mail in the local account here that says the server should pick it up but BES Manager is oblivious to the arrival of this message.

You are right, It is more complex than a windoze mobile phone.

There is no simple code, unless you have t support for a tool for Dataplan tests.

etp.dat? then you do knot have the correct permssions assigned set so BES can pick it up.

UPDATE:
Yes sir,
I have etp.dat in the INBOX.

The reason I had issues with the MAPI profile is that I wasn't logged in to the computer as the besadmin. I fixed that up now so that I am logged in as the besadmin and I am receiving no errors from the BB manager.

Yet the phone is still initilizing...

The besadmin has access to all the files and everything is running. What permissions might I be missing?

try to activate the phone one more time, does teh etp.dat file get sent and pickeed up by BES?

If knot then
View Document

OKay,
I did the six steps of authorization. Then I resent the OTA activation from the phone. It ended up in the INBOX with the etp.dat

initializing still being displayed in the BB manager. This has gone on for hours.
-=Expression of hate and discontent=-

It seems like I am so close. Why blackberry why?

Thank you very much for all the resources mr. knottyrope. I still find myself unable to untie this BES knot.

If the etp.dat is staying in the Inbox then the BES doesn't have the correct permissions to the mailbox. Try deleting any existing messages and try again.

David is right but I have also seen this where the MAPI profile of the person doing the EA is corrupt. OP definitly double check your perms coz this is the issue 99% of the time. Even if you think you have checked them, pls check em again coz there is a lot to check (as you have discovered).

After that, I would change the MAPI profile being used on the machine you are EAing from. Then just change it straight back to the valid one (you or besadmin, whichiever one you know has perms).

You are close and I know you are getting annoyed dude but stick with it as this is not a simple setup. I know you are frustrated but once you understand what is going on in the background you will realise why this can be such a hassle. But it's worth it coz once it's working, it's fairly easy to maintain and is still a fantastic solution imho.