Veeam M365 Console won't install after 8.0.3.1044 Update

[igibason]

We have been wrestling with the v8 update with our Veeam M365 Backups. We did install the 8.0.3.1044 update on the server and everything seems to be working so far. However now cannot install the console on my remote workstation. Every time I open the console it prompts to update then fails. After uninstalling the console and attempting to reinstall from the new update ISO the install fails on step 5 Applying the latest update.

Is there anything else I can try?

[mjr.epicfail]

Hi,

I would suggest logging a support ticket for this, Ive also seen issues with upgrade that the server upgrade installation wizard won't open.
https://community.veeam.com/discussion- ... oblem-8823

[Mildur]

Hello @igibason,

That sounds like a technical issue. We cannot investigate such issues through a forum topic.
Please provide a support case ID for this issue, as requested when you click New Topic. Without case number, the topic will eventually be deleted by moderators.

Best regards,
Fabian

[ngagne]

I'm experiencing this too - just logged case #07456953.

From the MSI log:

Code: Select all

MSI (s) (34!A4) [11:02:04:209]: Product: Veeam Backup for Microsoft 365 -- NATS Server connection string is missing.

NATS Server connection string is missing.
Failed with error: System.Exception: NATS Server connection string is missing.
   at Veeam.Archiver.Setup.CustomActions.JetStreamConfigurator.ConfigureConnectionString(Session session)
CustomAction ConfigureJetStreamConnectionString returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)

Uninstalling and cleaning out \ProgramData\Veeam\Backup365, then reinstalling doesn't help.

[aeph]

We are having exactly the same problem with updating our restore portal server (we are running the restore portal on a separate server).

Case-ID: #07457062

[dynamorob]

Same problem here

Case # 07457255

[aeph]

I had a remote session with Veeam support. It looks like there is an issue with the newly released patch. No details are available at the moment.
The case goes to RnD...

[andre.simard]

Hi,
Have same issue here case # 07456600

[Mildur]

Hi guys

I reviewed the cases and we see different issues. I may move each issue to a dedicated topic.

07456600 - Repeated "console must be updated" notification
- @andre.simard - No logs or screenshots provided, please upload them to the case

07457255 - Remote Console cannot be updated
- I'm waiting for the initial investigation of the logs through our support engineer

07457062 + 07456953 - RestAPI machine /RemoteConsole cannot be updated --> "NATS Server connection String is missing"
- Investigation is going on

Community Hub topic -
@mjr.epicfail - Different Error Message not related to the cases in this topic

_____________

May I ask from which build you are doing the update?
- Pre-V8?
- 8.0.2.159?
- 8.0.2.200?
- Any private build 8.0.2.***?

Best,
Fabian

[aeph]

@Mildur, We have upgraded from 8.0.2.9028.

[dave.moreland]

We are also experiencing issues installing the remote console and the Self Service Restore portal.

I did try running just the patch from the patches folder on the iso and on both the remote console and the SSR it gives and error that the NATS Jetstream connection string is missing or invalid.

Do these server need to connect to the NATS?

Anyone know where the NATS connection string should go? I'm thinking if I have the location of that string I can grab it from the Archiver server and populate it as a test.

[aeph]

Hi, had a second remote session with the veeam support.
First things first: it didn't work out again.

We have tried to insert the Nats Config String from the Config.xml of the management server into the Config.xml of the restore portal server. We have previously stopped the Veeam Rest Service. But as mentioned it did not work, Veeam Support is now working with RnD again and looking for a solution.

[Mildur]

@aeph
I'm following our R&D ticket to stay updated on the issue.

@dave.moreland
Please open your own case and provide me with the case number.
Every case helps us to track down this issue, and in the event of a private fix, you will need the case.

Best,
Fabian

[dave.moreland]

@mildur apologies, my case number is 07457255

[dave.moreland]

@Mildur I was able to find a work around and got my remote console and ssr working. It's not ideal but neither is having hundreds of customers calling because the ssr portal is down or to have support staff jockeying 2 rdp sessions.

I would be willing to share in a dm, but will refrain from posting publicly as its not without some caveats.

[aeph]

I would also like to see an update. In the meantime, the portal has been down for another 1.5 days..

[Mildur]

Hi Aeph
Our dev team is already working with high priority on a fix.

Hi Dave
Thank you. Please share the workaround within your support case. Your support engineer should be aware of any changes made while they assist you with the issue.
Our support teams in different cases are directly in contact with our QA team regarding update issues of the Remote Console and Restore Portal Server.

Best,
Fabian

[MILJW002]

Hi,

Same issue here. Tried to upgrade this morning only to find I then couldn't install or upgrade the console. Case logged #07460853.

[aeph]

It still does not work and there is no update from Veeam. It's really frustrating. We're talking about backup here - a critical infrastructure. Many people seem to have this error, it is inexplicable to me how Veeam can take so long here. We are talking about an installation that cannot be installed on a separate machine because a config cannot be found. Cannot be that hard to detect the problem?! Sorry for the words but its really frustrating and our customer are losing patience..

[mjr.epicfail]

Maybe a superfluous question, but is a rollback an option?

[Mike Resseler]

Hi all,

I do apologize for the delay. Our teams are now working around the clock trying to solve this. Unfortunately it is harder to detect the problem than expected. We will keep you informed once we know more...

[ACrispiels]

Same problem for me

[aeph]

Is there any progress here yet? We still have to keep our customers waiting. Thank you!

[dasfliege]

I've encountered the same issue updating REST API on separate server (Case 07457815).
Since the support was not able to tell me that this is a known issue, i tried several things myself. Ended up installing a fresh VM, installing the whole VBM365 suite from the iso and then deinstalled all components except the REST API. I now have the most recent version of the REST API installed, but restore portal is still not working ("Error: The server has rejected the client credentials"). But that may be another issue we are still trying to solve (Problem with wildcard?).

[aeph]

@dasfliege, we are having the same issue with "The server has rejected the client credentials".

Until now, I thought that this error was related to the fact that the versions between Restore Portal (old V8 version) and the new V8 version of the management server did not match. I had communicated this several times to the support with the answer “the error will be gone when the versions match”. According to your statement, this is probably not the case!
With the old V8 version, the restore portal with the certificate etc. worked without any problems!

So far I have always been put off by the fact that RnD is working on it. Is there any more transparency here? How far along is RnD? Close to the solution or far from it?

[Mike Resseler]

All, I expect to have something today. Gathering the final information as we speak. But I estimate that the new patch will be online today and it should fix the issue of updating the different components.
Additional info:
This build is the same as .1044 but adds the 1 fix for this specific issue.

[dasfliege]

@dasfliege, we are having the same issue with "The server has rejected the client credentials".

May i ask you to post your case ID in the following topic that i've initially created because of this error? Maybe the R&D is able to put some effort into fixing this one, since they have solved the update problem now: veeam-backup-for-microsoft-365-f47/rest ... 95970.html

[aeph]

@dasfliege, I have not yet received a working update, where is this info?

My case number regarding Restore Portal issues: Case #07457062

[pat_ren]

Same issue here, couldn't update. Tried uninstall/reinstall, also failed.
Case #07467477

Error seems to be that the latest ISO installs 8.0.2.159 then tries to patch it.
Patch fails due to NATS Server connection string is missing.

Looking forward to an update ASAP

[aeph]

Can we expect the update/ fix today?