Create Database failed error while creating new repository

[BVeeravelu]

Issue: Getting (attached) error message ("Create Database failed") while trying to create new repository. But able to create a child/sub repository of the repository that already exists.

Plastic SCM Version: 7.0.16.2356 installed in Windows Server 2012 R2

SQL Server 2008 R2; Microsoft SQL Server Management Studio 10.50.2500.0; Operating System 6.1.7600

Details: Was working fine with this server for more than 2 years and suddenly starting this week, we are not able to create any new parent repository in one the plastic scm server. Getting the attached error message.

Please provide some insights and recommendations what could be the reasons for this error and how to fix it.

Let me know for any more details or information required.

 Thanks,

Babu Veeravelu

 

[calbzam]

Hi,

Please, attach the full server debug log in order to debug the issue. But checking the error:

https://knowledgebase.abbyy.com/article/641

• This problem usually occurs when the user that is trying to create the database doesn't have the necessary permissions in SQL Server. If you use the Administrator's account to create the database, this situation can be avoided. You can also check if the account that failed to create the database has the permissions described in this article. 
• The problem can also occur if the name of the database you attempted to create is already in use by another database or if files from a database with the same name remain on the computer. Try creating a database with a different name.
• Check if the disk on which the SQL Server is trying to create the database has enough free space.

By the way, aren't you considering migrating your databases to Jet? Most of our bigger customers are already using it.

Regards,

Carlos.

[BVeeravelu]

Hi,

Thanks for the prompt response with your inputs. I am reaching out to the teams and will get back with details and outcomes, if we are still having issue.

Thanks,

Babu Veeravelu

[BVeeravelu]

Hi,

Thanks for the support, the issue has been resolved. 

There was a SQL Server upgrade happened that changes the database path. After coordinating with DBA team and setting up the new path in db.conf file the issue got resolved.

Thanks,

Babu Veeravelu

[calbzam]

Great! Thanks for the update