SharePointSupport

Error : We are getting below error while loading infopath form in SharePoint 2010: Solution : This has nothing to do with Infopath forms data connection or republish. We have to make an entry in HOST file for each of WFE's & adding site binding in the IIS web site for the web application having issue. This fixed the issue.

There are 3 different types of SQL Mirroring options available for use: 1. High Performance – Asynchronous (this requires the Enterprise Edition) 2. High Safety without Automatic Failover 3. High Safety with Automatic Failover (this requires a witness server running the same SQL version) All three require roughly the same steps: * Ensure the same login accounts are present on the Principal and the Mirror * Backup the Principal DB and Logs * Restore on the Mirror * Configure the Mirroring Endpoints * Set the partner on the Mirror * Set the partner on the Principal (and the witness if necessary) So lets work through the steps above…… Get our login’s in order To get our accounts in order between our two servers we can run the following SQL script to give us an output to run on our mirror. SELECT ‘create login [‘ + p.name + ‘] ‘ + case when p.type in(‘U’,’G’) then ‘from windows ‘ else ” end + ‘with ‘ + case when p.type = ‘S’ then ‘password = ‘ + master.sys.fn_varbintohe

During various search troubleshooting i came across the following crawling error in the Craw log of a SharePoint 2013 environment. Processing this item failed because of an unknown error when trying to parse its contents. (Error parsing document 'http://sharepoint.contoso.com/Project/abcd/Q_M/ABX/SitePages/Homepage.aspx'. Sandbox worker pool is closed.; ; SearchID = 820E86ZD-5252-4G5F-AK9U-2096ZV3L56PP ) In order to fix this you can try to perform the following action plan: Open "Local Policies” Click on “User rights assignment” Make sure that the search service account has the following rights: "Replace a process level token” "Adjust memory quotas for a process" "Impersonate a client after authentication" Please make sure that the policies don't get changed afterwards. After implementing the above changes please run a clear configuration cache After clearing the cache, start a full crawl and the erro

If you experience issues with WSS and MOSS timer jobs failing to complete are receiving errors trying to run psconfig, clearing the configuration cache on the farm is a possible method for resolving the issue. The config cache is where we cache configuration information (stored in the config database) on each server in the farm.  Caching the data on each server prevents us from having to make SQL calls to pull this information from the configuration database.  Sometime this data can become corrupted and needs to be cleared out and rebuilt.  If you only see a single server having issues, only clear the config cache on that server, you do not need to clear the cache on the entire farm. To do a single server, follow the steps below on just the problem server. To clear the config cache on the farm, follow these steps: 1. Stop the OWSTIMER service on ALL of the MOSS servers in the farm. 2. On the Index server, navigate to:                    Server 2008 location: Drive:\ProgramData\M

If your Usage and Health Data Collection Proxy is in a stopped state here is a quick bit of PowerShell to to get it started: $sap = Get-SPServiceApplicationProxy | where-object {$_.TypeName -eq “Usage and Health Data Collection Proxy”} $sap.Provision() The above can easily be adapted to allow you to start any Service Application Proxy. Video: service application proxy sharepoint

Partial Index Reset of a single content source This script will remove and re-add your content source's start addresses. SharePoint will more or less rebuild the index for these sources, when the next full crawl is started. $sourceName = "Local SharePoint sites" $SSA = Get-SPEnterpriseSearchServiceApplication $source = Get-SPEnterpriseSearchCrawlContentSource -Identity $sourceName -SearchApplication $SSA $startaddresses = $source.StartAddresses | ForEach-Object { $_.OriginalString } $source.StartAddresses.Clear() ForEach ($address in $startaddresses ){ $source.StartAddresses.Add($address) }

Very slow SharePoint, what can you do against it without upgrading your hardware : what you can do if your SharePoint is sometimes very slow. E.g.: on the first start of a Site Sometimes during the day a search query will take about a minute until you get results..... Just look on that article: http://support.microsoft.com/kb/2625048 it will improve your "feeled" performance (site response times) massive, if you're going to implement both solutions. Disabling CRL Check is just necessary if the SP Server does not have internet connectivity! -> that means proxy settings must be configured for the server itself http://technet.microsoft.com/de-de/library/bb430772(v=exchg.141).aspx , and your proxy must allow traffic from the server of course.

This script will list all SP Servers and restarts IIS on all of them. add-PSSnapin microsoft.sharepoint.powershell $spserver = get-spserver | ?{$_.role -eq "Application"} foreach ($server in $spserver) {     write-host "Performing IIS Reset on Server:"$server.name     iisreset $server.Name }

Add-PSSnapin microsoft.sharepoint.powershell $size = 0 foreach ($db in Get-SPContentDatabase) {     $size = $size + $db.DiskSizeRequired } $cdbs = "{0:N2}" -f($size/1gb) $ssa = Get-SPEnterpriseSearchServiceApplication $topo = $ssa | Get-SPEnterpriseSearchTopology  -Active $indexcomponent = (Get-SPEnterpriseSearchComponent -SearchTopology $topo | ?{$_.name -like "*index*"})[0] $folder = $indexcomponent.RootDirectory $indexsize = "{0:N2}" -f ((Get-ChildItem $folder -Recurse | Measure-Object -sum  Length).sum/1GB) $dbs = Get-SPDatabase cls write-host "--------------------------------------------------------------------------------------" -fore green Get-Date write-host "" write-host "--------------------------------------------------------------------------------------" -fore green write-host "SUM: Content DB Size in GB: " -NoNewline -fore White write-host $cdbs -fore Yellow write-host "-------

Error: SharePoint Crawl Log Error: The SharePoint item being crawled returned an error when attempting to download the item for example .aspx files Solution: 1.Open Regedit on your search server/s 2.Navigate to this registry key: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office Server\14.0\Search\Global\Gathering Manager . 3.Change Value “ UserAgent ” from “MSIE 4.01” to “ MSIE 8.0 ”. 4. Restart the SharePoint Search Service . 5.Open a SharePoint PowerShell 6. Get-SPSessionStateService 7.If this returns false then we need to deploy one 8. Enable-SPSessionStateService -DatabaseName “NameOfDatabase”

Domain Controller Roles A domain controller is a server that is running a version of the Windows Server® operating system and has Active Directory® Domain Services installed. Note: In Windows Server 2003 and Microsoft Windows® 2000 Server, the directory service is named Active Directory. In Windows Server 2008 R2 and WindowsServer 2008, the directory service is named Active Directory Domain Services. The rest of this topic refers to AD DS, but the information is also applicable to Active Directory. When you install Windows Server on a computer, you can choose to configure a specific server role for that computer. When you want to create a new forest, a new domain, or an additional domain controller in an existing domain, you configure the server with the role of domain controller by installing AD DS By default, a domain controller stores one domain directory partition consisting of information about the domain in which it is located, plus the schema and configuration director