none
Error upgrading a PWA instance to 2010 (Post provision setup failed) RRS feed

  • Question

  • Hi everyone,

    We're upgrading a 2007 instance to 2010, by moving the 5 DBs to a new server.

    After cleaning the orphaned sites, missing webparts et al the WSS_Content DB migrates successfully. When provisioning a new PWA site (PWATest) on this instance it works fine, when provisioning against the existing DB (PWA) it fails after the provisioning (logs indicate provisioning was 100% done with 0 errors and 0 warnings encountered.).

     

    Here's the ULS relevant part:

    Area                           Category                       EventID Level     Message Correlation

    Project Server                 General                       8zdy High     PSI resource assembly dll Microsoft.Office.Project.Shared.Intl, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c is loaded. e94c3953-eeca-4660-8975-76e986eca4f7

    Project Server                 General                       5961 Information GetLanguageInfo succeed for PWA site 92790ec6-fd4f-4d41-92be-8aa46b9fd7e1. Default language is 1033. Number of languages installed is 1 e94c3953-eeca-4660-8975-76e986eca4f7

    Project Server                 Security                       65uy High     User validation failed in platform context: UserName:, CallingUser: COMPANY\PrjAdmin, Site: http://csiv180/PWA e94c3953-eeca-4660-8975-76e986eca4f7

    Project Server                 Security                       cf2l Exception e94c3953-eeca-4660-8975-76e986eca4f7

    Project Server                 Unified Logging Service       c91s Monitorable Watson bucket parameters: Microsoft Project Server 2010, ULSException14, 070f6ea0 "project server", 0e00129b "14.0.4763.0", MISSING, MISSING, MISSING, MISSING, MISSING, MISSING, 6366326c "cf2l" e94c3953-eeca-4660-8975-76e986eca4f7

    Project Server                 Provisioning                   7013 Critical Provisioning 'SharePoint - 80:PWA': Post provision setup failed. An exception occured: Exception has been thrown by the target of an invocation.. e94c3953-eeca-4660-8975-76e986eca4f7

    SharePoint Foundation         Topology                       8xqz Medium   Updating SPPersistedObject ProjectSite Name=92790ec6-fd4f-4d41-92be-8aa46b9fd7e1. Version: 251718 Ensure: False, HashCode: 54529398, Id: 1fa910f8-b0cf-4aab-803a-a62ef72a990f, Stack:    at Microsoft.SharePoint.Administration.SPPersistedObject.BaseUpdate()     at Microsoft.Office.Project.Server.Administration.PsiServiceApplication.PostProvisionSetup(PostConfigType postConfigType, ProjectSite projectSite, Guid adminGuid)     at Microsoft.Office.Project.Server.Administration.PsiServiceApplication.CreateSite(ProjectProvisionSettings provset)     at Microsoft.Office.Project.Server.Administration.PsiServiceApplication.RunProvisionJob(ProjectProvisionSettings provset)     at Microsoft.Office.Project.Server.Administration.PsiServiceApplication.AdminSynchronize()     at Microsoft.Office.Project.Serv... e94c3953-eeca-4660-8975-76e986eca4f7

    SharePoint Foundation         Topology                       8xqz Medium   ...er.Administration.ProjectPSISharedApplicationTimerJob.Execute(Guid targetInstanceId)     at Microsoft.SharePoint.Administration.SPTimerJobInvokeInternal.Invoke(SPJobDefinition jd, Guid targetInstanceId, Boolean isTimerService, Int32& result)     at Microsoft.SharePoint.Administration.SPTimerJobInvoke.Invoke(TimerJobExecuteData& data, Int32& result)   e94c3953-eeca-4660-8975-76e986eca4f7

    Project Server                 Provisioning                   6966 Critical Provisioning 'PWA': Post provisioning setup failed. Exception 'Microsoft.Office.Project.Server.Administration.ProvisionException: Post provision setup failed. ---> System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.Security.SecurityException: Failed to create platform context: UserName:, CallingUser: COMPANY\PrjAdmin, Site: http://csiv180/PWA     at Microsoft.Office.Project.Server.Base.PlatformContext.FailInitialize(Exception e)     at Microsoft.Office.Project.Server.Base.PlatformContext..ctor(Boolean isWindowsUser, String username, Guid siteId, SPUrlZone urlZone)  The Zone of the assembly that failed was:  MyComputer     --- End of inner exception stack trace ---     at System.RuntimeMethodHandle._InvokeConstructor(Object[] ... e94c3953-eeca-4660-8975-76e986eca4f7

    Project Server                 Provisioning                   6966 Critical ...args, SignatureStruct& signature, IntPtr declaringType)     at System.Reflection.RuntimeConstructorInfo.Invoke(BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)     at System.RuntimeType.CreateInstanceImpl(BindingFlags bindingAttr, Binder binder, Object[] args, CultureInfo culture, Object[] activationAttributes)     at System.Activator.CreateInstance(Type type, BindingFlags bindingAttr, Binder binder, Object[] args, CultureInfo culture)     at System.RuntimeType.InvokeMember(String name, BindingFlags bindingFlags, Binder binder, Object target, Object[] providedArgs, ParameterModifier[] modifiers, CultureInfo culture, String[] namedParams)     at Microsoft.Office.Project.Server.Administration.PsiServiceApplication.GetPlatformContext(String Admin, Guid siteId)... e94c3953-eeca-4660-8975-76e986eca4f7

    Project Server                 Provisioning                   6966 Critical ...     at Microsoft.Office.Project.Server.Administration.PsiServiceApplication.PostProvisionSetup(PostConfigType postConfigType, ProjectSite projectSite, Guid adminGuid)     --- End of inner exception stack trace ---     at Microsoft.Office.Project.Server.Administration.PsiServiceApplication.PostProvisionSetup(PostConfigType postConfigType, ProjectSite projectSite, Guid adminGuid)     at Microsoft.Office.Project.Server.Administration.PsiServiceApplication.CreateSite(ProjectProvisionSettings provset)'. e94c3953-eeca-4660-8975-76e986eca4f7

    Project Server                 Provisioning                   7073 Information Removing ProjectSite object for 'SharePoint - 80:PWA'. e94c3953-eeca-4660-8975-76e986eca4f7

    SharePoint Foundation         Topology                       8dyx High     Deleting the SPPersistedObject, JobScheduler Name=PwaJobScheduler_SharePoint - 80:PWA. e94c3953-eeca-4660-8975-76e986eca4f7

    I've searched high and low but I can't find anything. Anyone has an idea?

    Many thanks!

    Simon

    Tuesday, January 17, 2012 8:01 PM

All replies

  • Hello Simon,

     

     

     

    Make sure that in 2007 PWA, you are not using one of the reserved custom field or lookup table

     

    Kindly review “Verify your Project Server 2007 data”  section from following TechNet article

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

     

    Also you need to check status of COMPANY\PrjAdmin account in Project Server Published database

    Post provisioning often fails if PWA admin account is inactive.

     Use following query

     

    Select RES_NAME,res_type from MSP_RESOURCES where  WRES_ACCOUNT=’ COMPANY\PrjAdmin’

     

    RES_TYPE=102 indicates account is in inactive state

     

    Thanks,

    Hrishi Deshpande

     

    Tuesday, January 17, 2012 9:34 PM
    Moderator
  • Hi Hrishi,

     

    As far as I can tell there aren't any reserved words. The PreUpgradeCheck on the old server was successful.

     

    The res_type result is 20 for COMPANY\PrjAdmin. It's the same account that is admin for both 2007 and 2010 instances.


    • Edited by Simon Roy Tuesday, January 17, 2012 10:24 PM
    Tuesday, January 17, 2012 10:21 PM
  • Hi there,

    The preupgrade check only checks the SharePoint config / data not project server. I would check the data for Project Server: http://technet.microsoft.com/en-us/library/ee662499.aspx#verifydata

    Thanks

    Paul


    Paul Mather | Twitter | http://pwmather.wordpress.com
    Tuesday, January 17, 2012 10:43 PM
    Moderator
  • Hi Paul,

    Outside of the 4 Custom fields that are already in 2007 (Cost Type, Health, State, Team Name) there aren't any reserved words used.

    Running the script here: http://technet.microsoft.com/en-us/library/gg595640.aspx, reserved words are not an issue but some projects haven't been republished since SP2. I'll try that and report back.

     

    Thanks,

    Simon

    Tuesday, January 17, 2012 11:28 PM
  • I've received the same error after republishing.
    In the ULS, there is a constant exception 'User validation failed in platform context', but it doesn't say what it refers to. Is there any way to set a more detailed logging?
    Wednesday, January 18, 2012 4:24 PM
  • So, i had the exact same problem and tried a lot of stuff to solve the problem.

    My Error:

    User validation failed in platform context: UserName:, CallingUser: [Customer]\[Account], Site: http://[ServerName]/PWA ce0ae20c-637f-48f0-b092-ad968a621760
    Project Server                 Security                       cf2l Exception ce0ae20c-637f-48f0-b092-ad968a621760
    Project Server                 Unified Logging Service       c91s Monitorable Watson bucket parameters: Microsoft Project Server 2010, ULSException14, 070f6ea0 "project server", 0e00178d "14.0.6029.0", MISSING, MISSING, MISSING, MISSING, MISSING, MISSING, 6366326c "cf2l" ce0ae20c-637f-48f0-b092-ad968a621760
    Project Server                 Provisioning                   7013 Critical Provisioning 'PWA Web Site:PWA': Post provision setup failed. An exception occured: Exception has been thrown by the target of an invocation.. ce0ae20c-637f-48f0-b092-ad968a621760
    SharePoint Foundation         Topology                       8xqz Medium   Updating SPPersistedObject ProjectSite Name=ce3cc576-e94f-424a-9670-d0076c108601. 

    Version: 3571404 Ensure: False, HashCode: 23972246, Id: 6bdfd8f2-ce6e-43ac-8ab8-e2fcab36008b, 
    Stack:    
    at Microsoft.SharePoint.Administration.SPPersistedObject.BaseUpdate()     
    at Microsoft.Office.Project.Server.Administration.PsiServiceApplication.PostProvisionSetup(PostConfigType postConfigType, ProjectSite projectSite, Guid adminGuid)     
    at Microsoft.Office.Project.Server.Administration.PsiServiceApplication.ProjectSitePostProvisionSetup(PostConfigType postConfigType, ProjectSite projectSite)     
    at Microsoft.Office.Project.Server.Cmdlet.PSCmdletUpgradePwaInstance.UpgradeProjectSite()     
    at Microsoft.Office.Project.Server.Cmdlet.PSCmdletUpgradePwaInstance.InternalProcessRecord()     
    at Microsoft.SharePoint.PowerShell.SPCmdlet.ProcessRecord()     

    at System.Management.Automation.CommandProcessor.ProcessRecord()     
    at System.Management.Automation.CommandProcessorBase.DoExecute()     
    at System.Management.Automation.Internal.PipelineProcessor.SynchronousExecuteEnumerate(Object input, Hashtable errorResults, Boolean enumerate)     
    at System.Management.Automation.PipelineNode.Execute(Array input, Pipe outputPipe, ArrayList& resultList, ExecutionContext context)     
    at System.Management.Automation.StatementListNode.ExecuteStatement(ParseTreeNode statement, Array input, Pipe outputPipe, ArrayList& resultList, ExecutionContext context)     
    at System.Management.Automation.StatementListNode.Execute(Array input, Pipe outputPipe, ArrayList& resultList, ExecutionContext context)     
    at System.Management.Automation.ParseTreeNode.Execute(Array input, Pipe outputPipe, ExecutionContext context)     
    at System.Management.Automation.ScriptCommandProcessor.ExecuteWithCatch(ParseTreeNode ptn, Array inputToProcess)     
    at System.Management.Automation.ScriptCommandProcessor.RunClause(ParseTreeNode clause, Object dollarUnderbar, Object inputToProcess)     
    at System.Management.Automation.CommandProcessorBase.DoComplete()     at System.Management.Automation.Internal.PipelineProcessor.SynchronousExecuteEnumerate(Object input, Hashtable
    at System.Management.Automation.Internal.PipelineProcessor.Execute()     
    at System.Management.Automation.Runspaces.LocalPipeline.InvokeHelper()     
    at System.Management.Automation.Runspaces.LocalPipeline.InvokeThreadProc()    
    at System.Management.Automation.Runspaces.PipelineThread.WorkerProc()     
    at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object 
    at System.Threading.ThreadHelper.ThreadStart()  

    Steps i used to solve the problem:

    1.   Running the PowerShell command: Upgrade-SPProjectWebInstance -Url http://dka459/pwa

    2. Restarting services

    3. Gave local admin to the farm account

    4. made sure the farmaccount was in the farm administrators group in Central admin.

    5. Resizing page file (and restart)

    6. Publishing the UMT Financials exstension

    (UMT gave a database permission error)

    7. Giving sysadmin permission to the farmaccount.

    I am pretty sure step 7 solved the problem, but included the other steps anyway.



    http://technicaltrix.blogspot.dk/

    Wednesday, February 3, 2016 1:18 PM