Zimbra offers Open Source email server software and shared calendar for Linux and the Mac
Go Back   Zimbra :: Forums > Zimbra Collaboration Suite > Administrators

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 04-23-2011, 09:30 PM
Intermediate Member
 
Posts: 15
Default [SOLVED] Soap Not Enabled

Hi,
My installation is ubuntu/Zimbra7.0. The 80 port is serving and we can login to admin the server or send/receive emails. However, it seems that the soap is not working correctly. When I use browser to visit:
http://mydomain/service/admin/soap/
The response always has something like:
<soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope"><soap:Body><soap:Fault><soap:Code><soap: Value>soap:Receiver</soap:Value></soap:Code><soap:Reason><soap:Text>system failure: Request not allowed on port 80</soap:Text></soap:Reason><soapetail><Error xmlns="urn:zimbra"><Code>service.FAILURE</Code><Trace>com.zimbra.common.service.ServiceExcep tion: system failure: Request not allowed on port 80
ExceptionId:btpool0-3://mydomain/service/admin/soap/:1303619239332:7c57c89c6bf314e2
Code:service.FAILURE
at com.zimbra.common.service.ServiceException.FAILURE (ServiceException.java:248)
at com.zimbra.cs.servlet.ZimbraServlet.service(Zimbra Servlet.java:196)
at javax.servlet.http.HttpServlet.service(HttpServlet .java:814)
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 org.mortbay.jetty.servlet.ServletHandler$CachedCha in.doFilter(ServletHandler.java:1157)
at org.mortbay.servlet.UserAgentFilter.doFilter(UserA gentFilter.java:81)
at org.mortbay.servlet.GzipFilter.doFilter(GzipFilter .java:132)
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.handler.DebugHandler.handle(Debu gHandler.java:77)
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.he aderComplete(HttpConnection.java:929)
at org.mortbay.jetty.HttpParser.parseNext(HttpParser. java:549)
at org.mortbay.jetty.HttpParser.parseAvailable(HttpPa rser.java:212)
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)
</Trace></Error></soapetail></soap:Fault></soap:Body></soap:Envelope>


The following is the output of zmcontrol status:

antispam Running
antivirus Running
ldap Running
logger Running
mailbox Running
mta Running
snmp Running
spell Running
stats Running
zmconfigd Running

Please help me to figure it out. Thanks.
Reply With Quote
  #2 (permalink)  
Old 04-23-2011, 11:06 PM
Zimbra Consultant & Moderator
 
Posts: 20,313
Default

Quote:
Originally Posted by nickzm View Post
My installation is ubuntu/Zimbra7.0. The 80 port is serving and we can login to admin the server or send/receive emails. However, it seems that the soap is not working correctly.
Yes it is.

Quote:
Originally Posted by nickzm View Post
When I use browser to visit:
http://mydomain/service/admin/soap/
You should read the Admin Guide for details of how to log in to the Admin UI.
__________________
Regards


Bill
Reply With Quote
  #3 (permalink)  
Old 04-24-2011, 01:05 AM
Intermediate Member
 
Posts: 15
Default

However, I wrote a standalone java application and try to create an account programmatically, the authentication process can never be done. The following is my code:
Code:
		try {

			SoapHttpTransport trans = null;
	
			trans = new SoapHttpTransport("http://mydomain/service/soap/");
	
			Element req = Element.XMLElement.mFactory.createElement(AccountConstants.AUTH_REQUEST);
			req.addAttribute(AccountConstants.E_ACCOUNT,"admin@mydomain");
			req.addAttribute(AccountConstants.E_PASSWORD,"PASSWORD");
			
			
			Element resp;
			resp = trans.invoke(req);
			
			SoapProvisioning sp = new SoapProvisioning();
			sp.soapSetURI("http://mydomain/service/soap/");
		
				sp.soapAdminAuthenticate("test", "aaaaa");
				Map m=new HashMap();
				m.put("firstName", "firstname");
				m.put("lastName", "lastname");
				sp.createAccount("aa@mydomain", "aaaa", m);
		
		} catch (SoapFaultException e) {
			e.printStackTrace();
		} catch (IOException e) {
			e.printStackTrace();
		}
There will be always a exception in this line:
resp = trans.invoke(req);

Below are the details:
Code:
- local config file `\opt\zimbra\conf\localconfig.xml' is not readable
com.zimbra.common.soap.SoapFaultException: invalid request: missing required element: account
ExceptionId:com.zimbra.common.service.ServiceException: invalid request: missing required element: account
ExceptionId:btpool0-4://mydomain/service/soap/AuthRequest:1303632129543:7c57c89c6bf314e2
Code:service.INVALID_REQUEST
	at com.zimbra.common.service.ServiceException.INVALID_REQUEST(ServiceException.java:255)
	at com.zimbra.common.soap.Element.checkNull(Element.java:302)
	at com.zimbra.common.soap.Element.getElement(Element.java:195)
	at com.zimbra.cs.service.account.Auth.handle(Auth.java:79)
	at com.zimbra.soap.SoapEngine.dispatchRequest(SoapEngine.java:412)
	at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.java:287)
	at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.java:158)
	at com.zimbra.soap.SoapServlet.doWork(SoapServlet.java:294)
	at com.zimbra.soap.SoapServlet.doPost(SoapServlet.java:215)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:725)
	at com.zimbra.cs.servlet.ZimbraServlet.service(ZimbraServlet.java:208)
	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:543)
	at org.mortbay.jetty.HttpConnection$RequestHandler.content(HttpConnection.java:946)
	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:405)
	at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:410)
	at org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:451)
The Zimbra Desktop works pretty well, but the java application does not work.
Reply With Quote
  #4 (permalink)  
Old 04-24-2011, 04:10 AM
Intermediate Member
 
Posts: 15
Default

it is the issue of the client. This thread should be closed.
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.