Manual Database Install fails with errors. (4271963)

During a manual Database Install you receive the following errors:

Column 'UnknownExchangeMailEnabledUserGUID' in table 'T_UnknownExchangeMailEnabledUser' is invalid for creating a default constraint.
Msg 1750, Level 16, State 0, Line 2
Could not create constraint. See previous errors.
Warning! The maximum key length is 900 bytes. The index 'UC_T_LN_ServerStoreCopies' has maximum length of 1040 bytes. For some combination of large values, the insert/update operation will fail.
Msg 4902, Level 16, State 1, Line 2
Cannot find the object "dbo.T_UnknownExchangeMailEnableduser" because it does not exist or you do not have permissions.
Msg 4902, Level 16, State 1, Line 2
Cannot find the object "dbo.T_UnknownExchangeMailEnableduser" because it does not exist or you do not have permissions.
Msg 137, Level 15, State 1, Procedure FU_QMSMostRecentTaskOccurrence, Line 6
Must declare the scalar variable "@Result".
Msg 319, Level 15, State 1, Procedure FU_QMSMostRecentTaskOccurrence, Line 7
Incorrect syntax near the keyword 'with'. If this statement is a common table expression or an xmlnamespaces clause, the previous statement must be terminated with a semicolon.
Msg 15151, Level 16, State 1, Line 1
Cannot find the object 'FU_QMSMostRecentTaskOccurrence', because it does not exist or you do not have permission.
Msg 15151, Level 16, State 1, Line 2
Cannot find the object 'FU_QMSMostRecentTaskOccurrence', because it does not exist or you do not have permission.
Msg 4121, Level 16, State 1, Procedure PR_CreateQMSTaskViews, Line 159
Cannot find either column "dbo" or the user-defined function or aggregate "dbo.FU_QMSMostRecentTaskOccurrence", or the name is ambiguous.
Msg 15151, Level 16, State 1, Line 1
Cannot find the object 'V_QMSTasks', because it does not exist or you do not have permission.
Msg 15151, Level 16, State 1,

The SQL Server has been installed with the incorrect Server Collation.
MessageStats does not support case sensitivity on SQL Server. Some non-Latin database collations can cause SQL Server to observe case sensitivity.
 

Re install SQL server specifing the default (Latin1_General_CI_AS) collation.