Error 5302
fail to start and generate "error 5302" on BlackBerry Enterprise Server Article Number:000037373 First Published:August 26, 2015 Last Modified:August 26, 2015 Type:Support Environment BlackBerry Enterprise Server for error no recuperable 5302 Microsoft ExchangeBlackBerry Professional Software for Microsoft Exchange Back to top ↑ memoread 0 unrecoverable error 5302 Overview When the BlackBerry Dispatcher, BlackBerry Policy Service, and BlackBerry Synchronization Service are started on the BlackBerry unrecoverable error 5305 conventional memory exhausted Enterprise Server, the following error message is displayed: Service failed to start, generating error 5302 The BlackBerry Enterprise Server debug log displays the following lines: [3] (03/07 unrecoverable error 5304 conventional memory exhausted 12:03:25):{0x31} *** MAPI ***MailboxManager::SubsystemInitialize - AdminServices (0x80070057 [4] (03/07 12:03:25):{0x31} *** MAPI ***MailboxManager::SubsystemInitialize - Prompting for MAPI [2] (03/07 12:03:25):{0x31} *** MAPI ***MailboxManager::SubsystemInitialize - MAPILogonEx (0x80040102) Back to top ↑ Cause This issue may be caused by one of the following:Cause 1:The BlackBerry Enterprise Server is trying to access a Messaging Application Programming Interface (MAPI) profile that does not exist. Cause 2:The PDF Vulnerability patch has been applied following the application of Maintenance Release 5. Back to top ↑ Resolution Resolution for Cause 1:Warning: The following procedure involves modifying the computer registry. This can cause substantial damage to the Windows® operating system. Document and back up the registry entries prior to implementing any changes.Point the BlackBerry Enterprise Server service to an existing MAPI profile by completing the following the steps: Log in to the BlackBerry Enterprise Server using the BlackBerry Enterprise Server administration account (for example, BESAdmin).Open the Registry Editor by clicking Start > Run, type regedit and click OK.Locate the MAPIProfile registry entry in one of the following locations: For BlackBerry Enterprise Server software version 2.1 and earlier, go to HKEY_CURRENT_USER\Software\Research In Motion\BlackBerryFor BlackBerry Enterprise Server software versions 3.5 and 3.6, go to HKEY_CURRENT_USER\Software\Research In Motion\BlackBerry Enterprise Server\Servers\
von GoogleAnmeldenAusgeblendete FelderNach Gruppen oder Nachrichten suchen
to corruption of the VM (Virtual Memory) system by bad memory chips or conflicting software drivers. The error message could be interpreted as "the table (index) that manages blocks of http://www.ghservices.com/gregh/clipper/ie52f.htm virtual memory has gone bad". Investigations are ongoing. Action: Try using: SET CLIPPER=//BADCACHE 5211 SWAPFILE creation error The virtual memory (VM) subsystem is unable to create a swap file on disk. See Also: Error 5311, "The Runtime Environment" chapter of the Programming and Utilities Guide. 5302 Conventional memory exhausted This is an "out of memory" message that indicates that the CA-Clipper application no longer has sufficient conventional unrecoverable error memory (below 640K) available to continue. Specifically, this error occurs when the virtual memory system attempts and fails to bring a VM segment into conventional memory that had been swapped out to disk or expanded memory. Action: Make more conventional memory available to the VM system. This can be done in several ways: 1) Increase the amount of conventional memory available before running the application -- remove TSRs, conventional memory exhausted make use of 386 memory manager, etc. 2) Use a third-party linker that can dynamically overlay C and assembly-language code. C and ASM are not automatically overlaid by RTlink and therefore sit in conventional memory throughout the execution of the application. 3) Ensure that any C or ASM code in use is making use of the virtual memory system if it is doing dynamic memory allocation. Any memory allocated using the Fixed Memory Allocator functions _xalloc() and _xgrab() reduces the amount of conventional memory available if it is not immediately freed. See Also: "VM API" chapter of the Technical Reference Guide. 5304 Conventional Memory Exhausted This is an "out of memory" message that indicates that the CA-Clipper application no longer has sufficient conventional memory available to continue. Specifically, this error occurs when a function attempts to allocate conventional memory and fails. This error can be received as a result of the failure of _xgrab() in Extend System functions. Action: See action for 5302. 5305 VM Swap Space Exhausted There is insufficient room in the VM swap area in real memory to load virtualized data. This only occurs in the undocumented internal function _vmTwo(). The CA-Clipper runtime issues calls to the _vmTwo() function when