I have installed version 1.0.0 of ejabberd running under Windows server and it is working fine. Now I am trying to authenicate against MS SQL and am having a lot of trouble getting it to work. I have read through posts and have downloaded the mssql.zip but I still cannot get the server to work off SQL.
Has anyone been able to get it work and would you be willing to share your experience and ncessary steps?
Thank you,
Michael
Re: Getting ejabberd working with MS SQL on Windows
Now I am trying to authenicate against MS SQL and am having a lot of trouble getting it to work. I have read through posts and have downloaded the mssql.zip but I still cannot get the server to work off SQL.
Has anyone been able to get it work and would you be willing to share your experience and ncessary steps?
I have no experience with MS SQL, so I only can recommend you trying next things:
Working Somewhat
Ok, I now have it authenicating and creating users against the SQL DB. However I am unable to add a contact or modify my vcard info.
I will continue plugging away but if anyone has any idea's I would appreciate any help I can get.
Mike
ejabberd/odbc error text
=ERROR REPORT==== 1-Feb-2006::15:50:05 ===
E(<0.287.0>:gen_iq_handler:67): {{case_clause,
{error,
"[Microsoft][ODBC SQL Server Driver][S
L Server]Invalid column name 'vcard'. SQLSTATE IS: 42S22"}},
[{mod_vcard_odbc,process_sm_iq,3},
{gen_iq_handler,process_iq,6},
{gen_iq_handler,queue_loop,3},
{proc_lib,init_p,5}]}
ODBC VCard Mod - MS SQL
It's been 9 months since the last comment in this thread, but I recently came across this same problem and thought I'd post the solution I used. As I'm neither an expert in ejabberd nor Erlang, any ideas concerning a better fix would be appreciated.
I should point out that this is modified from the ejabberd 1.1.2 release, NOT the 1.0.0 release mentioned in the original topic.
First, I uncommented this line in odbc_queries.erl and recompiled:
%-define(mssql, true).
Next, I modified mod_vcard_odbc.erl and recompiled:
In addition to modifying the source, I found the mssql.sql file was incorrect. The following is the appropriate schema:
If there are any questions, I could post the actual files.