Welcome!

Welcome to the official BlackBerry Support Community Forums.

This is your resource to discuss support topics with your peers, and learn from each other.

Reply
Contributor
Posts: 22
Registered: ‎08-23-2010
My Device: 2e2 Shared
My Carrier: 2e2 Shared

Issues during upgrading 5.0.3 to 5.0.4 - A/P config

Hi guys, We have two BES servers: 1 on each site. BES01 and BES02. - These servers are in an Active/Passive configuration. The BlackBerry Router component are installed on two servers in the DMZ. BR01 and BR02. In the middle of the upgrade, we have come to an issue: We have upgraded the passive BES Server (BES02) from v5.0.3 to v5.0.4. All the services remained active on BES01 during the upgrade and emails were being sent and received on the BB devices. At this point, only one BES node is on version 5.0.4 whereas the active node and both Router servers (in the DMZ) are on v5.0.3. After the first node upgrade, we did a manual failover to the 'Passive' node (BES02) to make it active. At this point, no emails were sent or received between BB devices. Some messages were getting failures. After noticing the outage, we failed back to BES01 and email service returned. Any idea what we have missed out here and why our BB devices cannot send/receive emails when the BES02 node which is on v5.0.4 is active? what should we be looking at in the logs? on the BES and Router servers? thanks in advance.
2e2 Shared
Retired
Posts: 166
Registered: ‎04-25-2013
My Device: BlackBerry Z10, BlackBerry Q10, Bold 9900

Re: Issues during upgrading 5.0.3 to 5.0.4 - A/P config

Hello jay247,

Thank you for your question regarding Upgrading issues to SP4.

 

What kind of errors are you seeing in the MAGT logs after you failover?

Let me know if you have any other questions.

- LW

 

Come follow your BlackBerry Technical Team on twitter! @BlackBerryHelp

Be sure to click Kudos! for those who have helped you.

Click Accept as Solution for posts that have solved your issue(s)!

Contributor
Posts: 22
Registered: ‎08-23-2010
My Device: 2e2 Shared
My Carrier: 2e2 Shared

Re: Issues during upgrading 5.0.3 to 5.0.4 - A/P config

Hi LW,

 

Thanks for your reply.

 

On the upgraded server (passive), MAGT logs are no longer being created since the upgrade took place.

 

These, below are extracted from 2 logs on the upgraded server:


 

 

[30000] (07/08 12:28:29.451):{0xFDC} [ENV] Failed to read 001e6602 reg value from the BlackBerry MAPI profile.
[30000] (07/08 12:28:29.451):{0xFDC} [ENV] BlackBerry Mailbox Agent 2 - BESX Version 5.0.4.17
[30000] (07/08 12:28:29.451):{0xFDC} [ENV] BES Service Name: BlackBerry Mailbox Agent
[30000] (07/08 12:28:29.451):{0xFDC} [ENV] BlackBerry Dispatcher: D:\Research In Motion\BlackBerry Enterprise Server\BlackBerryDispatcher.exe, Version: 5.0.4.11
[30000] (07/08 12:28:29.451):{0xFDC} [ENV] BlackBerry User Administration Service: NOT FOUND
[30000] (07/08 12:28:29.451):{0xFDC} [ENV] BlackBerry MDS Connection Service: D:\Research In Motion\BlackBerry Enterprise Server\MDS\bin\bmds.exe, Version: 5.0.5.15
[30000] (07/08 12:28:29.451):{0xFDC} [ENV] BlackBerry Database Consistency Service: NOT FOUND
[30000] (07/08 12:28:29.451):{0xFDC} [ENV] BlackBerry Policy Service: D:\Research In Motion\BlackBerry Enterprise Server\BlackBerryPolicyServer.exe, Version: 5.0.4.7
[30000] (07/08 12:28:29.451):{0xFDC} [ENV] BlackBerry Synchronization Service: D:\Research In Motion\BlackBerry Enterprise Server\SyncServer\BlackBerrySyncServer.exe, Version: 5.0.4.7
[30000] (07/08 12:28:29.451):{0xFDC} [ENV] BlackBerry Router: D:\Research In Motion\BlackBerry Enterprise Server\BypassRouter\BlackberryRouter.exe, Version: 5.0.4.11
[30000] (07/08 12:28:29.498):{0xFDC} [ENV] BlackBerry Controller: D:\Research In Motion\BlackBerry Enterprise Server\BlackBerryController.exe, Version: 5.0.4.17
[30000] (07/08 12:28:29.498):{0xFDC} [ENV] BlackBerry Alert: D:\Research In Motion\BlackBerry Enterprise Server\BESAlert.exe, Version: 5.0.4.15
[30000] (07/08 12:28:29.498):{0xFDC} [ENV] BlackBerry Attachment Service is installed remotely on
[35015] (07/08 12:28:29.498):{0xFDC} [ENV] Total number of requests for connections:  99
[35014] (07/08 12:28:29.498):{0xFDC} [ENV] Number of waits for connections since service was started:  0
[35019] (07/08 12:28:29.514):{0xFDC} [ENV] [DB] Database Schema Version:  5.0.4 <5.0.2012.08.09>
[30000] (07/08 12:28:29.514):{0xFDC} [ENV] [DB] Connection String = Server=SQLserver01\SQLInstance01;Database=BESMgmt;Network=dbmssocn;Trusted_Connection=Yes
[30000] (07/08 12:28:29.514):{0xFDC} [ENV] [DB] DBMS Name = Microsoft SQL Server;  DBMS Version = 09.00.4053;  Provider Name = sqlncli.dll;  Provider Friendly Name = Microsoft SQL Native Client;  OLE DB Version = 02.80;  Provider Version = 9.00.3042.00;  Failover Partner = SQLserver01\SQLInstance01
[30480] (07/08 12:28:29.514):{0xFDC} [CFG] BES failover mode is ACTIVE
[41120] (07/08 12:28:29.514):{0xFDC} [CFG] Address Lookup is enabled
[41122] (07/08 12:28:29.514):{0xFDC} [CFG] LDAP search is enabled, LDAP PIM search is disabled, LDAP ALP search is disabled
[35035] (07/08 12:28:29.529):{0xFDC} LDAP: Create 0x002d0a44
[30460] (07/08 12:28:29.592):{0xFDC} [CFG] LDAP Info: Host Name = DC01.Domain.LOCAL
[41123] (07/08 12:28:29.592):{0xFDC} [CFG] Using up to 10 external CDO Helpers in keep-alive mode
[41124] (07/08 12:28:29.592):{0xFDC} [CFG] AddOwnerApptID is disabled
[41125] (07/08 12:28:29.592):{0xFDC} [CFG] SetLocaleIDs is disabled
[30302] (07/08 12:28:29.592):{0xFDC} [CFG] OTAFM hard-delete server support is disabled, rescans are 0x00
[40532] (07/08 12:28:29.592):{0xFDC} [CFG] vCard conversion support has been enabled
[40892] (07/08 12:28:29.592):{0xFDC} [CFG] GlobalRescan config: messagingSmiley Surprised, calendarSmiley Surprised, pimSmiley Surprised
[41126] (07/08 12:28:29.592):{0xFDC} [CFG] EnableExceptionStackTrace is disabled
[40000] (07/08 12:28:29.592):{0xFDC} [CFG] MAPI Encoding is 1
[10277] (07/08 12:28:29.592):{0xFDC} BlackBerry Messaging Agent BESServerV503 Agent 2 failed to start. Error code 5305
[50106] (07/08 12:28:29.623):{0xFDC} Stopping BlackBerry Mailbox Agent 2 for Server BESServerV503
[30000] (07/08 12:28:29.623):{0x1950} [DIAG] EVENT=Register_thread, THREADID=0x1950, THREADNAME="TimerThread"
[40000] (07/08 12:28:29.623):{0x1950} [DEBUG] EVENTMSG="TimerThread thread started"
[40507] (07/08 12:28:29.810):{0x1514} ExtUDPLogThread: Code on closing = 0
[30000] (07/08 12:28:29.810):{0x1514} [DIAG] EVENT=Unregister_thread, THREADID=0x1514, THREADNAME="ExtUDPLogThread"
[35035] (07/08 12:28:29.842):{0xFDC} LDAP: Delete 0x002d0a44
[30065] (07/08 12:28:29.857):{0xFDC} BlackBerry Mailbox Agent 2 for Server BESServerV503 shutdown complete

 

 


 

Seperate MAGT Log on upgraded server:

 

[30053] (07/08 13:35:55.473):{0xDE4} Retry start for user: /o=Domain/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=Joe Bloggs
[30437] (07/08 13:35:55.473):{0xDE4} Starting handheld in STANDBY MODE for Joe Bloggs
[40704] (07/08 13:35:55.473):{0xDE4} MAPIMailbox::MAPIMailbox ServerDN=/o=Domain/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=EX_CAS_01.Domain.local/cn=Microsoft Private MDB, MailboxDN=/o=Domain/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=Joe Bloggs
[30033] (07/08 13:35:55.488):{0xDE4} ResolveName - g_pAddressBook->ResolveName( /o=Domain/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=Joe Bloggs ) (0x8004010f) failed
[30337] (07/08 13:35:55.488):{0xDE4} MAPIMailbox::MAPIMailbox - ResolveName[1] failed for Mailbox DN='/o=Domain/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=Joe Bloggs', trying method #2
[40739] (07/08 13:35:55.488):{0xDE4} MAPIMailbox::MAPIMailbox - ResolveName[2] success for SMTPAddress='j.bloggs@Company.com'
[40472] (07/08 13:35:57.189):{0xDE4} LDAP: Unable to resolve the address for user /o=Domain/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=Joe Bloggs using LDAP
[20400] (07/08 13:35:57.189):{0xDE4} {j.bloggs@Company.com} MAPIMailbox::MAPIMailbox - OpenMsgStore (0x8004011d) failed, MailboxDN=/o=Domain/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=Joe Bloggs, ServerDN=/o=Domain/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=EX_CAS_01.Domain.local/cn=Microsoft Private MDB
[40720] (07/08 13:35:57.189):{0xDE4} MAPI call failed. Error 'The information store could not be opened.', LowLevelError 0, Component 'MAPI 1.0', Context 649

 

 

 

2e2 Shared
Contributor
Posts: 22
Registered: ‎08-23-2010
My Device: 2e2 Shared
My Carrier: 2e2 Shared

Re: Issues during upgrading 5.0.3 to 5.0.4 - A/P config

In the High Availability Summary in the BES Web Console, we also see the following status:

 

Supported Dispatcher instance names Description Server name Availability state Failover status
 Active_503_Server_1 Active_503_ServerPrimaryRunning - Primary 
 Active_503_Server_2 Passive_504_ServerStandbyUnknown
2e2 Shared
Guru III
Posts: 31,674
Registered: ‎06-25-2008
My Device:

I'm rockin the BlackBerry Passport, Z30, Z10, Q10, BlackBerry Mini Stereo Speaker, 64 gig PlayBook, BlackBerry Wireless Headset HS-700

My Carrier: I am on AT&T. Please edit your Personal Profile with your DEVICE TYPE, DEVICE OS and Carrier

Re: Issues during upgrading 5.0.3 to 5.0.4 - A/P config

i would recreate the MAPI profile

http://www.blackberry.com/btsc/KB10285

 




Click here to Backup the data on your BlackBerry Device! It's important, and FREE!


Click "Accept as Solution" if your problem is solved. To give thanks, click thumbs up
Click to search the Knowledge Base at BTSC and click to Read The Fabulous Manuals

BESAdmin's, please make a signature with your BES environment info.


SIM Free BlackBerry Unlocking FAQ
Follow me on Twitter @knottyrope


Want to thank me? Buy my KnottyRope App here


BES 12 and BES 5.0.4 with Exchange 2010 and SQL 2012 Hyper V


Contributor
Posts: 22
Registered: ‎08-23-2010
My Device: 2e2 Shared
My Carrier: 2e2 Shared

Re: Issues during upgrading 5.0.3 to 5.0.4 - A/P config

Hi Knotty,

 

The MAPI Profile's been recreated.

 

Still no emails routing when failed over to 5.0.4.

thanks

 

2e2 Shared
Retired
Posts: 166
Registered: ‎04-25-2013
My Device: BlackBerry Z10, BlackBerry Q10, Bold 9900

Re: Issues during upgrading 5.0.3 to 5.0.4 - A/P config

Hello jay247,

BES 5.0.4 uses LDAP by default. It might be a good idea to disable it and switch back to MAPI for lookups. 

 

Disable the LDAPSearch on the BlackBerry Enterprise Server.

 

1. On the computer that hosts the BlackBerry Enterprise Server, click Start > Run

2. Type regedit and click OK. If a User Account Control dialog appears, click Yes to continue.

3. Navigate to the appropriate location:

32-bit: HKEY_LOCAL_MACHINE\Software\Research In Motion\BlackBerry Enterprise Server\Agents
64-bit: HKEY_LOCAL_MACHINE\Software\WOW6432Node\Research In Motion\BlackBerry Enterprise Server\Agents

 

4. Right-click on the Agents key in the left-hand pane and select Export

5. Save the exported key in an accessible location in case it is needed for reference or rollback

6. Set the contents of the LDAPSearch value to 0

 

Note: After modifying the above key, a restart of the BlackBerry Controller and BlackBerry MailStore services will be required for changes to take effect


Let me know if you have any other questions.

- LW

 

Come follow your BlackBerry Technical Team on twitter! @BlackBerryHelp

Be sure to click Kudos! for those who have helped you.

Click Accept as Solution for posts that have solved your issue(s)!