Repeatedly being prompted to load tables in the SQL Server Configuration area when configuring SQL (4215352)

When attempting to configure the SQL Server settings, you may be prompted to reload the database tables (and create the database) repeatedly in a loop; without any progress.

Issue 1:

When a new database creation is attempted (during the load tables process), MNE encounters the older database (nme40db.mdf) and cannot proceed.

The following error is seen in the Event Viewer application log:

"EventID: 5170
Description:

Cannot create file 'c:\program files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\NME40DB.mdf' because it already exists. Change the path or the file name, and retry the operation."

This problem may be caused by a previous incomplete installation of MNE 4.9. When the product is un-installed, the database is still left intact.

Issue 2:

Unable to create NME40DB database in SQL server and in the Migration Console log showing the following error:

Error: (4060)-Cannot open database "NME40DB" requested by the login. The login failed.

There is no issue with the login credential supplied in the Migrator console.

This problem caused by the required SQL Server Command Line utilities is not installed on the Migrator Console server.

Issue 3:

This can also be caused by User Account Control (UAC) being active.

Antivirus was also active in this instance

Resolution 1:

To resolve this issue, backup (if needed) and delete the nme40db.mdf and nme40db.ldf files mentioned in the above Event Viewer application log. Then attempt to configure the SQL Server settings within MNE 4.0 and reload the database tables. The looping dialogue should no longer occur, and a new database will be successfully created.

Resolution 2:

For database server running SQL Server 2012 , the Microsoft SQL Server 2012 Command Line Utilities must also be installed, on the Migrator Console server. This can be obtained from the Microsoft Website.

http://www.microsoft.com/en-us/download/details.aspx?id=36433

Resolution 3:

If it is caused by UAC being active, then make sure to turn it off along with Antivirus and Data Execution Protection (DEP)

This was also resolved in a case where the  database could not be created  manually with SQL management studio.

Another case was seen where a customer attempted to create a second instance in SQL Express since the first one did not work. When  the C:\Program Files\Microsoft SQL Server\MSSQL.2\MSSQL\Data folder  was reviewed, it was empty but  it was found that there was a residual nme40DB.mdf and .ldf. in the C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data folder. Once removed,  the Database was installed  properly.