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
New Contributor
DominikGR
Posts: 6
Registered: ‎05-13-2013
My Device: Z10 & 9900
My Carrier: vodafone.de

Z10 has no BDS10 connection in "Work" WIFI mode

Hi,
in our environment i setup a fresh BDS10 Server internally and a BDS Router in the DMZ.
The activation of Z10 devices, the sync of emails and receiving of policies are OK if i'm connected to the mobile network connection and the BB infrastructure.

Now on the Z10 Device:
I switch ON the internal "work" WIFI and switch OFF the mobile network connection.
The syncronisation of emails is also OK but i can't get any policy change on the Z10 devices any longer, (WIFI symbol is light white, no BB Symbol visible)

Seems there is no connection between the Z10 and the BDS10 (Enterprise Management Web Service) in Work-WIFI.

- A ping from the Z10 to the BDS10 Server is successfull.
- The "About - Category - Blackberry Balance - Network Connections" tells me: Personal=WIFI , Work=WIFI


any suggestions ?

By the way :
I setup a manual proxy profile with exclusions for internal addresses
This profile is used by the BDS component

Please use plain text.
Forums Advisor I
freakinvibe
Posts: 637
Registered: ‎08-29-2008
My Device: Q10
My Carrier: Swisscom

Re: Z10 has no BDS10 connection in "Work" WIFI mode

On my Z10 the "About - Category - Blackberry Balance - Network Connections" says: Personal = Wi-Fi, Work = Blackberry Mobile Data Service (MDS).

Check if you have set all the policies correctly on BES.
Please use plain text.
New Contributor
DominikGR
Posts: 6
Registered: ‎05-13-2013
My Device: Z10 & 9900
My Carrier: vodafone.de

Re: Z10 has no BDS10 connection in "Work" WIFI mode

[ Edited ]

Hi,
I checked my policy more than one time and play arround with these settings.
The only setting which will have influence for my matter is
"Network Access Control for Work Apps" i guess.

It's set to "No" (default)

 

I understand:


- "No" allows Z10 to connect to the BDS using (internal) WIFI. So here the Z10 should connect to the EMWS component ?!!?


- "Yes" will force Z10 to connect to "Mobile Network and RIM infrastructure" only. Direct connection using (internal) WIFI is disabled

Are there other settings i have to look for ?

 

regards

Dominik

Please use plain text.
Forums Advisor I
freakinvibe
Posts: 637
Registered: ‎08-29-2008
My Device: Q10
My Carrier: Swisscom

Re: Z10 has no BDS10 connection in "Work" WIFI mode

The easiest would be if you could assign the Default policy ( = policy with no settings ) to a test user. You should then be able to connect Work apps via WiFi. If this test works, you can selectively switch on policies to see which one prevents the work Wifi connection.
Please use plain text.
New Contributor
DominikGR
Posts: 6
Registered: ‎05-13-2013
My Device: Z10 & 9900
My Carrier: vodafone.de

Re: Z10 has no BDS10 connection in "Work" WIFI mode

Yep.. i did it this morning ... no success to push a IT-policy using "Work WIFI" only.

I wondering about two things:


1. The Z10 is connected to my "Work WIFI". I'm able to send a ping to the BDS Server in "Work WIFI" mode. The WIFI symbol on the Z10 is light white but there is no Blackberry Symbol displayed as in the Mobile Connection mode.
Should a Blackberry Symbol also displayed using the "Work WIFI" / EMWS connection ?

2. If my Z10 is connected to the "Work WIFI" the communication will be established using the BlackBerry Enterprise Management Web Service (EMWS) component. (right ?)
- The EMWS Windows Service is running,
- The EMWS instant status in the BAS console displays also a running state
but when i look into the EMWS error log on the BDS Server an error is displayed.
Maybe this could be the problem. But I have no idea how to debug and to fix this.

May 15, 2013 10:45:58 AM org.apache.catalina.core.StandardContext start
SEVERE: Error filterStart
May 15, 2013 10:45:58 AM org.apache.catalina.core.StandardContext start
SEVERE: Context [] startup failed due to previous errors

 

 

 

 

 

_____________________________________________________________
Complete EMWS_err.log

EMWSTomcatStartup.init begin
May 15, 2013 10:45:54 AM org.apache.catalina.core.AprLifecycleListener init
INFO: The APR based Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: C:\Program Files (x86)\Research In Motion\BlackBerry Device Service\EMWS\bin;
May 15, 2013 10:45:54 AM org.apache.tomcat.util.net.NioSelectorPool getSharedSelector
INFO: Using a shared selector for servlet write/read
May 15, 2013 10:45:54 AM org.apache.coyote.http11.Http11NioProtocol init
INFO: Initializing Coyote HTTP/1.1 on http-8081
May 15, 2013 10:45:55 AM org.apache.tomcat.util.net.NioSelectorPool getSharedSelector
INFO: Using a shared selector for servlet write/read
May 15, 2013 10:45:55 AM org.apache.coyote.http11.Http11NioProtocol init
INFO: Initializing Coyote HTTP/1.1 on http-8444
May 15, 2013 10:45:55 AM org.apache.catalina.startup.Catalina load
INFO: Initialization processed in 1479 ms
May 15, 2013 10:45:55 AM org.apache.catalina.core.StandardService start
INFO: Starting service Catalina
May 15, 2013 10:45:55 AM org.apache.catalina.core.StandardEngine start
INFO: Starting Servlet Engine: Apache Tomcat/6.0.32
May 15, 2013 10:45:55 AM org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deploying web application directory mdm
May 15, 2013 10:45:58 AM org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deploying web application directory ROOT
May 15, 2013 10:45:58 AM org.apache.catalina.core.StandardContext start
SEVERE: Error filterStart
May 15, 2013 10:45:58 AM org.apache.catalina.core.StandardContext start
SEVERE: Context [] startup failed due to previous errors
May 15, 2013 10:45:58 AM org.apache.coyote.http11.Http11NioProtocol start
INFO: Starting Coyote HTTP/1.1 on http-8081
May 15, 2013 10:45:58 AM org.apache.coyote.http11.Http11NioProtocol start
INFO: Starting Coyote HTTP/1.1 on http-8444
May 15, 2013 10:45:58 AM org.apache.jk.common.ChannelSocket init
INFO: JK: ajp13 listening on /0.0.0.0:8009
May 15, 2013 10:45:58 AM org.apache.jk.server.JkMain start
INFO: Jk running ID=0 time=0/40  config=null
May 15, 2013 10:45:58 AM org.apache.catalina.startup.Catalina start
INFO: Server startup in 3485 ms

Please use plain text.