[Serusers] Cannot authenticate with SER after upgrade to 0.9.6

[Stephen Helfen]

Here is what my userloc and auth_db params looked like on SER 0.8.12

# -- usrloc params --
# Change the default SER db user login and password
modparam("usrloc", "db_url", 
"mysql://nvproxy:<password>@localhost/nv_proxy")
#
# Set to persistent storage in SER db
modparam("usrloc", "db_mode", 2)
#
#
# -- auth_db params --
# Change the default SER db user login and password
modparam("auth_db", "db_url", 
"mysql://nvproxy:<password>@localhost/nv_proxy")
#
# Use a prepopulated ha1 authentication string
modparam("auth_db", "calculate_ha1", no)
#
# Change the default password column
modparam("auth_db", "password_column", "ha1")

Upon upgrading to 0.9.6, I now get the following messages in my 
/var/log/messages

May 15 16:09:18 ser /usr/sbin/ser[22006]: Maxfwd module- initializing
May 15 16:09:18 ser /usr/sbin/ser[22006]: submit_query(): Table 
'nv_proxy.version' doesn't exist
May 15 16:09:18 ser /usr/sbin/ser[22006]: submit_query(): Error while 
submitting query
May 15 16:09:18 ser /usr/sbin/ser[22006]: table_version(): Error in db_query
May 15 16:09:18 ser /usr/sbin/ser[22006]: auth_db:str_fixup(): Error while 
querying table version
May 15 16:09:18 ser /usr/sbin/ser[22006]: ERROR: fix_expr : fix_actions 
error

Why is it looking for a 'version' table in my proxy database rather than the 
ser database??  If I change the modparam statements to point to the ser 
database, SER starts correctly, but then I cannot register my UA with it, 
nor process any calls.

Thanks in advance.

Steve