When copying from DB connection at site level, migrations job may fail with the following error:
HResult:-2146233080
1) Don't include permissions for migrations running from Database connection adapter - deselect all options under "Permissions Options" tab as shown below:
2) Then, migrate permissions from SharePoint connection (Metalogix Extensions Web Service) in a separate action as explained in this here.
To identify the underlying group(s) causing this behavior..
1) Get the site id of your site from site properties in Content Matrix as shown in this screenshot:
2) Replace $SiteId$ in the following SQL queries with the site ID from the above step, and execute the queries against your content database in SQL server management studio (SSMS).
Query 1: Returns a list of all the groups from "Groups" table:
Select G.ID, G.Title, G.Description, G.Owner, G.OwnerIsUser, G2.Title as GroupOwnerName, U.tp_Login as UserOwnerLogin, G.Flags, G.RequestEmail from (Groups G WITH (NOLOCK) join UserInfo U WITH (NOLOCK) on (((G.OwnerIsUser=1 and G.Owner=U.tp_ID) or (G.OwnerIsUser=0 and G.OwnerIsUser+1=U.tp_ID)) and G.SiteId=U.tp_SiteId) join Groups G2 WITH (NOLOCK) on (((G.OwnerIsUser=0 and G.Owner=G2.ID)or (G.OwnerIsUser=1 and G.ID=G2.ID)) and G.SiteId = G2.SiteId)) Where G.SiteId='$SiteId$' Order By G.ID
Query 2: Returns a list of all the groups referenced in the "AllUserData" table:
SELECT G.ID, AUD.ntext2 FROM AllUserData AUD WITH (NOLOCK) JOIN GROUPS G WITH (NOLOCK) ON G.ID = AUD.tp_ID AND G.SiteId = AUD.tp_SiteId WHERE AUD.tp_SiteId = '$SiteId$' AND AUD.tp_ListId = (SELECT tp_ID FROM AllLists WITH (NOLOCK) WHERE tp_SiteId = '$SiteId$' AND tp_ServerTemplate = 112) ORDER BY AUD.tp_ID
3) Compare both the results using values in the first column which is the Group ID, to identify the missing Group IDs in the second list. Then, see if you can navigate to that group in your SharePoint site, update the description and save it.
4) Run the second query again to see if the record got written to the "AllUserData" table
Note:
If the group fails to load in SharePoint or if the corresponding record is not getting created in the "AllUserData" table, you should take appropriate corrective actions to fix this anomaly in the database. Note that any changes to live content databases could void your Microsoft warranty. Any corrective actions should performed on copies of the database outside of SharePoint with advice from Microsoft.
Disclaimer
Quest assumes no liabilities of misunderstanding or misinterpretation of the information discussed in this article. The information is meant for providing insights to expert users of SharePoint operating under the guidance of Microsoft inline with Microsoft's License Agreement.
© ALL RIGHTS RESERVED. Feedback Terms of Use Privacy Cookie Preference Center