Bionic: Unable to Remote Wipe

Take your Zimbra with you!
Post Reply
Jordack
Posts: 34
Joined: Sat Sep 13, 2014 2:15 am

Bionic: Unable to Remote Wipe

Post by Jordack »

New install:

zimbra-mta-7.1.3_GA_3346.RHEL6_64-20110928134515.x86_64

Fully Licensed (but never received my Support Portal Login)
Device:

Moto-DRIOD Bionic/5.5.1

Andriod Version = 2.3.4

Build 5.5.1_84
(Have ensure the device id fully updated.)
Q1) Can not get the device to remote wipe. Any thought on where to start on troubleshooting this one.
When I send the remote wipe the phone just says "Connection Error" I had similar issues with the bionic and Novell Data Sync Server. Those where resolved by enabling mobile policy, but that doesn't seem to fix it with Zimbra.
I know Zimbra has their own little client however I would like the devices to work without requiring the users to install anything special.
I have tried different settings in CoS and none seem to work.
Q2) is there a CLI reference guide for the Zimbra Mobile I am unable to disable the require encryption from the Web GUI. (No CheckBox to uncheck)
Q3) Does Zimbra Mobile have a restriction on the downloaded attachment size? Novell Data Sync did and we had to adjust that.
Jordack
Posts: 34
Joined: Sat Sep 13, 2014 2:15 am

Bionic: Unable to Remote Wipe

Post by Jordack »

Updated:
This will give you all the settings in the mobile policy. The encryption seems to only be addressable from CLI.
/opt/zimbra/bin/zmprov gc CoS| grep -i mobilepol
To disable the Encryption requirement.

zmprov mc CoS zimbraMobilePolicyDeviceEncryptionEnabled FALSE
Found the sync.log and this is what i get:

2011-12-14 16:17:14,102 INFO [btpool0-26://pluto.domain.com/Microsoft-Server-ActiveSync?Cmd=Provision&User=bbunny&DeviceId=Moto99000054321234&DeviceType=MotoDROIDBIONIC551] [name=bbunny@domain.org;mid=6;Cmd=Provision;DeviceID=Moto99000054321234;Version=12.0;] sync - HTTP/1.1 500 Unexpected server error

2011-12-14 16:17:24,616 INFO [btpool0-26://pluto.domain.com/Microsoft-Server-ActiveSync?Cmd=Sync&User=bbunny&DeviceId=Moto99000054321234&DeviceType=MotoDROIDBIONIC551] [] sync - POST Microsoft-Server-ActiveSync?Cmd=Sync&User=bbunny&DeviceId=Moto99000054321234&DeviceType=MotoDROIDBIONIC551

2011-12-14 16:17:24,616 INFO [btpool0-26://pluto.domain.com/Microsoft-Server-ActiveSync?Cmd=Sync&User=bbunny&DeviceId=Moto99000054321234&DeviceType=MotoDROIDBIONIC551] [] sync - DeviceID=Moto99000054321234; DeviceType=MotoDROIDBIONIC551; UA=Moto-DROID BIONIC/5.5.1; Protocol=12.0; PolicyKey=423670219

2011-12-14 16:17:24,617 INFO [btpool0-26://pluto.domain.com/Microsoft-Server-ActiveSync?Cmd=Sync&User=bbunny&DeviceId=Moto99000054321234&DeviceType=MotoDROIDBIONIC551] [name=bbunny@domain.org;mid=6;Cmd=Sync;DeviceID=Moto99000054321234;Version=12.0;] sync - HTTP/1.1 449 Retry after sending a PROVISION command

2011-12-14 16:17:25,233 INFO [btpool0-26://pluto.domain.com/Microsoft-Server-ActiveSync?Cmd=Provision&User=bbunny&DeviceId=Moto99000054321234&DeviceType=MotoDROIDBIONIC551] [] sync - POST Microsoft-Server-ActiveSync?Cmd=Provision&User=bbunny&DeviceId=Moto99000054321234&DeviceType=MotoDROIDBIONIC551

2011-12-14 16:17:25,233 INFO [btpool0-26://pluto.domain.com/Microsoft-Server-ActiveSync?Cmd=Provision&User=bbunny&DeviceId=Moto99000054321234&DeviceType=MotoDROIDBIONIC551] [] sync - DeviceID=Moto99000054321234; DeviceType=MotoDROIDBIONIC551; UA=Moto-DROID BIONIC/5.5.1; Protocol=12.0; PolicyKey=null

2011-12-14 16:17:25,236 INFO [btpool0-26://pluto.domain.com/Microsoft-Server-ActiveSync?Cmd=Provision&User=bbunny&DeviceId=Moto99000054321234&DeviceType=MotoDROIDBIONIC551] [name=bbunny@domain.org;mid=6;Cmd=Provision;DeviceID=Moto99000054321234;Version=12.0;] sync - Response size 128 bytes

2011-12-14 16:17:25,236 INFO [btpool0-26://pluto.domain.com/Microsoft-Server-ActiveSync?Cmd=Provision&User=bbunny&DeviceId=Moto99000054321234&DeviceType=MotoDROIDBIONIC551] [name=bbunny@domain.org;mid=6;Cmd=Provision;DeviceID=Moto99000054321234;Version=12.0;] sync - HTTP/1.1 200 OK

2011-12-14 16:17:25,773 INFO [btpool0-26://pluto.domain.com/Microsoft-Server-ActiveSync?Cmd=Provision&User=bbunny&DeviceId=Moto99000054321234&DeviceType=MotoDROIDBIONIC551] [] sync - POST Microsoft-Server-ActiveSync?Cmd=Provision&User=bbunny&DeviceId=Moto99000054321234&DeviceType=MotoDROIDBIONIC551

2011-12-14 16:17:25,774 INFO [btpool0-26://pluto.domain.com/Microsoft-Server-ActiveSync?Cmd=Provision&User=bbunny&DeviceId=Moto99000054321234&DeviceType=MotoDROIDBIONIC551] [] sync - DeviceID=Moto99000054321234; DeviceType=MotoDROIDBIONIC551; UA=Moto-DROID BIONIC/5.5.1; Protocol=12.0; PolicyKey=null

2011-12-14 16:17:25,775 WARN [btpool0-26://pluto.domain.com/Microsoft-Server-ActiveSync?Cmd=Provision&User=bbunny&DeviceId=Moto99000054321234&DeviceType=MotoDROIDBIONIC551] [name=bbunny@domain.org;mid=6;Cmd=Provision;DeviceID=Moto99000054321234;Version=12.0;] sync - Unexpected server error

java.lang.NullPointerException

at com.zimbra.zimbrasync.commands.Provision.process(Provision.java:70)

at com.zimbra.zimbrasync.ZimbraSyncServlet.processCommand(ZimbraSyncServlet.java:549)

at com.zimbra.zimbrasync.ZimbraSyncServlet.processPostRequest(ZimbraSyncServlet.java:456)

at com.zimbra.zimbrasync.ZimbraSyncServlet.doPost(ZimbraSyncServlet.java:329)

at com.zimbra.zimbrasync.ZimbraSync$HttpHandler.doPost(ZimbraSync.java:55)

at com.zimbra.cs.extension.ExtensionDispatcherServlet.service(ExtensionDispatcherServlet.java:99)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:814)

at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:511)

at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1166)

at com.zimbra.cs.servlet.SetHeaderFilter.doFilter(SetHeaderFilter.java:79)

at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157)

at org.mortbay.servlet.UserAgentFilter.doFilter(UserAgentFilter.java:81)

at org.mortbay.servlet.GzipFilter.doFilter(GzipFilter.java:155)

at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157)

at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:388)

at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:218)

at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:182)

at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:765)

at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:422)

at org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:230)

at org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:114)

at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)

at org.mortbay.jetty.handler.rewrite.RewriteHandler.handle(RewriteHandler.java:230)

at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)

at org.mortbay.jetty.handler.DebugHandler.handle(DebugHandler.java:77)

at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)

at org.mortbay.jetty.Server.handle(Server.java:326)

at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:583)

at org.mortbay.jetty.HttpConnection$RequestHandler.content(HttpConnection.java:986)

at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:756)

at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:218)

at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:414)

at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:429)

at org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:451)

2011-12-14 16:17:25,776 INFO [btpool0-26://pluto.domain.com/Microsoft-Server-ActiveSync?Cmd=Provision&User=bbunny&DeviceId=Moto99000054321234&DeviceType=MotoDROIDBIONIC551] [name=bbunny@domain.org;mid=6;Cmd=Provision;DeviceID=Moto99000054321234;Version=12.0;] sync - HTTP/1.1 500 Unexpected server error
How do I get the Mobile Server to wipe the Bionic?
dywang
Advanced member
Advanced member
Posts: 118
Joined: Sat Sep 13, 2014 1:47 am

Bionic: Unable to Remote Wipe

Post by dywang »

We have a bug to track this. Bug 69499 – NPE initiating Remote Wipe of Bionic devices
It should be a device issue.
Post Reply