ejabberd 2.0.1 (solved: mod_*_odbc) and (unsolved: roster status updates)

Hello all! This is really two questions, but I didn't want to appear to be spamming with two topics. I'm using the Debian stable version of ejabberd (2.0.1), with authentication done via Kerberos via PAM.

1. Using the Mnesia database for roster, vcards, etc., everything works fine. The only problem is, when I connect with Pidgin or Psi (both latest), I get my roster but no presence information. I have to either wait for one of the clients to change status (i.e. to Away), or manually click "re-request authorization". Additionally, none of the IM gateways send my IM roster ot my client (i.e. my AIM contact list does not appear). This works fine in Jabberd 2, so what have I done wrong?
2. Using mod_*_odbc (preferred), nothing works. I've configured the database correctly (MySQL, the username and passwords work), I ran the MySQL script to set up the schema, and all permissions are granted to the ejabberd user. Despite all of this, whenever I attempt to perform an action that would touch ODBC (such as a vcard update), I get the following error message in the log:
   =ERROR REPORT==== 2009-07-16 11:52:54 ===
   E(<0.305.0>:gen_iq_handler:118) : {noproc,
                                      {gen_server,call,
                                       ['ejabberd_odbc_sup_redacted.org',
                                        which_children,infinity]}}

      

   EDIT: This one has been solved.

I can provide my configuration if you need to see it.

Thanks in advance!