Sharepoint Backup Failure "hexadecimal value 0x00"

[agrob]

Good Day

Since one day i get the follwoing Error on different Sharepoint Sites during Backup:
18.10.2018 07:13:04 :: Failed to process site: https://company.sharepoint.com/sites/site. '.', hexadecimal value 0x00, is an invalid character. Line 1, position 1. :: 0:41:37

I did already install KB2765 but behaviour is still the same.
Did MS maybe made some changes?
Thanks
Best Regards

[nielsengelen]

Hi Andre, please contact support to find a solution for this.

[agrob]

Thanks, opened a case, id #03246524
best regards

[Mike Resseler]

Andre,

Thanks for the support case ID. It looks like you are using Unicode NUL somewhere in that site which makes us fail. Let us know what the engineers find

Thanks
Mike

[agrob]

Hi Mike
Thanks for the information. Could be, the strange thing is, two days before it was working normaly, then suddenly those messages appears on maybe many different sites which where fine before... Anyway, lets wait and hope... )

Regards
André

[tommy.lidal]

We also got same error suddenly (didnt see this a few days ago) on sharepoint sites and users Onedrive buissness (that is sharepoint).
guessing som Microsoft changes done ?



Regards
Tommy
VBO365 v 2.0.0.567

[agrob]

thats what i guess as well. let's wait what support finds. I'll update the case as soon as i have news.

[agrob]

just checked the latest job log. the 0x00 Erros seems to be gone right now... but have a lot of "404" and "Failed to backup item: , The underlying connection was closed: An unexpected error occurred on a receive".

I'll check how the job does run the next few days

[Mike Resseler]

Andre,

What did support say?

[agrob]

not much. action plan is to create a seperate job with only one site who has the error to investigate further. so i checked latest log from backup last night and there is no 0x00 error right now. i guess it is again (not the first time) something microsoft changed temporary.

[Mike Resseler]

Might be indeed the case. My suggestion here would be to add this information (that it works now) into the support call but also still sent new logs because of the 404 and failed to backup item.

[agrob]

0x00 seems to be a temp error which was gone without modify anything from veeam side. Other errors like 404 and connection timeout was fixed with adding the following line to the proxy.xml file vor VBO

</Options>
<Source SPO365ConnLimit="4" WebTimeout="900" WorkerThreads="32" BatchSize="50" BatchPart="50" BatchTimeout="1200" BatchMaxItemSize="20" BandwidthLimit="0" BandwidthLimitUnit="MegabitsPerSecond" />
</Archiver>

[Mike Resseler]

Andre,

Thanks for telling us what happened. Hoping that it was only temporary for the others that had the 0x00 error also.