Project Server

Project 2013: Upgrade-SPProjectWebInstance – ActivatePWAWebThemesFeature failed

0
1 month ago
by Mathieu CHATEAU in , ,

Trying to upgrade a Project instance from 2010 to 2013:

Upgrade-SPProjectWebInstance https://url/pwa

I got the following error:

Upgrade-SPProjectWebInstance : Post provision setup failed.
ActivatePWAWebThemesFeature failed.
At line:1 char:1
+ Upgrade-SPProjectWebInstance https://url/pwa
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 + CategoryInfo : InvalidData: (Microsoft.Offic...radePwaInstance:
 PSCmdletUpgradePwaInstance) [Upgrade-SPProjectWebInstance], ProvisionException
 + FullyQualifiedErrorId : Microsoft.Office.Project.Server.Cmdlet.PSCmdletUpgradePwaInstance

 

Solution:

You need to firstly upgrade the SharePoint site to 20103 to get the feature available::

Upgrade-SPSite -Identity https://url/pwa -versionupgrade

Then start again the pwa upgrade:

Upgrade-SPProjectWebInstance https://url/pwa

CAPI2 Failed extract thirdt party data is invalid

SharePoint 2010: CAPI2 failed extract root list the data is invalid

0
1 year ago
by Mathieu CHATEAU in , ,

One of the SharePoint 2010 started to throw the following error in loop (every 20 seconds):

Failed extract of third-party root list from auto update cab at....With error: the data is invalid

CAPI2 Failed extract thirdt party data is invalid

The most notable impact is a huge slow on every single page, while SQL and cpu was much low.

This is known that assembly .Net are signed, and that Windows try to check signature validity. This can generate slowness when doing the first call to application pool. I had already posted this problem on my blog for SharePoint 2007.

But that’s far after first call, and server can download from internet directly.

A wireshark trace later, we can see repeated try to download certificates:

To get the guilty, just need to go back to the eventlog and get the process PID from the detailled view (PID 344):

Then fire Process Monitor from Sysinternals, filtering on PID 344:

We see repeated try to use a  Cab.tmp, trying to go in cryptneturlCache.

I saw this article from another MVP, and applied the KB even if it was not exactly the same error message.

  • Error in the eventlog stop immediately,
  • Slowness stay.

It keeps trying to download file still taking a 304.

I did a variant from the article, I removed folder CryptNetUrlCache but inside SharePoint account.

Case solved ^^

Cannot start queue. SSP: <GUID> SiteUID: <GUID> Url: Queue: ProjectQ

0
1 year ago
by Mathieu CHATEAU in , , 
Log Name: Application
Source: Microsoft-SharePoint Products-Project Server
Event ID: 7626
Task Category: Queue
Level: Critical
Description:
Cannot start queue. SSP: <GUID Project server application> SiteUID: <GUID Site> Url: Queue: ProjectQ

You also have his twin, with another Url: Queue: TimesheetQ

We are going to fix that, but for next time, you MUST delete PWA instance before Web Application.

#Get Project application

$a= get-spserviceapplication | ? {$_.Typename -like "*Project*"} 
#Check that we got the good ghost one (siteUID)
$bad=$a.SiteCollection | ?{$_.SiteID -eq "a2c27d0d-1e66-43af-94d2-83b1b268658f"} 
$bad| select id,name,siteid,webappid |fl

Id : 4d4389d1-e32b-43a3-8043-9105a83fceb8
Name : PWA ghost name:
SiteId : a2c27d0d-1e66-43af-94d2-83b1b268658f
WebAppId : 9a618b96-6b00-472c-93f7-4c5f53822050 

#if ok, here we go! 
$bad.Delete() 
#Launch again previous command to confirm delete
$bad=$a.SiteCollection | ?{$_.SiteID -eq "a2c27d0d-1e66-43af-94d2-83b1b268658f"} 
$bad| select id,name,siteid,webappid |fl

 

Go to Top