MDB Install: Error Code 110, Pre-process failed error message on new MDB install (not an upgrade)
search cancel

MDB Install: Error Code 110, Pre-process failed error message on new MDB install (not an upgrade)


Article ID: 18453


Updated On:


CA Client Automation CA Client Automation - Patch Manager CA Client Automation - IT Client Manager


During the MDB installation, the following error is encountered during the setup. This error message could have multiple possible causes; this document will define one of the causes (NOTE: This is a fairly generic error and can have many causes. This doc outlines one such cause. It should not be considered the only possible one):

Inside the setup log tab, the following text is observed:

Upon further analysis, the %temp%\ITRM\database\mdb_install\install_mdb.log reveals the following error.

The text of the error reads:

Msg 5170, Level 16, State 1, Server FONBR01-U116380, Line 1Cannot create file 'C:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\DATA\mdb.mdf' because it already exists. Change the file path or the file name, and retry the operation.Msg 1802, Level 16, State 4, Server FONBR01-U116380, Line 1CREATE DATABASE failed. Some file names listed could not be created. Check related errors.05-08,12:21:50 Failed to create the database (errorlevel=1)          05-08,12:21:50 Setupmdb_pre exit /B return code=400   05-08,12:21:52 Pre-process failed (errorlevel=400) 05-08,12:21:52 Setupmdb exit  return code=110


Client Automation - All versions


No 'mdb' database is seen in SQL Management Studio, but the DATA folder inside the database instance for the SQL server shows a prior MDB that exists, but is detached from the database server:



The presence of the mdb.mdf and mdb_log.ldf files indicate there's already an MDB on this SQL Server. The MDB is currently detached from the SQL server which is why it's not seen in SQL Management Studio. Before deleting the conflicting MDB files, be sure to check the detached MDB is safe to delete. Once the files are deleted, re-run the installer and the MDB creation will now be successful.