This article was created in response to a support issue logged with K2. The content may include typographical errors and may be revised at any time without notice. This article is not considered official documentation for K2 software and is provided "as is" with no warranties.
This article has been archived, and/or refers to legacy products, components or features. The content in this article is offered "as is" and will no longer be updated. Archived content is provided for reference purposes only. This content does not infer that the product, component or feature is supported, or that the product, component or feature will continue to function as described herein.
Installing K2 against a pre-created database results in an error:
The SQL Server database configuration test failed as databases of the wrong type exists
This is expected behavior. The K2 Installer currently does not support installation against a pre-created database. You must allow the K2 Installer (K2 Setup Manager) to create the database.
Additionally, the installation account (account performing the installation) will need to be part of the following SQL Server Roles:
dbcreator on the SQL Server.
securityadmin on the SQL Server.
Deleting the pre-created database and allowing the K2 installer (K2 Setup Manager) to create the database resolved the issue.
If you would like this functionality to install against a pre-created database, please log or upvote this idea at: