"...their vision has been instrumental in our adoption of these technologies before they become buzzwords." - Network Manager at Nelson Mullins
"I would simply say that they do the work you need and do it very well." - Director of IT at Piedmont Healthcare
"Not only are the eGroup engineers extremely good, they have all been able to fit in with my existing staff and build relationships that are beneficial for all of our projects." - VP and CIO, Beaufort Memorial Hospital
We called around to other companies to see who they used and over and over the name eGroup was given. After the first meeting, I knew they had the knowledge and staff to meet our needs." - IT Director, MCAngus, Goudelocke and Courie
"I was skeptical about the amount of work they wanted to do in a short amount of time. But we were able to get it all accomplished in less time than they expected. Totally blew us away." - IT Manager, Horry Electric Cooperative
"With their expertise at our disposal, it is like having additional staff on hand. They have never made us feel like we were just another client. More like colleagues." - IT Manager, Horry Electric Cooperative
I installed SharePoint 2010 Service Pack 1 and the June 2011 CU tonight on a fairly new farm, but with a complicated User Profile Synchronization configuration. After installing the patches, everything appeared to work fine.
However, when I went to do a Full User Profile Sync, I saw some of these errors…
System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. —> System.PlatformNotSupportedException: Microsoft SharePoint is not supported with version 4.0.30319.225 of the Microsoft .Net Runtime.
Cannot open the FIM Synchronization Service database because the database schema version in existing database does not match the required version.
The solution? Uninstall .NET 4 Extended Properties and Client Profiles and reboot! No more errors!
SharePoint’s User Profile Synchronization service is by FAR it’s most complicated and painful part to deal with. It is a bear to setup, modify, and maintain. To add to that, if you are importing supplemental User Profile Properties from a BCS connection, like SQL, then you should know that importing URL and Person data types are not supported.
For example, if you have a SQL Table with a “Manager” field in it; you cannot import that field into the “Manager” Profile Property in SharePoint. There is a very ugly and unsupported way of doing this here, but I would not recommend it.
The best solutions?
1. Import these fields directly into AD from whatever connection your BCS connection is pulling from. This is fairly simple when using Microsoft’s AD API.
2. Create a Timer Job Definition that uses the BCS connection to get the Profile Properties from SQL and then use the SharePoint API to manually set the properties on each user’s profile.
Office 2010 and SharePoint 2010 allow you to edit documents at the same time. Just select ‘Edit in Microsoft [Word, Excel, etc]‘ in the context menu of the document that you want to edit and you will be collaborating with any other users that are using that document.
I recently setup a User Profile Synchronization service to sync with AD and then use BCS for supplemental profile properties. I ran into several issues with the User Profile Synchronization service. Here are a few errors and the solutions for them…
Events 1001, 1004, and 1015
Errors
• The resource ‘C:Program FilesMicrosoft Office Servers14.0SQLDatabaseSettings.sql’ does not exist.
• The resource ‘C:Program FilesMicrosoft Office Servers14.0ServiceMicrosoft.ResourceManagement.Service.exe’ does not exist.
• Detection of product ‘{90140000-104C-0000-1000-0000000FF1CE}’, feature ‘PeopleILM’ failed during request for component ‘{9AE4D8E0-D3F6-47A8-8FAE-38496FE32FF5}’
• Failed to connect to server. Error: 0×80070005
Solution
• The WMI service uses the Network Service account to access these resources, but the Network Service account does not have access to them.
• Give the Network Service Read & Execute permissions on the following folders…
BAIL: MMS(7824): eafam.cpp(1295): 0×80230304 (The image or dimage already has an attribute with that name.)
BAIL: MMS(7824): eafam.cpp(943): 0×80230304 (The image or dimage already has an attribute with that name.)
BAIL: MMS(7824): eafam.cpp(1010): 0×80230304 (The image or dimage already has an attribute with that name.)
BAIL: MMS(7824): amexec.cpp(1630): 0×80230304 (The image or dimage already has an attribute with that name.)
BAIL: MMS(7824): amexec.cpp(2018): 0×80230304 (The image or dimage already has an attribute with that name.)
BAIL: MMS(7824): eaf.cpp(1373): 0×80230304 (The image or dimage already has an attribute with that name.)
BAIL: MMS(7824): eaf.cpp(653): 0×80230304 (The image or dimage already has an attribute with that name.)
ERR: MMS(7824): synccoreimp.cpp(5211): 0×80230304 – export-flow failed 0×80230304
BAIL: MMS(7824): synccoreimp.cpp(5212): 0×80230304 (The image or dimage already has an attribute with that name.)
BAIL: MMS(7824): synccoreimp.cpp(4816): 0×80230304 (The image or dimage already has an attribute with that name.)
BAIL: MMS(7824): synccoreimp.cpp(10567): 0×80230304 (The image or dimage already has an attribute with that name.)
BAIL: MMS(7824): synccoreimp.cpp(10313): 0×80230304 (The image or dimage already has an attribute with that name.)
BAIL: MMS(7824): synccoreimp.cpp(2524): 0×80230304 (The image or dimage already has an attribute with that name.)
BAIL: MMS(7824): synccoreimp.cpp(4333): 0×80230304 (The image or dimage already has an attribute with that name.)
BAIL: MMS(7824): synccoreimp.cpp(8485): 0×80230304 (The image or dimage already has an attribute with that name.)
BAIL: MMS(7824): synccoreimp.cpp(3802): 0×80230304 (The image or dimage already has an attribute with that name.)
ERR: MMS(7824): synccoreimp.cpp(3818): 0×80230304 – CS to MV to CS synchronization failed 0×80230304: [CN=Doe\, John,OU=Contractors,OU=DE,DC=MYDOM,DC=com]
BAIL: MMS(7824): synccoreimp.cpp(3623): 0×80230304 (The image or dimage already has an attribute with that name.)
ERR: MMS(7824): syncmonitor.cpp(2512): SE: Rollback SQL transaction for: 0×80230304
Solution
This error occurs when you have 2 sources mapped to the same Profile Property
To fix, change the Policy for the property to ‘Optional’. See this blog post for more info.
If that still doesn’t work, then this forum post explains how to use the miisclient.exe to fix sync issues
MSDTC Error
Errors
• System.Transactions.TransactionManagerCommunicationException: Network access for Distributed Transaction Manager (MSDTC) has been disabled. Please enable DTC for network access in the security configuration for MSDTC using the Component Services Administrative tool. —> System.Runtime.InteropServices.COMException (0x8004D024): The transaction manager has disabled its support for remote/network transactions. (Exception from HRESULT: 0x8004D024)
Solution
• Here is a blog post that gives a step-by-step on how to resolve this.
• Here are the basic steps on what to do. Control Panel – Administrative Tools – Component Services – My Computer properties – MSDTC tab – Security Configuration tab – Network DTC Access (checked) / Allow Remote Clients (checked) / Allow Inbound (checked) / Allow Outbound (checked) / Enable TIP Transactions (checked)
• Improved support for Internet Explorer 9.
• Recycle bin: Lets you restore a site collection or a web that was deleted.
• Remote Backup Systems (RBS) and shallow copy can decrease downtime and increase efficiency by moving pointers to databases instead of moving databases.
• You can see which folders are taking up valuable space with the improved Storage Management feature in site settings.
• Support for Microsoft SQL Server 2011.
• A more robust Search Host Distribution service that improves error recovery and performance during the search crawl.
• Adds backup and restore functionality to recover deleted site collections and webs.
• Improved support for Internet Explorer 9.
• Recycle bin: Lets you restore a site collection or a web that was deleted.
• Remote Backup Systems (RBS) and shallow copy can decrease downtime and increase efficiency by moving pointers to databases instead of moving databases.
• You can see which folders are taking up valuable space with the improved Storage Management feature in site settings.
• Support for Microsoft SQL Server 2011.
• The Project Web App now supports all the SharePoint supported browsers in team member scenarios. The scenarios include timesheeting, my tasks, issues/risks, and the homepage.
• Fixed work and effort driven tasks can now be edited in the schedule Web Part
• Manually scheduled tasks now support timephased edits in the timesheet, and usage views in the Project Web App and Project 2010.
• Lets users search within PPSX files.
• Scopes can be displayed in the correct language for non-English tenants, not just in English tenants.
• Lets you use host-header site collections and crawl targets together.
• An Order By clause can return results from multiple query components.
• Turkish locale users who have SharePoint installed can search for any string in offline SharePoint help.
• OpenDocument Format (ODF) support:
• Lets you view and edit ODF documents in Office Web Apps.
• Lets you use Office Web Apps with the Google Chrome browser.
• Outlook Web App document attachment viewing (for Exchange Online only):
• Lets you view Office document attachments in the browser directly from Outlook Web App.
• Lets you use Office Web Apps with Internet Explorer 9 in Native mode.
Word Web App
Lets you print Word documents from Edit mode (in addition to View mode).
Excel Web App
• Added a Close button.
• Lets you insert charts in Excel Web App.
• Lets you copy and paste values and formulas by dragging the fill handle.
PowerPoint Web App
• Lets you print presentations from PowerPoint Web App.
• Lets you edit text in more shapes, not just placeholder shapes.
• Lets you insert clip art in PowerPoint Web App. (By default clip art support is disabled. An administrator can decide to enable it.)
