This is my first time on posting on the forums so i'm sorry if my details aren't that good.

I have a BES server running version 4.1.7.17 and a BlackBerry 8900 running OS 5. From what Blackberry has told us when we actually got a hold of them was that it was possible to do an activation over wifi which worked when we used OS 4.6 on the devices. Since we have upgraded, we have been unable to activate them at all and have received an error saying "Activation failed. An error was encountered when sending the activation transmission."

I went out and bought an AT&T Sim card with a blackberry data plan to try and activate the phone using the carrier. This also has not worked and I have been unable to contact blackberry on this issue. I believe that this may be an problem with our corporate firewall blocking any ports. I ran Wireshark though and have found that the Exchange Server and the BES Server are contacting each other and the activation data is being sent between the two. Right now I have no other thoughts on how to fix this issue. If anyone can help me, it would be greatly appreciated.

~Voalte

look at my signature and sign up, there is a dataplan tester with those tools.

I went to your link and I assumed you wanted me to click the "Enterprise activation readiness" link. When I did and put in my phones info, it says that my device was not provisioned to be activated. Yet I have the sim card in that I was told from AT&T has a blackberry data plan on it. I also noticed that in the Service books that two of the many are named "Provisioning". Any idea what to do now?

Call AT&T and have the correct the plan.

Just got off the phone with them and everything is working on their end. The provisioning is all set and says that i'm connected with blackberry. Although I had a question that they could no answer. Could having a 5.0 device with a different carrier and an AT&T sim card conflict with each other? Because I found out that AT&T only has 4.6 for their 8900 phones. Just a thought unless you think it's something else.

If the device is unlocked, any BES enabled SIM will work in it.

What does the status on the phone say when you go to

Manage Connections > Services Status

In the upper right corner of the screen, what do you see (EDGE, GPRS, 3G)?

Mobile Voice
Status: available
Connection: Mobile Network

Blackberry Internet Service
Connection: Mobile Network

Blackberry Enterprise Server
Connection: not connected (With WiFi on it says WiFi)

Mobile Network
EDGE

Mobile Network Provider
AT&T

Also says EDGE in the upper right hand corner.

So it looks like you are on the BIS data plan. For wireless activation, you need the BES data plan. You can still activate over the wire (USB).

I was told by our higher class server engineer that we require wireless activation and not usb. He didn't clarify that well on why, but our servers are shipped out to hospitals and that may be a reason.

You can activate via USB, but on BES 4.1 you will not get emails via carrier until the dataplan is a BES one.

What would I have to do to get a BES plan? If you don't mind explaining.

you need to ask the carrier. They can enable this

Thank You! I will do that right away and get back to you if my problem was fixed

So according to AT&T, we are on a BES data plan. We did find however that our license on a program called POPcon which manages our POP3 emails had expired a while ago and may be causing the problem. But then again, it's just another guess of mine.

Have you checked on the BES if your SRP connection works fine? Port 3101 must be opened on the firewall for that.

The SRP is active according to BlackBerry and port 3101 is open on our firewall.

check mailbox for etp.dat files and remove those messages.
Wipe device
Then activate again and look at the MAGT log on BES to see any info about the activation.

For some reason the MAGT log for today doesn't exist. So I attached one that is a few days old but the problem was still occurring during that time. I uploaded it if you want to take a look because I honestly don't know what i'm looking for exactly.

That log file is all jumbled up.