Standalone backup agent for Microsoft Windows servers and workstations (formerly Veeam Endpoint Backup FREE)
X-ian
Novice
Posts: 4 Liked: 1 time
Joined: Nov 02, 2020 7:33 am
Full Name: Christian
Location: Hamburg area, Germany
Contact:
Post
by X-ian » Feb 21, 2023 1:40 pm
this post
Hello everyone,
I'm trying to update Veeam Agent on remote machines via CLI.
Code: Select all
VeeamAgentWindows_6.0.0.960.exe /silent /accepteula /acceptthirdpartylicenses
Unfortunately, the setup wizard exits with exit code 1004. Executing the installer via normal double click works just fine but I'm asked to migrate the database. After that, reinstalling via CLI also returns code 1000. Shouldn't the installer do the migration unless I tell it not to with /skipmigration? Or am I doing anything wrong? The same switches have worked ever since from at least any V5.x, as I recall.
Dima P.
Product Manager
Posts: 14576 Liked: 1632 times
Joined: Feb 04, 2013 2:07 pm
Full Name: Dmitry Popov
Location: Prague
Contact:
Post
by Dima P. » Feb 21, 2023 2:49 pm
this post
Hello and welcome to the forums Christian,
Indeed VeeamAgentWindows_6.0.0.960.exe /silent /accepteula /acceptthirdpartylicenses should install new version on top of v5 and migrate the database settings. Any chance you have a case ID to share?
Dima P.
Product Manager
Posts: 14576 Liked: 1632 times
Joined: Feb 04, 2013 2:07 pm
Full Name: Dmitry Popov
Location: Prague
Contact:
Post
by Dima P. » Feb 21, 2023 3:40 pm
this post
QA team believes that the issue with database migration itself, is it possible to raise a support ticket and share the case ID with us? Thank you!
X-ian
Novice
Posts: 4 Liked: 1 time
Joined: Nov 02, 2020 7:33 am
Full Name: Christian
Location: Hamburg area, Germany
Contact:
Post
by X-ian » Feb 22, 2023 8:37 am
this post
Hello Dima,
the support ID is #05891277.
Best regards
Christian
Dima P.
Product Manager
Posts: 14576 Liked: 1632 times
Joined: Feb 04, 2013 2:07 pm
Full Name: Dmitry Popov
Location: Prague
Contact:
Post
by Dima P. » Feb 22, 2023 10:31 am
this post
Perfect, passed to the QA team. Thank you Christian!
guiper
Lurker
Posts: 1 Liked: never
Joined: Feb 22, 2023 7:25 pm
Full Name: Guillermo Perez Iglesias
Contact:
Post
by guiper » Feb 22, 2023 7:46 pm
this post
Hello, I was only able to do the upgrade making workaround with localdb:
"C:\Program Files\Microsoft SQL Server\110\Tools\Binn\sqllocaldb.exe" s v11.0 >nul 2>&1
ping -n 5 127.0.0.1 >nul 2>&1
for /F "delims=" %%f IN ('dir /b "%~dp0bin\VeeamAgentWindows_6*.exe"') DO (
"%~dp0bin\%%f" /silent /accepteula /acceptthirdpartylicenses
) >nul 2>&1
"C:\Program Files\Microsoft SQL Server\110\Tools\Binn\sqllocaldb.exe" p v11.0 >nul 2>&1
Best regards,
Guillermo
X-ian
Novice
Posts: 4 Liked: 1 time
Joined: Nov 02, 2020 7:33 am
Full Name: Christian
Location: Hamburg area, Germany
Contact:
Post
by X-ian » Feb 23, 2023 10:06 am
this post
Hi Guillermo,
I am using PsExec to start the setup on the remote machines from my PC. Unfortunately, your workaround did not work for me.
Best regards,
Christian
Dima P.
Product Manager
Posts: 14576 Liked: 1632 times
Joined: Feb 04, 2013 2:07 pm
Full Name: Dmitry Popov
Location: Prague
Contact:
Post
by Dima P. » Feb 23, 2023 10:45 am
this post
QA and Support folks are investigating the case, indeed they suspect localdb to misbehave during migration. Stay tuned!
X-ian
Novice
Posts: 4 Liked: 1 time
Joined: Nov 02, 2020 7:33 am
Full Name: Christian
Location: Hamburg area, Germany
Contact:
Post
by X-ian » Mar 08, 2023 2:20 pm
1 person likes this post
Hello all,
adding the -s switch to PsExec helped. The SYSTEM context is able to migrate the LocalDB.
Best regards,
Christian
Users browsing this forum: No registered users and 5 guests