KB15805 - BlackBerry Dispatcher fails to start with error 5061
KB15805 - BlackBerry Dispatcher fails to start with error 5061
Environment
- BlackBerry® Enterprise Server software version 4.0 and later for IBM® Lotus® Domino®
- BlackBerry® Enterprise Server software version 4.0 and later for Microsoft® Exchange
- BlackBerry® Enterprise Server software version 4.0 and later for Novell® GroupWise®
- Microsoft® SQL Server®
- Microsoft® SQL Server® Desktop Engine (MSDE)
Overview
The BlackBerry Dispatcher fails to start and returns an error 5061 when an administrator attempts to start it manually on the Windows® Services console.
The BlackBerry Messaging Agent (MAGT) log file may show lines similar to the following:
[30058] (03/03 09:10:29):{0x1E5C} Starting Database
[40000] (03/03 09:10:29):{0x2E74} [DIAG] EVENT=Register_thread, THREADID=0x2E74, THREADNAME="ExtUDPLogThread"
[50049] (03/03 09:10:29):{0x2E74} Waiting for external UDP log messages on port 4094
[30000] (03/03 09:10:29):{0x1E5C} ADO ConnectionTimeout value = 384s
[50000] (03/03 09:10:29):{0x2E74} Controller: This BES Agent is under control of BlackBerry Agent Controller
[40000] (03/03 09:10:44):{0x1E5C} ConnectionPool: Created pool of 5 connections
[30442] (03/03 09:11:44):{0x1E5C} [PMDatabaseSQLImp::GetUserList] Timeout or deadlock. 4 re-tries left. [ SELECT a.DisplayName, a.MailboxDN, a.ServerDN, a.DeviceType, a.PIN, a.RedirectionState, a.ExtServicesState, a.CalendarEnableState, a.CreationTime, a.OverrideSMTPAddr, a.OTAFMState, a.OTAFMConflictResolution, a.OTAPIMState, a.lurnum, a.MailboxSMTPAddr, a.ServerConfigId, a.PendingServerConfigId, a.PendingKey, a.CurrentKey, a.PreviousKey, a.OTAFMUserConfig, a.ITPolicy2Id, a.Id, a.DeviceCapabilities, a.KeyDate, a.DataSourceId, a.ServiceBookName, a.AckData, a.ActivationTime, a.RoutingInfo, a.UserDeleteStatus, a.PendingRoutingInfo, a.KeyGenPassword, a.KeyGenExpiryTime, a.AutoSignature, a.RedirectWhenInCradle, a.DisableSentItems, a.AutoKeyGenerate, a.DefaultFilterAction, a.Filters, b.LastSentTime, b.LastFwdTime, b.LastXPAction, b.MsgsSent, b.MsgsForwarded, b.MsgsPending, b.MsgsFailed, b.MsgsExpired, b.MsgsFiltered, b.LastMsgExpired, b.Status, b.UserConfigId, b.Id FROM UserConfig a, UserSta
[30442] (03/03 09:12:31):{0x1E5C} [PMDatabaseSQLImp::GetUserList] Timeout or deadlock. 3 re-tries left. [ SELECT a.DisplayName, a.MailboxDN, a.ServerDN, a.DeviceType, a.PIN, a.RedirectionState, a.ExtServicesState, a.CalendarEnableState, a.CreationTime, a.OverrideSMTPAddr, a.OTAFMState, a.OTAFMConflictResolution, a.OTAPIMState, a.lurnum, a.MailboxSMTPAddr, a.ServerConfigId, a.PendingServerConfigId, a.PendingKey, a.CurrentKey, a.PreviousKey, a.OTAFMUserConfig, a.ITPolicy2Id, a.Id, a.DeviceCapabilities, a.KeyDate, a.DataSourceId, a.ServiceBookName, a.AckData, a.ActivationTime, a.RoutingInfo, a.UserDeleteStatus, a.PendingRoutingInfo, a.KeyGenPassword, a.KeyGenExpiryTime, a.AutoSignature, a.RedirectWhenInCradle, a.DisableSentItems, a.AutoKeyGenerate, a.DefaultFilterAction, a.Filters, b.LastSentTime, b.LastFwdTime, b.LastXPAction, b.MsgsSent, b.MsgsForwarded, b.MsgsPending, b.MsgsFailed, b.MsgsExpired, b.MsgsFiltered, b.LastMsgExpired, b.Status, b.UserConfigId, b.Id FROM UserConfig a, UserSta
[30442] (03/03 09:13:05):{0x1E5C} [PMDatabaseSQLImp::GetUserList] Timeout or deadlock. 2 re-tries left. [ SELECT a.DisplayName, a.MailboxDN, a.ServerDN, a.DeviceType, a.PIN, a.RedirectionState, a.ExtServicesState, a.CalendarEnableState, a.CreationTime, a.OverrideSMTPAddr, a.OTAFMState, a.OTAFMConflictResolution, a.OTAPIMState, a.lurnum, a.MailboxSMTPAddr, a.ServerConfigId, a.PendingServerConfigId, a.PendingKey, a.CurrentKey, a.PreviousKey, a.OTAFMUserConfig, a.ITPolicy2Id, a.Id, a.DeviceCapabilities, a.KeyDate, a.DataSourceId, a.ServiceBookName, a.AckData, a.ActivationTime, a.RoutingInfo, a.UserDeleteStatus, a.PendingRoutingInfo, a.KeyGenPassword, a.KeyGenExpiryTime, a.AutoSignature, a.RedirectWhenInCradle, a.DisableSentItems, a.AutoKeyGenerate, a.DefaultFilterAction, a.Filters, b.LastSentTime, b.LastFwdTime, b.LastXPAction, b.MsgsSent, b.MsgsForwarded, b.MsgsPending, b.MsgsFailed, b.MsgsExpired, b.MsgsFiltered, b.LastMsgExpired, b.Status, b.UserConfigId, b.Id FROM UserConfig a, UserSta
[30442] (03/03 09:13:44):{0x1E5C} [PMDatabaseSQLImp::GetUserList] Timeout or deadlock. 1 re-try left. [ SELECT a.DisplayName, a.MailboxDN, a.ServerDN, a.DeviceType, a.PIN, a.RedirectionState, a.ExtServicesState, a.CalendarEnableState, a.CreationTime, a.OverrideSMTPAddr, a.OTAFMState, a.OTAFMConflictResolution, a.OTAPIMState, a.lurnum, a.MailboxSMTPAddr, a.ServerConfigId, a.PendingServerConfigId, a.PendingKey, a.CurrentKey, a.PreviousKey, a.OTAFMUserConfig, a.ITPolicy2Id, a.Id, a.DeviceCapabilities, a.KeyDate, a.DataSourceId, a.ServiceBookName, a.AckData, a.ActivationTime, a.RoutingInfo, a.UserDeleteStatus, a.PendingRoutingInfo, a.KeyGenPassword, a.KeyGenExpiryTime, a.AutoSignature, a.RedirectWhenInCradle, a.DisableSentItems, a.AutoKeyGenerate, a.DefaultFilterAction, a.Filters, b.LastSentTime, b.LastFwdTime, b.LastXPAction, b.MsgsSent, b.MsgsForwarded, b.MsgsPending, b.MsgsFailed, b.MsgsExpired, b.MsgsFiltered, b.LastMsgExpired, b.Status, b.UserConfigId, b.Id FROM UserConfig a, UserStats
[10249] (03/03 09:14:30):{0x1E5C} PMDatabaseSQLImp::GetUserList: COM Error 0x80040E31 - IDispatch error #3121 - Source: "Microsoft OLE DB Provider for SQL Server" - Description "Timeout expired" - Command "(null)"
[20284] (03/03 09:14:30):{0x1E5C} OpenDB: Populate list of pagers failed.
[10031] (03/03 09:14:30):{0x1E5C} Open() failed
[50004] (03/03 09:14:30):{0x1E5C} Stopping BlackBerry
Cause
The BlackBerry® Enterprise Server is querying the BlackBerry Configuration Database for startup data and is not receiving timely responses from the database server. The result is a database timeout or deadlock.
Resolution
To prevent a database timeout or deadlock that affects the BlackBerry Enterprise Server, complete the following steps:
- Make sure that unnecessary BlackBerry Enterprise Server services are not started. For example, duplicate BlackBerry Enterprise Server services set for disaster recovery on separate computers. These duplicate BlackBerry Enterprise Server services may cause an increased load and decrease performance on the database server.
- Review the Microsoft SQL Server or MSDE for blocked store procedure IDs (SPIDs) using the following Structured Query Language (SQL) query:
SELECT * FROM SYSPROCESSES.
- If there are blocked SPIDs, consult Microsoft for the most efficient course of action.
- If multiple BlackBerry Enterprise Server instances are affected, stagger the startup of the BlackBerry Enterprise Server instances to minimize the load put on the database server.
- In large environments, consider increasing database performance by using a regional model for the BlackBerry Configuration Database. This minimizes the number of BlackBerry Enterprise Server instances that connect to a single BlackBerry Configuration Database.
Additional Information
Contact Microsoft support for the most efficient performance analysis for a Microsoft SQL Server or MSDE database.
Review the Database Connections in BlackBerry Enterprise Server Version 4.1 document located at the following link:
Livelink - Redirection
__________________
http://blog.port3101.org/hdawg/
The views expressed by me on Port3101 and its affiliated sites are my own and do not necessarily reflect the views of my employer.
|
Linear Mode
