Interesting. Could it be that the catalogs/schemas are not visible to
the user/password credentials used? The database name in the profile
properties may be set to a database that isn't visible to the user?
We tested using the older 1.2 driver from Microsoft as well and really
haven't had a chance to test with the new 2.0 driver. That may be an
issue as well.
If you are sure that a) the user has credentials for the database and b)
you get the same result using the older driver, please log a Bugzilla
entry for this and we'll try and take a look.