Hi, We are getting the following regularly on our Sharepoint 2007 web application server: Event Type: Error Event Source: Office SharePoint Server Event Category: User Profiles Event ID: 5553 Date: <date> Time: <time> User: N/A Computer: <machinename> Description: failure trying to synch site <siteID> for ContentDB <contentDBID> WebApp <webAppID> Exception message was The SID structure could not be converted to string SID. The Win32 API call failed.. The content DB was moved over to a new farm running Sharepoint 2007 SP2 on W2k8R2 with no post SP2 updates applied. I did run the preparetomove operation before we removed the content DBs from the old server, and then I read about the preparetomove operation causing other issues. I did notice that the move flag was set on the relevant sites, so I ran the -undo command, and now all the sites are not marked as being moved. This is causing AD information and Sharepoint memberships not to be reflected in the web apps themselves. Any suggestions? Thanks. Andrew. Andrew Hodgson

Hi, From your symptom, there are several reasons for this issue: firstly, if one user profile were corrupt and mapped against the wrong my site. The resolution were to delete the profile entry and start the full profile sync, optional you can delete the affected My site. Secondly, corruption in SSP could also result in this issue. The resolution is to create new SSP and set to default. Thanks, Rock Wang TechNet Subscriber Support in forum If you have any feedback on our support, please contact tnmff@microsoft.com.Regards, Rock Wang Microsoft Online Community Support

Hi, Thanks, I will try and delete my MySite to see if it fixes the issue. I should also point out that when I run the command stsadm -o sync -listolddatabases 0, I am getting my content DB listed there as the only item in the list. Thanks. Andrew.Andrew Hodgson

Hi, From you reply, you had run the stsadm -o sync -listolddatabases 0, and you got your content DB listed there as the only item in the list. You can run stsadm -o sync –deleteolddatabases 0, then check the effect. For more information about sync : stsadm operation, check out this article. Thanks, Rock Wang Forum Support Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com. Regards, Rock Wang Microsoft Online Community Support

Hi, I did run the sync -deleteolddatabases 0, however, the content DB comes back as the only database after the next sync. Thanks. Andrew.Andrew Hodgson

Hi all, Sorry to re-open this thread but I have a solution to this problem and a question. Whilst trying to do some other code I came across the same issue which we had hanging around and needed to get it fixed. I did some more debugging of the code and came across another error which pointed me at this article: http://salascz.wordpress.com/2011/09/14/sharepoint-the-sid-structure-could-not-be-converted-to-string-sid/ If you look at the Shared Services database in the table "UserProfileValue" look at the property for the SID which is 2, some of the user accounts have a NULL SID. If you look at the table "UserProfile_Full" then the SID is present. I ran the query on the blog against our SSP: --[ USE OUR SSP DB / USERS PROFILE DB ] --[ RESULT SHOULD BE EMPTY ] SELECT p.RecordId, p.UserId, p.SID, d.PropertyVal AS 'SID in properties', p.NTName, p.PreferredName, p.LastUserUpdate, p.Lastimported FROM UserProfile_Full p INNER JOIN UserProfileValue d ON p.RecordId = d.RecordId WHERE d.PropertyID = 2 AND d.PropertyVal IS NULL Sure enough I got several hits back. I deleted all the profiles that were listed in this table using the SSP admin, and once all the profiles were gone user syncs started working again (joy!) However, once a full crawl of the AD is done we get several users back in this situation again. If I look more closely at the AD import, I can see that the import looks to finish successfully, but if we look at the last message received in the SSP we are getting the error "The Parameter is incorrect." Has anyone seen this before and knows what it may be to do with? Thanks. Andrew.Andrew Hodgson