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
  #1 (permalink)  
Old 03-24-2010, 12:08 PM
Junior Member
 
Posts: 9
Default Clicking Setup in main window gives error

I'm running Zimbra Desktop 2.0 Beta 1. I have created around 15 accounts. Now when I click on Setup in the main window, I get the following error (see below). How can I edit my acccount settings now?!


HTTP ERROR 500

Problem accessing /zimbra/. Reason:

com.zimbra.common.soap.SoapFaultException: system failure: java.lang.NullPointerException
ExceptionId:com.zimbra.common.service.ServiceExcep tion: system failure: java.lang.NullPointerException
ExceptionId:btpool0-11:1269453997880:0c056726f38916df
Code:service.FAILURE
at com.zimbra.common.service.ServiceException.FAILURE (ServiceException.java:248)
at com.zimbra.soap.SoapServlet.doWork(SoapServlet.jav a:308)
at com.zimbra.soap.SoapServlet.doPost(SoapServlet.jav a:212)
at javax.servlet.http.HttpServlet.service(HttpServlet .java:727)
at com.zimbra.cs.servlet.ZimbraServlet.service(Zimbra Servlet.java:181)
at javax.servlet.http.HttpServlet.service(HttpServlet .java:820)
at org.mortbay.jetty.servlet.ServletHolder.handle(Ser vletHolder.java:511)
at org.mortbay.jetty.servlet.ServletHandler.handle(Se rvletHandler.java:390)
at org.mortbay.jetty.security.SecurityHandler.handle( SecurityHandler.java:216)
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:418)
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:939)
at org.mortbay.jetty.HttpParser.parseNext(HttpParser. java:755)
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:409)
at org.mortbay.thread.BoundedThreadPool$PoolThread.ru n(BoundedThreadPool.java:451)
Caused by: java.lang.NullPointerException
at com.zimbra.cs.account.offline.OfflineProvisioning. isZcsAccount(OfflineProvisioning.java:583)
at com.zimbra.cs.account.offline.OfflineProvisioning. getProxyAuthToken(OfflineProvisioning.java:2393)
at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.jav a:229)
at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.jav a:157)
at com.zimbra.soap.SoapServlet.doWork(SoapServlet.jav a:291)
... 23 more

Code:service.FAILURE
Reply With Quote
  #2 (permalink)  
Old 03-27-2010, 01:25 PM
Junior Member
 
Posts: 9
Default

Any solution?
Reply With Quote
  #3 (permalink)  
Old 04-09-2010, 10:28 AM
Junior Member
 
Posts: 9
Default

Just downloaded Zimbra 2 beta 2, and the problem is still there. I CANNOT OPEN THE ACCOUNT SETUP WINDOW. I get the error below. I think maybe there is a problem with having a few too many accounts for the window to handle?


HTTP ERROR 500

Problem accessing /zimbra/. Reason:

com.zimbra.common.soap.SoapFaultException: no valid authtoken present
ExceptionId:com.zimbra.common.service.ServiceExcep tion: no valid authtoken present
ExceptionId:btpool0-4:1270830336101:4b2aac1113a94074
Code:service.AUTH_REQUIRED
at com.zimbra.common.service.ServiceException.AUTH_RE QUIRED(ServiceException.java:292)
at com.zimbra.cs.service.admin.AdminAccessControl.get AdminAccessControl(AdminAccessControl.java:102)
at com.zimbra.soap.SoapEngine.dispatchRequest(SoapEng ine.java:347)
at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.jav a:273)
at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.jav a:157)
at com.zimbra.soap.SoapServlet.doWork(SoapServlet.jav a:291)
at com.zimbra.soap.SoapServlet.doPost(SoapServlet.jav a:212)
at javax.servlet.http.HttpServlet.service(HttpServlet .java:727)
at com.zimbra.cs.servlet.ZimbraServlet.service(Zimbra Servlet.java:182)
at javax.servlet.http.HttpServlet.service(HttpServlet .java:820)
at org.mortbay.jetty.servlet.ServletHolder.handle(Ser vletHolder.java:511)
at org.mortbay.jetty.servlet.ServletHandler.handle(Se rvletHandler.java:390)
at org.mortbay.jetty.security.SecurityHandler.handle( SecurityHandler.java:216)
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:418)
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:939)
at org.mortbay.jetty.HttpParser.parseNext(HttpParser. java:755)
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:409)
at org.mortbay.thread.BoundedThreadPool$PoolThread.ru n(BoundedThreadPool.java:451)

Code:service.AUTH_REQUIRED
Reply With Quote
  #4 (permalink)  
Old 04-09-2010, 11:45 PM
Zimbra Consultant & Moderator
 
Posts: 19,655
Default

Quote:
Originally Posted by MattD123 View Post
I think maybe there is a problem with having a few too many accounts for the window to handle?
How many accounts do you think are a 'few too many'? Is this an upgrade or a new install, which operating system, any anti-virus software running?
__________________
Regards


Bill
Reply With Quote
  #5 (permalink)  
Old 04-11-2010, 06:28 AM
Junior Member
 
Posts: 9
Default

Thanks for your reply.

Have the same problem on both Windows Xp and Vista (seperate machines). Running Commodo firewall and Avast antivrius.

Uninstalled Zimbra Desktop 1.0 on both machines before installing 2.0 beta 1 (and now beta 2) (so fresh install - added email accounts from scratch for 2.0).

Just tried disabling both my firewall and antivirus - but problem is still there.

Happened after adding 10 to 15 accounts via the setup window after the install. Now cannot open the Setup page - gives the error above. Been running Zimbra Desktop 1.0 fine with more accounts than this - never had this problem prior to installing 2.0.
Reply With Quote
  #6 (permalink)  
Old 04-16-2010, 02:12 PM
Junior Member
 
Posts: 9
Default

Is there any support here at all? I am still waiting a solution to the above bug. I'm radiply losing confidence with trying Zimbra products if when I give you feedback I don't get any assistance / response.
Reply With Quote
  #7 (permalink)  
Old 06-21-2010, 06:50 AM
Intermediate Member
 
Posts: 20
Default Similar problem

HTTP ERROR 500

Problem accessing /zimbra/. Reason:

com.zimbra.common.soap.SoapFaultException: no valid authtoken present
ExceptionId:com.zimbra.common.service.ServiceExcep tion: no valid authtoken present
ExceptionId:btpool0-1833:1277117639731:946652d5d28c6b28
Code:service.AUTH_REQUIRED


I see this if I try to go to setup.

I have probably 6 accounts. ssl is enabled on the server. NE version.
Reply With Quote
  #8 (permalink)  
Old 07-14-2010, 11:55 AM
Junior Member
 
Posts: 9
Default

It's like talking to a brick wall itsn't it? I or my collegues will not use Zimbra Desktop until this bug is fixed. Notice Zimbra now haven't even updated their product portal for the next release of Desktop - doesn't fill us with any confidence as to when this product will be stable and usable. Shame as our initial impressions of the product were positive, but support is extremely poor.
Reply With Quote
  #9 (permalink)  
Old 08-23-2010, 10:35 AM
Intermediate Member
 
Posts: 20
Default

I still have this problem.

I uninstalled then re-installed the latest beta (beta4).

It seems that uninstalling didn't remove the settings, because it remembers the mail accounts. So when I use setup, the error screen appears again.

I assume the settings source is corrupt in some way.

Where are the settings stored - How can I do a clean install?
Reply With Quote
  #10 (permalink)  
Old 08-23-2010, 01:20 PM
Zimbra Employee
 
Posts: 96
Default

Settings storage varies depending on platform, and in some cases can be changed during installation. I have listed the defaults below. Before you uninstall and delete, can you attach the files in the log directory? This might give us some additional information about the error you are experiencing.

Mac: ~/Library/Zimbra Desktop

Linux: ~/zdesktop

Windows XP: C:\Documents and Settings\<user>\Local Settings\Application Data\Zimbra\Zimbra Desktop

Windows 7/Vista: C:\Users\<user>\AppData\Local\Zimbra\Zimbra Desktop
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.