i'm guessing that the application does not expect an empty database...it expects a database with specific tables, procedures, views etc to exist, but probably many of those objects are allowed to be empty(as in now ROWS of data) for a new installation.
it looks for a certain table, and if it doesn't find it, it knows the "database is not configured for this application", and bails out.
Lowell