[Danny_Larouche]

oly1eagle: I don't know what do you mean by "BIS" or how is T-mobile. The BES is installed on an Exchange2000.

D_Fisher: I am using BES 4.0 (the lastest one)

Udontknowjack: As proposed, i verify the "option, security" on the device that was previously attached to a deskop software and i don't see the SRP in there. Between the bracket i only see the email address:

Services:
Desktop [username@domainname.com]

Also, when i check the BES`s server stats in the manager, all counters are still zeroed after 24hrs while user`s stats are growing.

[Gregory Ptrolati]

We have a BES 4.0 on one side of the country and one of our Exchange 2003 servers is on the other side. Users on this Exchange server regularly have their wireless activations fail. Connecting the device to the workstation and generating an encryption key gets the PIN info over to the server, and once wireless contact is established, the activation begins. Sometimes it can take up to 6 hours (!) depending, I'm guessing, on mailbox size and bandwidth, but one the server knows the PIN and you can see wireless contact with the device, you've got the ball rolling.

Once the activation is complete, email can lag a little sometimes but it's not too bad.

[jwhitford]

We ran into this issue and realized that the SQL database was full or very very close to full. We moved the db and pointed the BES mgr to a real SQL server instead of MSDE and our problems went away. There is also a hack/reg modification to allow the MSDE database to expand further than its original design. Hope this helps!

[W(G)]

Have you enabled the Enterprise Service Policy?