Forum Discussion
Sharepoint lists mirroring issue
Hi Murtaza_Ghafoor ,
Thank you for your message.All the replicated lists contained many fields with complex ones aswell. Some were succeeded and others no so it was obviously not a problem with the types of the fields. They all seem to be accepted, even the most complex ones.
Also I had already tried to clean and re-establish the connection dozens of times so there was another issue with the list I needed to find. As mentionned in my previous comment, it was a naming issue with the columns. The sharepoint lists replicating component was not able to manage different columns with the same name causing this kind of unexpected and not documented issue.
Again thank you for your help, this is now solved.
Community SupportHi Gllme
Thank you for coming back and documenting the outcome so thoroughly that's genuinely valuable, and it will help the next person who hits this.
Root cause: two columns with the same name in the SharePoint list. SharePoint permits this, but the Fabric replication component doesn't, and the result is a generic Internal system error rather than a useful message.
Worth knowing why SharePoint allows it: every column has both a display name and a fixed internal name. The UI blocks a duplicate display name at creation time, but if a column is renamed and a new one is later created using the original name, you end up with two columns that look identical to users while their internal names still differ. To check, edit a column and read the Field= value in the URL.
The diagnostic path that worked, for future reference: OperationName in the monitoring logs showed ReplicatingSchema followed by FailTable meaning the failure was at the schema stage, before any data was read. That's what narrowed it to a column definition problem rather than data volume or data types.
Also useful that you ruled out column count ~40 columns in the working lists versus 80+ in the failing ones, with no impact.
Best regards,
C Srikanth
Community Support Team