ejabberd - Comments for "Ejabberd in Windows - getting started"

I've temporary changed the

sander — Tue, 27 Jun 2006 18:15:42 +0000

I've temporary updated the download URL so that it directly points to a working Erlang binary.

--
sander

RE: ejabberd-1.1.1-windows built with Erlang R10B

vlayton — Mon, 26 Jun 2006 20:19:04 +0000

Thank you so much, fseesink! This did fix the problem. I had actually downloaded Erlang R10B based off of http://www.ejabberd.im/node/854, but I neglected to uninstall Erlang R11B and change where ejabberd looked for Erlang, so I still ran into the same problem. If anyone out there is as computer ignorant as I am, it is going to be easier to uninstall everything you just downloaded (including ejabberd) and start over, making sure that this time you download Erlang R10B-10 instead of the latest version, unless they fix ejabberd 1.1.1 to work with the latest Erlang.

I hope this helps future users. :)

ejabberd-1.1.1-windows built with Erlang R10B

fseesink — Mon, 26 Jun 2006 16:04:45 +0000

This issue seems to keep coming up. For example:

http://www.ejabberd.im/node/852
http://www.ejabberd.im/node/854

I'm going to guess that you're running ejabberd under Windows 2K/XP, and that more than likely you downloaded/installed Erlang R11B-0 and ejabber 1.1.1 using their binary installers.

The issue is that the current Windows binary of ejabberd--still ejabberd-1.1.1-windows (released 2006-04-28) as I write this--was built with Erlang R10-B it seems. The error message

...
** Reason for termination ==
** {badarg,[{erlang,binary_to_term...
...

is the tipoff it seems.

Anyway, your solution for now, especially if you're on Windows, is to either uninstall Erlang R11B-0 and install R10B-10, or to download the source code for ejabberd and compile it with R11B-0. The former is your best bet if you're not inclined to compile your own code; the latter if you are. At least until the Windows binary installer of ejabberd is recompiled using Erlang R11B.

Hope this helps.