none
PS2010 queued got stucked. How to force cleaning? RRS feed

  • Question

  • Hi Guys

    We have developed some forms using infopath 2010 with some code (C#) behind. We add the custom web part with the forms to a new site and we provisioned the site as a template, so far so good.  But when we created a new project we got an error that stucked the queue. We have deleted the projects and the site template, but the queue is still stucked with this job and the option "Cancel Job" is disable.

    I still can not use any provisioned site template because I would get the same error.  All of them gives me the same error and the queue is getting bigger.  I think if clean the queue and try again, the problem will be resolved.

    On the other hand PS2010 let's me use the default site template without any error.

    My question is:  Is there a way to force cleaning the queue?  What can I do to fix this?

    Thanks for the help.

    The errors the queued job gives me is the following:

    • CreateWssSiteContent: Creating project site failed! Project Uid=2d13f678-aea6-4dc8-bd04-f0f820e261e6, site URL=http://xxxxx/PWA/ProjetoModeloMV, site name=ProjetoModeloMV. Microsoft.SharePoint.SPException: O modelo de site requer a instalação do Recurso {a193dfc4-563c-4786-95ff-3f9a52bdccdf} no conjunto de sites. at Microsoft.SharePoint.Utilities.SPUtility.ThrowSPExceptionWithTraceTag(UInt32 tagId, ULSCat traceCategory, String resourceId, Object[] resourceArgs) at Microsoft.SharePoint.SPWebTemplateElement.VerifyFeatures(XmlNodeList xmlNodeFeatures, SPWeb applyTemplateToThisWeb, Boolean checkIsFeatureActivatedInSiteCollection) at Microsoft.SharePoint.SPWebTemplateElement.VerifyFeaturesInWebTemplate(SPWeb applyTemplateToThisWeb) at Microsoft.SharePoint.SPWeb.LoadFeatureWebTemplateContent(SPFeatureWebTemplate featureWebTemplate) at Microsoft.SharePoint.SPWeb.ApplyWebTemplate(String strWebTemplate) at Microsoft.SharePoint.SPSite.CreateWeb(String strUrl, String strTitle, String strDescription, UInt32 nLCID, String strWebTemplate, Boolean bCreateUniqueSubweb, Boolean bConvertIfThere, Guid webId, Guid rootFolderId, Boolean createSystemCatalogs) at Microsoft.SharePoint.SPSite.SPWebCollectionProvider.CreateWeb(String strWebUrl, String strTitle, String strDescription, UInt32 nLCID, String strWebTemplate, Boolean bCreateUniqueSubweb, Boolean bConvertIfThere) at Microsoft.SharePoint.SPWebCollection.Add(String strWebUrl, String strTitle, String strDescription, UInt32 nLCID, String strWebTemplate, Boolean useUniquePermissions, Boolean bConvertIfThere) at Microsoft.Office.Project.Server.BusinessLayer.Admin.CreateSPWeb(SPSite topSite, String spWebUrl, String spWebName, String spWebDescription, String spWebLogoUrl, Int32 webTemplateLCID, String webTemplateName, String& errorMessage):
      • WSSCreateSiteFailure (16400). Detalhes: id='16400' name='WSSCreateSiteFailure' uid='e97faef6-a68c-4689-8695-628e9157dec1' projectUID='2d13f678-aea6-4dc8-bd04-f0f820e261e6' workspaceUrl='http://xxxxx/PWA/ProjetoModeloMV/ProjetoModeloMV' projectWorkspaceName='ProjetoModeloMV'.
    • Queue:
      • GeneralQueueJobFailed (26000) - CreateWssSite.CreateWssSiteMessage. Detalhes: id='26000' name='GeneralQueueJobFailed' uid='506b7ee9-174a-4150-8868-192b7d94ac8e' JobUID='dac1092f-d18c-4e46-be71-3f735b8fbf7f' ComputerName='xxxxxxxx' GroupType='CreateWssSite' MessageType='CreateWssSiteMessage' MessageId='1' Stage=''.

    PL

    Wednesday, August 15, 2012 12:03 AM

Answers

  • Generally when i experience this error in 2010 it means i have left a feature activated in the site template which is not available in the destination environment. I found you get a more meanningful error message by creating the site through SharePoint rather than letting MS Porject provision the site for you.

    Navigate to Site Settings>New Site, create the site using your template and see what message you get this time. Ideally it would be good to monitor the SharePoint logs at this point for all information but if this is the problem you will find a reference to a feature ID. Take this id and use PowerShell on the SharePoint server to track down what this feature is in your source template location.

    Get-SPFeature <FEATURE GUID>

    This will return the text name of the feature.

    You may find some hidden features aare required but not accessible via the normal site feature GUI so use the following command line code to active the site feature in the destination environment. Either this or deactive the feature in the source location and re-provision the site template.

    stsadm -o activatefeature -id "<FEATURE GUID>" -url "http://projects.client.com.au/pws"
    Hope this helps :)

    Regards,

    Piet Remen
    http://pietremen.blogspot.com.au

    Wednesday, August 15, 2012 2:59 AM

All replies

  • Generally when i experience this error in 2010 it means i have left a feature activated in the site template which is not available in the destination environment. I found you get a more meanningful error message by creating the site through SharePoint rather than letting MS Porject provision the site for you.

    Navigate to Site Settings>New Site, create the site using your template and see what message you get this time. Ideally it would be good to monitor the SharePoint logs at this point for all information but if this is the problem you will find a reference to a feature ID. Take this id and use PowerShell on the SharePoint server to track down what this feature is in your source template location.

    Get-SPFeature <FEATURE GUID>

    This will return the text name of the feature.

    You may find some hidden features aare required but not accessible via the normal site feature GUI so use the following command line code to active the site feature in the destination environment. Either this or deactive the feature in the source location and re-provision the site template.

    stsadm -o activatefeature -id "<FEATURE GUID>" -url "http://projects.client.com.au/pws"
    Hope this helps :)

    Regards,

    Piet Remen
    http://pietremen.blogspot.com.au

    Wednesday, August 15, 2012 2:59 AM
  • Hi PL

    Piet already gave answer to what the issue might be, adding to it,

    Just cleaning the queue might not help unless the template is fixed, the problem seems to be with the template would suggest start customizing a fresh site template and using it to create workspace from it, you might want to have a look at this blog : http://blogs.msdn.com/b/brismith/archive/2010/03/15/customizing-the-project-site-in-project-server-2010.aspx

    Assuming by force cleanup you are referring to removing the items displaying in queue job grid, Just want to point out as long as the queue job is not blocking all other jobs in correlation you are fine as other jobs will get processed irrespective of faield job, for force cleaning you might want to reduce the clean up interval, clean up interval offset,  in queue settings and accordingly will clean the jobs

    Let us know if this helps


    Thanks | Sunil Kr Singh | http://epmxperts.wordpress.com

    Wednesday, August 15, 2012 2:40 PM
    Moderator