New BES Server, 4.0, Nothing will activate (OTA, Direct Connect,7100s,7290s). I've blown everything away and started over a few times including the directory and SQLServer. All services start/ Everything shows normal. SRP Connected.

Any help is appreciated

1) OTA Attempts. Phone sticks on "Activating..." I noticed there is no MAGT Log to check for OTAKEYGEN Messages even though the logging is specified on for everything...

The users Mailbox will get messages in their mailbox similar to below message everytime they try and activate...

From:
This message is used to carry data between the BlackBerry Handheld and an associated server. Please do not delete, move or respond to this message - it will be processed by the server.

BEGINETP 288
...
ENDETP -1406689435

The Dispatcher Log has expired messages:

Dispactcher Log:
[30181] (10/09 11:41:04):{0x1368} Performing system health check (BlackBerry Dispatcher Version 4.0.2.3)
[30317] (10/09 11:42:12):{0x898} {xxxx} Packet from PIM Connector has expired, extTag=22
[30317] (10/09 11:44:07):{0x1848} {xxxx} Packet from PIM Connector has expired, extTag=23
[30317] (10/09 11:45:15):{0x1630} {xxxx} Packet from PIM Connector has expired, extTag=24
[30317] (10/09 11:46:45):{0x1A4C} {xxxxi} Packet from PIM Connector has expired, extTag=25

------------------------------------------------------------------------
2) Direct Connect

An error occured while assigning the handheld to the user.

The user is not yet known to the BlackBerry Agent. It can take several minutes for a newly added user to be fully initialized by the server before they can be provisioned. (of course it's been days)...

1) BlackBerrySync Server clearly shows User started up
2) BlackBerry Dispatch server shows user started up
------------------------------------------------------------------------

What mail system are you using?

If you try to remove the user and add them again can you check the dispatcher logs for an RPC error?

Are you using the BlackBerry Manager from a remote workstation or on the BES server?

Here's the deal. I found it odd that the *MAGT logs weren't being created.

I found no BlackBerryAgent processes running (as with a normal install). The BlackBerryAgent executable looks like it's launched by the Dispatcher service - when I kill the Dispatcher on a working BES server, the BlackBerryAgent Service dies.

I'm not sure why the dispatcher won't launch the BlackBerryAgent executable on this fresh install, but when I launch it by hand (BlackBerryAgent.exe -agent 1) - everything works.

Does anyone know why the BlackBerryAgent.exe wouldn't get kicked off properly?

JB

In case anyone comes across this problem... The BlackBerryController was unable to query the running services. You can test this by running:

sc.exe \\127.0.0.1 query

and get back the response:
[SC] OpenSC Manager FAILED 5: Access is denied.

The BlackBerryAgent will not get kicked off if the Controller fails to query the local service database (similar to the above command line). I was unable to figure out why the controller can't query the service database on this computer (2003 Enterprise Edition), but I suspect it has something to do with this article:

http://www.blackberry.com/knowledgec...65876&vernum=3

Even though I'm not running Small Business Server, I exhibited the same symtoms as described here:
1) Task Manager shows no process BlackBerryAgent.exe running
2) No *MAGT logs in the log directory
3) No users can activate

I'm hoping somebody knows why the controller gets the permission denied when querying the localhost service database. Running sc.exe \\<realip> query works, but the BES server queries using 127.0.0.1.

If you're banging your head against a wall with this issue, you can start BlackBerryAgent.exe -agent 1 by hand until somebody helps out here.

I'm seeing this on my server as well. Windows 2000 Standard Server, BES 4.0.2, Exchange 2003 on a seperate Windows 2003SP1 server. SQL server on the BES server. SRP works fine, getting the PIM connector thing has expired message.

My agent was not running. I manually started it as you suggested and mail is now flowing.

I'll do some digging as well but please post if you've found a solution.

Thanks!

-m