Skip to main content

Installation error with iso for VBR v11a P20211211


JMeixner
Forum|alt.badge.img+17

Hello,
I tried to install a new VBR server with the iso of Version 11a P20211211 (VeeamBackup&Replication_11.0.1.1261_20211211.iso).

This fails at once with a strange error…

Tells you everything you have to know… :joy::joy::joy:

 

After that I tried the install on the same machine with an iso Version 11a P20211005 (VeeamBackup&Replication_11.0.1.1261_20211005.iso) and the Patch to V11a (P20211211 VeeamBackup&Replication_11.0.1.1261_20211211.zip) and all is working fine.

 

Did anyone get this error, too? I did not find anything in the forums to this behavior…

Unfortunately I did not have much time and had to get this installed, so I did not get all logs for Veeam support. I will try to recreate this situation….

15 comments

Chris.Childerhose
Forum|alt.badge.img+21
  • Veeam Legend, Veeam Vanguard
  • 8400 comments
  • January 12, 2022

Have not seen this one before.  We are already on 11a so we use the patch installers now not the ISO files typically.  Hopefully you will get something on this though in the install logs?


JMeixner
Forum|alt.badge.img+17
  • Author
  • Veeam Vanguard
  • 2650 comments
  • January 12, 2022
Chris.Childerhose wrote:

Have not seen this one before.  We are already on 11a so we use the patch installers now not the ISO files typically.  Hopefully you will get something on this though in the install logs?

Yes, this was my approach with my existing servers, too.

But now it is a completely new one :sunglasses:

As I said, I will try to recreate the error...


Iams3le
Forum|alt.badge.img+11
  • Veeam Legend
  • 1374 comments
  • January 12, 2022

Hello @JMeixner Which OS version did you try to install the new VBR server with the iso Version 11a P20211211 (VeeamBackup&Replication_11.0.1.1261_20211211.iso?


JMeixner
Forum|alt.badge.img+17
  • Author
  • Veeam Vanguard
  • 2650 comments
  • January 12, 2022

It is a Windows Server 2019 Standard with the newest updates.


Iams3le
Forum|alt.badge.img+11
  • Veeam Legend
  • 1374 comments
  • January 12, 2022
JMeixner wrote:

It is a Windows Server 2019 Standard with the newest updates.

Then that should be fine.. I was thinking it was WinSer2022. You could try it again on a different VM to see if it will work This could be due to other related issues. 


Mildur
Forum|alt.badge.img+12
  • Influencer
  • 1035 comments
  • January 12, 2022

You can try to find more about the issue in this path.

C:\ProgramData\Veeam\Setup\Temp

But I’m afraid, that if veeam wasn’t able to start the installation splash screen, there won’t be any logs written already.


JMeixner
Forum|alt.badge.img+17
  • Author
  • Veeam Vanguard
  • 2650 comments
  • January 12, 2022

Correct, it breaks at the very beginning of the process.

This is the content of the logfile C:\ProgramData\Veeam\Setup\Temp\VeeamSetupLog_2022_01_10_14_41_29.log. this file seems to be the only one preserved from the failed install attempts.

2022-01-10 14:41:30 [UI MESSAGE]

2022-01-10 14:41:58 [UI MESSAGE] Interaction result: OK

 

I will try to recreate the problem and will the update this thread.


MicoolPaul
Forum|alt.badge.img+23
  • 2358 comments
  • January 12, 2022
JMeixner wrote:

It is a Windows Server 2019 Standard with the newest updates.

Fresh image straight from Microsoft or custom/hardened image?

 

Have you validated ISO checksum?


JMeixner
Forum|alt.badge.img+17
  • Author
  • Veeam Vanguard
  • 2650 comments
  • January 12, 2022

Yes, the checksum is ok.

It is a fresh Windows Server installation, no customization so far.
And the older iso + patch is working.

 

I understand this is not a common error, this was what I wanted to know :sunglasses:
It will take a moment to recreate….


marcofabbri
Forum|alt.badge.img+13
  • On the path to Greatness
  • 990 comments
  • January 12, 2022

It seems this fresh OS installation is corrupted @JMeixner 

Try a cmd

Dism /Online /Cleanup-Image /RestoreHealth

and then again Veeam setup.


Link State
Forum|alt.badge.img+11
  • Veeam Legend
  • 602 comments
  • January 12, 2022

hi @JMeixner 

curious,
did you mount the ISO on Vmware side?
Did you copy the ISO to the OS and mount it?
Does the problem occur in both cases?

thx


JMeixner
Forum|alt.badge.img+17
  • Author
  • Veeam Vanguard
  • 2650 comments
  • January 12, 2022

Hi @Link State ,
I copied the ISO to the filesystem ion the VM and mounted it from there.


Link State
Forum|alt.badge.img+11
  • Veeam Legend
  • 602 comments
  • January 12, 2022
JMeixner wrote:

Hi @Link State ,
I copied the ISO to the filesystem ion the VM and mounted it from there.

Post crash are there any detectable :no_entry: ID events on the event viewer to analyze?


marcofabbri
Forum|alt.badge.img+13
  • On the path to Greatness
  • 990 comments
  • January 21, 2022

Any update @JMeixner ?


JMeixner
Forum|alt.badge.img+17
  • Author
  • Veeam Vanguard
  • 2650 comments
  • January 21, 2022
marcofabbri wrote:

Any update @JMeixner ?

Unfortunately not :frowning2: I was busy this week with other topic.

I will try to get this done next week and keep you posted.