Jeff,

The services were all ok.

In one of the processes that I ran I made sure also that I stopped  
them and restarted them correctly 
(http://thebackroomtech.com/2008/03/05/the-correct-order-to-stop-and-start-bes-services/
 
).
They are all running under the admin account. In a more standard  
environment where you have a separate box for the BES, they'd run  
under the BES admin user (which in the end is also an admin account).

I tore the whole BES set up apart, recreated it under a totally  
different user. I am not seeing any more errors related to default  
message store or messaging agent. I was able to activate a testing BB.  
A couple of users were also able to activate. So far it seems to be  
working. Let's see how stable it is.

thanks for the help

Regards,

Julio Ochoa
t...@webjogger.net
845-757-4000

On Jan 23, 2009, at 11:25 AM, May, Jeff wrote:

I would suggest looking at the services and see what is started to make
sure they are using the besservice account and the correct password and
also verifying the service account is active and not locked out, past
that and if you are still getting errors a trouble call to blackberry
would be my next step.....Sounds like you have done all the proper tasks
and still no go....so best step would be to work with BES and they
should get you fixed up pretty quick.

-----Original Message-----
From: Julio Ochoa [mailto:t...@webjogger.net]
Sent: Friday, January 23, 2009 11:19 AM
To: MS-Exchange Admin Issues
Subject: Re: BES Messaging Agent Errors

Jeff,

Thanks for the link. I went through the different options, but still
no dice.
Here's another error that is showing up right after I start the BES
manager

Event Type:     Warning
Event Source:   MNGR
Event Category: None
Event ID:       20000
Date:           1/23/2009
Time:           10:57:13 AM
User:           N/A
Computer:       MAILHOST
Description:
[ExchangeAdaptorDLL::Initialize] Failed to open default message store,
result=0x8004011d.

This would indicate permissions issues with the besadmin account I'm
using. However, I have gone through the permissions set up so many
times I can do it with my eyes closed now
http://www.blackberry.com/btsc/search.do?cmd=displayKC&docType=kc&extern
alId=KB02276&sliceId=SAL_Public&dialogID=1487349&stateId=0%200%201485666

In addition to the event viewer message above, I also get a warning to
the effect of "Failed to open the default message store using the MAPI
profile..."
Again, these errors seem to point to permissions issues for the MAPI
user.



Regards,

Julio Ochoa
t...@webjogger.net
845-757-4000

On Jan 23, 2009, at 10:16 AM, May, Jeff wrote:

Julio, here is the blackberry KB article, a lot of different
suggestions, too many to list here but I would suggest running through
one by one and see what you find.....Thanks.

http://www.blackberry.com/btsc/dynamickc.do?externalId=KB01018&sliceId=S
AL_Public&command=show&forward=nonthreadedKC&kcId=KB01018

-----Original Message-----
From: Julio Ochoa [mailto:t...@webjogger.net]
Sent: Friday, January 23, 2009 9:46 AM
To: MS-Exchange Admin Issues
Subject: BES Messaging Agent Errors

Hi,

I'm seeing some issues in one of the BES servers. Anybody's input
would be appreciated.
Here's the environment we're running
Windows 2003 R2 SP1 running on a VPS
Exchange 2003 SP1
BES 4.1.4A

This is a very small environment with about 5 users so that is why the
BES is installed on the same server as Exchange. We have similar
environment running without problems, so that is why I'm confident
this is supposed to run.

Here's the error:

Event Type:     Error
Event Source:   BlackBerry Messaging Agent MAILHOST Agent 1
Event Category: None
Event ID:       10277
Date:           1/22/2009
Time:           11:31:14 PM
User:           N/A
Computer:       MAILHOST
Description:
BlackBerry Messaging Agent MAILHOST Agent 1 failed to start. Error
code 5305

I have made sure all the permissions are correct. I have uninstalled
and re-installed BES a couple of times. I'm able to add users to BES,
but the activation hangs there forever.
Here's for example one of the entries in dispatcher service logs for
BES (I replaced the user's private info)

[30450] (01/23 10:03:50.273):{0x1C40} {XXXX-XXXX} User unchanged
(disp): id=1, email=u...@domain.com, device=<none>, routing=<none>,
agent=<none>, ext=1, wl=0, keys=(0:0:0)

usually there would be a code in the routing and agent fields.

Has anybody seen this and if so how were you able to deal with it.

thanks!
Julio
~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~
~             http://www.sunbeltsoftware.com/Ninja                ~


~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~
~             http://www.sunbeltsoftware.com/Ninja                ~


~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~
~             http://www.sunbeltsoftware.com/Ninja                ~



~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~
~             http://www.sunbeltsoftware.com/Ninja                ~


~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~
~             http://www.sunbeltsoftware.com/Ninja                ~

Reply via email to