Zimbra offers Open Source email server software and shared calendar for Linux and the Mac
Go Back   Zimbra :: Forums > Zimbra Desktop > Error Reports

Welcome to the Zimbra :: Forums!
Welcome, if you would like to post a comment please register. We also encourage you to explore all things Zimbra with our team and members of the community.

Reply
 
LinkBack Thread Tools Search this Thread Display Modes
  #51 (permalink)  
Old 08-11-2011, 02:11 AM
Intermediate Member
 
Posts: 16
Default Fixed

ZD 7.1.1 (Build 10917) Resolved it for me. Thanks
Reply With Quote
  #52 (permalink)  
Old 10-14-2011, 07:29 PM
Junior Member
 
Posts: 6
Default Can't sync all Yahoo contacts

I have used both Zimbra desktop version 7.1.1 and now 7.1.2 and neither version syncs all my Yahoo contacts. I have about 1400 contacts in my Yahoo account but only 169 got synced into Zimbra and no more. I am using Windows 7 Home premium 64 bit. When I went to set up to resync everything and reentered my password on the Zimbra 'setup' page I got this error message:

: error when sending req at (step 1) Internal reason: unauthonized error (401) at (step 1) .This error is normally caused by a problem with the OAuth parameters attached to your request. The OAuth signature or OAuth Verifier may be incorrect or one of the tokens is in a bad state
Display error details
com.zimbra.cs.offline.util.yc.oauth.OAuthException : error when sending req at (step 1) Internal reason: unauthonized error (401) at (step 1) .This error is normally caused by a problem with the OAuth parameters attached to your request. The OAuth signature or OAuth Verifier may be incorrect or one of the tokens is in a bad state ExceptionId:btpool0-257:1318648832923:fa91476605d5be06 Code: at com.zimbra.cs.offline.util.yc.oauth.OAuthRequest.s end(OAuthRequest.java:107) at com.zimbra.cs.offline.util.yc.oauth.OAuthManager$O AuthCredential.getAccessURL(OAuthManager.java:152) at com.zimbra.cs.offline.util.yc.oauth.OAuthManager$O AuthCredential.access$700(OAuthManager.java:133) at com.zimbra.cs.offline.util.yc.oauth.OAuthManager.g etAccessTokenURL(OAuthManager.java:110) at com.zimbra.cs.offline.jsp.YmailBean.doRequest(Ymai lBean.java:56) at com.zimbra.cs.offline.jsp.FormBean.doRequest(FormB ean.java:150) at sun.reflect.NativeMethodAccessorImpl.invoke0(Nativ e Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Native MethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(De legatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at com.sun.el.parser.AstFunction.getValue(AstFunction .java:127) at com.sun.el.ValueExpressionImpl.getValue(ValueExpre ssionImpl.java:206) at org.apache.jasper.runtime.PageContextImpl.evaluate Expression(PageContextImpl.java:1001) at org.apache.jsp.desktop.accsetup_jsp._jspx_meth_c_w hen_5(Unknown Source) at org.apache.jsp.desktop.accsetup_jsp._jspx_meth_c_c hoose_0(Unknown Source) at org.apache.jsp.desktop.accsetup_jsp._jspService(Un known Source) at org.apache.jasper.runtime.HttpJspBase.service(Http JspBase.java:109) at javax.servlet.http.HttpServlet.service(HttpServlet .java:814) at org.apache.jasper.servlet.JspServletWrapper.servic e(JspServletWrapper.java:389) at org.apache.jasper.servlet.JspServlet.serviceJspFil e(JspServlet.java:486) at org.apache.jasper.servlet.JspServlet.service(JspSe rvlet.java:380) at javax.servlet.http.HttpServlet.service(HttpServlet .java:814) at com.zimbra.webClient.servlet.JspServlet.service(Js pServlet.java:64) at org.mortbay.jetty.servlet.ServletHolder.handle(Ser vletHolder.java:511) at org.mortbay.jetty.servlet.ServletHandler$CachedCha in.doFilter(ServletHandler.java:1166) at com.zimbra.cs.servlet.SetHeaderFilter.doFilter(Set HeaderFilter.java:79) at com.zimbra.webClient.filters.SetHeaderFilter.doFil ter(SetHeaderFilter.java:239) at org.mortbay.jetty.servlet.ServletHandler$CachedCha in.doFilter(ServletHandler.java:1157) at org.mortbay.jetty.servlet.ServletHandler.handle(Se rvletHandler.java:388) at org.mortbay.jetty.security.SecurityHandler.handle( SecurityHandler.java:218) at org.mortbay.jetty.servlet.SessionHandler.handle(Se ssionHandler.java:182) at org.mortbay.jetty.handler.ContextHandler.handle(Co ntextHandler.java:765) at org.mortbay.jetty.webapp.WebAppContext.handle(WebA ppContext.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(Ha ndlerWrapper.java:152) at org.mortbay.jetty.handler.rewrite.RewriteHandler.h andle(RewriteHandler.java:230) at org.mortbay.jetty.handler.HandlerWrapper.handle(Ha ndlerWrapper.java:152) at org.mortbay.jetty.Server.handle(Server.java:326) at org.mortbay.jetty.HttpConnection.handleRequest(Htt pConnection.java:543) at org.mortbay.jetty.HttpConnection$RequestHandler.co ntent(HttpConnection.java:946) at org.mortbay.jetty.HttpParser.parseNext(HttpParser. java:756) at org.mortbay.jetty.HttpParser.parseAvailable(HttpPa rser.java:218) at org.mortbay.jetty.HttpConnection.handle(HttpConnec tion.java:405) at org.mortbay.io.nio.SelectChannelEndPoint.run(Selec tChannelEndPoint.java:410) at org.mortbay.thread.BoundedThreadPool$PoolThread.ru n(BoundedThreadPool.java:451) Caused by: com.zimbra.cs.offline.util.yc.oauth.OAuthException : unauthonized error (401) at (step 1) .This error is normally caused by a problem with the OAuth parameters attached to your request. The OAuth signature or OAuth Verifier may be incorrect or one of the tokens is in a bad state ExceptionId:btpool0-257:1318648832921:fa91476605d5be06 Codeauth.Unauthorized at com.zimbra.cs.offline.util.yc.oauth.OAuthException .UNAUTHORIZED(OAuthException.java:44) at com.zimbra.cs.offline.util.yc.oauth.OAuthException .handle(OAuthException.java:71) at com.zimbra.cs.offline.util.yc.oauth.OAuthRequest.s end(OAuthRequest.java:95) ... 45 more

Any clue what might be wrong?

Thanks

Matt
Reply With Quote
  #53 (permalink)  
Old 11-06-2011, 12:55 AM
Zimbra Employee
 
Posts: 119
Default

Are you still getting this error ? Yahoo Contact sync needs OAuth for authorization, that's why ZD needs you to input a verify code from yahoo. From your error msg, it seems the authorization process failed at the beginning. I don't know why you can still get some contacts, maybe those are the ones you kept from older version of ZD (when yahoo contacts sync was not broken)?
Reply With Quote
  #54 (permalink)  
Old 11-08-2011, 10:34 AM
Junior Member
 
Posts: 6
Default

Yes, I am still getting this error. When I press "validate and save" and am not even asked for the verify code from Yahoo. I just get this error message that I posted previously immediately. I am not sure when I was able to sync that first set of 169 contacts. Maybe with version 7.1 but I have never used any other previous version.

And NOW I can not even download any of my emails at all. When I press "sync" I get the message that I am off line even though I am not -- but that could be because I am using a super slow internet connection.
Reply With Quote
  #55 (permalink)  
Old 11-08-2011, 10:49 AM
Zimbra Employee
 
Posts: 119
Default

This sounds more like a network related problem rather than yahoo contact sync problem.
Reply With Quote
  #56 (permalink)  
Old 11-09-2011, 06:18 AM
Junior Member
 
Posts: 6
Default

I am moving around a lot but even when I had a very fast connection I could not sync yahoo contacts. It is only now with a slow connection that I also can no longer sync any yahoo email at all. Thanks
Reply With Quote
  #57 (permalink)  
Old 11-09-2011, 09:55 AM
Zimbra Employee
 
Posts: 119
Default

Could you try a newer version ? If you choose to sync contact, there should be no UI for verify code at first, only after you "validate and sync", the UI will appear.
Reply With Quote
  #58 (permalink)  
Old 11-10-2011, 05:16 AM
Junior Member
 
Posts: 6
Default

Sorry my last post about my version number was not exactly correct. I believe I do currently have the most recent version: "Zimbra Desktop 7.1.2 (build 10978)". Another interesting note about my current problem is that I can now SEND emails from zimbra perfectly fine but I can not receive them any longer. In 7.1.1 the problem was the reverse.

Thanks
Reply With Quote
Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes


Similar Threads

Why Join?

Registering let's you ask questions, makes it easier to search, displays any files attached to posts, and notifies you about replies.

blog.zimbra.com




 

SEO by vBSEO ©2011, Crawlability, Inc.