Hi People, I'm not exactly sure when this started happening, but it's happening in our Dev, Test and Production environments! Dev and Test are on SP1, while production is still on the original install. I've not been able to locate any errors in the logs and I've confirmed via an LDAP query tool and doing packet captures during an AD import, that only the correct user accounts are being returned. And yet, MOSS is still holding onto all the expired/excluded accounts. This used to work just fine, but now we have about 30 accounts (and their profiles/mysites) still active, for people who have left the firm. I haven't seen the "AR_CacheCounters" issue that's been reported post SP1 (http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=2551530&SiteID=1) and I appear to have the same problem, pre and post SP1. Anyone got any ideas? Soon'ish Craig

You may have already tried, but if not, I'd try a full import. I'm not sure that an incremental import will delete anything. --Paul Galvin, Conchango RSS @ http://feeds.feedburner.com/PaulGalvinsSharepointSpace Web site @ http://paulgalvin.spaces.live.com

I am having the same error in all of my environments. I run a full profile import weekly and it doesn't solve the issue. If you go and look at your logs, you'll the MySiteCleanup is having an issue. Mine says the the domain cannot be found. I'm not sure why, since the import works fine. Here are my logs: 04/14/2008 03:37:39.24 OWSTIMER.EXE (0x0B60) 0x0B90SharePoint Portal Server User Profiles 6y3uUnexpectedMySiteCleanup: Unable to delete user profile (DOMAIN\USER1). Exception: Microsoft.Office.Server.UserProfiles.DSDomainNotFoundException: The specified domain either does not exist or could not be contacted. ---> System.ComponentModel.Win32Exception: The specified domain either does not exist or could not be contacted --- End of inner exception stack trace --- at Microsoft.Office.Server.UserProfiles.DS.ProcessDCWIn32Exception(Int32 ret, Int32 win32err) at Microsoft.Office.Server.UserProfiles.DS.GetDomainControllerInfo(String strDomain) at Microsoft.Office.Server.UserProfiles.DS.GetDCName(String strDomain) at Microsoft.Office.Server.UserProfiles.MySiteCleanupJob.IsActiveUser(LDAPConnection connLDAP, String filter, Credentials credentials) at Microsoft.Office.Server.... 04/14/2008 03:37:39.24*OWSTIMER.EXE (0x0B60) 0x0B90SharePoint Portal Server User Profiles 6y3uUnexpected...UserProfiles.MySiteCleanupJob.IsActiveUser(UserProfile up, UserProfileConfigManager upcm, String searchApplicationName) at Microsoft.Office.Server.UserProfiles.MySiteCleanupJob.ProcessPendingDeletion(String username, ServerContext context, UserProfileManager upm, UserProfileConfigManager upcm, String searchApplicationName) Any help would be appreciated. Thanks!

Hi Paul,we do an incremental at mid-day and a full at 6pm. It's not helping.I'm probably going to have to clear out all the existing profiles in our dev environment and do a full import and see how quickly it gets out of sync....I don't think the Infrastructure Update has made any difference to this issue...

Take a look at the documentation here for more information:http://technet.microsoft.com/en-us/library/ee721049(office.14).aspxhttp://technet.microsoft.com/en-us/library/ee890104(office.14).aspxhttp://technet.microsoft.com/en-us/library/ee890103(office.14).aspx

Hi Clake,that's not particularly helpful, as it's for SharePoint 2010, where the AD/Profile Syncing is quite different.Later'ishCraig

Hi Craig,Anything to be gleaned from this? .....http://blogs.msdn.com/gyorgyh/archive/2009/11/13/how-it-works-moss-2007-automatic-user-profile-removal.aspxIf it's not able to access AD maybe the accounts are screwed up?

Hey Tom,that's a great article. I've gone through and double checked and because we're getting new/updated users, I don't think AD access is the issue.I've also gone and checked a couple of recent departures and they seem OK, though another one hadn't been updated to reflect that they'd left the firm (my AD filter is based on enabled accounts that have a phone extension), so there was one still turning up...So it looks like it's behaving currently (I have the Oct 09 CU installed, not Dec 09), so a patch may have cleaned it up.Next time I get a compaint that a departed user is still on the system, I'll have to look through this again.Thanks!Later'ishCraig