Skip to main content
Solved

VBM : Issue with Restoring SharePoint Lists


Hello,

We have an issue with restoring SharePoint lists to another pre-production location. A case has already been opened under reference: 07261975, but we haven't received any explanation so far.

Do you have any idea about the error shown in the screenshot, please?
 

 

Best answer by asaadidi

Hello @Chris.Childerhose ,

As a solution, I restored the lists on another blank SharePoint site, but this solution was not accepted by our client.
The support team did not really help with this issue.

View original
Did this topic help you find an answer to your question?

5 comments

MicoolPaul
Forum|alt.badge.img+23
  • 2358 comments
  • June 10, 2024

Hi, what content type is in those fields/lists? Have you made sure the content types match between new and old lists?


coolsport00
Forum|alt.badge.img+20
  • Veeam Legend
  • 4109 comments
  • June 10, 2024

Hi @asaadidi -

I haven’t seen this error/issue before here on the Community Hub. Your best bet is to wait for Support. Another option is to post on the Forums your issue and see what the Product Mgmt team say.


Chris.Childerhose
Forum|alt.badge.img+21
  • Veeam Legend, Veeam Vanguard
  • 8398 comments
  • June 10, 2024

Also are you on the most recent patch for VB365 v7?  If not check here and the release notes - https://www.veeam.com/kb4106


Chris.Childerhose
Forum|alt.badge.img+21
  • Veeam Legend, Veeam Vanguard
  • 8398 comments
  • June 27, 2024

Hi @asaadidi - I wanted to follow up with you on this post to see if you were able to resolve it and if you did what the solution was?  If you can post the solution and then mark the best answer for others to reference this thread that would be great.  The best answer can be one of the posts or if you solved it yourself put the details then mark that as best answer.


  • Author
  • Comes here often
  • 9 comments
  • Answer
  • June 27, 2024

Hello @Chris.Childerhose ,

As a solution, I restored the lists on another blank SharePoint site, but this solution was not accepted by our client.
The support team did not really help with this issue.