Failed to create database VeeamBackup. Please help :(

[neux]

CASE #: 01424353

Hello all,

I'm trying to install a trial version of Backup & Replication v9 on a clean Windows Server 2012R2 virtual machine. I keep getting the following error:

Failed to create database VeeamBackup. Create failed for Database 'VeeamBackup'.

I tried searching online but couldn't find any solutions.

Please help.

[Vitaliy S.]

Are you using remote SQL Server or trying to install VBR with all the defaults?

[tore.meum@99x.no]

Good afternoon.

I am experiencing the same issue. Exactly the same message as neux posted.
Straight installation of VBR on Windows 7 Pro SP1, all the default options.
I've looked in the debug logs (BackupSuite_03_02_2016_13_55_12 - hopefully the right one - it was plenty to choose from), with no clear error to look or.

I've done 15+ installations on different PC's with the same setup no issues.

Assistance appreciated.

Regards
Tore Meum

[foggy]

Hi Tore, as far as I can see from the OP's case details, he was managed to resolve the issue with the help of support during a short webex session. So I recommend you to contact them directly to get the same assistance. Thanks.

[tore.meum@99x.no]

Thank you.

Will contact support

Regards Tore

[spricer]

What is with forums nowadays...purpose?...."I know/got my answer but I will not share with you"..
Anyway solution for me (after carefully checked logs) was to remove file that was already existing (I assume from previous failed installation):

c:\Program Files\Microsoft SQL Server\MSSQL11.VEEAMSQL2012\MSSQL\DATA\VeeamBackup.mdf

[lars@norstat.no]

I so agree, and my opinion is that Veeam is the absolutely worst in this regard. Every f...... post is the same. Contact support, contact support ..... If you have the answer then post it !!!!!

I'm sitting now at 0101 at night doing a new installation and i need the answer now, not tomorrow or monday when i get the answer from support.

The reason you give is that you don't wont people to do something wrong and you want to make sure it's really the same problem as the other guy.

The real reason is that you don't want people to see the problems you have with the software.

Do you think we are children ? it's the same with all systems, yes we know something can go wrong and it's our problem if we choose the wrong solution. We all know how forums work. It's seems you are the only ones that don't know.

And i really don't understand why. Every software have issues and we all want to fix it as fast as possible. Why do you want to use so much support resources on something that users can fix themselves.

Thanks for the solution Spricer

[foggy]

Ok, a few comments on this, since I feel like this portion of "criticism" is dished out to my post above.

It is true that we always recommend to verify you're experiencing the exact same issue prior to applying a hotfix or taking any resolution steps (to avoid even more problems). We also do that for tracking purposes, so that the top issues get addressed in the next product updates.

We always share solutions that we know work (product configuration, registry values, design decisions, etc.), but always advise to get support assistance in more complex cases. Regarding that particular case (and many others similar), the case notes didn't contain any details about the actual issue/solution, but just customer and engineer negotiations regarding the time of webex session, then mentioned customer's gratitude and was closed. So neither I nor other members of the team behind this forum were aware of the steps required to address this issue (funny thing, sometimes cases are handled in customer's native language, so no matter how hard we try, we cannot make any sense of them).

[xiaochris]

Hi Guys,

To solve the issue ,

Go to,
C:\Program Files\Microsoft SQL Server\MSSQL11.VEEAMSQL2012\MSSQL\DATA

You will see two files.

VeeamBackup
VeeamBackup_log

remove these two files. And try reinstalling.

This should work. Worked for me.

[ahmed.abdelrazzak]

Best Reply ...... This worked for me also
Great & Easy Solution

[pireseder]

thanks spricer removing .mdf files from sql location from previous failed installs worked for me.

[drewblood]

Go to,
C:\Program Files\Microsoft SQL Server\MSSQL11.VEEAMSQL2012\MSSQL\DATA

You will see two files.

VeeamBackup
VeeamBackup_log

remove these two files. And try reinstalling.

Thank you for this,

Also note that if you want to change the computer name or join to the domain it is ideal to install Veeam first, or your console will break. Trial and Error.

[markzz]

Thanks Spicer for the solution and of course for raising the issue of this repetitive statement "Contact Support"
I can not contact support at midnight..

Please people. If you have a solution post it.. If it breaks my server I'll deal with it.. I wear big boys pants these days..

[jmmarton]

As an aside, as long as you have production support (which means 24x7) then yes you can contact support at midnight. I often advocate going with production support even in environments that aren't 24x7 because most updates/upgrades occur outside of normal business hours.

Joe

[egavasu]

Perfect solution. thanks for this.

----------------------------------------------------------------------------------------------
xiaochris wrote:
Go to,
C:\Program Files\Microsoft SQL Server\MSSQL11.VEEAMSQL2012\MSSQL\DATA

You will see two files.

VeeamBackup
VeeamBackup_log

remove these two files. And try reinstalling.
----------------------------------------------------------------------------------------------

[njdavis0812]

Thanks xiaochris, worked a treat!

[chilkers]

Worked out great for me too! I had to reinstall B&R 9.5U3 so the uninstall process also requires removing all of the SQL components as well since the install process for Update 3 requires an install of 9.5 first and then updates the database and Veeam B&R to U3. You'll get an error if you just uninstall B&R 9.5U3 and try to reinstall, hence the need to remove the SQL stuff as well.

[denser]

Same thing at fresh setup 11 version. Why install script don't check existence of this files. Idk.
Solved via remove MSSQL db files as described above.

[PetrM]

Hello,

What kind of check are you looking for? If I understand correctly the error message is shown as database files already exist in the target location. We cannot delete these files automatically on background without the user's consent. Also, I strongly recommend to contact our support team for any technical issue related to our product, especially if we're talking about setup. Usually, the problems with installation are sophisticated and difficult for troubleshooting.

Thanks!

[denser]

I don't know. But my position to make separate VM with VBR server. May be you should take attention with this and give me decide to allow installing program to what necessary to install product successfully.

[PetrM]

Hello,

Thanks for the idea! We'll consider such an improvement as long as we have enough requests for it.

Thanks!

[pallingd]

@PetrM : The error message is not anything related to "database files already exist". The error is just "Failed to create database VeeamBackup. Create failed for Database 'VeeamBackup", and the log file that is pointed to is even less helpful:

Code: Select all

Exception occurred (Veeam products installation section).
Info: System.ComponentModel.Win32Exception (0x80004005): Fatal error during installation
   at Veeam.Setup.MsiLibrary.VmMsiCommon.CheckError(VmMsiDatabase db, UInt32 result)
   at Veeam.Setup.MsiLibrary.VmMsiCommon.InstallProduct(String product, String commandLine, Boolean& bReboot)
   at Veeam.Setup.Wizard.VmInstallProduct.RunInstallation(Boolean& bReboot)
   at Veeam.Setup.Wizard.VmInstallEngine.Install(ShowControlFunc showActionData, Boolean bRepair, Boolean bUpgrade, VmDialogEngineHandler dialogEngineHandler)
   at Veeam.Setup.Wizard.PredefinedDialogs.VmInstallDialog.m_installWorker_DoWork(Object sender, DoWorkEventArgs e)

A simple "The database exists already. Do you wish to overwrite/create new/cancel?" prompt would have been much more helpful.

[PetrM]

Hi Per,

Did database itself exist on SQL instance or there were just some files on the file system? Also, may I ask you to share a support case ID?

Basically, this prompt must be shown, for example as we can see on this page of our help center:

If the configuration database already exists on the Microsoft SQL Server instance (for example, it was created by a previous installation of Veeam Backup & Replication), the setup wizard will notify about it. To connect to the detected database, click Yes.

Thanks!

[bmp999]

Thank You Spricer. Indeed the files existed from the previous MSP who left with the Backup non-existant.

[EliandroRenato]

Muito bom, removendo os arquivos resolveu meu problema. Obrigado pessoal.

[Mildur]

Hi Eliandro

I'm glad you could solve it with this topic.
Please only use English in this forums. This is an English only forum.

Best,
Fabian