During the installation of System Center 2012 R2 – Data Protection Manager, you may experience a failure and receive event ID 811:

DPM Error 1   DPM Error 2

As is often the case with these installation errors, the information provided doesn’t really give you much to on, plus the DPM error code catalogue had no information and neither did perusing articles after a Bing search.  With this, I had to open up the DPM install log and after trawling through it, I found this….

[17/09/2014 11:49:26] Information : Creating database
[17/09/2014 11:49:26] * Exception :  => System.Data.SqlClient.SqlException (0x80131904): The — CREATE DATABASE statement failed. The primary file must be at least 512 MB to accommodate a copy of the model database.
at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action1 wrapCloseInAction)
at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose)
at System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady)
at System.Data.SqlClient.SqlCommand.RunExecuteNonQueryTds(String methodName, Boolean async, Int32 timeout, Boolean asyncWrite)
at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(TaskCompletionSource
1 completion, String methodName, Boolean sendToPipe, Int32 timeout, Boolean asyncWrite)
at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
at Microsoft.Internal.EnterpriseStorage.Dls.DB.SqlRetryCommand.ExecuteNonQuery()
at Microsoft.Internal.EnterpriseStorage.Dls.Setup.Configuration.DBConfigurator.CreateDB(String databaseLocation, Boolean upgrading, Boolean isRemoteDb)
ClientConnectionId:f3d0974b-742b-4b76-a8e2-4a076b2fe09e

 

The cause of this turned out to be that the “model” database in the SQL instance being used for DPM has been increased to a size that the installer can’t handle, and causes this unclear error to occur.

To resolve the issue, simply reduce the “model” database size back down to its default, or smaller, value.  In my scenario, the database administrators set the default size of the “model” database to 512MB, which caused the DPM installation to fail, however after reducing this down to 10MB, the installation completed successfully.

The following TSQL can be used to adjust the “model” database size.

— configure Model

–Increase Model DB size

Use Master

ALTER DATABASE [Model] MODIFY FILE

(NAME = Modeldev,

SIZE = 10MB , FILEGROWTH = 10MB )

ALTER DATABASE [Model] MODIFY FILE

(NAME = ModelLog,

SIZE = 10MB , FILEGROWTH = 10MB)

Obviously, update the size values as appropriate for your environment.

Enjoy!

David