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.

inside custom component

BlackBerry® Enterprise Service 10

Reply
Contributor
Posts: 11
Registered: ‎05-24-2012
My Device: Bold 9900
My Carrier: Vodafone

Re: BES 5.0.4 & BAS-NCC.exe Application Error & Administration Service - Native Code Container service terminating

Ours also seems to be fixed. The problem in our case was that the database (one box internal SQL express)  was set to dynamic port mapping rather than being fixed to a port. Not sure why this wasn't an issue until we upgraded.

Highlighted
Guru III
Posts: 32,190
Registered: ‎06-25-2008
My Device:

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

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

Re: BES 5.0.4 & BAS-NCC.exe Application Error & Administration Service - Native Code Container service terminating


ederkley wrote:
Ahh thankyou! That looks like it was the problem. Redefining the proxy exceptions seems to have stopped the crashing. Weird we never had this problem in 5.0.3 and haven't changed the proxy exception list in many months.


glad it helped

 




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


Forums Advisor III
Posts: 1,481
Registered: ‎08-29-2008
My Device: Blackberry Classic
My Carrier: Swisscom

Re: BES 5.0.4 & BAS-NCC.exe Application Error & Administration Service - Native Code Container service terminating

[ Edited ]

I have got that solved as well.

 

As we need a rather complex proxy exception string, the solution was to use wpad.dat instead of the explicit proxy setting.

 

So we created the wpad.dat and the wpad DNS entry. Then, in Internet Explorer on the BES server, we removed the proxy setting and ticked "Automatically detect settings" (which searches and reads the wpad.dat for proxy settings).

 

To have BAS also use the wpad settings, we used option IV of the following KB:

 

http://btsc.webapps.blackberry.com/btsc/viewContent.do?externalId=KB25252&sliceId=1

 

  1. On the computer that hosts the BlackBerry Administration Service, at the command prompt, navigate to the folder that contains the Traittool.exe file (eg: C:\Research In Motion\BlackBerry Enterprise Server 5.0.3\Tools ).
  2. Type the following: TraitTool.exe -global -trait BASIsProxyWPADOptionEnabled -set 1.

After that the BAS-NCC.exe service works normally and the device.xml and vendor.xml are retrieved successfully at 10 minutes past each hour.

 

New Contributor
Posts: 2
Registered: ‎01-31-2013
My Device: Bold 9790
My Carrier: Telekom, Germany

Re: BES 5.0.4 & BAS-NCC.exe Application Error & Administration Service - Native Code Container service terminating

Hi, we also have the problem on our BES 5.0.4 Express server (IBM Lotus Domino 8.5.x).

Can you define more in detail what do you mean with "Redefining the proxy exceptions". First I cannot get, what you mean with that.

 

Thanks

New Contributor
Posts: 8
Registered: ‎11-28-2010
My Device: Not Specified

Re: BES 5.0.4 & BAS-NCC.exe Application Error & Administration Service - Native Code Container service terminating

@meckes2000

 

"Redefining the proxy exceptions" meant simplifying down the number of servers that should be directly accessed rather than going via the proxy, from about 10 entries to 4.  For instance, instead of individual IP addresses in a few subnets we just changed it to 192.168.1.0-192.168.64.255 and instead of various server's FQDNs in our local domain we just put *.[local domain name]

The goal was to reduce the number of characters used to describe the servers and domains that would be directly accessed.  I think it would have been over 200 characters to describe these entries before and now it's about 90 characters.

In our case, this was done on the Forefront TMG Server under "Configure Web Proxy" Web Browser tab and editing the entries under "Directly access these servers or domains".

 

Hope this helps.