Welcome to Port3101.org : Your BES Connection Mark forums read | View Forum Leaders
Port3101.org : Your BES Connection



Reply
LinkBack (3) Thread Tools Display Modes
KB03322 - Service specific error 5608
 
  3 links from elsewhere to this Post. Click to view. #1 (permalink)  
Old 04-01-2009, 02:46 PM
hdawg's Avatar
Proprietor
 
Join Date: Nov 2008
Posts: 2,257
Blog Entries: 147
Default KB03322 - Service specific error 5608

Environment

  • BlackBerry® Enterprise Server software versions 4.0 to 4.1 for Microsoft® Exchange
  • Microsoft® SQL Server®
  • Windows Server®



Overview

The following error message occurs when starting the BlackBerry Enterprise Server:
Windows could not start the BlackBerry Policy Service on Local Computer. For more information, review the System Event Log. If this is a non-Microsoft service, contact the service vendor, and refer to service-specific error code 5608.



Cause

This issue may be caused by one of the following:
  1. Structured Query Language (SQL) Service is not running.
  2. Named pipes or Transmission Control Protocol/Internet Protocol (TCP/IP) or both are disabled.
  3. The BlackBerry Enterprise Server Management database log file is running out of space.
  4. The account used to install the BlackBerry Enterprise Server software did not have the necessary permissions.
  5. The BlackBerry Enterprise Server service account was not used during installation.
  6. The BlackBerry Enterprise Server configuration is incomplete.
  7. The BlackBerry Configuration Database setup is incomplete or corrupted.
  8. The BlackBerry Enterprise Server service account is using SQL server authentication (SA) to connect to the Microsoft SQL Server database. The password for SA is changed on the Microsoft SQL Server but is not changed on the BlackBerry Server Configuration Panel.



Resolution

Cause 1
The Microsoft SQL Server service used by the BlackBerry Enterprise Server is not running.
Resolution
Start the MSSQLServer service.
Note: The Microsoft SQL Server service will be named MSSQL <server_name> if multiple instances of Microsoft SQL Server are running on the server computer.

Cause 2
One or both of the Named Pipes and TCP/IP protocols are disabled on the Microsoft SQL Server.
Resolution
Turn on Named Pipes and TCP/IP on the Microsoft SQL Server. For information on how to turn on Named Pipes and TCP/IP protocols, go to the Microsoft Knowledge Base and search for "TCP/IP Named Pipes server network libraries".

Cause 3
The log file for the BlackBerry Configuration Database has reached the maximum space limitation and is unable to record any more transactions. The BlackBerry Enterprise Server and Microsoft SQL Server application logs show the following error message:
Event Type: Error

Event Source: BlackBerry Messaging Agent BESNAME Agent 4

Event ID: 10249

Description:

The description for Event ID ( 10249 ) in Source ( BlackBerry Messaging Agent BESNAME Agent 4 ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. The following information is part of the event: PMDatabaseSQLImp::SetAlLStatProps: COM Error 0x80040E14 - IDispatch error #3092 - Source: "Microsoft OLE DB Provider for SQL Server" - Description "The log file for database 'BESMgmt01' is full. Back up the transaction log for the database to free up some log space." - Command "".
Resolution
Back up the BlackBerry Configuration Database and transaction log. This will move transaction log data into a backup file and will free up disk space allocated to the transaction log.
See KB10292 for instructions to back up the BlackBerry Configuration Database. See KB03968 for information about shrinking the database and transaction log to free up disk space.

Cause 4
The account used to install the BlackBerry Enterprise Server does not have the necessary permissions.
Resolution
To resolve this issue, remove and re-install the BlackBerry Enterprise Server software using the correct service account, by completing the following steps:
  1. Create a BlackBerry Enterprise Server service account. For more information, refer to the BlackBerry Enterprise Server Installation Guide.
  2. Remove the BlackBerry Enterprise Server software.
  3. Log on to the computer that will host the BlackBerry Enterprise Server using the service account (BESAdmin).
  4. Re-install the BlackBerry Enterprise Server software.

Cause 5
The BlackBerry Enterprise Server was not installed using a BlackBerry Enterprise Server service account (e.g., BESAdmin).
Resolution
To resolve this issue, copy the Research In Motion registry key to the correct user account.
Warning: The following procedure requires modifying the computer registry, which can cause substantial damage to the Windows® operating system. Document and back up the existing registry entries prior to implementing any changes.
  1. Using the Windows Services administration tool, stop all BlackBerry Enterprise Server services. Log on to the BlackBerry Enterprise Server using the account that was used to install the BlackBerry Enterprise Server software.
  2. Navigate to and create a backup of the following registry key: HKEY_CURRENT_USER\Software\Research In Motion
  3. Restart the BlackBerry Enterprise Server and log on using the correct service account.
  4. Restore the backed up registry key from Step 2.
  5. Create a Messaging Application Programming Interface (MAPI) profile. See the BlackBerry Enterprise Server Installation Guide for detailed instructions on creating a MAPI profile.
  6. Restart the BlackBerry Enterprise Server.
Important: Restarting the BlackBerry Enterprise Server will delay email message delivery to BlackBerry smartphones. For more information, see KB04789.

Cause 6
The BlackBerry Enterprise Server configuration is incomplete.
Resolution
  1. Go to Start > Programs > BlackBerry Enterprise Server > BlackBerry Server Configuration.
  2. Complete the setup, linking the BlackBerry Enterprise Server to the correct Microsoft SQL Server and BlackBerry Configuration Database.
  3. If the setup completes without returning any errors, start the BlackBerry Dispatcher service.
Important: Restarting the BlackBerry Enterprise Server will delay email message delivery to BlackBerry smartphones. For more information, see KB04789.

Cause 7
The BlackBerry Configuration Database setup is incomplete or corrupted, resulting in SQL missing some necessary BlackBerry Enterprise Server error codes.
This could also appear as an executing SQL statements error when upgrading the database or performing a Change Database from the BlackBerry Server Configuration panel.
The db_install log files display lines similar to the following:
[10000] (11/09 14:46:07):{0x8FC} SQL Error Message from CBESDBInstaller::ExecuteSql.executeDirect: SQLSTATE: 42000 Native error: 2758 Message: RAISERROR could not locate entry for error 70000 in sysmessages.

[10000] (11/09 14:46:07):{0x8FC} SQL Error Message from CBESDBInstaller::ExecuteSql.executeDirect: SQLSTATE: 42000 Native error: 2758 Message: RAISERROR could not locate entry for error 70010 in sysmessages.

Resolution
Update the BlackBerry Configuration Database manually to correct the missing information, by completing the following steps:
  1. Place the Database folder from the setup files of the current BlackBerry Enterprise Server version onto the computer hosting the Microsoft SQL Server. If Service Packs have been applied since the initial installation, use the setup files for the most recent Service Pack applied.
  2. From within the Database folder, open BESMgmt.cfg in Notepad or a similar text editor application.
  3. Ensure the line DATABASE_NAME=BESMgmt matches the BlackBerry Configuration Database name.
  4. Do one of the following:
    1. For BlackBerry Enterprise Server version 4.0.x, Change the line CMD=Install to CMD=Migrate
    2. For BlackBerry Enterprise Server version 4.1.x, Change the line CMD=Install to CMD=Upgrade
  5. Save and close the configuration file.
  6. Open a command prompt and navigate to the database folder.
  7. Run the following command:

    createdb besmgmt.cfg
  8. If the setup completes without returning any errors, start the BlackBerry Dispatcher service.
Important: Restarting the BlackBerry Enterprise Server will delay email message delivery to BlackBerry smartphones. For more information, see KB04789.


Cause 8
The BlackBerry Enterprise Server service account is using SQL Server authentication (SA) to connect to the Microsoft SQL Server database. The password for SA is changed on the Microsoft SQL Server but is not changed on the BlackBerry Server Configuration Panel.
Resolution
Change the password for SA on the BlackBerry Server Configuration Panel.
__________________
http://blog.port3101.org/hdawg/
Reply With Quote
Sponsored Links
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is On
Trackbacks are On
Pingbacks are On
Refbacks are On


LinkBacks (?)
LinkBack to this Thread: http://www.port3101.org/featured-blackberry-kb-articles/797-kb03322-service-specific-error-5608-a.html
Posted By For Type Date
View Single Post - Kb03322 - Service Specific Error 5608 Post #0 Refback 04-01-2014 08:10 PM
All posts by jtrumpio This thread Refback 03-24-2011 08:58 PM
The great BlackBerry debacle of 2010 This thread Refback 01-11-2010 03:05 AM

Similar Threads
Thread Thread Starter Forum Replies Last Post
KB04797 - "Service-specific error 5613" when attempting to start the Dispatcher hdawg Featured BlackBerry KB Articles 0 09-20-2009 04:18 PM
KB05036 - Service specific error 5003, 5007 or 5502 when starting the Policy and ... hdawg Featured BlackBerry KB Articles 0 09-15-2009 08:02 PM
KB04049 - Service-specific error code 0 hdawg Featured BlackBerry KB Articles 0 05-26-2009 02:21 PM
KB03321 - Service-specific error 5003 hdawg Featured BlackBerry KB Articles 0 01-28-2009 07:08 PM
KB15991 - Service specific error 5203 when starting BlackBerry Synchronization....... Si Featured BlackBerry KB Articles 0 12-19-2008 12:35 PM


All times are GMT -4. The time now is 11:09 AM.
Powered by vBulletin® Version 3.8.9
Copyright ©2000 - 2019, vBulletin Solutions, Inc.


 

SEO by vBSEO 3.3.2 PL2