Invalid object name 'mfEntLicenses'

This error indicates that

When setting up the databases for ENT Server you basically have two options. The first option is that you create the databases yourself (using the create_db.sql script that you will find in

  [Program Files]\Microforge.net\Enterprise Server\Tools

Once you've created the databases and the necessary tables etc. using this create_db.sql script, you can then provide the details of this database during the database setup wizard to have ENT Server use this database.

The second possibility is that you provide the name of a database that does not exist already, during the database setup wizard. If you give ENT Server the name of a database catalog that does not already exist on your SQL Server during the database setup wizard, it will attempt to create this database for you (along with all the necessary tables, views, stored procedures etc. that it needs).

In the second case, ENT Server will obviously need all the necessary permissions to create tables and modify these.

If you're getting an Invalid object name 'mfEntLicenses' error message when trying to connect to your ENT Server then you should take a look at the [Program Files]\Microforge.net\Enterprise Server\Working\settings.ini file and see what the name of the database is that ENT  Server is configured to use. This will be stored in the settings.ini file as a name=value pair with the name DB Catalog.

You can either run the create_db.sql script against this database (to create the necessary database tables etc. in that database) or you can delete the lines that relate to the database settings from this settings.ini file (i.e. the lines that start with DB Type, DB Server, DB Catalog, DB UserId and DB Password).

If you delete the existing database settings then the next time you try to connect to your ENT Server you will see the database setup wizard again, and you can provide the name of a new database here (i.e. one that does not already exist on your SQL Server) to have ENT Server create this database for you along with the tables, views, stored procedures etc. that ENT Server requires.

Once ENT Server has been configured to use a database that exists and has all the required tables, views and stored procedures, you should no longer see this error.