[cglaser]

Hello,

We've been trying to install BES express on our SBS 2008 64 bit server. The install went fine, but we are getting an 5305 error regarding the agent not starting.

Prior to trying to install BES express we had a BPS installation on a separate 2003 server and it worked just fine. I used the BESAdmin domain account that worked fine on the BPS server as the admin account when installing the BES express as I figured all permissions were already set on the account for it to work properly.

I can't figure out what's causing these 5303 errors. Any ideas?

The old server is turned off so it's not some kind of interference from the BPS software.

Any help is appreciated. Thanks.

[besadmin23]

did you install Express while logged in as the BESADMIN account?

[mschauber]

I've spent the better part of three days trying to solve this problem.

Only solution I was able to come up with that worked was creating an entry in the hosts file (c:\windows\system32\drivers\etc\hosts)... Open with notepad.. that has the internal ip and internal fqdn for your Exchange/BESX server. (eg: 192.168.211.39 exchange.domain.local)

For some reason, despite Exchange and BESX being on the same box and the dns for the lan connection being the internal dns, both of which are also domain controllers, BES was unable to find the DC when using the mapi connection... (Even though it resolved the besadmin account when setting up the mapi profile.)

I hope this helps you and others save a lot of time.

Good luck..

[DJS1234]

OK I installed BES Express 5 on Friday night and am now testing it at work this morning with my spare Curve 8310. This handset is on a BES data plan so no issues with OTA activation.

Anyhow it won't activate just sits there for ages so I look in event viewer and there's the dreaded 5305 error - "Blackberry messaging agent xxxn BES Agent 1 Failed to start. Error Code 5305"

Installation in on SBS2003 and all installed as per RIM video on the Express site (I've installed BPS 4.1 on SBS2003 loads of times so have some installation experience)

Any ideas where I can start the diagnosis? All BES 5 threads I find online just say you shouldn't be installing it on the Exchange server which obviously doesn't apply with Express.

I've added the internal IP to the host file with the FQDN of the server and restarted the BES Services but the Messaging Agent error straight away.

Anyone got any ideas?

Cheers
Dan

[DJS1234]

OK it gets weirder (If weirder is a word) I can run IEMSTest.exe on a domain user and it all works - folders create and delete successfully.

So it looks as thought the MAPI profile works so why can't the BES see the message store?

[DJS1234]

Right, now it's working although I'm not 100% sure why...

First I created a host file entry for the server again just for luck.

Second I edited the registry as per these instructions however the correct server name was already there.

I changed the server name in the registry from being server.domain.local to just being server - this didn't work so I changed it back to server.domain.local (With correct server name obviously) and restarted the BES services again. This time the Messaging connected! I looked in the MAGT logs in the BES folder and could see everything was OK - weird eh!

Now a reboot of the server could perhaps of fixed this but as it's SBS I can't reboot in the day (Standalone BES is very nice for that reason!) so perhaps me changing the registry then restarting the server just kind of jogged something into life.

So to any other 5305 sufferers the problem is definitely in the BES not seeing Exchange even though it's on the same box and has DNS pointing to itself etc etc. Could be a bug there for RIM to look at as this product is designed to be installed on SBS servers (Or at least is a supported configuration)

Also just to give credit I found the last post in this thread by Aribrown to be helpful in me getting to the resolution.

Now I'm nervous that next time the server is rebooted the Messaging Agent will bomb out again... (Crosses fingers)

[mschauber]

Originally Posted by DJS1234

Right, now it's working although I'm not 100% sure why...

First I created a host file entry for the server again just for luck.

Second I edited the registry as per ... instructions however the correct server name was already there.

I changed the server name in the registry from being server.domain.local to just being server - this didn't work so I changed it back to server.domain.local (With correct server name obviously) and restarted the BES services again. This time the Messaging connected! I looked in the MAGT logs in the BES folder and could see everything was OK - weird eh!

Now a reboot of the server could perhaps of fixed this but as it's SBS I can't reboot in the day (Standalone BES is very nice for that reason!) so perhaps me changing the registry then restarting the server just kind of jogged something into life.

So to any other 5305 sufferers the problem is definitely in the BES not seeing Exchange even though it's on the same box and has DNS pointing to itself etc etc. Could be a bug there for RIM to look at as this product is designed to be installed on SBS servers (Or at least is a supported configuration)

Also just to give credit I found the last post in ... thread by Aribrown to be helpful in me getting to the resolution.

Now I'm nervous that next time the server is rebooted the Messaging Agent will bomb out again... (Crosses fingers)

Glad to hear it's working. I was going to say you probably have to flush the local dns (ipconfig /flushdns) to force the server to use the hosts file entry instead of the cached dns entry it already had. That's probably why the reboot worked

I hope this solves the problem for lots of people There must be some "bug" some place in the code that is not correctly checking the DC (registered local DNS) for the fqdn, but instead is looking elsewhere.

[DJS1234]

Originally Posted by mschauber

That's probably why the reboot worked

\
I haven't rebooted yet... gulp. Here's hoping it will hold once I do

[cglaser]

Originally Posted by besadmin23

did you install Express while logged in as the BESADMIN account?

Yes. In fact I used the same domain account 'BESAdmin' as was used to set up the BPS server on the Win2003 server. I figurd taht acount would already have all the mailbox permissions, etc set on it since it was working fine for the BPS install.

I did shutdown the old win2003 server with BPS installed on it before attempting to install BES Express on the SBS 2008 server.

[cglaser]

Well,

I just tried to re-install...same issue.. 5305 errors. So I tried the hosts file fix. I added server name ot the hosts file with the correct IP address and then rebooted.

Unfortunately it did not solve the issue. The server is still throwing 5305 errors.

So it looks this hosts file does not resolve it in all cases.

[cglaser]

OK. After applying the registry changes in KB03304 the server IS now working. NOTE: I had to create the 001e6602 string value in both locations, but once I created the key, entered the internal FQDN for our exchange server, and then restarted the router the messaging agent came up.

[DJS1234]

Originally Posted by cglaser

OK. After applying the registry changes in KB03304 the server IS now working. NOTE: I had to create the 001e6602 string value in both locations, but once I created the key, entered the internal FQDN for our exchange server, and then restarted the router the messaging agent came up.

Glad it's all working for you

[mschauber]

Originally Posted by cglaser

Well,

I just tried to re-install...same issue.. 5305 errors. So I tried the hosts file fix. I added server name ot the hosts file with the correct IP address and then rebooted.

Unfortunately it did not solve the issue. The server is still throwing 5305 errors.

So it looks this hosts file does not resolve it in all cases.

The host entry was for your domain controller? I have had the same error now on three servers and the host file entry pointing to my domain controller has worked each time. Even the one that was an SBS server, needed a host entry to itself. Hope RIM fixes this soon.

Marc

[knottyrope]

BlackBerry Messaging Agent log shows "Failed to read 001e6602 reg value from the BlackBerry MAPI profile"
Also messaging agent failed to start error code 5305

View Document

also

Curious, were there any LDAP errors during install or in the install logs? If there were can you please post it.

[kapasaca]

we've come across this issue as well a couple of times now.
The RIM KB explains what to do, but isn't really clear I think.

there should be three reg keys (mapi profile's)

BlackBerryServer
BlackBerryServer_Agent1
BlackBerryServer_MailStorProfile

the first and third should have the DCA key within the profile

the string value should be 001e6602 and value data should be exchangeservername.domain.com

[knottyrope]

Originally Posted by kapasaca

the string value should be 001e6602 and value data should be exchangeservername.domain.com

That only works if your Exchange server is a GC.

Only my DC's have GC roles.