Wednesday, February 22, 2012 11:23 PM
SharePoint 2010 Enterprise with December 2011 CU 14.0.6114.5000
I'm getting errors with the FIM tool. The error status is "stopped-extension-dll-exception". I'm also trying to export pictures from user profiles to Active Directory.
Error in the event viewer:
The extensible extension returned an unsupported error.
The stack trace is:
"System.Net.WebException: The remote server returned an error: (404) Not Found.
at System.Net.WebClient.DownloadDataInternal(Uri address, WebRequest& request)
at System.Net.WebClient.DownloadData(Uri address)
at Microsoft.Office.Server.UserProfiles.ManagementAgent.ProfileImportExportExtension.DownloadPictures(ProfileChangeData profiles)
at Microsoft.Office.Server.UserProfiles.ManagementAgent.ProfileImportExportExtension.Microsoft.MetadirectoryServices.IMAExtensibleFileImport.GenerateImportFile(String fileName, String connectTo, String user, String password, ConfigParameterCollection configParameters, Boolean fFullImport, TypeDescriptionCollection types, String& customData)
Forefront Identity Manager 4.0.2450.34"
Any tips? Thanks!
Wednesday, February 22, 2012 11:41 PM
Fastest way to solve USer Profile Synchronization issues would be to stop the synch service, then restart it again(with farm account as local admin).
Thomas Balkeståhl - Technical Specialist - SharePoint - http://blksthl.wordpress.com
Thursday, February 23, 2012 1:38 AMHi Thomas, unfortunately that didn't fix it.
Friday, February 24, 2012 1:29 AM
I'm having the same issue after installing Dec 2011 Cu today... Anyone know how to fix this?
Friday, February 24, 2012 1:33 AMHi gmon16, I currently have a support ticket open with MSFT and will hopefully hear back from them tomorrow after they try to reproduce in their lab. So far, we've spent about 5 hours on the phone troubleshooting.
Friday, February 24, 2012 2:50 AM
I just installed this today and it's throwing many FIM errors. The AD import does seems to work and bring in attributes.. Please keep me posted.. i think this Dec CU has issues..
Friday, February 24, 2012 3:03 AMModeratorDid you reprovision the UPSS after installing the Dec CU?
Friday, February 24, 2012 3:11 AMwhat is that.. what do you mean.. After the install I just ran the wizard and restarted the user profile server.. Can you explain.. thanks
Friday, February 24, 2012 3:12 AMModeratorStop the User Profile Sync Service, start it up again. Restart the Central Admin Application Pool once the service is in the Started state.
Friday, February 24, 2012 3:20 AM
Yep.. did that. Stopped UPSS and restarted. Also, restarted server a few times.
Not sure what else to try
Tuesday, February 28, 2012 8:40 AM
Did you do any code for Provisioning dll and MA dll in AD side?
If yes, please make sure the extension Implemented IMVSynchronization interface.
Tuesday, February 28, 2012 5:35 PMHi Seven, I'm not sure I understand. What are the Provisioning and MA DLLs? I don't manage Active Directory but if you could give me more information about that, I can ask the proper team more specific questions. Thanks!
Tuesday, February 28, 2012 5:38 PMSo far, after almost 3 days with phone support, I've requested an escalation. This is after the support engineer said that the User Profile and Social Tagging DBs were not meant to be restored and that all my users will lose all of their personalized profile and tagging information. I said that was an unacceptable scenario. Has anyone else been able to successfully restore these databases and get the sync to work (post December 2011 CU)?
Tuesday, February 28, 2012 6:22 PM
After days of trying to figure this out, i ended up deleting the UPS service which deleted the ad connector and all the user profiles. After recreating the UPS and Ad connector I had to remap everything whihc took time, however all the problems were gone when a did a full sync. No more FIM errors
Tuesday, February 28, 2012 6:24 PMHow did you deal with the lost profile and social tagging information?
Tuesday, February 28, 2012 10:34 PMHi.. THis is a new rollout so users have not seen this yet and that made it easy.. tks
Wednesday, February 29, 2012 7:04 AM
First off, you can tell the Support engineer that they are wrong.
The UPS can be restored and are meant to be restored, what you should not restore is the synch DB, but restoring that makes no sence anyway. The actual Service App I would rebuild, but then point to the same restored databases.
You can ask the support tech about these:
Restore a User Profile Service service application (SharePoint Server 2010)
Back up a User Profile Service application (SharePoint Server 2010)
On the issue itself, read this:
SP2010: FIMSynchronizationService errors when running Profile Synchronization
SharePoint 2010 User Profile Service fails to start
From the last link you can note this: 'To resolve this issue what I did was delete the User Profile Service Application from the Service Application page and recreated it. IMPORTANT recreating the user profile servie application with exactly the same name will result in these errors reappearing so I advise that when recreating you give the service application a different name.'
I would however rebuild the whole UPS, read the entire article by Spencer Harbar(below) first, even the notes at the bottom, then give it a try. Usually following the guide gets it working.
Rational Guide to implementing SharePoint Server 2010 User Profile Synchronization
This is THE place of info on the UPS!
Thomas Balkeståhl - Technical Specialist - SharePoint - http://blog.blksthl.com
Monday, March 05, 2012 7:14 PM
Thank you for the input Thomas. I eventually found out this was an issue related to CMYK JPG images that users were uploading to their My Sites. This picture property was also set to export to AD which is for some reason incompatible with SharePoint/FIM. I wrote up a case study and troubleshooting steps here:
- Proposed As Answer by Thomas BalkeståhlMVP Monday, March 05, 2012 9:32 PM
Monday, March 05, 2012 7:31 PM
Had a nearly identical situation but I was attempting to import photos from AD. I had the same 6801, 6803 errors and FIM displayed "stopped-extenstion-dll-exception" error for the MOSS_FULLIMPORT. I used and HTTP debugger like Fiddler and traced the 404 that was causing MOSS_FULLIMPORT to fail before completing. It turned out to be a particular user's photo that SP thought existed and was looking for, but there was no associated jpg in the Photo Library. Went to the UPA's Edit User Profile for that user and found a red X next to the user's picture. Clicked the remove button, then reran a full profile sync with sucess.
Friday, March 30, 2012 6:04 PM
To find out if you have bad picture urls simply connect to your sharepoint database, find your profiles database and run this query.
SELECT RecordID, NTName, PictureUrl
fix the bad urls and update any that are blank with NULL
SET PictureUrl = NULL
WHERE (PictureUrl = N'')
Friday, March 30, 2012 6:23 PMModerator
Writing to the database directly is unsupported. Technically so is querying, but if you're going to query, always use NO LOCK.
Friday, March 30, 2012 6:59 PM
SELECT RecordID, NTName, PictureUrl
FROM UserProfile_Full WITH (NOLOCK)
but it has issues as well...(http://blogs.msdn.com/b/davidlean/archive/2009/04/06/sql-server-nolock-hint-other-poor-ideas.aspx)
If Microsoft did a little better work on the QA or provided better logging this would never be required.
Any person who has worked with SharePoint, SAP, etc has gone into the backend and manipulated data....Although unofficially supported or recommended support will offer direct database updates as solutions.
Friday, March 30, 2012 7:04 PMModerator
Only when PSS offers solutions that directly manipulate the back end is it deemed "supported" and you can call on the support case as evidence you did do something that was considered "supported". Doing it on your own will lead you to an unsupported state and if you have to call PSS, you may be having to restore the database to the point prior to the modification.
When it comes to business, going down the supported route is a lot safer.
Friday, March 30, 2012 7:16 PM
I have had the pleasure of calling our indian friends at Microsoft three times since implementing sharepoint and have yet to have them solve an issue; In every case we solved it before them. So my suggestion to anyone wanting to open a support call...Don't waste your money on regular support, pay the 80K and get a real support contract.
For those of you who are not comfortable with databases, data or SharePoint....Never do anything directly against the database as Trevor suggests. And for the rest of you always test in a development environement before attempting anything on production and backup your databases.
- Edited by dwpmartin Friday, March 30, 2012 7:17 PM
Friday, March 30, 2012 8:16 PM
$80k? Yikes, I think I like the idea of figuring it out on our own better =p
Friday, March 30, 2012 8:20 PMModeratorIt costs $80k if you want to be able to create a T3 ticket on-the-spot. Those T3 engineers are often wasted on remedial issues, unfortunately. However, your standard case (what, a few hundred?) can get escalated from T1 to T3. You just have to ask.
Tuesday, May 08, 2012 8:30 PMDid you find a solution for this issue? We are experiencing the same errors. Nothing seems to help and rebuilding the profile service is not an option.
Tuesday, May 08, 2012 9:19 PMYes see my post above