SharePointSupport

Issue: SharePoint 2010 Query component is at initializing state. Found the following error in the event log: Component ff097580-80b1-4d0d-9e94-9cf122327c00-query-0 of search application 'Search Service App' has failed to execute transition sequence 'initialize with empty catalog' due to the following  error: System.ComponentModel.Win32Exception: The Server service is not started    at Microsoft.SharePoint.Win32.SPNetApi32.DeleteFileShare(String name)    at Microsoft.SharePoint.Win32.SPNetApi32.CreateFileShare(String name, String description, String path)    at Microsoft.SharePoint.Administration.SPServer.CreateFileShare(String name, String description, String path)    at Microsoft.Office.Server.Search.Administration.QueryComponent.CreatePropagationShare(QueryComponent component)    at Microsoft.Office.Server.Search.Administration.QueryComponent.ExecuteCurrentStage(). It is now in state Uninitialized. Fix: Ensure the “ Server ” servi

Issue : Unable to open the Timer Job Definition in the Central Administration "Unknown Error". Cause: Was able to browse through the Job History and the status. Found that there were couple of timer jobs stuck from 2 months and causing this issue.  Fix: Ran the " stsadm -o exeadmsvcjobs ", but still the error was persist and the jobs were not getting removed. Ran the following commands and removed the stuck jobs: Get-SPTimerJob | ? {$_.Displayname -like “Name”} $job = Get-SPTimerJob -id "" $job.Delete()

ERROR MESSAGE:  1. Error on Server status for query server in Search Administration. 2. While search getting error " The search request was unable to connect to the Search Service. " RESOLUTION: Accessed the URL from the Index server https://queryservername:56738/SharedServices1(whatever_ssp_name_is)/Search/Searchadmin.asmx and got 404 page cannot be found error. The Port Number 56737, 56738 was not opened between the Index & Query servers. Got the port opened between the INdex & Query servers and the error message on Search Administration  got disappeared. But still we were not able to propagate the content. Found that the TCP/UDP 445 port number was not opened between the servers. Got the ports opened between servers and the Indexed items got propagated successfully. We were able to search on the website without any error.

Issue: Unable to add user properties for user profile connection. Getting Unable to process Create message error in the event log and ULS logs. Error’s in the event log and ULS Logs: OWSTIMER.EXE (0x075C)            0x0DD4 SharePoint Portal Server User Profiles      9q17     High            UserProfileApplication.SynchronizeMIIS: Failed to configure ILM MA, will attempt during next rerun. Exception: Microsoft.ResourceManagement.WebServices.Faults.ServiceFaultException: Unable to process Put message     at Microsoft.ResourceManagement.WebServices.Client.Resource.Update()     at Microsoft.ResourceManagement.WebServices.ResourceManager.UpdateResource()     at Microsoft.Office.Server.UserProfiles.Synchronization.ILMMAConfiguration. UpdateSQLConnectionInformation(String server, String databaseName, String user, String domain, SecureString password)     at Microsoft.Office.Server.UserProfiles.UserProfileConfigManager.UpdateILMMA(String databaseServerIlm, String da

Today I was helping one of my customer with creating the UPS sync connection on SharePoint 2010 environment and ran into the below errors, after going through all the dramas I was able to found the cause and fix it. Thought of sharing it with all: SharePoint Errors: ERROR Unable to process Create message In the Application event log: Source: Forefront Identity Manager Event ID: 3 Microsoft.ResourceManagement: System.InvalidOperationException: Retrieve schema failed at Microsoft.ResourceManagement.Utilities.ExceptionManager.ThrowException(Exception exception) at Microsoft.ResourceManagement.ActionProcessor.SyncConfigActionProcessor.Create(String typeName, IList`1 createParameters, Guid creator, Guid cause) at Microsoft.ResourceManagement.ActionProcessor.SyncConfigActionProcessor.ProcessInputRequest(RequestType request) at Microsoft.ResourceManagement.ActionProcessor.ActionDispatcher.ProcessInputRequest(RequestType request) at Microsoft.ResourceMana

Issue An exception is thrown when retrieving a user profile: Microsoft.Office.Server.UserProfiles.UserNotFoundException was unhandled   Message=An error was encountered while retrieving the user profile.   Source=Microsoft.Office.Server.UserProfiles   StackTrace:        at Microsoft.Office.Server.UserProfiles.UserProfileCache.GetUserData(UserProfileManager objManager, Nullable`1 recordId, Guid gAcct, String strAcct, Byte[] bSid, String strEmail, Boolean doNotResolveToMasterAccount)        at Microsoft.Office.Server.UserProfiles.UserProfile.RetrieveUser(String strAcct, Guid gAcct, Byte[] bSid, Nullable`1 recordId, Boolean doNotResolveToMasterAccount, Boolean loadFullProfile)        at Microsoft.Office.Server.UserProfiles.UserProfile..ctor(UserProfileManager objManager, String strAcct, Boolean doNotResolveToMasterAccount, Boolean forceUserIsSelf, Boolean loadFullProfile)        at Microsoft.Office.Server.UserProfiles.UserProfileManager.GetUserProfile(String strAcco

Create the My Site Web Application We begin by first creating a Web Application that house our My Site. Navigate to  *  Go to Central Administration  * Select Application Management  * Create a New Web Applications Authentication: Classic Mode Authentication IIS Web Site: SharePoint – My Site Authentication Provider: NTLM Public URL: http://mysite.spdev.local:120/ Application Pool: SharePoint – My Site Configurable user : DOMAIN\SPMYSITEACC Database Name and Authentication: WSS_Content_MYSITE  Create the My Site Host Site Collection Now that we have successfully created our My Site Web Application, we can now proceed to create our My Site Host Site Collection. This will be the top level site that will house our individual user’s site collections. Navigate to * Central Administration * Application Management * Create site collections Ensure that the recently created My Site Web Application is selected, enter in a Title and click select the My

Introduction The User Profile Synchronization service can take up to ten minutes to start. The User Profile Synchronization service is successfully started when:   * The User Profile Synchronization service has a status of Started on the Services on Server page in Central Administration.   * The Forefront Identity Manager Service and the Forefront Identity Manager Synchronization Service have a status of Started in the Services Microsoft Management Console. Both services run using the farm account. Issue The status of the User Profile Synchronization service is still Starting/Stopped even after waiting for a long time. Checking the Event Application Logs (Windows Logs > Application) reveals a 1004 error. Cause The Network Service account does not have sufficient rights to the folder %programfiles%\Microsoft Office Servers\14.0 Resolution Grant Read/Write Permission for the user “ NETWORK SERVICE ” for the folder  %programfiles%\Microsof

BDC = SharePoint 2007 BCS = SharePoint 2010 * BCS is new in SharePoint2010 and stands for Business connectivity Services. Using BCS one can read and write into the external Database. * In BDC, one can only perform the reading from external Database BCS Architecture  BDC Metadata Store – The BDC Metadata Store provides storage for a collection of external content types, each of which describes how to connect to the external store. The Metadata Store acts as part of the services layer. External content types are a fundamental building block of BCS. BDC Server Runtime – The BDC Server Runtime understands how to reach into the back-end store and connect to data based on the external content types defined within the content type store. It’s important to note the new usage of the acronym BDC to refer to the set of services that provides connectivity that is a component of BCS. Security – BCS provides integration with the Secure Store Service (SSS), as well as

Debug Mode Developer use debug mode for debugging the web application on live/local server. Debug mode allow developers to break the execution of program using interrupt 3 and step through the code. Debug mode has below features: * Less optimized code * Some additional instructions are added to enable the developer to set a breakpoint on every source code line. * More memory is used by the source code at runtime. * Scripts & images downloaded by webresource.axd are not cached. * It has big size, and runs slower. Release Mode Developer use release mode for final deployment of source code on live server. Release mode dlls contain optimized code and it is for customers. Release mode has below features: * More optimized code * Some additional instructions are removed and developer can’t set a breakpoint on every source code line. * Less memory is used by the source code at runtime. * Scripts & images downloaded by webresource.axd are cached. * It has small s

This Explains how to plan user profiles for server-to-server authentication in SharePoint Server 2013. * Server-to-server authentication allows for servers that are capable of server-to-server authentication to access and request resources from one another on behalf of users. Therefore, the server that runs SharePoint Server 2013 and that services the incoming resource request must be able to complete two tasks: Resolve the request to a specific SharePoint user Determine the set of role claims that are associated with the user, a process known as rehydrating the user’s identity * To rehydrate a user’s identity, a server that can perform server-to-server authentication requests access to SharePoint resources. SharePoint Server 2013 takes the claims from the incoming security token and resolves it to a specific SharePoint user. * By default, SharePoint Server 2013 uses the built-in User Profile service application to resolve the identity. The key user attri

SharePoint generates multiple log types. Logs in SharePoint require three basic steps like all other logs: Logging, Processing and  Reporting . * The logging can take place to file locations on front-end server s or to the associated content databases for each Site Collection s (including SSP). * Processing happens via Timer Jobs on the front end servers and the SSP server (if different) using the Timer Service at various configurable intervals. * Reports are available via the web browser at Site, Site Collection, Web Application or Farm Level. MOM packs are available both for WSS 3.0 and MOSS 2007 and help administrators in maintaining the entire farm from a centrel location. All file based logs can be read by text editors and can be parsed by using popular log parsing tools ( Log Parser 2.2 from Microsoft or Funnel Web). It will also be a good idea to read the IIS Logs which are generally saved at  (System Drive):\ WINDOWS\system32\LogFiles a) Diagnostics Logs ·  Event

Getting Started Planning Upgrade Security Governance Deployment Social Business Intelligence Web Content Management Search Other Technologies Composites Performance and Capacity Planning Additional Resources Getting Started Getting Started with Enterprise Search in SharePoint 2010 Products http://technet.microsoft.com/en-us/library/ff631149.aspx Planning Evaluation Guide for SharePoint Server 2010 http://technet.microsoft.com/en-us/library/cc262881.aspx SharePoint Server 2010 Usage Best Practices http://www.microsoft.com/downloads/en/details.aspx?FamilyID=5c562f71-3aa9-46fd-abac-7d381813f2b8 Sharepoint Server 2010 Adoption Best Practices http://www.microsoft.com/downloads/en/details.aspx?FamilyID=94ee6518-75f7-47be-b4c1-0d6ec1248486 SharePoint Server 2010 Enterprise Search Evaluation Guide http://technet.microsoft.com/en-us/library/ff631150.aspx Best Practices for using Fine-Grained Permissions http://technet.microsoft.com/en-us/librar

Use Windows PowerShell to administer SharePoint 2013 Windows PowerShell Documentation on TechNet This section of the TechNet Library contains web copies of the core Windows PowerShell Get-Help topics. The section also has web copies of the Windows PowerShell Getting Started document, the PowerShell.exe help, and a Windows PowerShell primer. Scripting With Windows PowerShell The home page for Windows PowerShell scripting learning resources. Windows PowerShell Owner's Manual web-based guide for getting started with Windows PowerShell. Windows PowerShell Quick Reference Downloadable copy of the Quick Reference document that is installed with Windows PowerShell. As you read these resources, consider that the following concepts and cmdlets are useful ones to learn before you use Windows PowerShell for SharePoint 2013: Get-Command Get-Member Get-Help Aliasing Piping and the Pipeline in Windows PowerShell Cmdlet Pa