New Exchange Server
Hey there, so we added a new Exchange server 2003 to our lineup and have moved a couple of BB users there, but they are not getting emails.
Is there something i need to do for BES to start connecting to it? Thank you. |
Yes.
Did you grant the BESAdmin account the appropriate permissions on the server as instructed per the installation guide? Send As / Receive As / Administer Information Store |
Quote:
I will get that checked out, thank you for you fast response. |
Ok, so the permissions are checked. I have switched the other 2 users mailboxes out to another server and i moved myself to the new one for testing.
I do receive emails randomly, but usually takes about 5 minutes. I am able to send right away and do lookups. When i do a Reload User i get all the new emails right away, but everything that comes in after that doesnt go through. |
Same LAN?
|
Quote:
We have a total of 8 exchange servers, and i increased the number of agents to 5. That seems to work randomly. |
By default if you have 5 Exchange servers talking to a single Exchange BES it should spawn 5 agents.
Did you change the NumAgents value? Managing BES <> Exchange Mappings |
[QUOTE=hdawg;1434271]By default if you have 5 Exchange servers talking to a single Exchange BES it should spawn 5 agents.
Did you change the NumAgents value?QUOTE] Yes, i manually do that, however, every time i restart the number of agents changes back to 2. We are running SQL Express, andi was told thats what was causing the reset. I'll go ahead ahead and increase it to 8 tomorrow. I did noticed that any other user thats not on the new server receive emails right away. It looks isolated to the new addition of another exchange server. Switching it to 5 agents helped, but there was still a delay on my test BB. i'll see if 8 agents work fine. |
Quote:
Quote:
|
Quote:
So what else can i do? The server clearly responds better when i increase the agents to 5 from 2. If i leave it at 2 i get PIPE FULLS all day long. That was the solution given by the BES5.0 tech team from RIM. Im going to upgrade to MS SQL 2005 within this week and see how it goes. Any other ideas? Honestly, i just want to get this issue resolved as we are going to be getting more servers set up and i want to be prepared for it. I really appreciate your support on this, once this has a solution im going to send you guys giftcards on behald of my company ;-), thank you very much. |
Quote:
|
Quote:
|
Is there an article on how to move from MSDE to SQL? Thanks. Im on 5.0, i only found one for 4.0 -4.1, not sure if thats the same.
|
Honestly, I haven't done a 5.0 move yet ... the procedures should be the same. CreateDB.exe is your friend; it'll do the hard work.
|
Quote:
That sucks, i mean, why would they do that? Anyways, we are adding another BES server and SRP to our lineup, with a remote SQL database as suggested by you. Thanks a lot hdawg. I need to thank your for your help, please, PM me your address so i can send you a giftcard on behalf of my company, thank you so much. |
WHAT?!?!?!?
Can't move a database with 5.0; that is the biggest load of garbage I've ever heard. This makes me want to go to a move right now and document it, because there is no way the ability to move database servers would ever be taken out of support. my email is ... but if you'd rather just call RIM and demand an answer that'd be good enough for me :) |
Quote:
Yup, it seems that way. I have talked to 5 different techs, the last one being the highest level database expert. The answer is NOPE. "You want to migrate, you need to start fresh buddy" In those words. |
Either somehow the question isn't being asked in a manner that they understand, or you've spoken to 5 people that don't know what they're talking about.
You can most definitely move databases with 5.0 ... this would have been a huge step backwards with the product if this is the case. |
Part of RIM's HA strategy is to configure database mirroring between two SQL servers, which is essentially nothing more than a database backup/restore that is continually synchronized between the two partners. From a failover perspective, you are 'migrating' from one SQL server to the other in an event of a failure. I'm not buying the inability to move the database to a new SQL server and reconfiguring BES to point to the new server.
|
Ok, now they are pointing to the article for moving 4.1 databases out to another one, but have strongly suggested that i be on the phone with the to provide any support should an issue arise.
I dont think they have been trained on how to do it and are awating a guinea pig. |
All times are GMT -5. The time now is 04:20 AM. |
Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2024, vBulletin Solutions Inc.