none
Upgrade PS07 to PS2010 - PWA Provision Error RRS feed

  • Question

  • Dear All,

    I am migrating system from PS2007 to PS2010. During the PWA provisioning I got following errors:


    [OWSTIMER] [PublishedDatabaseSequence] [INFO] [8/12/2012 1:56:34 PM]: ProjectDatabase Name=XXX_ProjectServer_Published
    [OWSTIMER] [PublishedDatabaseSequence] [WARNING] [8/12/2012 1:56:34 PM]: Could not find membership provider AspNetSqlMembershipProvider

    [OWSTIMER] [PublishedDatabaseSequence] [INFO] [8/12/2012 1:56:34 PM]: ProjectDatabase Name=XXX_ProjectServer_Published
    [OWSTIMER] [PublishedDatabaseSequence] [WARNING] [8/12/2012 1:56:34 PM]: Exception: Could not find membership provider AspNetSqlMembershipProvider

    [OWSTIMER] [PublishedDatabaseSequence] [INFO] [8/12/2012 1:56:34 PM]: ProjectDatabase Name=XXX_ProjectServer_Published
    [OWSTIMER] [PublishedDatabaseSequence] [WARNING] [8/12/2012 1:56:34 PM]:    at Microsoft.Office.Project.Server.ClaimsHelper.ConvertAccountFormat(String account)
       at Microsoft.Office.Project.Server.Upgrade.ProjectDatabaseSequence.PopulateClaimsAccounts()


    I checked the 2007 system, there is only one AspNetSqlMembershipProvider:XXXX user. Should I try again after removing this user?


    So, any idea how to resolve this issue and make the PWA provisioning smooth?


    Thank you
    Best Regards


    Mohsin Raza





    Sunday, August 12, 2012 10:44 AM

All replies

  • Hi Moshin,

    What is the current CU or SP level of source 2007 and destination 2010 farm?


    Hrishi Deshpande – Senior Consultant DeltaBahn
    Blog | < | LinkedIn

    Sunday, August 12, 2012 5:23 PM
    Moderator
  • Hi,

    Could you also answer what kind of authenication you use in your farm?

    With Kind Regards,

    Robin Kruithof


    Technical Consultant EPM

    Monday, August 13, 2012 6:18 AM
  • Hrishi,

    we have SP3.


    Mohsin Raza

    Monday, August 13, 2012 7:53 AM
  • on 2007, we have been using both AD and Form Based. but i dont want this FB authentication on 2010, so we can omit this during the migration.

    So, can I delete AspNetSqlMembershipProvider user and try it now again?


    Mohsin Raza

    Monday, August 13, 2012 7:54 AM