@gogi100 This issue may be caused by some legacy lists or fields.
To resolve this issue, as you cannot find them via UI, you can try to remove them via PowerShell.
To remove a legacy list, you can use the following cmdlets:
Add-PSSnapin Microsoft.SharePoint.Powershell -ErrorAction SilentlyContinue
Get-SPWeb "http://YourWebURL" | Where-Object { $_.Lists.Delete([System.Guid]"{8a0aa5b1-3dd2-4b89-8d94-a4a6a7b336c1}") }
Note: you need to change the GUID to your owns in the error message.
To remove a legacy field, you can use the following cmdlets:
Add-PSSnapin Microsoft.SharePoint.Powershell -ErrorAction SilentlyContinue
$Web = Get-SPWeb "http://YourWebURL/"
foreach ($field in $web.Fields)
{
if($field.Id -eq "43de0d0f-d9fc-46dd-ab43-19f8b9d219c1")
{
$field.Delete()
write-output “Title: $($field.Title) | ID: $($field.Id) has deleted”
}
}
$web.Dispose()
Note: you need to change the GUID of the above cmdlets to your field GUID in the error message.
Result is like:
After removing these problematic lists and fields, re-save the site template again and create a new site using the new site template. Please have a try and let's know the result. :)
If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.