BAS-NCC process crashes at ten minutes past the hour

Article ID: KB28190

Type: Support Content

Last Modified: 01-22-2013


Product(s) Affected:

  • BES5
  • BlackBerry Enterprise Server 5.0 SP3
  • DT 1990442

At ten minutes past the hour, the BAS-NCC service fails, starts back up and fails again, and then starts up successfully. This occurs every hour. The following will be found in the BAS-NCC log:

(08/16 18:10:06:083):{WorkerThread#0[]} [com.rim.bes.bas.windowsaccess.windowshttpaccessor.WindowsHTTPAccessorImpl] [TRACE] [BBAS-100] {u=SystemUser, t=9} Exit JWinHTTP::JWinHTTP
(08/16 18:10:06:083):{WorkerThread#0[]} [com.rim.bes.bas.windowsaccess.windowshttpaccessor.WindowsHTTPAccessorImpl] [TRACE] [BBAS-100] {u=SystemUser, t=9} Enter JWinHTTP::getResultFile
(08/16 18:10:06:083):{WorkerThread#0[]} [com.rim.bes.bas.windowsaccess.windowshttpaccessor.WindowsHTTPAccessorImpl] [DEBUG] [BBAS-200] {u=SystemUser, t=9} [JWinHTTP::getResultFile], [Attempting WinHTTPConnect with the host [], port [443] using the default proxy]
(08/16 18:10:06:083):{WorkerThread#0[]} [com.rim.bes.bas.windowsaccess.windowshttpaccessor.WindowsHTTPAccessorImpl] [DEBUG] [BBAS-200] {u=SystemUser, t=9} [JWinHTTP::getResultFile], [Successfully connected. Now attempting WinHttpOpenRequest [GET] to the URL [/Desktop/Download/XML/Vendor.xml] using the default proxy]
(08/16 18:10:06:145):{WorkerThread#0[]} [com.rim.bes.bas.windowsaccess.windowshttpaccessor.WindowsHTTPAccessorImpl] [DEBUG] [BBAS-200] {u=SystemUser, t=9} [JWinHTTP::getResultFile], [WinHttpSendRequest ignoring SSL cert issues..]
(08/16 18:10:27:208):{WorkerThread#0[]} [com.rim.bes.bas.windowsaccess.windowshttpaccessor.WindowsHTTPAccessorImpl] [DEBUG] [BBAS-200] {u=SystemUser, t=9} [JWinHTTP::getResultFile], [WinHttpSendRequest no results found, error [12029]. Going to attempt to use a proxy]
(08/16 18:10:27:208):{WorkerThread#0[]} [com.rim.bes.bas.windowsaccess.windowshttpaccessor.WindowsHTTPAccessorImpl] [TRACE] [BBAS-100] {u=SystemUser, t=9} Enter JWinHTTP::SetupProxy
(08/16 18:10:27:208):{WorkerThread#0[]} [com.rim.bes.bas.windowsaccess.windowshttpaccessor.WindowsHTTPAccessorImpl] [DEBUG] [BBAS-200] {u=SystemUser, t=9} [JWinHTTP::SetupProxy], [WinHttpGetDefaultProxyConfiguration could not find default proxy, error [0]. Going to attempt next method to detect a proxy..]


If an environment has been configured with proxy exceptions through Internet Options (Control Panel > Internet Options > Connections > Lan Settings > Proxy Server) where the proxy exception string exceeds 250 characters, the BAS-NCC service will fail as a result at ten minutes past the hour, which is the scheduled time for BAS to check for updates to Device.xml and Vendor.xml.

This can also be checked via Registry Editor on the BlackBerry Enterprise Server:

  1. Click Start.
  2. Click Run.
  3. Type regedit.
  4. Click OK to open the Registry Editor.
  5. Go to HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Internet Settings

NOTE: Ensure to be logged on to the BlackBerry Enterprise Server as the BlackBerry service account when performing the steps above. If logged on as a different account change the path in Step 5 to:

HKEY_USERS\<SID_of_ServiceAccount>\Software\Microsoft\Windows\CurrentVersion\Internet Settings

Once in this registry key look for the following strings:

  • ProxyServer
  • ProxyOverride

ProxyServer will contain the name of any proxy server assigned. 

ProxyOverride contains proxy exceptions. If this string contains more than 250 characters, the issue described in this article will apply.

This is a previously reported issue that is being investigated by our development team. A resolution is currently unavailable.
Remove the proxy exceptions, or reduce the size of the list of exceptions to below 250 characters.


By downloading, accessing or otherwise using the Knowledge Base documents you agree:

   (a) that the terms of use for the documents found at apply to your use or reference to these documents; and

   (b) not to copy, distribute, disclose or reproduce, in full or in part any of the documents without the express written consent of RIM.

Visit the BlackBerry Technical Solution Center at