App Model Troubleshooting Guide SharePoint 2013

This summary is not available. Please click here to view the post.

SharePoint 2013 update conflict has occurred, and you must re-tr this action. The object SPWebApplication Name

While running the command to remove the dodgy extranet web app, got this error

Remove-SPWebApplication : An update conflict has occurred, and you must re-tr
this action. The object SPWebApplication Name=extranetppd.contoso.com was updated by Service Account, in the w3wp
(6180) process, on machine Contoso001.  View the tracing log for more
information about the conflict.
At line:1 char:1

Clear the SharePoint cache , refer to the technet article

Ran the command again, works absolutely fine

Remove-SPWebApplication https://extranetppd.contoso.com/  -Confirm -DeleteIISSite -RemoveContentDatabases

Delete / Force / Remove Rogue or Orphaned Site Collection in SharePoint 2013

Whilst provisioning app catalog site, encountered an issue with the database permissions. Aftering sorting that out, whilst re-provisioning the app catalog site , found the previous attempt added a rogue / orphaned site colleciton.

Though the site colleciton was visible in central admin, however, the option to delete was graded out.

Use the following Powershell, this did the trick.

$site = Get-SPSite https://intranet.contoso.com/apps/appstore
$siteId = $site.Id
$siteDatabase = $site.ContentDatabase
$siteDatabase.ForceDeleteSite($siteId, $false, $false)

Error while crawling LOB contents. ( Error caused by exception: Microsoft.BusinessData.Infrastructure.BdcException The shim execution failed unexpectedly - Exception has been thrown by the target of an invocation..: System.Net.WebException The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel.; SearchID

Error while crawling LOB contents. ( Error caused by exception: Microsoft.BusinessData.Infrastructure.BdcException The shim execution failed unexpectedly - Exception has been thrown by the target of an invocation..: System.Net.WebException The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel.; SearchID 

The issue with the certificates not being recognized as trusted in the SharePoint Farm. To resolve this:

• Go the the Certificate, Click on Certificate Path 
• Select the Root Certifcate, Double Click on it
• Click on Details 
• Click on Copy to File
• Save the file
• Now Go to SharePoint > Security > Manage Trust
• Create a New Trust >  Import the Root certificate
• Click oK
• Run and iisreset on the SharePoint servers
• Run a full crawl now

Issue resolved for me.

Check the ULS to find more information , may have to switch on verbose extended logging, but generally speaking, the cause of the issue will be the certificates.

THE EXECUTE permission was denied on the object 'proc_GetProductVersions' Database '_Config', schema 'dbo'.

We had an issue where search was being used as a core component on the home page for one of the solution's. On further research we identified the it was an access issue on the database side. We are using SharePoint 2013 Enterprise Search which is on Always on Availability Group.

Here are the two errors we got

Error 1: 'The EXECUTE permission was denied on the object 'proc_MSS_GetLease', 

Error 2: THE EXECUTE permission was denied on the object 'proc_GetProductVersions' Database '_Config', schema 'dbo'.

For the Error 1, the search service account needs to have access on SPSearchDBAdmin role on the following databases

• _Search
• _Search_AnalyticsReportingStore
• _Search_CrawlStore
• _Search_LinksStore

For the Error 2, the search service account needs to have  access on WSS_Content_Application_Pools role  for the following databases 

• _Config
• _Admin

After giving the access, bounced the IIS , issue resolved for us. Check the logs to identify the problem.

SharePoint 2013 Service Pack 1 Withdrawn

Microsoft has withdrawn Service Pack 1 from general public availability as it will block or won't allow future public or cumulative updates  from installing. There are no other issues reported as per the notes. They are going to release a new version of Service Pack in future no timeline defined for this yet.

There are no clear notes about how to roll back for clients who have already implemented it on their farms.

The download links are broken.

A call with MS Support team may guide them on next steps stay tuned.

Service Pack 1 Update on 08/04/2014:  Checked with  Microsoft's Technical Account Manager and subsequently a call with Suppor Team. "Guidance is not to rollback as the existing Service Pack 1 won't affect anything apart from stopping future upgrades. Once the re-released version of Service Pack 1 / hotfix is available , customers can install it. There is no ETA on the release date" .


"We have recently uncovered an issue with this Service Pack 1 package that may prevent customers who have Service Pack 1 from deploying future public or cumulative updates. As a precautionary measure, we have deactivated the download page until a new package is published. "

Links: 

http://support.microsoft.com/kb/2817429/en-gb

http://blogs.technet.com/b/office_sustained_engineering/archive/2014/02/25/announcing-the-release-of-service-pack-1-for-office-2013-and-sharepoint-2013.aspx

Service Pack 1 Update: Microsoft has re-released a newer version of the service pack with the fix i.e. to allow installing future CU's. The challenge we had was to re-install newer version of service pack 1 on all of our SharePoint Farms which comprises of 40 plus servers. I would have expected Microsoft to release a hot-fix for customers who have already installed Service Pack instead of going for a full blown deployment of Service Pack. This caused enormous time to coordinate the deployment of service pack going through CAB, deployment etc.

SharePoint 2013 Service Pack 1 Fails

Rolled out Service Packs on  6 DEV Servers , Shared Services UAT farm all went well apart from couple of niggling issues like the following but overall it was successful:

Search Host Controller Service stuck in Starting State
User Profile Sync Service stuck in Starting state

Those were pretty straight forward to fix but the killer one appeared on the Pre-Prod environment which connects to Production domain controller. Everything looked good  till we ran Product and Config Wizard I reckon that's where all the Fun starts huh :). Failed at the Last step.

“   Unable to create a Service Connection Point in the current Active Directory domain. Verify that the SharePoint container exists in the current domain and that you have rights to write to it.

Microsoft.SharePoint.SPException: The object LDAP://CN=Microsoft SharePoint Products,CN=System,DC=emea,DC=cbre,DC=net doesn't exist in the directory.

   at Microsoft.SharePoint.Administration.SPServiceConnectionPoint.Ensure(String serviceBindingInformation)

   at Microsoft.SharePoint.PostSetupConfiguration.UpgradeTask.Run() “

The container Microsoft SharePoint Products was missing in ADSI Active Directory Service Interface Editor. 

As it's a Shared Services environment and so many install / farms account and Pre-Prod environment for Shared Services leveraged across Intranet and Extranet farms,  it made sense to create an Active Directory Group called as SharePointFarmAdmins and add all install and farms accounts in it.

Once that was done, our AD guy created the container and granted the required ( write on the container ) permissions to SharePointFarmAdmins group. 

Re-ran the Product Configuration Wizard success. 

There are some specific Power Shell command let's which allows you to Get  and Set the Service Connection Point SCP which you can run from SharePoint 2013 Management Shell. 

To Get: 

Get-SPFarmConfig -ServiceConnectionPoint 

To Set : 

 Set-SPFarmConfig -ServiceConnectionPointBindingInformation StringwithBindingInformation

To create the Microsoft SharePoint Products container in ADSI  ,  follow the instructions from here: http://technet.microsoft.com/en-us/library/ff730261(v=office.14).aspx

The roll out of Service Packs , Cumulative updates , solutions  etc.. to go through a SDLC process etc.... emphasizes the importance of having a Pre-Prod environments which I have seen some organization ignores due to cost related issues or awareness of how it will play a pivotal role.

PS: Make sure WSS Usage DB is not part of Always On Group in case you're using Availability Groups in SQL Server 2012