There was a known issue in Desired Configuration Monitoring (DCM) Solution Accelerator v 1.0 where the DCMSolution database was not created during installation in specific cases. The issue occurred because the v 1.0 installer retrieved SQL information from a different registry path. However it happens only when the default data / log file locations is altered after SQL Server is installed.
This issue has been fixed in the DCM v 2.0 releases. I am outlining how DCM installer detects the data / log folders for creating the DCMSolution database.
For SQL Server Default Instance:
For SQL Server Named Instance:
The above is true for SQL Server 2000 SP3 and above. If you are facing a problem where the DCMSolution database is not being created at install time, you should check these registry locations and verify that the physical paths pointed to by these registry values exist on the physical server. Let me know if you have further questions.