Cannot start service SPAdminv4 on computer – SharePoint 2010 Administration

If you’ve experienced this error (System.InvalidOperationException, “Cannot start service SPAdminv4 on computer ‘.’) after installing/rebooting a SharePoint 2010 server and failing consistently at the SharePoint 2010 Products Configuration Wizard, then this is likely to help:

(1) Browse to C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\BIN

(2) In this directory Create a file called “WSSADMIN.EXE.CONFIG“

(3) Populate it with the following:

<configuration>

      <runtime>

<generatePublisherEvidence enabled=“false”/>

      </runtime>

</configuration>

(4) Start the “SharePoint 2010 Administration” services again

Now everything should be working….

This disables checking for CAS (Code Access Security) publisher policy. MSDN article, http://msdn.microsoft.com/en-us/library/bb629393.aspx

More details, read http://blogs.msdn.com/johan/archive/2009/11/12/make-sure-you-have-an-internet-connection-when-using-signed-assemblies.aspx and http://blogs.msdn.com/dsvc/archive/2008/06/24/troubleshooting-startup-issues-with-managed-application-having-authenticode-signature.aspx

Queue Service and Event Service will not start in Project Server 2007/2010

Open the registry editor

Start=>Run=>Regedit

Once the registry editor has been opened navigate to

HKLM\System\CurrentControlSet\Control

Here it will be necessary to create a new DWORD key with the following value:

ServicesPipeTimeout DWORD 60000 (decimal)

Note: 60000 = 60 Seconds.

Next, look for the WaitToKillServiceTimeout key – take note of its current value – and then change the value to 120000

Note: 120000=120 Seconds.

Reboot the Server.

Test by going to Start=>Run=>services.msc and examining the Microsoft Office ProjectServer Queue Service and Event Service. These services should now show as started, and assuming nothing else is wrong with the environment, the Queue Service should now be able to process jobs. The error messages in the event viewer should also have stopped.

Queue – ReportingProjectChangeMessageFailed (24006) – The INSERT statement conflicted with the FOREIGN KEY constraint FK_MSP_EpmAssignment_ResourceOwnerUID

Sintoma

            Ao publicar alguns projetos o job “Reporting (Project Publish)” relacionado ao projeto falha com a seguinte mensagem de erro:

“ReportingProjectChangeMessageFailed (24006) – The INSERT statement conflicted with the FOREIGN KEY constraint “FK_MSP_EpmAssignment_ResourceOwnerUID””

Causa

            Há várias causas distintas para a falha do job “Reporting (Project Publish)”. Neste caso em decorrência da mensagem de erro descrita acima a causa estava relacionada a falha de sincronização de um recurso membro do projeto com o base de dados de Reporting.

Solução

1. Executar a query abaixo na base de dados de Reporting (ProjectServer_Reporting – usar o nome conforme seu ambiente) com o intuito de identificar quais recursos tem problema de sincronização

select PubMR.Res_UID, PubMR.RES_Name, PubMR.WRES_Account, RepMER.ResourceName from ProjectServer_Reporting.dbo.MSP_Resources PubMR

left outer join ProjectServer_Reporting.dbo.MSP_EpmResource RepMER on PubMR.RES_UID = RepMER.ResourceUID where ResourceName is NULL

2. Da lista acima para o usuário que é membro do projeto forçar seu sincronismo com a base de Reporting através dos passos abaixo:

a. Acessar o PWA -> Resource Center

b. Selecionar o usuário no Resource Center e Editar

c. Salvar sem fazer qualquer alteração

d. Verificar se o seguinte job é completado com sucesso

 

3. Publicar novamente o projeto e verificar se o job “Reporting (Project Publish)” completa com sucesso.

Informações adicionais

            Conforme dito há várias outras razões que podem ocorrer a falha do job “Reporting (Project Publish)”, mas as causas dependem diretamente da descrição do erro gerado. Duas outras causas mais conhecidas do erro são:

1. Recurso atribuido a uma tarefa do tipo “Sumarry Task”
2. Tarefas nas Linhas de base orfãs. Como detectar este cenário e corrigir:

Please test the behavior on a test environment before.

Run the following scripts on your draft and published databases:

- First run this script to detect them:

select PROJ_NAME, MTB.PROJ_UID,TASK_UID,TB_BASE_NUM from MSP_TASK_BASELINES MTB

inner join MSP_PROJECTS MP on MTB.proj_uid=MP.proj_uid

where TASK_UID not in (select TASK_UID from MSP_TASKS)

- Next, we need to delete them:

—Script top run on the draft DB

USE ProjectServer_Draft – specify the appropriate draft database

delete from MSP_TASK_BASELINES

where TASK_UID not in (select TASK_UID from MSP_TASKS)

—Script top run on the published DB

USE ProjectServer_Published — specify the appropriate published database

delete from MSP_TASK_BASELINES

where TASK_UID not in (select TASK_UID from MSP_TASKS)

Erro ao acessar uma lista customizada do SharePoint coletando dados no Project Server 2010

Mensagem de erro:

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 error:

Resolução:

Aumentar o timeout nas listas:

$farm = Get-SPFarm

$farm.XsltTransformTimeOut = 10

$farm.Update()

Link de referencia: 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.

Daylight saving time ended and Sharepoint still off by 1 hour

The daylight saving time ended, but SharePoint still saving all items which require a date time stamp reference with 1 hour less (in my case).

Screenshot of the behavior:

1.Modify the Timezone.xml file to include the correct date and time for standard time and for daylight saving time. To do this, follow these steps:

a. Start Notepad, and then open the Timezone.xml file.

The Timezone.xml file is located in the following folder:

SharePoint Server 2013

Drive:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\15\Config

SharePoint Server 2010

Drive:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\Config

Windows SharePoint Services 3.0 / MOSS 2007

Drive:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\Config

Microsoft Windows SharePoint Services 2.0

Drive:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\60\Config

b. The contents of the Timezone.xml file should resemble the following example bellow that I will modify.

c. Locate the time zone that you want to modify. In my case was Name=”(UTC-03:00) Brasilia”

<TimeZone ID=”8″ Name=”(UTC-03:00) Brasilia” Hidden=”FALSE”>
<Bias>180</Bias>
<StandardTime>
<Bias>0</Bias>
<Date>
<Month>2</Month>
<Day>4</Day>
<Hour>23</Hour>
<Minute>59</Minute>
<Second>59</Second>
<Milliseconds>999</Milliseconds>
<DayOfWeek>6</DayOfWeek>
</Date>
</StandardTime>
<DaylightTime>
<Bias>-60</Bias>
<Date>
<Month>10</Month>
<Day>3</Day>
<Hour>23</Hour>
<Minute>59</Minute>
<Second>59</Second>
<Milliseconds>999</Milliseconds>
<DayOfWeek>6</DayOfWeek>
</Date>
</DaylightTime>
</TimeZone>

d. Modify the StandardTime element to specify the correct date and time for standard time. For the current time zone, change the Day fields from 4 to 3.

<TimeZone ID=”8″ Name=”(UTC-03:00) Brasilia” Hidden=”FALSE”>
<Bias>180</Bias>
<StandardTime>
<Bias>0</Bias>
<Date>
<Month>2</Month>
<Day>3</Day>
<Hour>23</Hour>
<Minute>59</Minute>
<Second>59</Second>
<Milliseconds>999</Milliseconds>
<DayOfWeek>6</DayOfWeek>
</Date>
</StandardTime>
<DaylightTime>
<Bias>-60</Bias>
<Date>
<Month>10</Month>
<Day>3</Day>
<Hour>23</Hour>
<Minute>59</Minute>
<Second>59</Second>
<Milliseconds>999</Milliseconds>
<DayOfWeek>6</DayOfWeek>
</Date>
</DaylightTime>
</TimeZone>

e. Click Save on the File menu to save your changes.

f. Clean the SharePoint cache using PowerShell on SharePoint 2010 or manually for other versions. Bellow the PowerShell script:

#PowerShell Script to clean SharePoint Configuration cache:

Add-PSSnapin -Name Microsoft.SharePoint.PowerShell –erroraction SilentlyContinue

Stop-Service ProjectQueueService14

Stop-Service ProjectEventService14

Stop-Service SPTimerV4

$folders = Get-ChildItem C:\ProgramData\Microsoft\SharePoint\Config
foreach ($folder in $folders)
{
$items = Get-ChildItem $folder.FullName -Recurse
foreach ($item in $items)
{
if ($item.Name.ToLower() -eq “cache.ini”)
{
$cachefolder = $folder.FullName
}

}
}

$cachefolderitems = Get-ChildItem $cachefolder -Recurse
foreach ($cachefolderitem in $cachefolderitems)
{
if ($cachefolderitem -like “*.xml”)
{
$cachefolderitem.Delete()
}

}

$a = Get-Content  $cachefolder\cache.ini
$a  = 1
Set-Content $a -Path $cachefolder\cache.ini
start-Service SPTimerV4
IISRESET

########################

g. Test your environment again. Now, everything will be working right.

Good references:

http://support.microsoft.com/kb/888253/en-us

http://spinternals.blogspot.com.br/2014/01/sharepoint-powershell-script-para.html

This workbook is larger than the maximum workbook size allowed to be opened in the browser

 

How to change the upload size restriction (can I upload a 10mb doc/xls or a 1GB doc/xls) within Central Admin so that display a workbook in a web part (browser) using Excel Services.

1. Log in to Central Admin as a Farm Administrator
2. Click “Application Management” in the left nav.
3. Click “Manage service applications” under Service Applications.
4. Click “Excel Services Application” next to “Excel Services Application Web Service Application”  Note: not the item in grey under this (Proxy). You want the blue item.
5. 
6. Click the “Trusted File Locations” link:
7. 
8. Then, select the reports library or document library your web part is calling or where the files are.
9. Scroll down to “Workbook Properties” and change the ‘Maximum Workbook Size” if it’s set to 10mb’s try and change it to 50 or 100mb’s and save the change. Note: 20mb is the default configuration.
10. 
11. Go back to the page with the reports web part and refresh it.

    This should fix your issue with “This workbook is larger than the maximum workbook size allowed to be opened in the browser” and Excel Services in SharePoint 2010.

    Here’s a link to help you out: TechNet – http://technet.microsoft.com/en-us/library/ff191192.aspx

New-SPLogFile – Troubleshooting SharePoint Easily

If you are troubleshooting some SharePoint Environment, a good tip is start a new SharePoint Log to facilitate the error captures.

To start a new SharePoint Log follow these steps:

1) Open the SharePoint 2013 Management Shell as Administrator;

2) Type the command ant press Enter:

New-SPLogFile

3) Navigate to the drive/folder of the SharePoint log files. To check where the log files are, Open the “Central Administration”, click on “Monitoring” menu, click on “Configure diagnostic logging” menu:

4) Scroll down until “Trace log” and select the “Path” and click “Ok”:

5) Open Windows Explorer and navigate until the “Path” that you got previously. In Windows Explorer window, click on the “Date modified” column to set up descending order;

6) Open the last log file and good troubleshooting :-)

New-SPLogFile – Troubleshooting SharePoint Easily

If you are troubleshooting some SharePoint Environment, a good tip is start a new SharePoint Log to facilitate the error captures.

To start a new SharePoint Log follow these steps:

1) Open the SharePoint 2013 Management Shell as Administrator;

2) Type the command ant press Enter:

New-SPLogFile

3) Navigate to the drive/folder of the SharePoint log files. To check where the log files are, Open the “Central Administration”, click on “Monitoring” menu, click on “Configure diagnostic logging” menu:

4) Scroll down until “Trace log” and select the “Path” and click “Ok”:

5) Open Windows Explorer and navigate until the “Path” that you got previously. In Windows Explorer window, click on the “Date modified” column to set up descending order;

6) Open the last log file and good troubleshooting :-)

Using Merge-SPLogFile – Consolidate Log files on SharePoint

According to the description of Merge-SPLogFile on Microsoft TechNet:

“Combines trace log entries from all farm computers into a single log file on the local computer.”

Let me explain how you can use this powerful command.

Basic Usage

Lets visualize a simple farm.

As the sample Farm image above we have 2 frontend servers, 1 application server and 1 database server. If you wanted to consolidated the last hour of SharePoint log entries from the front-end server and application server you would open the SharePoint Management Shell on one of the servers and type the following command:

Merge-SPLogFile –Path “E:\SPLogs\MergedLogs.log” –Overwrite

Finding Correlation ID

What the following example show is how to find the log entries for a specific correlation id:

Merge-SPLogFile –Path “S:\SPLogs\MergedLogs.log” –Correlation 3ae2a6c0-da14-43a1-afda-5bb6bbff3d43 -Overwrite

Como fazer "refresh" de PWA – Project Server 2010

Cenário: Você tem 2 farms de Project Server 2010, 1 de Produção e 1 de Homologação e deseja atualizar o ambiente de Homologação com os dados de Produção. Este post irá informar os passos necessaries para tal.

Passos Necessários:

1) Desprovisione o PWA em Homologação:

Abra a Central de Administração do SharePoint 2010;

Acesse a opção “Manage Service Applications”;

Acesse a opção “Project Service Service Application”;

Acesse o menu suspenso junto ao nome do seu “PWA” que está provisionado, e selecione a opção “Delete”;

Uma tela contendo as informações do seu “PWA” será aberta para confirmação da deleção. Confirme clicando no botão “Delete”;

Aguarde enquanto o SharePoint executa a ação informando em tela o progresso;

Ao término do processo, o PWA não existirá mais;

2) Desatachar a(s) base(s) de conteúdo(s) via powershell do Web application que hospedava o PWA;

Abra o SharePoint 2010 Management Shell como administrator do Farm;

Rode o comando: Dismount-SPContentDatabase “<ContentdBName>”

Onde <ContentdBName> é o nome do content database que você deseja desatachar.

Em nosso ambiente usamos o commando: Dismount-SPContentDatabase “DBSPS_PWAContent”

Confirme a solicitação com “Y” e aguarde o resultado:

3) Efetuar o backup Full dos 5 bancos de dados do servidor de SQL de Produção. Em nosso cenário as bases chamam-se:

a) DBSPS_PWAContent – Base contendo os Project Sites – Content Database

b) DBPRS_PWA_Archive – Base de arquivamento do PWA

c) DBPRS_PWA_Draft – Base de rascunho do PWA

d) DBPRS_PWA_Published – Base de publicação do PWA

c) DBPRS_PWA_Reporting – Base de relatórios do PWA

4) Efetuar o restore do backup efetuado no passo 3 dos 5 bancos de dados no servidor de SQL de Homologação. Em nosso cenário as bases possuem os mesmos nomes em Produção e Homologação:

a) DBSPS_PWAContent – Base contendo os Project Sites – Content Database

b) DBPRS_PWA_Archive – Base de arquivamento do PWA

c) DBPRS_PWA_Draft – Base de rascunho do PWA

d) DBPRS_PWA_Published – Base de publicação do PWA

c) DBPRS_PWA_Reporting – Base de relatórios do PWA

5) Ajustar as permissões para os usuários do ambiente de homologação nos 5 bancos de dados restaurados no servidor de SQL de Homologação. Em nosso cenário as usuários são:

a) User_1 (Setup Account), User_2 (Farm Admin), User_3 (AppPool Account) – Owner das bases DBPRS_PWA_xxx;

a) User_1 (Setup Account), User_2 (Farm Admin), User_3 (AppPool Account), User_4 (Excel Service Account), User_8 (Secure Store User account) – Owner das bases DBPRS_PWA_Reporting;

b) User_1, User_2, User_3, User_4 – Owner das bases DBSPS_PWAContent;

6) Atachar a base de conteúdo dos Projects Sites no web application de Homologação:

a) Em nosso cenário a base DBSPS_PWAContent via PowerShell;

Mount-SPContentDatabase “<ContentDb>” -DatabaseServer “<DbServer>” -WebApplication http://SiteName

Onde:

<ContentDb> é o ocontent databaseque sera atachado.

<DbServer> é o nome do servidor SQL.

http://SiteName é o nome do web application para o qual o content database está sendo atachado.

Nosso comando:

Mount-SPContentDatabase “DBSPS_PWAContent” -DatabaseServer “DBxxxxx” -WebApplication http://epmqa.xxxxxxx

O resultado será conforme o print abaixo, onde o mesmo demonstra que existe um site collection:

7) Confira se o site collection chama-se “PWA”

Acesse o Menu “Application Management”:

Acesse o Menu “View all site collections”:

Selecione o Web application, em nosso caso: http://epmqa.xxxxxxx, será mostrado o site collection do PWA que iremos reprovisionar. Em nosso ambiente, o Project Web App chama-se “PWA”:

8) Reprovisionar o PWA

Acessar o menu “Manage Service applications” sob o menu “Service Applications” sob o menu “Application Management”:

Acesse o Menu “Project Server Service Application”:

Acesse o menu “Create Project Web App Site” para reprovisionar o PWA apontando as bases restauradas, já existentes em nosso SQL de homologação:

Preencha os dados corretamente conforme o seu ambiete. Em nosso, os dados relevantes foram o user_3, o nome do PWA como “PWA”, linguagem em inglês e o apontamento do SQL de homologação com os nomes das bases restauradas:

Um vez preenchidos os campos corretamente, confirme no botão “OK” e agurde os recursos iniciarem o processo:

Uma vez iniciado o processo de “reprovisionamento”, o status será atualizado:

Novo status:

Aguarde até o status apresentar que o PWA está provisionado:

Verifique se os projetos estão lincados. Para tal, acesse o site do PWA (em meu cenário: http://epmqa.meudominio.local/PWA), “Server Settings”:

Acesse o menu “Project Sites”:

Se os sites não estiverem todos “lincados”, acesse o menu “Bulk Update Project Sites”:

Acesse o menu “Bulk Update Project Sites”:

Preencha os campos “Previous Site Path”, em meu cenário o campo “Web Application” era “http://epm.meudominio.local” e para o campo “Site URL” o nome do PWA era “PWA”;

Para os campos “New Site Path”, em meu cenário o campo “Web Application” é o novo nome do ambiente, “http://epmqa.meudominio.local” e para o campo “Site URL” o nome do PWA era “PWA”;

Por questões de agilizar o processo, eu desmarquei a opção “Synchronize site permissions”, mas aqui se você deseja sincronizar as permissões do seu PWA com cada site, mantenha esta opção marcada;

Preenchidos os campos, apenas clique no botão “Update” e aguarde o processo que em nosso caso durou cerca de 2 horas para 10k projetos e sites;

Para validar o resultado do “Bulk Update Project Sites”, acesse o site PWA, clique no menu “Server settings”, clique no menu “Project Sites”, o resultado deverá ser:

OBS.: Ofuscamos os nomes dos projetos e sites por motivos de segurança.

Esta é a forma correta de ser efetuado um “refresh” de um ambiente (farm) para outro.

Error relinking Project Site to Project in Project Server 2010

If you are trying to relink a Project Site with its Project through the option “Edit site address” and you are receiving this error message below:

The first thing that you need to verify is the “web.config” file for your PWA application (e.g.: c:\inetpub\wwwroot\VirtualDirectories\epm.domain.local80\), where the default “globalization fileEncoding” TAG is set up for “UTF-8“.

In my scenario we had changed this TAG to “<globalization fileEncoding=”iso-8859-1″ requestEncoding=”iso-8859-1″ responseEncoding=”iso-8859-1″ />” by our developer to test other options. This kind of configuration prevents the PWA application to read URLs with special characters like “http://epm.domain.loca/PWA/Ações requeridas” (PT-BR).

To solve this problem, just swap to the default/Correct TAG:

<globalization fileEncoding=”utf-8″ />

If you don’t have this scenario, you could try to consult this link: http://pwmather.wordpress.com/2011/07/20/error-relinking-project-site-to-project-in-projectserver-2010-ps2010-project-epm/

My Queue is stuck – Project Server 2010

Cause: Indices ou estatíticas desatualizadas nas bases

How to solve:

1) Parar os serviços de fila em todos os servidores;

2) script para atualizar indices e estatísticas dos bancos (rodar em cada db do project, Archive, Reporting, Draft, Published):

DECLARE @TableName VARCHAR(255) DECLARE @sql NVARCHAR(500) DECLARE @fillfactor INT SET @fillfactor = 90 DECLARE TableCursor CURSOR FOR SELECT OBJECT_SCHEMA_NAME([object_id])+’.’+name AS TableName FROM sys.tables OPEN TableCursor FETCH NEXT FROM TableCursor INTO @TableName WHILE @@FETCH_STATUS = 0 BEGIN SET @sql = ‘ALTER INDEX ALL ON ‘ + @TableName + ‘ REBUILD WITH (FILLFACTOR = ‘ + CONVERT(VARCHAR(3),@fillfactor) + ‘)’ EXEC (@sql) FETCH NEXT FROM TableCursor INTO @TableName END CLOSE TableCursor DEALLOCATE TableCursor GO

sp_updatestats  EXEC sp_MSforeachtable ‘UPDATE STATISTICS ? WITH FULLSCAN’

3) iniciar os serviços de fila novamente;

4) Testar se a fila voltou a processor suas tarefas;

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.