ejabberd - Comments for "ejabberd 2.1.0 - HTTP-Bind, LDAPS, PubSub 1.12, STUN, Ping, Roster Versioning"

Problem not yet solved in Windows

mfoss — Mon, 28 Dec 2009 15:54:52 +0000

The problem is that the ejabberd 2.1.0 and 2.1.1 Windows installers don't include the *.dll binary files of the exmpp-0.9.2 library, because those are not yet easy to compile in Windows.

I've created this ticket to remember the problem: Include exmpp *.dll files in the Windows ejabberd installer

Alternative solution

mfoss — Mon, 16 Nov 2009 23:47:36 +0000

I don't know what's the problem. I'll investigate.

In your case, you can try to copy the database directory (with the files acl.DCD, acl.DCL, ...) from the 2.1.0-rc1 installation directory to the new 2.1.0 installation directory. You probably also want to copy ejabberd.cfg. Then start the new ejabberd and you will see you have again the users, rooms...

XEP-0227

f095 — Sun, 15 Nov 2009 11:13:45 +0000

I'm exporting data from ejabberd 2.1.0 RC1, but I can't import them to ejabberd 2.1.0 :(

C:\>ejabberdctl import_piefxis 20091115-112949.xml
Problem 'error badarg' occurred executing the command.
Stacktrace: [{ets,member,[exmpp_xml_engines_registry,expat]},
{exmpp_xml,is_engine_available,1},
{exmpp_xml,get_engine_from_options,1},
{exmpp_xml,start_parser,1},
{ejabberd_piefxis,import_file,2},
{ejabberd_ctl,call_command,3},
{ejabberd_ctl,try_call_command,3},
{ejabberd_ctl,process2,3}]