New Mailbox backup Issue?

[hankk17]

updated to the latest version of VeeamO365 Friday and initially backups seemed to go OK, but now about 90% of my accounts are throwing the unknown opcode found:4 error

I'm already on powershell 5.1 and am still getting the issue. multiple retrys are also not working.

opened a case on this today after seeing this thread - 07099442.

support contacted me with the latest hotfix and things seem to be fixed.

[mfc]

Support just let me know they have a KB up: https://www.veeam.com/kb4540

[blochner]

I started out with 10-15 errors, and I was up to 70+ as of this morning. Just happened to check for any new updates on this forum and came across the KB link. So far it's working, I just ran a full job manually and not a single error.

[smedeDKsmeden]

Thanks for the link, it is all good and running again. Never did hear from veeam support. Case # 07098355

[rsk@mb-solutions.dk]

Anyone have a fix for this yet?

[ACrispiels]

Without having changed anything yet or having applied the suggested patch (Fix_641296_7831ceb086.zip), the backup of the impacted organization is working again !
So I'm not currently applying this patch yet but I'm continuing to monitor it.

[Polina]

Hi All,

Hotfixes are indeed publicly available starting last night: https://www.veeam.com/kb4540
Cumulative patches are coming soon.

Thanks!

[jidiaz]

Thanks you all, case 07096826 open from friday and KB worked fine
https://www.veeam.com/kb4540

[ProfileX]

Without having changed anything yet or having applied the suggested patch (Fix_641296_7831ceb086.zip), the backup of the impacted organization is working again !
So I'm not currently applying this patch yet but I'm continuing to monitor it.

Same here, the errors went away without installing the hotfix, so I'll hold off a few days & see if it comes back, monitor here for any possible new issues introduced by the hotfix.

[RGlintmeijer]

Had two tenants with this issue, I did not install the hotfix and today the jobs were succesful again.

Seems like Microsoft reverted a change or fixed a problem.

[Mike Resseler]

Sigh... Thanks for all the comments folks!

I don't like the fact that suddenly the problem went away even if you haven't installed the hotfix yet. Please keep it ready for the next occurrence. What I predict is that we will see it appear again in a week or 2 on a new set of tenants. I still don't know the exact root cause but since it is the second time it happens in 2 weeks, and it does "disappear" I kind of suspect that every tenant will have to deal with this at some point in time. I assume it is an update to the M365 tenant, causing some issues for a limited time because of background processes (sort of upgrades I assume) and when that is done everything returns to normal. But that is just an assumption at this point in time

[m.novelli]

I've got only one Customer out of about 25 with this issue, for 3 or 4 days, and then disappeared

Marco

[oflores]

Hi, I updated to the latest patch today 03/07/2024, and presented this bug in my exchange job's.

KB4540 says that updating resolves but this is not correct.

Case #07168369

[Sipox93]

Hi Guys,

Samme issue here, i Updated to ...1301 and got this Issue. 56 of 501 Objects Failed. I Tried again some times, but didnt work.
Now i Updated to 1501 because some People said it would fix it. Now it is running, noting failed yet. Seems to be working.

So even if you just did the update, try to search for updates and go to ..1501 Version, it should fix it.

Have a nice day and Greetings from Germany.

[Mildur]

Hi, I updated to the latest patch today 03/07/2024, and presented this bug in my exchange job's.
KB4540 says that updating resolves but this is not correct.
Case #07168369

Hi Oflores

Thank you for the case number.
The provided logs shows us that you are still running 7.1.0.1401.
The issue is fixed in 7.1.0.1501 (as mentioned in KB4540), which is correct.
Please update to the requested version. You may need to download it manually from here:
https://www.veeam.com/kb4533

Best,
Fabian

[oflores]

Thank you for the case number.
The provided logs shows us that you are still running 7.1.0.1401.
The issue is fixed in 7.1.0.1501 (as mentioned in KB4540), which is correct.
Please update to the requested version. You may need to download it manually from here:
https://www.veeam.com/kb4533

Thanks for the reply, the error was resolved when updating the proxies in my infrastructure, I'm sorry to discredit the KB4540, it works by having the latest version for the components.

my problem was solved, greetings from México.

[rmacena]

Hey folks! Here, the issue was resolved after upgrading to patch version 7.1.0.1502_P20240411. After the upgrade, all is working fine!
https://www.veeam.com/kb4533

[slackhouse]

I started seeing the same issue a day or so ago. Can confirm that the update in kb4533 resolved my issues as well.