Failed to process team: Team XXXX- . Cannot parse page operation response.

[ks.any.cloud]

Im not too fund by applying the hotfix until more have reported back, if it breaks something else.
I have seen too many times allready that a patch/hotfix breaks something else.

Where is the KB article regarding the hotfix, so i can download it ? it wass official ?

[Gostev]

As I already explained this earlier, at this time you need to contact support.

Our standard release process involves the Early Availability stage, when the new code is distributed through our support organization in a controlled manner. This way we track everyone who received it, in case we need to re-issue the hot fix for whatever reason. This distribution method does not make the hotfix "unofficial" though.

Then, once the hotfix is proven in the field by EA stage deployments, we will create a KB article with a direct download link. In this particular case though, there's a good chance this may not happen at all, because Microsoft just fixes a bug on their end. But at the very least, we need to wait until Microsoft makes up their mind about this API regression. Only then we will know what to actually say in the KB article

[Switchie_Urs]

hotfix deployed, 'older' affected Teams now back up normally at least those tested. will report back in case the hotfix does not fix all of the 250+ Teams that failed.
thanks for the swift response!

[Robvil]

IT is not only old team sites which causes this. I have a fairly new team site with the issue.
The hotfix solves it though.

[smarivoet]

I have the impression that it is mainly linked to teams that were restored already;
it can even be reproduced by the demo-tenant provided by MS by restoring a team. The next backup-run will pop up this error.
For sure something that was not an issue some time ago (great hidden MS changes I assume)

[Polina]

Hi All,

The same hotfix is now available for public download > KB4182.

[popjls]

MS need to stop changing their API every 35 seconds. This looks to have fixed us too. Thanks

[Keith.Gregory]

Thats well worked out VEEAM guys! We have a lot of "ancient" Teams that I don't know if they actually get used, so the two that are failing aren't particularly special - but are old. So where do we get the hotfix? I have support.

[VNR-LF]

Of course, in the ideal world Microsoft will simply fix down the road whatever they broke for those old team objects, making the workaround that the hotfix brings unneeded.

since i just noticed the hotfix mentioned before has now been made available (KB4182), do you think this "ideal world scenario" is going to come true? i don't mind waiting a bit more... or would you advise to just install the hotfix and be done with the issue?

[ks.any.cloud]

What version does this "fix" apply to, can i update to the latest 5.0.1.252 and then apply the fix ?

[VNR-LF]

according to https://www.veeam.com/kb4182:

Hotfix Version Compatbility
The hotfix for this issue was created only for Veeam Backup for Microsoft Office 365 builds 5.0.1.225 or 5.0.1.252.

If the currently installed build of Veeam Backup for Microsoft Office 365 is lower, you must upgrade before installing this hotfix.

[Gostev]

since i just noticed the hotfix mentioned before has now been made available (KB4182), do you think this "ideal world scenario" is going to come true?

I think yes, as the change looks accidental and makes no technical sense... the restore issue I described above shows that other parts of their own API are just as not ready for the change of the value type as our product was.

It's just hard to predict how much time they will need to make a decision and implement the fix, but Microsoft rarely moves with #VeeamSpeed in our previous experience. And due to the heavy support load from this issue, it was getting harder and harder for us to wait for their decision - so we decided to publish the hotfix anyway. The hotfix is ready for Microsoft to roll back the change though.

[VNR-LF]

thank you very much for clarification!

[ks.any.cloud]

Where to install the DLL on a proxy server ?

[Mildur]

Please read the KB Article. All required Paths are provided there
On proxy, there shouldnt be neccessary to provide the dlls.
https://www.veeam.com/kb4182

On step 9, you do a proxy upgrade, Most likely that will be distribute the dll to all proxys server.

Upgrade the backup proxy servers using the Veeam Backup for Microsoft Office 365 console.