Patty

Look in your servers event logs and you should find an error/warning about a site exceeding qouta (Sorry don’t have the exact event format at hand).
Execute stsadm -o enumallwebs and save it’s output to a file.
Take the Site GUID listed in the event error and search for it in the enumallwebs output and you should be able to pinpoint the problem site

I am trying to migrate groups using SPFarm.MigrateGroup but am getting the dreaded “Your changes could not be saved because this SharePoint Web site has exceeded the storage quota limit” error. Is there any way to capture what site is sending back this error? I think it’s being caused because it’s trying to change a group that has access to all of our MySites, and it’s hitting a MySite that is at its storage limit. The thing is, we have thousands of these and I don’t know which one is causing it. Is there any way to get under the hood of MigrateGroup()?

Thanks,
Patty

The migrated accounts appear to have the correct access, however we would like to have display names correct for housekeeping.

Someone else told me to try Stsadm Migrateuser command on the test server.

I created a user (with the same login names etc. as was on Live AD) and execute the following commands on my test server as:
stsadm -o migrateuser -oldlogin abc.local/s.wilton -newlog
abc.local/s.wilton -ignoresidhistory

Also, tried with a Temporary account with ignoreSid flag but the error is same as below

Error Message in both cases: “Cannot Complete the Action”

Please, I desperately need a solution as the deadline is approaching fast I am stuck with AD users problem from quite sometime. Please suggest me what’s the easiest possible way to migrate users from Live AD to Test AD or do something that my application start recognizing those users.