It seems that this question is best asked in a forum for CRM Dynamics.
I would assume that Microsoft do not ship setups with such glaring errors in general, so I would guess that the problem is that your database has a name which the Setup does not handle properly.
Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se