We just completed a migration of a SharePoint 2007 SP2 Feb 2010 CU farm from one domain to another (two way trust between them). Search is working fine, as is profile import. However, in the ULS logs I'm getting this error every few seconds: w3wp.exe (0x1E24) 0x033C Windows SharePoint Services General 72o9 High loadDomainGroupMapFromDb, insertRecord failed Any ideas on what this means? The only other odd error that came before this one was: w3wp.exe (0x1E24) 0x1FB0 Windows SharePoint Services General 72e1 High Unable to get domain DNS or forest DNS for domain NT AUTHORITY. ErrorCode=1212 http://sharepoint.nauplius.net

Search engine brought me the following post sharing similar error message “Unable to get domain DNS or forest DNS for domain NT AUTHORITY. ErrorCode=1212”: http://social.technet.microsoft.com/forums/en-US/sharepointgeneral/thread/f09bcb5e-ecd0-4b9d-9ff3-4b1b5d46ae31 they suggested to update the farm account in it. I found no systematical troubleshooting approach to trace back from the error message because my knowledge in this Active Directory communication area is limited. What kind of migration procedure did you follow? Created a new farm (new configuration database) and attached the content database or migrated with the old configuration database? Here is a hub for common migrating steps: http://technet.microsoft.com/en-us/library/cc288664.aspx; Here is a blog about migrating users: http://blogs.technet.com/mhass/archive/2006/02/15/419657.aspx Gu Yuming TechNet Subscriber Support in forum If you have any feedback on our support, please contact tngfb@microsoft.com

Created a new farm in the new domain, restored a full SharePoint farm backup from old domain, properly configured what needed to be configured (new farm accounts, etc.), then a few days later detached content databases, took BAKs of content databaes from old domain, and attached them to the new farm.http://sharepoint.nauplius.net

According to the Recovering the configuration database and Central Administration content database section in http://technet.microsoft.com/en-us/library/cc287880.aspx : Important: Although the configuration database and Central Administration content database can be backed up, restoring backups of the configuration database and Central Administration content database taken from a running farm by using the tools built in to SharePoint Products and Technologies or SQL Server is not supported. This is because data in these databases may not be synchronized with data in other Office SharePoint Server 2007 or Windows SharePoint Services 3.0 databases. Therefore, the tools built in to SharePoint Products and Technologies do not recover these databases during a farm-level restore operation. If this data is not synchronized, users might experience various random errors. For more information, see Microsoft Knowledge Base article 948725: Restoration of the configuration database is not supported in SharePoint Server 2007 and in Windows SharePoint Services 3.0 (http://go.microsoft.com/fwlink/?LinkId=117755&clcid=0x409). So, you’d better create a new farm (configuration database) in the new domain. SharePoint 2010 has improvement in this aspect, please read http://technet.microsoft.com/en-us/library/ee428326(office.14).aspx Gu Yuming TechNet Subscriber Support in forum If you have any feedback on our support, please contact tngfb@microsoft.com

That is exactly what we did. We created a new farm, restored from a farm backup using a new configuration, then later on restored over web application content databases only to move the new farm into production.http://sharepoint.nauplius.net

Sorry for the delay. What about current situation? Search is working fine, as is profile import Could you please share with us how did you migrate your SSP? Create a new SSP from scratch or restored from the SSP backup? Gu Yuming TechNet Subscriber Support in forum If you have any feedback on our support, please contact tngfb@microsoft.com

We restored the SSP from backup.http://sharepoint.nauplius.net