Everything appears to be configured correctly. Was able to confirm ODBC is working, and updated ejabberd.yml to use odbc, but getting the following
Problem 'error {try_clause,{selected,["password"],[]}}' occurred executing the command.
Stacktrace: [{ejabberd_auth_odbc,is_user_exists,2,
[{file,"src/ejabberd_auth_odbc.erl"},
{line,210}]},
{ejabberd_auth,'-is_user_exists/2-fun-1-',3,
[{file,"src/ejabberd_auth.erl"},{line,311}]},
{lists,any,2,[{file,"lists.erl"},{line,1210}]},
{ejabberd_auth,try_register,3,
[{file,"src/ejabberd_auth.erl"},{line,185}]},
{ejabberd_admin,register,3,
[{file,"src/ejabberd_admin.erl"},{line,329}]},
{ejabberd_ctl,call_command,3,
[{file,"src/ejabberd_ctl.erl"},{line,293}]},
{ejabberd_ctl,try_call_command,3,
[{file,"src/ejabberd_ctl.erl"},{line,269}]},
{ejabberd_ctl,process2,3,
[{file,"src/ejabberd_ctl.erl"},{line,218}]}]
When I run
ejabberdctl register admin1 localhost password
Has anybody had any success running against MSSQL?
I'm having the exact same
I'm having the exact same issue but using odbc with postgreql. Inside the brackets after the password the error message even shows the correct password fetch from the database. Does anyone have any news on this?
What ejabberd version are you
What ejabberd version are you using, and what exact log lines do you get?
I came back to say I solved
I came back to say I solved the problem, but I'm glad someone has answered my previous question.
I was using ejabberd 14.07-4+deb8u3 (version on debian jessie). The log lines were exactly the same as the one above in the first post. After searching through the forum, I ended on one comment on another topíc suggesting that old versions of ejabberd had some issues and after not being able to solve his problem, updating ejabberd solved it (https://www.ejabberd.im/node/23217). So I tried it and installed ejabberd 16.03-1~bpo8+1 (from jessie backports) with the same config files and the problem simply vanished. I think this kind of makes sense since the problem I was having was crash on erlang level on an ejabberd core class. I'm also pretty sure the problem is database agnostic.
I hope this may help someone else in the future.