SharePoint - Erro na ativação do feature “Report Server Integration Feature”

O erro abaixo ocorre normalmente se houve algum problema na instalação dos features do Report Server. A ativação por meio do Powershell cmdlet Enable-SPFeature e do parâmetro force funciona, entretanto não habilita os tipos de conteúdo. 

Sorry, something went wrongThe content type with Id 0x010100C3676CDFA2F24E1D949A8BF2B06F6B8B defined in feature {e8389ec7-70fd-4179-a1c4-6fcb4342d7a0} was found in the current site collection or in a subsite.

O content type ausente que causou esse evento foi Report Builder Report (0x010100C3676CDFA2F24E1D949A8BF2B06F6B8B). 

Execute os seguintes comandos do stsadm para instalar os features e content types necessários para ativar o “Report Server Integration Feature”.

1. stsadm -o installfeature -name ReportServer
2. stsadm -o installfeature -name ReportServerCentralAdmin
3. stsadm -o installfeature -name ReportServerItemSync
4. stsadm -o installfeature -name ReportServerStapling

Em seguida, ative o feature por meio do Powershell:

Enable-SPFeature -Identity E8389EC7-70FD-4179-A1C4-6FCB4342D7A0 -Url http://<sua página>/

Isso ativará o feature e os tipos de conteúdo nas bibliotecas da página

Feature

Content Types

IDs dos content types:

Report Builder Model 
0x010100D8704AF8ED734F4088724751E0F2727D

Report Builder Report
0x010100C3676CDFA2F24E1D949A8BF2B06F6B8B

Report Data Source
0x0101007DFDDF56F8A9492DAA9366B83A95B3A0

Enable-SPFeature

[]

SharePoint 2013 - "The URL is invalid." na criação de subsites.

Os eventos abaixo ocorrem normalmente na criação de subsites caso que campos nativos foram modificados no pai do novo subsite.

1. O evento na interface do SharePoint:

Sorry, something went wrong The URL '<URL>/<SITE>.aspx' is invalid.  It may refer to a nonexistent file or folder, or refer to a valid file or folder that is not in the current Web.

2. No ULS: "The URL '<URL>/<SITE>.aspx' is invalid." 

System.Runtime.InteropServices.COMException: <nativehr>0x81020030</nativehr><nativestack></nativestack>The URL '<URL>/<SITE>.aspx' is invalid.  It may refer to a nonexistent file or folder, or refer to a valid file or folder th   at is not in the current Web., StackTrace:      at Microsoft.SharePoint.SPListItem.AddOrUpdateItem(Boolean bAdd, Boolean bSystem, Boolean bPreserveItemVersion, Boolean bNoVersion, Boolean bMigration, Boolean bPublish, Boolean bCheckOut, Boolean bCheckin, Guid newGuidOnAdd, Int32& ulID, Object& objAttachmentNames, Object& objAttachmentContents, Boolean suppressAfterEvents, String filename, Boolean bPreserveItemUIVersion)       at Microsoft.SharePoint.SPListItem.UpdateInternal(Boolean bSystem, Boolean bPreserveItemVersion, Guid newGuidOnAdd, Boolean bMigration, Boolean bPublish, Boolean bNoVersion, Boolean bCheckOut, Boolean bCheckin, Boolean suppressAfterEvents, String filename, Boolean bPreserveItemUIVersion)    

3. No ULS: "Parameter '@tp_Author' was supplied multiple times."

System.Data.SqlClient.SqlException (0x80131904): Parameter '@tp_Author' was supplied multiple times.             at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)             at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose)             at System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady)             at System.Data.SqlClient.SqlDataReader.TryHasMoreRows(Boolean& moreRows)             at System.Data.SqlClient.SqlDataReader.TryReadInternal(Boolean setTimeout, Boolean& more)             at System.Data.SqlClient.SqlDataReader.TryNextResult(Boolean& more)             at System.Data.SqlClient.SqlDataReader.NextResult()             at Microsoft.SharePoint.SPSqlClient.ExecuteQueryInternal(Boolean retryfordeadlock)             at Microsoft.SharePoint.SPSqlClient.ExecuteQuery(Boolean retryfordeadlock)

O seguinte script identifica o campo a partir da coluna identificada "tp_author" no evento 3.

## informe o url do pai do novo subsite

$web = get-spweb "http://url/pai"

## informe a coluna identificada 

$web.fields | where-object {$_.schemaxml -like "*tp_author*"} | select title

Os desenvolvedores do SharePoint introduziram no SharePoint 2013 um novo método para esse caso - Microsoft.SharePoint.SPField.RevertCustomizations() que nós podemos utilizar para reverter as customizações em campos nativos:

($web.fields | where-object {$_.schemaxml -like "*tp_author*"}).RevertCustomizations()

Observação: Não utilize o método update para concluir a atualização, isso adicionaria a infomação (indesejada) da versão no schema do campo:

[] 

SharePoint - Sys.WebForms.PageRequestManagerServerErrorException: An unexpected error occured.

O evento descrito ocorreu na edição de uma pagina no SharePoint, conforme abaixo:

Evento no UI (User Interface):

"Sys.WebForms.PageRequestManagerServerErrorException: An unexpected error occured."

Evento nos logs do SharePoint:

w3wp.exe (0x182C) 0x2720 SharePoint Foundation Runtime tkau Unexpected System.UnauthorizedAccessException: Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED))    at Microsoft.SharePoint.Library.SPRequest.GetListsWithCallback(String bstrUrl, Guid foreignWebId, String bstrListInternalName, Int32 dwBaseType, Int32 dwBaseTypeAlt, Int32 dwServerTemplate, UInt32 dwGetListFlags, UInt32 dwListFilterFlags, Boolean bPrefetchMetaData, Boolean bSecurityTrimmed, Boolean bGetSecurityData, Boolean bPrefetchRelatedFields, ISP2DSafeArrayWriter p2DWriter, Int32& plRecycleBinCount)     at Microsoft.SharePoint.SPListCollection.EnsureListsData(Guid webId, String strListName)     at Microsoft.SharePoint.SPListCollection.Undirty()     at Microsoft.SharePoint.SPBaseCollection.GetEnumerator()     at Microsoft.SharePoint.SPWeb.GetCatalog(SPListTemplateType typeCatalog)     at Microsoft.SharePoint.Publishing.WebControls.MediaWebPart.get_WebPartAdderId()     at Microsoft.SharePoint.Publishing.WebControls.InsertMediaRibbonButton.RegisterRequiredScripts()     at Microsoft.SharePoint.Publishing.WebControls.InsertMediaRibbonButton.OnPreRender(EventArgs e)     at System.Web.UI.Control.PreRenderRecursiveInternal()     at System.Web.UI.Control.PreRenderRecursiveInternal()     at System.Web.UI.Control.PreRenderRecursiveInternal()     at System.Web.UI.Control.PreRenderRecursiveInternal()     at System.Web.UI.Control.PreRenderRecursiveInternal()     at System.Web.UI.Control.PreRenderRecursiveInternal()     at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) 

Solução / Causa:

Acima ocorre normalmente se os grupos default do SharePoint foram deletados / alterados. Nesse caso aqui "Leitores do Recurso de Estilo" que eu recriei. Você pode editar a pagina assim que você recriou o(s) grupo(s).

Grupos padrão do SharePoint no SharePoint Server

[]