SQL Server is not available

[BenB]

Hello,

I tried opening up a case from the interface, but when I try to report an issue, I get the error that my e-mail address is not validated yet, but I'm sure it is (tried with both my private and work e-mail address, both have active Veeam accounts). So I hope it's OK to get some support this way.

When I try installing Veeam endpoint (latest version) or the Veeam agent 2.0 RTM, the setup ends with a critical error just before the tray icon is starting. In the end, I do get the tray icon, but when I want to configure a backup job, I get the following error:
---------------------------
Veeam Agent for Microsoft Windows
---------------------------
Microsoft SQL server hosting the configuration database is currently unavailable. Possible reasons are heavy load, networking issue, server reboot, or hot backup.

Please wait, and try again later.



Error information:

SQL server is not available
---------------------------

This is on a Windows 10 PC (at home, so Home edition, not pro, but I can't find anywhere that the pro version of windows is a requirement).
At first, Avast was installed which I thought might be causing the issue, so I also already tried removing Avast and Veeam completely (and at the same time, trying to remove all the Veeam traces including the .ldf files and registry keys), rebooting and trying to re-install without any luck.
I hope this is an easy fix, because I do love the simple effectiveness of Veeam endpoint backup, even for home


Thanks,
Ben

[Mike Resseler]

Hi Ben,

First! Welcome to the forums!

Let's start with the email verification problem. You say you have active email accounts at Veeam.com but the system for VEB support is separate. (We need to keep the data separated for various reasons). So can you try the procedure again: https://www.veeam.com/blog/technical-su ... -free.html It is explained over there

If that doesn't work, we will reverse it and try to get support to contact you (but let's keep that as a last step )

[BenB]

Thanks Mike!
I did had to register with yet a third e-mail address, but was able to open up a case

[Mike Resseler]

Thanks for letting me know Ben!

Make sure you address that issue also. If it is something with us, we would like to fix it

Thanks
Mike

[BenB]

I addressed the issue too.
As far as the original issue is concerned: this was caused by webcompanion software installed on the PC.
Just wanted to let this know as it might help out other people too.

Cheers!
Ben

[Mike Resseler]

Thanks for letting us know Ben.

Did you uninstall the software or some tweaks/ config to webcompanion to get it running?

[KyleWhite]

I too was getting the same issue (with 1.5); however after updating I now simply get the error:

Error: The wait operation timed out

I've gone through a variety of different KB articles / solutions on the web, all to no avail.

For anyone else who had this problem, what was the exact steps you followed to remedy this issue?

Thanks

[Mike Resseler]

Can you check if the SQL server service is running?

[btimmins]

FYI, I had the same problem and uninstalling Lavasoft Web Companion also fixed it

[Dima P.]

Hello and welcome Bill.

Yes, Lavasoft is a known problem and we recommend to remove this software. Thanks for confirming the solution.

[glennholt]

I had a number of Veeam Agent (version 1.5 for Windows) backups fail, unable to find the SQL server. This error has morphed into "The wait operation timed out" in version 2.0, but it's the same issue. Is there no removal tool that can "clean slate" an installation? Removing the various components does not remove all the registry entries or files, and any further re-installs fail.

Thanks,
Glenn

[Dima P.]

Glenn,

Kindly open a support case via VAW Control Panel > Support > Technical Support (it's free) and share the case ID. Thanks in advance.

[glennholt]

Thanks! The case # is 02320735.

-Glenn

[guigeek]

Hi,
did you resolve the issue ?
Thanks,

[Dima P.]

guigeek,

This error requires debug log analysis, so please submit a support case and share your case ID. Thanks in advance.