Error after upgrading veeam from v5.0.2.4567 to v6.0.0.1060

[blaze351]

After upgrading veeam from v5.0.2.4567 to v6.0.0.1060 the script produces the following error:

Error: in prepare, no such column: start_time (1)
/data/scripts/vee-mail.sh: line 193: [: -gt: unary operator expected
/data/scripts/vee-mail.sh: line 209: [: : integer expression expected
/data/scripts/vee-mail.sh: line 212: [: : integer expression expected
/data/scripts/vee-mail.sh: line 215: [: : integer expression expected
/data/scripts/vee-mail.sh: line 218: [: : integer expression expected
date: invalid date ‘@’
date: invalid date ‘@’
date: invalid date ‘@’
date: invalid date ‘@’
Failed to convert [023-02-1] to UUID.

[Thormir84]

I have the same errors.

[grufocom]

Please execute the following commands:
/usr/bin/veeamconfig agreement acceptEula
/usr/bin/veeamconfig agreement acceptThirdPartyLicenses
And try again!

[Thormir84]

Please execute the following commands: /usr/bin/veeamconfig agreement acceptEula /usr/bin/veeamconfig agreement acceptThirdPartyLicenses And try again!

Nothing changed.

[spupuz]

i have the same error too

[grufocom]

veeam probably changed something in the data structure, i'll look into it and fix the problem!

[blaze351]

I have already accepted the licenses via GUI but run the commands anyway:

/usr/bin/veeamconfig agreement acceptEula
/usr/bin/veeamconfig agreement acceptThirdPartyLicenses

The error still exists:

Error: in prepare, no such column: start_time (1)
/data/scripts/vee-mail.sh: line 193: [: -gt: unary operator expected
/data/scripts/vee-mail.sh: line 209: [: : integer expression expected
/data/scripts/vee-mail.sh: line 212: [: : integer expression expected
/data/scripts/vee-mail.sh: line 215: [: : integer expression expected
/data/scripts/vee-mail.sh: line 218: [: : integer expression expected
date: invalid date ‘@’
date: invalid date ‘@’
date: invalid date ‘@’
date: invalid date ‘@’
Failed to convert [023-02-1] to UUID.

[grufocom]

They changed the database structure:

CREATE TABLE IF NOT EXISTS "JobSessions" (
"id" PRIMARY KEY NOT NULL UNIQUE ,
"job_id" ,
"job_name" TEXT ,
"type" INTEGER ,
"state" INTEGER ,
"state_changed_utc" DATETIME ,
"log_text" ,
"logs_dir" TEXT ,
"progress" INTEGER ,
"progress_details" TEXT ,
"details" TEXT ,
"retried_session_id" TEXT,
"usn" INTEGER DEFAULT 0 ,
"policy_tag" TEXT ,
"bobject_id" TEXT ,
"point_id" TEXT ,
"creation_time_utc" DATETIME ,
"start_time_utc" DATETIME ,
"end_time_utc" DATETIME
);

added _utc to start_time...
I'll fix that soon! :-)

[grufocom]

please try the new version 0.5.45 - should fix the problem!

[Thormir84]

Now it works, but i receive this error:

Failed to convert [023-02-1] to UUID.

[blaze351]

Now it works, but i receive this error:

Failed to convert [023-02-1] to UUID.

same here

[grufocom]

version 0.5.46 addresses this issue! :-)

[Thormir84]

Ok, now it works perfectly!

[grufocom]

thanks for testing and reporting back quickly!