Zimbra Forums

Hi all,

When I first installed the zimbra server, I disabled the chat as I wasn't planning on using it. Wanted to go back and have a play now, but i'm getting errors.

I have re-enabled the zimlet and done a full restart, also updated the chat module via apt. When logging in I get the following error:

Unknown command sent to server: ZxChatRequest
method: [unknown]
msg: unknown document: ZxChatRequest
code: service.UNKNOWN_DOCUMENT
detail: soap:Sender
trace: qtp66233253-253:1546779083371:7e849baa566204d2
request:
<soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope ... r><context xmlns="urn:zimbra"><userAgent name="ZimbraWebClient - GC71 (Win)" version="8.8.11_GA_3737"/><session id="18"/><account by="name">my@email.address</account><format type="js"/><csrfToken>0_26e3996e0d6589740a097625485c4b529bf5ce26</csrfToken></context></soap:Header><soap:Body><ZxChatRequest xmlns="urn:zimbraAccount"><type>16</type><clientVersion>11</clientVersion><action>register_session</action></ZxChatRequest></soap:Body></soap:Envelope>

Any help would be appreciated... (I'm guessing it's something i've forgot to re-enable)

I solved following the steps reported here: viewtopic.php?t=63184
yum remove zimbra-chat
yum install zimbra-chat
redeployed the zimlet
zmcontrol restart

I'm still have this error even after reinstall zimbra-chat, redeployed the zimlet, clear cache and restart zimbra.

Same error here after upgrading to 8.8.15 patch 5!!!

Same error. Fresh server install. CentOS 7.7.1908 and Zimbra version="8.8.15_GA_3890"

The same problem. After installing 8.8.15 patch 5.
As far as I understand this feature (or bug?) has not yet been solved....
Will we waiting for patch 6+ ?
Any ideas?

Hi,
I just have this error after updating the Zimbradrive.
I undeployed then redeployed it without success.
Is it removed from the OSE version 8.8.15?

I have just updated Zimbra 8.7.11 to 8.8.15 on Ubuntu 14.04 and have the same error.

I have tried uninstalling and reinstalling zimbra-chat, redeploying the zimlet etc.

same issue with the new patch

same issue after upgrade from 8.8.15 p4 to 8.8.15 p5