Zimbra offers Open Source email server software and shared calendar for Linux and the Mac
 
Go Back   Zimbra - Forums > Zimbra Collaboration Suite > Mobility > Zimbra Connector for BlackBerry

Welcome to the Zimbra - Forums!
Welcome, if you would like to post a comment please register. We also encourage you to explore all things Zimbra with our team and members of the community.

Reply
 
LinkBack Thread Tools Display Modes
  #11 (permalink)  
Old 08-24-2009, 06:14 PM
Zimbra Employee
 
Posts: 117
Default

Thanks for posting MAGT log file. Based on the content, it looks like agent does not get notified upon arrival of activation message(there is no record in MAGT log confirming that new mail has arrived). It usually implies that message did not arrive succesfully to the 'BlackBerryServer' mail profile. Did you try to open this profile with Outlook and check for activation message? It is possible that message is visible in webclient but not in BES mail profile. Please also find relevant discussion in the following post:

[SOLVED] BES Activation problem

As you can see the solution was to add the 'network@etp2111.etp.eu.blackberry.net' email in the users mailbox to the safe senders list.

Here are a couple of additional possibilities that i was thinking of:

- it is possible that BB user in question resides on zimbra mail node which has port 443 closed. If this is the case then port 443 has to be opened. Please use 'telnet mailnode 443' and see if you are able to connect.

- it is possible that alias and not primary user's email address is used at the time of activation on enterprise activation screen on device - i would check email address used for activation and compare it to the email address listed in the GAL.

- it is possible that user had not been purged when he was re-added in BB manager - i would try to re-add user and make sure that user has been purged.

- it is possible that BES machine is configured to use proxy server to connect to LAN. If this is the case then i would recommend to configure BES machine to connect without proxy.

- also in case if none of above suggestions worked then i would need to look into zcb log file with 'BlackBerryAgent' component in the name covering period of time when device was going though the process of activation. Please use the following description on how to get zcb logs ZCB and BES Logs - BlackBerry - Zimbra :: Wiki. Please send zcb logs over to support@zimbra.com or eugene@zimbra.com.
Reply With Quote
  #12 (permalink)  
Old 08-24-2009, 07:47 PM
Active Member
 
Posts: 29
Default

Thanks so much Eugene for all the suggestions you have provided thus far.

Quote:
Originally Posted by eugener View Post
Thanks for posting MAGT log file. Based on the content, it looks like agent does not get notified upon arrival of activation message(there is no record in MAGT log confirming that new mail has arrived). It usually implies that message did not arrive succesfully to the 'BlackBerryServer' mail profile. Did you try to open this profile with Outlook and check for activation message? It is possible that message is visible in webclient but not in BES mail profile. Please also find relevant discussion in the following post:
Last week I did check through Outlook to see if the message was going into the user's the inbox, it was.



Quote:
- it is possible that BB user in question resides on zimbra mail node which has port 443 closed. If this is the case then port 443 has to be opened. Please use 'telnet mailnode 443' and see if you are able to connect.
Port 443 is definitely open.

Quote:
- it is possible that alias and not primary user's email address is used at the time of activation on enterprise activation screen on device - i would check email address used for activation and compare it to the email address listed in the GAL.
The user doesn't have an alias and he is using the same email address in the GAL.

Quote:
- it is possible that user had not been purged when he was re-added in BB manager - i would try to re-add user and make sure that user has been purged.
You're unable to re-add the user if it hasn't been purged so I don't think that's it.

Quote:
- it is possible that BES machine is configured to use proxy server to connect to LAN. If this is the case then i would recommend to configure BES machine to connect without proxy.
No that's not the case either. Sorry!

Quote:
- also in case if none of above suggestions worked then i would need to look into zcb log file with 'BlackBerryAgent' component in the name covering period of time when device was going though the process of activation. Please use the following description on how to get zcb logs ZCB and BES Logs - BlackBerry - Zimbra :: Wiki. Please send zcb logs over to support@zimbra.com or eugene@zimbra.com.
I will email them directly to you Eugene if you don't mind. I'll send you over Aug 20th and today's for the time period the user tried activating.

Last edited by newtobes : 08-24-2009 at 07:49 PM.
Reply With Quote
  #13 (permalink)  
Old 08-28-2009, 01:26 PM
Active Member
 
Posts: 29
Default

We finally got the issue resolved. Even though the user was signed up with the BES plan through their ISP, the ISP did not "refresh" their account so RIM still saw this as a BIS account not BES. When the ISP finally refreshed it, the user was able to activate their device right away. Unfortunately, this required the ticket being escalated to 2nd tier support as 1st level didn't catch this when the user called the first 2-3 times.

Other reasons why this error might occur is if the network message does not reach the inbox - so ensure the message is not being filtered or forwarded to another account. It's also suggested to remove auto signature from the device before activating.
Reply With Quote
Reply


Thread Tools
Display Modes


Similar Threads

Why Join?

Registering let's you ask questions, makes it easier to search, displays any files attached to posts, and notifies you about replies.

Zimbrablog.com




 

Search Engine Optimization by vBSEO 3.1.0