Come see me at: SRC 102 – FAST for SharePoint 2:00 – 3:15 http://www.sharepointfest.com
Archive for September, 2010
http://channel9.msdn.com/shows/Identity/Sharepoint-2010-and-Claims-Based-Identity/
When it comes to identity management intensive applications, it’s hard to top Sharepoint. Whether you are signing in a portal, accessing a document or using a webpart for reaching out to external web services, your identity is going to be the factor that drives it all.
Vittorio went to visit Venky Veeraraghavan, Program Manager Lead in the Sharepoint team, to discuss how Sharepoint deals with identity challenges. Venky gives a fantastic explanation of how claims-based identity and Windows Identity Foundation helped the Sharepoint team to deliver on the identity functionalities they needed without getting entangled in low level details such as protocol handling.
Tune in!
This error occurred when clicking “FAST Search Keywords” within the site collection.
Error from ULS Logging :
Admin OM Exception occurred. Message: Failed to communicate with the WCF service. , Error Code:e107, Stacktrace:Microsoft.SharePoint.Search.Extended.Administration.Common.AdminException: Failed to communicate with the WCF service. —> System.ServiceModel.FaultException`1[System.ServiceModel.ExceptionDetail]: The trust relationship between the primary domain and the trusted domain failed. (Fault Detail is equal to An ExceptionDetail, likely created by IncludeExceptionDetailInFaults=true, whose value is: System.SystemException: The trust relationship between the primary domain and the trusted domain failed. at System.Security.Principal.NTAccount.TranslateToSids(IdentityReferenceCollection sourceAccounts, Boolean& someFailed) at System.Security.Principal.NTAccount.Translate(IdentityReferenceCollection sourceAccounts, Type targetType, Boolean forceSuccess) at System.Security.Permissions.IDRole.get_Sid() at System.Security.Permissions.PrincipalPermission.Demand() at System.Security.PermissionSet.DemandNonCAS() at Microsoft.SharePoint.Search.Extended.Administration.WCF.KeywordServiceImpl.GetNamedSearchSettingGroup(String name) at SyncInvokeGetNamedSearchSettingGroup(Object , Object[] , Object[] ) at System.ServiceModel.Dispatcher.SyncMethodInvoker.Invoke(Object instance, Object[] inputs, Object[]& outputs) at System.ServiceModel.Dispatcher.DispatchOperationRuntime.InvokeBegin(MessageR…). — End of inner exception stack trace — at Microsoft.SharePoint.Search.Extended.Administration.WCF.ServiceClientExceptionHandler.TranslateException(Exception e) at Microsoft.SharePoint.Search.Extended.Administration.Common.ServiceClientExceptionHandlingInterceptor.Execute[T](Func`1 target, String errorCode, String[] values) at Microsoft.SharePoint.Search.Extended.Administration.Common.ServiceClientExceptionHandlingInterceptor.Execute[T](Func`1 target) at Microsoft.SharePoint.Search.Extended.Administration.WCFClient.SearchSettingGroupCollectionImplWCF.GetSearchSettingGroup(String groupName) at Microsoft.SharePoint.Search.Extended.Administration.WCFClient.SearchSettingGroupCollectionImplWCF.ContainsSearchSettingGroup(String groupName) at Microsoft.Office.Server.Search.Extended.Administration.Facade.AdminOMHelperBase..ctor(String siteID) at Microsoft.Office.Server.Search.Extended.Administration.Facade.KeywordHelper..ctor(String siteId) at Microsoft.Office.Server.Search.Extended.Administration.Internal.UI.ContextualKeywordManagement.OnLoad(EventArgs e)
Resolution :
This customer had both DNS issues with the domain controllers in there development environment and they had inactive trusts that remained due to an old company merger.
