hi @gkmanlangit 

Please refer to the installation logs in this path C:\ProgramData\Veeam\Setup. Can you provide us more info about your LHR (such as OS version, user account used DNS resolution etc etc)

Thanks 

@gkmanlangit , sorry to contradict @Andanet, but that log location is not relevant -- that is for installation of the program and features itself (e.g., Veeam Backup and Replication Server install, EM Install, Storage Integration Plugin install, etc.), and won’t help here.

Exit Code 1 means a command that was trying to be run over the initial configuration SSH connection failed and returned exit code 1. You can try checking /var/log on the Hardened Repository, but it’s best to open a Support Case and let Support review.

You will want to use the 3rd radio button to export form hosts and select the Veeam Server itself and the Linux server to export logs from. If you cannot select the Linux server (or log export fails), manually archive all of /var/log from the Hardened Repository and include it on the case for Veeam Support to review.

@gkmanlangit -

Possibly the user account you’re using doesn’t have “sudo” permissions to install? Other than making sure of that, I concur with the suggestion of opening a Support case.

Best.

oh no problem for me… surely my info was written as generic info and I like learning from those who know more.

You can also try when setting the Single-Use credentials to click the Advanced button and specify the SUDO information as well to see if that will get the install completed, otherwise like others have mentioned a Support ticket might be the easiest and best route.

Are all ports on the firewall (both centrally and on the RHEL server) open?
SSH (port 22) is required for the “initial contact” and to log on to the server, the installer then goes via port 6160. 
Later the data mover and the data via 6162 and 2500 to 3300.

So the following must be open:
Backup Server --> 22,6160,6162,2500-3300 --> Repo Server
Repo Server --> 2500-3300 --> Backup Server

using the Veeam 2.0.x custom Linux hardened iso this error can also occur is you're not using VBR 12.3 

gkmanlangit is it fix that? then you could provide solution

i had such an issue during release 12.1 on same linux repository, what did not happen before on previous versions, now on 12.2.0.334 is everything fine

solution for that version was try to run wizard few times and then is was working

Yes...with this post being a bit dated, would be nice to know what the resolution was, if you found one ​@gkmanlangit ?

Best.