SqlChecker.vbs doesn't work automatically with SureBackup ?

[Oka Soh]

Hi All,

I have the question about vbs script which is included in Veeam installation folder.
It's "Veeam.Backup.SqlChecker.vbs".

I read the article by your Engineer, Danilo Chiavari.
http://www.danilochiavari.com/2014/12/0 ... eam-br-v8/

I've read the description in file, as far as I read,
this will be used in SureBackup by "Test Script" in Application Group.
My environment is WORKGROUP, so I specify this script with SQL Server credentials.
But this doesn't work in SureBackup automatically.

Oddly, when I run this script manually from Veeam server, this script works.

I wonder why there is such difference so I open the ticket Case # 00846095,
then the support said "if you want to use SQL Server credentials, you must run manually."

I'm confused the correct script usage when I use with SQL Server credentials.
Could you clarify this ?

Regards,
Sohei

[foggy]

Sohei, as far as I can judge, you're doing everything correct (at least if you're following Danilo's article). SQL authentication should work this way, so I suggest you to continue investigating the reasons of the observed behavior with your support engineer.

[dpgator333]

I am having an issue with the SQL script. I added a script above the SQL check script to check for port 1433, and it is working so it's not a network/firewall thing. I made sure I can log into SSMS with the credentials that I'm using also, so that shouldn't be a problem. Not getting anywhere with support so far. This is a Windows domain joined SQL server, with a Global Catalog DC/DNS server already up and running in the Surebackup job. Any ideas/thoughts would be welcome.

[foggy]

Hi Dan, could you please share the support case ID? Thanks!

[jac_607]

For anybody who comes across this, I have an update if you get SSL errors when trying to test.

If you have TLS 1.2 only turned on, as is standard since 2019, the script fails because the vbs script is trying to connect via an older encryption algorightm (or non at all).

Open the Veeam.Backup.SQLChecker.vbs script, and search for "sConnString". Copy the line and paste it directly below it. Comment the first line just to keep as a backup.

Replace the newly duplicated line with this:

sConnString = "Provider=SQLNCLI11;DataTypeCompatibility=80;Initial Catalog=master;Server=" & sInstance

Basically, SQLNCLI11 instead of SQLOLEDB.1 and adding DataTypeCompatibility=80 as a parameter. Then the script started connecting for all of our SQL servers.

[Egor Yakovlev]

Hi Jonathan.

Thanks for sharing your solution.
I will discuss this case with devs.

/Cheers!