Error 24006/26000 on publishing project – Orphans Tasks

Screenshot:

General error message:

Reporting message processor failed:
ReportingProjectChangeMessageFailed (24006) – The INSERT statement conflicted with the FOREIGN KEY constraint “FK_MSP_EpmTaskBaseline_ProjectUID_TaskUID”. The conflict occurred in database “DB_Reporting”, table “dbo.MSP_EpmTask”. The statement has been terminated.. Detalhes: id=’24006′ name=’ReportingProjectChangeMessageFailed’ uid=’faa290f5-7c9a-4a88-bb43-29c2e047896e’ QueueMessageBody=’Project UID=’7a6aa976-ab1e-4287-b58b-191c4e9f2a5e‘. PublishType=’ProjectPublish” Error=’The INSERT statement conflicted with the FOREIGN KEY constraint “FK_MSP_EpmTaskBaseline_ProjectUID_TaskUID”. The conflict occurred in database “DB_Reporting”, table “dbo.MSP_EpmTask”. The statement has been terminated.’.
ReportingProjectChangeMessageFailed (24006) – The INSERT statement conflicted with the FOREIGN KEY constraint “FK_MSP_EpmTaskBaseline_ProjectUID_TaskUID”. The conflict occurred in database “DB_Reporting”, table “dbo.MSP_EpmTask”. The statement has been terminated.. Detalhes: id=’24006′ name=’ReportingProjectChangeMessageFailed’ uid=’bbadd3b8-6560-4ea4-8672-eb1591c4eb7c’ QueueMessageBody=’Project UID=’7a6aa976-ab1e-4287-b58b-191c4e9f2a5e’. PublishType=’ProjectPublish” Error=’The INSERT statement conflicted with the FOREIGN KEY constraint “FK_MSP_EpmTaskBaseline_ProjectUID_TaskUID”. The conflict occurred in database “DB_Reporting”, table “dbo.MSP_EpmTask”. The statement has been terminated.’.
ReportingProjectChangeMessageFailed (24006) – The INSERT statement conflicted with the FOREIGN KEY constraint “FK_MSP_EpmTaskBaseline_ProjectUID_TaskUID”. The conflict occurred in database “DB_Reporting”, table “dbo.MSP_EpmTask”. The statement has been terminated.. Detalhes: id=’24006′ name=’ReportingProjectChangeMessageFailed’ uid=’77b417c5-da4f-43d6-ab99-7dee4bc08c88′ QueueMessageBody=’Project UID=’7a6aa976-ab1e-4287-b58b-191c4e9f2a5e’. PublishType=’ProjectPublish” Error=’The INSERT statement conflicted with the FOREIGN KEY constraint “FK_MSP_EpmTaskBaseline_ProjectUID_TaskUID”. The conflict occurred in database “DB_Reporting”, table “dbo.MSP_EpmTask”. The statement has been terminated.’.
ReportingProjectChangeMessageFailed (24006) – The INSERT statement conflicted with the FOREIGN KEY constraint “FK_MSP_EpmTaskBaseline_ProjectUID_TaskUID”. The conflict occurred in database “DB_Reporting”, table “dbo.MSP_EpmTask”. The statement has been terminated.. Detalhes: id=’24006′ name=’ReportingProjectChangeMessageFailed’ uid=’ec4e5993-6f3a-4242-b321-754d9b85437f’ QueueMessageBody=’Project UID=’7a6aa976-ab1e-4287-b58b-191c4e9f2a5e’. PublishType=’ProjectPublish” Error=’The INSERT statement conflicted with the FOREIGN KEY constraint “FK_MSP_EpmTaskBaseline_ProjectUID_TaskUID”. The conflict occurred in database “DB_Reporting”, table “dbo.MSP_EpmTask”. The statement has been terminated.’.
ReportingProjectChangeMessageFailed (24006) – The INSERT statement conflicted with the FOREIGN KEY constraint “FK_MSP_EpmTaskBaseline_ProjectUID_TaskUID”. The conflict occurred in database “DB_Reporting”, table “dbo.MSP_EpmTask”. The statement has been terminated.. Detalhes: id=’24006′ name=’ReportingProjectChangeMessageFailed’ uid=’2b4e5ca3-98d4-4bce-a4fe-27d83503d886′ QueueMessageBody=’Project UID=’7a6aa976-ab1e-4287-b58b-191c4e9f2a5e’. PublishType=’ProjectPublish” Error=’The INSERT statement conflicted with the FOREIGN KEY constraint “FK_MSP_EpmTaskBaseline_ProjectUID_TaskUID”. The conflict occurred in database “DB_Reporting”, table “dbo.MSP_EpmTask”. The statement has been terminated.’.
ReportingProjectChangeMessageFailed (24006) – The INSERT statement conflicted with the FOREIGN KEY constraint “FK_MSP_EpmTaskBaseline_ProjectUID_TaskUID”. The conflict occurred in database “DB_Reporting”, table “dbo.MSP_EpmTask”. The statement has been terminated.. Detalhes: id=’24006′ name=’ReportingProjectChangeMessageFailed’ uid=’317ed405-3081-4e8b-a899-825a0968d9b9′ QueueMessageBody=’Project UID=’7a6aa976-ab1e-4287-b58b-191c4e9f2a5e’. PublishType=’ProjectPublish” Error=’The INSERT statement conflicted with the FOREIGN KEY constraint “FK_MSP_EpmTaskBaseline_ProjectUID_TaskUID”. The conflict occurred in database “DB_Reporting”, table “dbo.MSP_EpmTask”. The statement has been terminated.’.
Queue:
GeneralQueueJobFailed (26000) – ReportingProjectPublish.ReportProjectPublishMessageEx. Detalhes: id=’26000′ name=’GeneralQueueJobFailed’ uid=’17d35b4d-b58a-40fc-96a4-9a0f1774f3cf’ JobUID=’50ad5fc3-a1d2-41d4-ac98-98bb11e445a8′ ComputerName=’EPMGERBA04′ GroupType=’ReportingProjectPublish’ MessageType=’ReportProjectPublishMessageEx’ MessageId=’1′ Stage=”. Para obter detalhes, verifique os logs ULS no computador EPMGERBA04 para ver as entradas com JobUID 50ad5fc3-a1d2-41d4-ac98-98bb11e445a8. 

Solution:

Run this script on the SQL instance that hosts yours Project Server 2010 databases.

Note: Change the databases names to apply to your environment. In my case the names are DB_Draft, DB_Published, DB_Reporting, DB_Archive.

declare @proj nvarchar (50)

set @proj = ‘7a6aa976-ab1e-4287-b58b-191c4e9f2a5e‘

delete  from DB_Draft.dbo.MSP_TASK_BASELINES

where DB_Draft.dbo.MSP_TASK_BASELINES.PROJ_UID = @proj and DB_Draft.dbo.MSP_TASK_BASELINES.TASK_UID NOT IN (

                select TASK_UID

                from DB_Draft.dbo.MSP_TASKS

                where PROJ_UID =@proj

)

delete  from DB_Published.dbo.MSP_TASK_BASELINES

where DB_Published.dbo.MSP_TASK_BASELINES.PROJ_UID = @proj and DB_Published.dbo.MSP_TASK_BASELINES.TASK_UID NOT IN

                (

                                                select TASK_UID

                                                from DB_Published.dbo.MSP_TASKS

                                                where PROJ_UID =@proj

                )

Erro ao provisionar PWA com mesmo nome PWA

Sintoma:

Ao tentar reprovisionar o PWA utilizando as mesmas bases de content e do PWA utilizando o nome original (PWA) o erro abaixo era apresentado:

Mensagens de erros:

1) ProjectSite not created.

2) System.NullReferenceException: Object reference not set to an instance of an object.   
at Microsoft.SharePoint.SPSite..ctor(Guid id, SPFarm farm, SPUrlZone zone, SPUserToken userToken)   
at Microsoft.SharePoint.SPSite..ctor(Guid id)   
at Microsoft.Office.Project.Server.Administration.ProjectSite..ctor(Guid webAppId, Guid siteId, String adminName, Int32 lcid, Boolean needsUpgrade, PsiServiceApplication parent)   
at Microsoft.Office.Project.Server.Administration.ProjectSiteCollection.Add(Guid webAppId, Guid siteId, String adminName, Int32 lcid, String PubDBConnString, String VerDBConnString, String WorkDBConnString, String RepDBConnString, Boolean needsUpgrade)

3) Provisioning ‘PWA’: Project site object creation failed. Exception ‘System.NullReferenceException: Object reference not set to an instance of an object.   
at Microsoft.SharePoint.SPSite..ctor(Guid id, SPFarm farm, SPUrlZone zone, SPUserToken userToken)   
at Microsoft.SharePoint.SPSite..ctor(Guid id)   
at Microsoft.Office.Project.Server.Administration.ProjectSite..ctor(Guid webAppId, Guid siteId, String adminName, Int32 lcid, Boolean needsUpgrade, PsiServiceApplication parent)   
at Microsoft.Office.Project.Server.Administration.ProjectSiteCollection.Add(Guid webAppId, Guid siteId, String adminName, Int32 lcid, String PubDBConnString, String VerDBConnString, String WorkDBConnString, String RepDBConnString, Boolean needsUpgrade)   
at Microsoft.Office.Project.Server.Administration.PsiServiceApplication.CreateSite(ProjectProvisionSettings provset)’.

4) Failed to provision site PWA with error: System.NullReferenceException: Object reference not set to an instance of an object.   
at Microsoft.SharePoint.SPSite..ctor(Guid id, SPFarm farm, SPUrlZone zone, SPUserToken userToken)   
at Microsoft.SharePoint.SPSite..ctor(Guid id)   
at Microsoft.Office.Project.Server.Administration.ProjectSite..ctor(Guid webAppId, Guid siteId, String adminName, Int32 lcid, Boolean needsUpgrade, PsiServiceApplication parent)   
at Microsoft.Office.Project.Server.Administration.ProjectSiteCollection.Add(Guid webAppId, Guid siteId, String adminName, Int32 lcid, String PubDBConnString, String VerDBConnString, String WorkDBConnString, String RepDBConnString, Boolean needsUpgrade)   
at Microsoft.Office.Project.Server.Administration.PsiServiceApplication.CreateSite(ProjectProvisionSettings provset) 

Solução:

1) Reprovisionamos com sucesso o PWA com outro nome utilizando as mesmas bases. Neste caso, utilizamos o nome PWAQA;

2) Desprovisionamos o PWAQA;

3) Reprovisionamos com sucesso o PWA com o nome original utilizando as mesmas bases. Neste caso, utilizamos o nome PWA;

Com esta ação, a base de config do SharePoint ficou limpa da referência do nome PWA anteior no Web Application utilizado.

Excel calculation services – The Workbook cannot be opened

Symptom:

When you configure the Excel calculation services (ECS) on your SharePoint2010 farm it might happen that you (or latest your endusers) face some error when trying to open an excel sheet stored in a document library.

When you check your ULS logs, you will find something like:

ServerSession.ProcessServerSessionException: An exception during ExecuteWebMethod has occurred for server: http://yourserver andsomeguid/ExcelService*.asmx, method: OpenWorkbook, ex: Microsoft.Office.Excel.Server.CalculationServer.Proxy.ServerSessionException: The workbook cannot be opened..

Result=Microsoft.Office.Excel.Server.CalculationServer.Proxy.ServerSession Exception: The workbook cannot be opened.  
at Microsoft.Office.Excel.Server.CalculationServer.Proxy.ServerSession.Execute WebMethodCore(WebMethodType webMethodType, WebMethodBehaviorAttribute webMethodBehavior, CommandParameter parameter, CoreWebMethod coreWebMethod)  
at Microsoft.Office.Excel.Server.CalculationServer.Proxy.ServerSession.Execute WebMethod(WebMethodType webMethodType, WebMethodBehaviorAttribute webMethodBehavior, CommandParameter parameter, CoreWebMethod coreWebMethod)

To solve this error, the account that is running the Excel Services application pool must have access to the content database where the PWA site resides.

To correct it, just run the script below:

$w = Get-SPWebApplication -identity “http://ourserver.domain”    # change here to the correct web application
$w.GrantAccessToProcessIdentity(“Domain\UserAccountThatRunTheExcelService”)

Ok, now all content databases hosted on this web application should have received dbowner role for that user account (Excel Service Account).

Error on access a SharePoint List – Collecting data on Project Server 2010

Error:

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. 

Correlation ID:9b6b1653-baef-46a4-ace8-ff9a1f535f87 

Screenshot:

Resolution:

Increase the lists timeout through below PowerShell:

$farm = Get-SPFarm
$farm.XsltTransformTimeOut = 5
$farm.Update()

Reference: http://www.brandonclaps.com/?p=51

This was caused by the XsltTransformTimeout when using an Xslt list view. This is corrected by installing the February 2012 Cumulative Update and by making the following change via PowerShell.

Central Administration regional settings in sharepoint 2010

To change Regional Setting in SharePoint 2010 Central Administration web site to check and receive the correct date and time format for the performed jobs.

Regional Settings are hidden for the Central Admin site collection. However, you can get to them by typing the url (substitute mysharepointserverCA:2010 for your central admin web application):

http://mysharepointserverCA:2010/_layouts/regionalsetng.aspx

WorkFlow customizado no Project Server parando em determinados Steps

Sintoma:

Ao tentar prosseguir em um workflow customizado no project server 2010, um erro de acesso negado é apresentado nos logs do SharePoint bem como uma mensagem customizada de não ser possível salvar o projeto será apresentada.

Solução:

Adicionar o grupo Administrators aos quais o usuário de workflow configurado no PWA utiliza:

1) Acessar o site do PWA -> Server Settings -> Manage Users

2) Procurar o usuáriode workflow e editá-lo:

3) Adicionar o grupo “Administrators“:

4) Salvar o cadastro do usuário.

5) Testar um projeto reiniciando o fluxo. Se tudo estiver ok, o worflow deverá andar para os próximos passos.

An unexpected error occurred. Error 19106. – Performancepoint Dashboard Designer not working

Screenshot Error:

Error:

An unexpected error occurred. Error 19106. Exception details: System.ServiceModel.ServiceActivationException: The requested service, ‘http://epmserver:32843/a326fd7459d34025a9357a248171c3a2/PerformancePointService.svc’ could not be activated. See the server’s diagnostic trace logs for more information. Server stack trace: at System.ServiceModel.Channels.HttpChannelUtilities.ValidateRequestReplyResponse(HttpWebRequest request, HttpWebResponse response, HttpChannelFactory factory, WebException responseException, ChannelBinding channelBinding) at System.ServiceModel.Channels.HttpChannelFactory.HttpRequestChannel.HttpChannelRequest.WaitForReply(TimeSpan timeout) at System.ServiceModel.Channels.RequestChannel.Request(Message message, TimeSpan timeout) at System.ServiceModel.Channels.SecurityChannelFactory`1.SecurityRequestChannel.Request(Message message, TimeSpan timeout) at System.ServiceModel.Dispatcher.RequestChannelBinder.Request(Message message, TimeSpan timeout) at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout) at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation) at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message) Exception rethrown at [0]: at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg) at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type) at Microsoft.PerformancePoint.Scorecards.IBIMonitoringServiceApplication.RenderReport(Boolean proxyCacheAttempt, String& proxyCacheKey, SubstitutionList& proxyCacheSubs, DateTime& proxyCacheExpiration, String& html, String& script, WebPartContextUpdate& webPartContextUpdate, RepositoryLocation reportLocation, String renderTargetId, String availableHeight, String availableWidth, WebPartContext webPartContext, Boolean isAccessibilityMode) at Microsoft.PerformancePoint.Scorecards.BIMonitoringServiceApplicationProxy.RenderReport(String& html, String& script, WebPartContextUpdate& webPartContextUpdate, RepositoryLocation reportLocation, String renderTargetId, Unit availableHeight, Unit availableWidth, WebPartContext webPartContext, Boolean isAccessibilityMode)

Possible Solution:

1. Restart the “Performance Point Service” from central admin

2. Perform an IISRESET

Search status stuck in “Waiting on Initialization” or “Propagating to query server” messages for a long time

Symptom:

After a P2V process performed on our environment, we found that the indexes were not getting propagated to our Query server (Server01 / Server02).

Within Central Admin, we would see messages like “Waiting on Initialization (Server01) (on Search Admin screen above).

Search propagation would be stuck in this state forever.

Resolution:

Turns out that “Windows SharePoint Administration Service” was not started on Query server Server01. We have started it:

Once re-started, indexes started getting propagated to the Query server:

Error ao reparar SharePoint 2013 Language Pack

Sintoma:

Ao tentar reparar a instalação do Language Pack do SharePoint 2013, recebemos o erro abaixo:

Erro:

Solução:

Efetuamos backup da chave de registro referente ao language pack Espanhol e após a removemos com delete. A chave está em:

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Office15.OSMui.es-es]

Reinstalamos o language pack;

Rodamos o SharePoint Configuration Wizard;

Capturar logs do Farm através de 1 servidor via PowerShell

Merge-SPLogFile -Path <String> [-Area <String[]>] [-AssignmentCollection <SPAssignmentCollection>] [-Category <String[]>] [-ContextFilter <String[]>] [-Correlation <Guid[]>] [-EndTime <DateTime>] [-EventID <String[]>] [-ExcludeNestedCorrelation <SwitchParameter>] [-Level <String>] [-Message <String[]>] [-Overwrite <SwitchParameter>] [-Process <String[]>] [-StartTime <DateTime>] [-ThreadID <UInt32[]>]

Exemplo:

Merge-SPLogFile -Path D:\merged_log.log -Correlation 9b6b1653-baef-46a4-ace8-ff9a1f535f87

Referência:

http://technet.microsoft.com/en-us/library/ff607721.aspx