Monday 1 January 2018

SP2016 Installation Issue

SharePoint 2016  . PSCONFIG Failed during creation of CONFIG DB


SYMPTOMS
==========
SharePoint server 2016 is installed but while running the PSCONFIG 
we are getting an error while creating the configuration DB.


ERR     LookupAccountName failed to get the SID for account @@@@@@@@@@@

ERR     An exception of type System.ComponentModel.Win32Exception was thrown. 
 Additional exception information: No mapping between account names and security IDs was done
 System.ComponentModel.Win32Exception (0x80004005): No mapping between account names
 and security IDs was done
 at Microsoft.SharePoint.PostSetupConfiguration.Win32Wrapper.NativeMethods.
 LookupAccountName(String accountName, String& domainName, SID_NAME_USE& use)
 at Microsoft.SharePoint.PostSetupConfiguration.Common.ValidateAccount
 (String username, SID_NAME_USE& type)
  at Microsoft.SharePoint.PostSetupConfiguration.ConfigurationDatabaseTask.ValidateFarmCreds()

ERR      Task configdb has failed with an unknown exception 
ERR      Exception: Microsoft.SharePoint.Upgrade.SPUpgradeException:
         One or more types failed to load. Please refer to the upgrade log for more details.


CAUSE
=======
The issue only appears to occur, if you are downloading the Microsoft WCF Data Services 5.6” prerequisites component using the direct download (Offline installer) link or if you copy the Microsoft WCF Data Services 5.6” executable from a network location.   
Files that are downloaded from the internet or copied from a Network location are blocked by Windows Operating System SmartScreen Program/ File Security feature.
 In some cases, though installation of the blocked file is allowed.  However, this may affect the installation or the registration of certain components.  

Also after installing the "Microsoft WCF Data Services 5.6" please reboot the server, before running the SharePoint Configuration Wizard.  Rebooting the server appears to register the component.   Therefore, this issue could be avoided.


WORKAROUND
=============

Workaround 1 ( with Internet Connectivity)

If the server where SharePoint Server 2016 is installed is connected to the internet, then use the PrerequisiteInstaller.exe to download the necessary prerequisites component using the prerequisite installer.  Microsoft WCF Data Services 5.6” component that was installed using the PrerequisiteInstaller.exe is not affected by this issue.

Workaround 2   (without Internet Connectivity)

If the SharePoint 2013 Server is not connected to the internet, then unblock the WCFDataServices.exe file from the File properties.  Rerun the executable and click Repair to re-install/repair the component.
After a successful repair of the WCF Data Services component, rerun the SharePoint Configuration Wizard for a successful creation of a New SharePoint Farm.

Wednesday 26 November 2014

SharePoint 2010 does not show search results when consuming SharePoint 2013 Search Service Application

Symptoms
 
When we performing a search from a SharePoint 2010 farm which is consuming a SharePoint 2013 search service application, all users receive the error as follows

"Unable to display this Web Part. To troubleshoot the problem, open this Web page in a Microsoft SharePoint Foundation-compatible HTML editor such as Microsoft SharePoint Designer. If the problem persists, contact your Web server administrator"
 
if we take look into ULS log we may find below error in ULS
 
"w3wp.exe (0x02D4) 0x1788 SharePoint Server Search Query dn0c High CoreResultsDatasourceView: Could not find location with internal name LocalSearchIndex"
 
Cause
The locationconfigurations property in the search service application proxy could be blank in the SharePoint 2013.
 
 
 

Resolution
we need to check if  locationconfigurations property is null. And to do that we need to take help from PowerShell. We can use below script for the same.
 
$Url = "http://siteurl"
$site = Get-SPSite $Url
$serviceContext = [Microsoft.SharePoint.SPServiceContext]::GetContext($site)
$searchProxy = [Microsoft.Office.Server.Search.Administration.SearchServiceApplicationProxy]::GetProxy($serviceContext)
$searchProxy.LocationConfigurations

If this returns blank or null , we can repopulate that using PowerShell as below

$ssa = Get-SPEnterpriseSearchServiceApplication "Search Service Application"

$ssa.Status = "Disabled"

$ssa.Update()

$ssa.Provision() 


this will actually recreate the Out Of the box location configurations again in the SSA Admin DB.

We can confirm that again running first script and once it got confirmed , users will able to get the search results in SharePoint 2010

 
 
 

 

 

 

Monday 21 July 2014

Unable to add non - admin node to FAST server

Symptom

Unable to add non - admin node to FAST server, getting error "E:\FASTSearch\bin\MonitoringServiceConfig.exe" Output - Error: The file 'E:\FASTSearch\etc\middleware.cfg' was not found.

Cause

Automatic configuration enabled under the IE Options - Connections - Lan settings 

Resolution

We had automatic configuration enabled under the IE Options - Connections - Lan settings , we turn off that and after that we able to ran the psconfig successfully.

Unable to get search results for all users except service account


Symptom

Only Service accounts able to get the search results in SharePoint 2010

Resolution

1. Add Services account and search account into the Pre-Windows 2000 Compatible Access group.

2. Run below Power shell to update configuration
$searchapp = get-spenterprisesearchserviceapplication
$searchapp.SetProperty("ForceClaimACLs",1)

SharePoint 2013: Access Denied


SharePoint 2013: Access Denied

Symptoms
All users including admins with full control policy get Access Denied.
 
they get the standard SharePoint access denied page that says:
“Sorry, you don’t have access to this page”

Cause
In the Local Security Policy | Local Policies | User Rights Assignment, “Bypass traverse checking” doesn't have IIS_IUSR added.

Resolution
1. Add a group that contains IUSR  or IIS_IUSR to “Bypass traverse checking” in the Local Security Policy. 
2. Gpudate /force
3. IISReset

Unable to open SharePoint 2013 site into SharePoint DESIGNER 2013


Issue
=====
While trying to open a SharePoint 2013 site using Microsoft SharePoint Designer 2013,
we get the below error message "The Server could not complete your request"

Cause
=====
Anonymous Authentication is disabled on the web application
 
Resolution
=========
Enable Anonymous authentication for the site from SharePoint.
We should enable it from SharePoint End rather than IIS web site

Monday 7 July 2014

SharePoint 2010 - Unable to set audience using Internet Explorer 9 in global navigation

Issue
======
Unable to set the audiences on the Global Navigation when using Internet Explorer 9 give an unexpected error has occurred.

When we try to set audiences on Global navigation (http://kyz.com/_layouts/AreaNavigationSettings.aspx ) for links it give us error as follows

 
 
Checked into ULS logs we are getting below error
======================================

System.InvalidOperationException: Namespace prefix 'xsd' is not defined.  
 at System.Xml.Serialization.XmlSerializationReader.ToXmlQualifiedName(String value, Boolean decodeName) 
 at Microsoft.Xml.Serialization.GeneratedAssembly.XmlSerializationReaderDictionaryEntryArray.Read1_Object(Boolean isNullable, Boolean checkType)   
 at Microsoft.Xml.Serialization.GeneratedAssembly.XmlSerializationReaderDictionaryEntryArray.Read2_DictionaryEntry(Boolean checkType)   
 at Microsoft.Xml.Serialization.GeneratedAssembly.XmlSerializationReaderDictionaryEntryArray.Read3_ArrayOfDictionaryEntry()
 
 
Solution
=======
This Issue has been fixed in April CU 2014 for SharePoint 2010.
 
Please make sure that you apply patch in Test or Dev enviroment to make sure it's no breaking anything else.