Installation of Project Server 2010 over 2 App, 2 WFE, NLB Farm

We are installing Project Server 2010 in a 6-server farm with 2 App, 2 WFE, 2 DB (Cluster) architecture on Win 2012 R2 Serrvers. And will be using hardware NLB.
Though I am aware of setting up MS Project Server in 3-tier architecture using NLB, I am not sure how to set up in the farm mentioned above.
Till now, I have installed and configured SharePoint 2010 in both the App servers and WFE's. Created SP site collection and Project Server Service application in App01. Now how do I proceed with App02 and 2 WFE's.
Do I need to extend the SharePoint Application on App01 to App02 or create a new SharePoint Application and site collection on App02? I am hoping to extend the SP Application from App01 to App02 using "Donot host website on this server option".
I have enabled all the services and features required for SharePoint and Project Server on App01. I am thinking of will do the same on App02 as well, but not sure if that is what I am supposed to do.
What about the WFE's. If I create Service application and enable services on App servers, what will I be hosting on WFE's. Am I supposed to only enable services and Features on App servers and create service applications on WFE's.
As we have two WFE's am I supposed to create Project Server Service applications on each of the WFE or configure the WFE01 with project server service application created on App01 with "Host Website on this server" option and then extend the same
to WFE02. 
I am sure, I will use the host header name, used for creating DNS alias while setting up NLB, in WFE's.
Sorry for many questions but it is currently my state of mind on this.

Hello,
In a typical 2 app and 2 WFE topology I would have the Project Server Service Application running on both App servers so that SharePoint internally load balances the requests then have the PWA site load balanced between the 2 WFEs - set up the web application
that hosts the PWA site using a DNS name, point the DNS name to the load balanced IP. So most of the SharePoint services will run across both App servers once started on both, some services will only run on one App but the additional services (not including
the minimum for SharePoint) required by Project Server (Excel Calc, PerformancePoint, Secure Store, Project Server) can safely run on both app servers. I wouldn't start the Project Server service application on the WFEs as the WFE wouldn't be true
WFE.
Paul
Paul Mather | Twitter |
http://pwmather.wordpress.com | CPS

Similar Messages

  • Project Server 2010 - Project Center is stuck on loading

    Hello,
    I have a new installation of project server 2010. When I go to the pwa site and click on project center it is stuck on loading (see print screen)
    Any Idea?
    Thanks

    Hi,
     Please connect to IIS manager
    In IIS, expand sites click on SharePoint Web Service 
    In the right hand side panel, double click on compression
    Uncheck Dynamic compression and static compression and click on apply
    Repeat the steps for PWA web application site
    Hrishi Deshpande – Senior Consultant DeltaBahn
    Blog | < |
    LinkedIn
    Please click Mark As Answer; if a post solves your problem or Vote As Helpful; if a post has been useful to you

  • Do I *really* need a Service Connection Point in AD to complete a Project Server 2010 SP2 installation?

    Hi all,
    I have installed Project Server 2010 SP2 and run psconfig.exe
    PSCONFIG is failing because it cannot set up a Service Connection Point in AD. I've checked in AD and the contains 'Microsoft SharePoint Products' does not exist. All the resolutions I can find suggest adding the container into AD.
    The issue I have is that I have no control of the AD, and adding containers will take lengthily negotiation.
    Is there any way of completing the installation and getting my site back without adding the container into AD?
    Thanks in advance.

    other solutions
    1) check timer service see if it is running
    http://www.jonthenerd.com/2011/06/30/sharepoint-2010-sp1-upgrade-error-unable-to-create-a-service-connection-point-in-the-current-active-directory-domain/
    2) check UAC (and the rest of the technet answers - some are listed below)
    http://social.technet.microsoft.com/Forums/en-US/94a8bb64-e0ea-493f-8e29-01347b1fc6c7/psconfig-fails-failed-to-upgrade-sharepoint-products
    3) My workaround:I
    run once again the command „PSConfig.exe -cmd upgrade -inplace b2b -force -cmd applicationcontent -install -cmd installfeatures“  in
    the “Bin” Folder as an administrator console session.In the moment I saw the staus “Configurationtask 5 of 6 is executed”
    I start to run the command “net start SPTraceV4 & net start SPWriterV4 & net start SPAdminV4 & net start SPSearch4 & net start SPTimerV4” in a parallel administrator console session and after that the configuration task finished successfully.
    http://social.technet.microsoft.com/Forums/en-US/94a8bb64-e0ea-493f-8e29-01347b1fc6c7/psconfig-fails-failed-to-upgrade-sharepoint-products
    4) Try running the psconfig.exe command a second time
    5) had the same issue and called Microsoft support.  Here is the fix:
    Stop the "SharePoint 2010 Timer" service
    Delete ONLY the xml files from C:\ProgramData\Microsoft\SharePoint\Config\216f8013-b78b-4e5b-8631-3a5f4c7277e8
    Note: Do NOT delete the cache.ini file in this folder
    Edit cache.ini and change to "1"
    Start "SharePoint
    2010 Timer" service
    Run psconfig again:  PSConfig.exe -cmd upgrade -inplace b2b -wait -force
    6) Initially I tried http://support.microsoft.com/kb/2009272 but
    it did not help (I re-implemented later).
    I re-registered the DLL’s as perhttp://social.technet.microsoft.com/Forums/da/winservergen/thread/b4bd0deb-45d0-4661-8c50-a2b45db41103 from
    NareshD.  I do not believe this is necessary unless there is a corruption in the system but I am noting here just
    in case.
    I tried to run The PSConfig but it was failing:  I
    had to do the following in order to make it finish successfully:
    (from same page at http://social.technet.microsoft.com/Forums/en-US/smallbusinessserver/thread/94a8bb64-e0ea-493f-8e29-01347b1fc6c7/)
    On the migrated SBS2011 PSCDiagnostic Log I found no entry to detect or start the services SPWriterServiceInstance and SPTimerServiceInstance.
    I run once again the command „PSConfig.exe -cmd upgrade -inplace b2b -force -cmd applicationcontent
    -install -cmd installfeatures“ in the “Bin” Folder as an administrator console session.
    In
    the moment I saw the status “Configuration task 5 of 6 is executed” I
    start to run the command “net start SPTraceV4 & net start SPWriterV4 & net start SPAdminV4 & net start SPSearch4 & net start SPTimerV4” in a
    parallel administrator console session and after that, the configuration task finished successfully.  (I
    just opened another cmd window and copy/paste the sequence below when I saw the status “Configuration Task x of y” on the screen:
    net start SPTraceV4 
    net start SPWriterV4 
    net start SPAdminV4 
    net start SPSearch4 
    net start SPTimerV4
    -Note SPSearch4 is disabled in our system…
    Very awkward but it worked…
    I implemented http://support.microsoft.com/kb/2009272 again.
    Backup started working with no errors.

  • Project Server 2010 - Active Directory Enterprise Resource Pool Synchronization limitations

    Greetings again.
    I have a quick question about the limitations of Active Directory Enterprise Resource Pool Synchronization.  Specifically, what has your experience
    been with extremely large numbers of users (10k plus).  Is anyone aware of a
    practical limit of users in your AD group you would recommend when using the
    Schedule Synchronization feature on a nightly or weekly basis?
    There is a caveat to this question however.  The client has decided (perhaps for some misinformed reasons) to allow access for every user, to every
    project site, within their PWA environment.  They’ve selected the View Project Site option within the
    Categories for the Team Members PWA Group for which 90% of their intended users reside.  So when we ran a couple test syncs in DEV with a smaller AD group of about 8,000 users, the sync understandably
    lasted upwards of 18 hours.  Obviously unacceptable for a PROD environment on a nightly basis and not necessarily ideal for a weekly sync either.
    Experience in addition to documents like these, “Best
    practices for managing a large number of resources in Project Server 2010” tell me that we are way over the practical limit of a scheduled resource pool synchronization...IF
    the client really desires that all users access all their sites.  But before I submit my recommendations, I wanted to check with the community just in case others may have found a way to synchronize large numbers of users (10k plus) on a nightly or weekly
    basis, within a reasonable time frame AND allowed all users to access all sites within PWA.
    What do you think?
    As always, thanks for your help.
    Chris Addis - MCTS

    Hello Hrishi.
    My delayed response has been due to a large amount of testing we have been performing on this particular topic.  Here is an update, please feel free to provide feedback.
    We went back to testing and spent more time reviewing the documents: 
    Best practices for managing a large number of resources in Project Server 2010 and
    SharePoint Server 2010 capacity management: Software boundaries and limits.  Our team interpreted those documents as saying, 1,000 security
    scopes per site is a recommended limit.  It does not say it’s a hard limit, just a recommended limit.  “When the recommended unique security scope boundaries are exceeded, performance issue can occur.”
    So we decided to perform some tests (31 in total) to try and get a gage of what we are seeing.
    We needed to establish a baseline first.  So we performed a series of 23 Active Directory Resource Pool Synchronizations with various settings in a clean, Out of the Box, environment in order to see some consistent numbers.  Here is it’s summary:
    Our AD group of 8,000 users took about 32 minutes, on average, every time to sync.  The difference between the first sync and last sync differed only by 1-3 minutes.
    Adding 40 project sites increased the average sync time from 32 to 120 minutes.
    Adding 100 users to each of those 40 project sites, did not increase the sync times.
    One setting (identified at this time) reduced the synchronization time.  It was the
    Project Site Permissions check box found within the Project Web App > Server Settings > Project Site Provisioning Settings area.  By deselecting this check box we reduced or synchronization time back to the 32 minute
    average.
    The View Project Site check box within the Project Web App > Server Settings > Manage Groups > Team Members group had no apparent effect on the sync times besides what we had gleaned from the Microsoft documentation.
    Naturally, this left us with a problem.  As I’m sure you know, by deselecting the check box (Project Site Permissions), our project sites are now (figuratively speaking) orphans with no connection to the parent site.  This generates
    a new set of issues.  For example:
    Newly created project sites cannot be accessed by the owner and team members.  They will require someone like the farm admin to come in behind them and add the intended users to the project site along with their required permissions.
    All current and futures sites will no longer have users added via the standard method of building a team and publishing the project, but will have to be added manually.
    You can use the Synchronize option found within Project Web App > Server Settings > Project Sites page, but that kinda defeats the purpose.  It would require constant updating on a per site basis to keep up with
    PM changes.  Not very sensible, but it does work.
    With this baseline information, we moved our tests into our DEV environment which somewhat mimics our PROD environment.  This environment has 352 project sites and we performed 8 tests.  This is where we had some large sync time numbers. 
    Here is the DEV test summary:
    With the Project Site Permissions check box cleared, our AD group of 8,000 users took on average 30 minutes to sync.  This was in line with our baseline times.  With the exception of one test sync that took 99 minutes to complete. 
    That anomaly is acquiescent with what I’ve seen over the years.  Sometimes syncs do some unusual things.
    With the Project Site Permissions check box selected, our AD group of 8,000 users took on average 690 minutes (11.5 hours) to sync.  Unacceptable of course.
    So here’s what we’ve learned when dealing with extremely large numbers of active directory users in your Resource Pool sync:
    We did not see a decrease in subsequent sync times after the initial Active Directory Resource Pool Synchronization as some might expect.
    Our attempt to decrease sync time via the option of removing the View Project Sites was not successful.  (Unless we interpreted Microsoft's document incorrectly.)
    However, our interpretation of the recommended software boundaries and limits of SharePoint Server 2010 as it pertains to security scopes per site at 1,000, appears to be correct.
    Using the option of clearing the Project Site Permissions does produce a reduction in AD sync time, but at a cost segregating your project sites and thus the creation of new processes of maintaining them.
    I’ll remind others that these results are particular to our environments, there may still be exceptions yet to discover.  Others may see numbers contrary to ours.
    The biggest surprise to some members on our team (myself excluded) was that we did not see a reduced sync time after any of our initial syncs.  Some are under the impression that after your initial sync, you should see reduced sync times.  I haven’t
    found that to be the absolute case in all situations, just in some situations.  The reason for this still eludes me.  Any thoughts would be appreciated.
    I’ll let this sit a bit longer, but if no one disagrees with the results, I think we have our answer:
    The number of project sites directly affects your Active Directory Resource Pool Synchronizations if you are using the
    Project Site Permissions option.  If you plan on synchronizing over 1,000 users
    and you have a large number of project sites, proceed with the knowledge that you may have performance issues and long sync times.
    As always, I’d love to hear from you or others just in case I’m missing something.
    Chris Addis - MCTS

  • Bulk Project Site option isn't working in project server 2010 migrated from PS 2007.

    Hi,
    I am doing a test migration from epm 2007 to epm 2013. 
    So first, i need to migrate the project server 2007 to project server 2010. i have 2 separate environments for EPM 2007 and EPM 2010).
    there is no problem in migration process and i successfully migrate entire PWA 2007 to 2010, except Workspaces (Project sites).
    Bulk project site option is not helping. I have tried 4-5 times with different PWA 2007 databases (PWA1, PWA2...) but this option did not work. and errors in queue are WSSWebDoesNotExist(16405) and GeneralQueueJobFailed(26000).
    Then next time while migrating all over again i kept the same port and same PWA name then bulk project site option worked.
    Question is, Do i need to keep the same PWA name and same port for the new upgraded PWA??,  one more issue regarding this is that if don't keep the same PWA name and i open the project site and click on the "Project web app" back link, it
    redirects me to old PWA site which doesn't exist and give me page not found error (Obviously).
    Below, you can see the both scenarios.
    my previous PWA 2007 site, say  - http://epm2007:2222/PWA
    When  -  migrated PWA 2010 site, say  - http://epm2010:3000/NewPWA    (Bulk project site update just doesn't work)
    When -  migrated PWA 2010 site, say  - http://epm2010:2222/PWA    (Bulk project site update worked)
    Whats the solution of this problem. is there any utility or query to link all project sites correctly?
    Will i face the same problem while migrating PS 2010 to PS 2013??
    Thank you.
    sandeep

    Hi,
    I would say it is easier to keep the same PWA name between 2007 and 2010 (no need to have the same port).
    If you want to move to a new PWA URL maybe you can use stsadm backup/restore as detailed in this article?
    http://technet.microsoft.com/en-gb/library/ee662500(v=office.14).aspx
    Hope this helps
    Paul

  • Problem: Task completion sync back from Exchange 2010 to Project Server 2010

    I have new installation of PS 2010 and Exchange 2010 (one server holds all roles including CAS).
    For sync between PS and EX 2010, I following the technet article Configure Project Server 2010 to work with Exchange Server 2010 at http://technet.microsoft.com/en-us/library/ff468700%28office.14%29.aspx (yes I read the second part on Impersonation, too).
    Basically I followed the video and opted for "Impersonation for all users".
    I got tasks appear in resources outlook "Tasks" folder no problem. They appeared instantly after project is published. But when the resource update the completion in outlook, it failed to update the Project server.
    The applog on Exchange server has the following events:
    A notification for subscription [IABmaWxiZXJ0Lm1zYy5hbHR1cmFzYW5hbHl0aWNzLmNvbRAAAABpsVspLo+TSpth0iMukr+TjiFq73wS0Qg=] against endpoint [http://MyPSserver/PWA/_vti_bin/PSI/ExchangeSync.asmx] couldn't be sent. (Send attempts: 2) Details: WebException:
    The remote server returned an error: (500) Internal Server Error. StatusCode: InternalServerError Internal Server Error    at System.Net.HttpWebRequest.EndGetResponse(IAsyncResult asyncResult)
       at Microsoft.Exchange.Services.Core.NotificationServiceClient.HandleResponse(IAsyncResult responseAsyncResult)
    After 8 unsuccessful attempts to send a notification for subscription [IABmaWxiZXJ0Lm1zYy5hbHR1cmFzYW5hbHl0aWNzLmNvbRAAAABaEEJ+4ahFSY6IVGcSZ7/m4kLgKCES0Qg=] against endpoint [http://MyPSserver/PWA/_vti_bin/PSI/ExchangeSync.asmx], the subscription has
    been removed. Details: WebException: The remote server returned an error: (500) Internal Server Error. StatusCode: InternalServerError Internal Server Error    at System.Net.HttpWebRequest.EndGetResponse(IAsyncResult asyncResult)
       at Microsoft.Exchange.Services.Core.NotificationServiceClient.HandleResponse(IAsyncResult responseAsyncResult
    The W3C log on PS app server has the following related entries (401 and 500 errors. 10.0.0.76 is Exch server. 10.0.0.77 is the PS app server):
    2014-03-20 18:12:39 10.0.0.77 POST /PWA/_vti_bin/PSI/ExchangeSync.asmx - 80 - 10.0.0.76 - 401 2 5 0
    2014-03-20 18:12:39 10.0.0.77 POST /PWA/_vti_bin/PSI/ExchangeSync.asmx - 80 - 10.0.0.76 - 401 1 2148074254 15
    2014-03-20 18:12:39 10.0.0.77 POST /_vti_bin/PSI/ExchangeSync.asmx - 80 MyDomain\MyExchServer$ 10.0.0.76 - 500 0 0 31
    2014-03-20 18:12:39 10.0.0.77 POST /PWA/_vti_bin/PSI/ExchangeSync.asmx - 80 - 10.0.0.76 - 401 2 5 0
    2014-03-20 18:12:39 10.0.0.77 POST /PWA/_vti_bin/PSI/ExchangeSync.asmx - 80 - 10.0.0.76 - 401 1 2148074254 0
    2014-03-20 18:12:39 10.0.0.77 POST /_vti_bin/PSI/ExchangeSync.asmx - 80 MyDomain\MyExchServer$ 10.0.0.76 - 500 0 0 31
    2014-03-20 18:12:39 10.0.0.77 POST /PWA/_vti_bin/PSI/ExchangeSync.asmx - 80 - 10.0.0.76 - 401 2 5 0
    2014-03-20 18:12:39 10.0.0.77 POST /PWA/_vti_bin/PSI/ExchangeSync.asmx - 80 - 10.0.0.76 - 401 1 2148074254 0
    2014-03-20 18:12:39 10.0.0.77 POST /_vti_bin/PSI/ExchangeSync.asmx - 80 MyDomain\MyExchServer$ 10.0.0.76 - 500 0 0 31
    2014-03-20 18:12:41 10.0.0.77 POST /PWA/_vti_bin/PSI/ExchangeSync.asmx - 80 - 10.0.0.76 - 401 2 5 0
    2014-03-20 18:12:41 10.0.0.77 POST /PWA/_vti_bin/PSI/ExchangeSync.asmx - 80 - 10.0.0.76 - 401 1 2148074254 0
    2014-03-20 18:12:41 10.0.0.77 POST /_vti_bin/PSI/ExchangeSync.asmx - 80 MyDomain\MyExchServer$ 10.0.0.76 - 500 0 0 62
    2014-03-20 18:28:39 10.0.0.77 POST /PWA/_vti_bin/PSI/ExchangeSync.asmx - 80 - 10.0.0.76 - 401 2 5 15
    2014-03-20 18:28:39 10.0.0.77 POST /PWA/_vti_bin/PSI/ExchangeSync.asmx - 80 - 10.0.0.76 - 401 1 2148074254 0
    2014-03-20 18:28:39 10.0.0.77 POST /_vti_bin/PSI/ExchangeSync.asmx - 80 MyDomain\MyExchServer$ 10.0.0.76 - 500 0 0 46
    2014-03-20 18:28:39 10.0.0.77 POST /PWA/_vti_bin/PSI/ExchangeSync.asmx - 80 - 10.0.0.76 - 401 2 5 15
    2014-03-20 18:28:39 10.0.0.77 POST /PWA/_vti_bin/PSI/ExchangeSync.asmx - 80 - 10.0.0.76 - 401 1 2148074254 0
    2014-03-20 18:28:39 10.0.0.77 POST /_vti_bin/PSI/ExchangeSync.asmx - 80 MyDomain\MyExchServer$ 10.0.0.76 - 500 0 0 31
    2014-03-20 18:28:39 10.0.0.77 POST /PWA/_vti_bin/PSI/ExchangeSync.asmx - 80 - 10.0.0.76 - 401 2 5 0
    2014-03-20 18:28:39 10.0.0.77 POST /PWA/_vti_bin/PSI/ExchangeSync.asmx - 80 - 10.0.0.76 - 401 1 2148074254 0
    2014-03-20 18:28:39 10.0.0.77 POST /_vti_bin/PSI/ExchangeSync.asmx - 80 MyDomain\MyExchServer$ 10.0.0.76 - 500 0 0 15
    2014-03-20 18:28:41 10.0.0.77 POST /PWA/_vti_bin/PSI/ExchangeSync.asmx - 80 - 10.0.0.76 - 401 2 5 15
    2014-03-20 18:28:41 10.0.0.77 POST /PWA/_vti_bin/PSI/ExchangeSync.asmx - 80 - 10.0.0.76 - 401 1 2148074254 0
    2014-03-20 18:28:41 10.0.0.77 POST /_vti_bin/PSI/ExchangeSync.asmx - 80 MyDomain\MyExchServer$ 10.0.0.76 - 500 0 0 15
    I am new to PS 2010. Help is appreciated. Thanks.

    Here are the errors found in Project Queues:
    ExchangeSyncExchangeSubscriptionUpdateForUserFailed (40511). Details: id='40511' name='ExchangeSyncExchangeSubscriptionUpdateForUserFailed' uid='ef501cc2-9305-47b5-92b3-021e3b41d1b5' teamMemberUid='b8f2e0cd-9882-4677-be61-b2780b32bae5' exception='System.NullReferenceException:
    Object reference not set to an instance of an object. at Microsoft.Office.Project.Server.ExchangeSync.ExchangeSyncUtil.UpdateExchangeSubscription(Guid resourceUid, SubscriptionContext context) at Microsoft.Office.Project.Server.ExchangeSync.ExchangeSyncUtil.UpdateExchangeSubscription(Guid
    resourceUid) at Microsoft.Office.Project.Server.ExchangeSync.ExchangeSubscriptionRefreshProcessor.Refresh(PlatformContext ctx)'.
    ReportingProjectChangeMessageFailed (24006) - The INSERT statement conflicted with the FOREIGN KEY constraint "FK_MSP_EpmAssignment_ResourceOwnerUID". The conflict occurred in database "ProjectServer_Reporting", table "dbo.MSP_EpmResource", column 'ResourceUID'.
    The statement has been terminated.. Details: id='24006' name='ReportingProjectChangeMessageFailed' uid='ef4e51a1-8cb2-4ec2-bfc4-530f1f34cd8c' QueueMessageBody='Project UID='2668bb26-5c23-42ce-843a-fa49feadba05'. PublishType='ProjectPublish'' Error='The INSERT
    statement conflicted with the FOREIGN KEY constraint "FK_MSP_EpmAssignment_ResourceOwnerUID". The conflict occurred in database "ProjectServer_Reporting", table "dbo.MSP_EpmResource", column 'ResourceUID'. The statement has been terminated.'.
    ReportingProjectChangeMessageFailed (24006) - The INSERT statement conflicted with the FOREIGN KEY constraint "FK_MSP_EpmAssignment_ResourceOwnerUID". The conflict occurred in database "ProjectServer_Reporting", table "dbo.MSP_EpmResource", column 'ResourceUID'.
    The statement has been terminated.. Details: id='24006' name='ReportingProjectChangeMessageFailed' uid='0b88178b-2e45-41af-a85f-8c5590e9c3e7' QueueMessageBody='Project UID='2668bb26-5c23-42ce-843a-fa49feadba05'. PublishType='ProjectPublish'' Error='The INSERT
    statement conflicted with the FOREIGN KEY constraint "FK_MSP_EpmAssignment_ResourceOwnerUID". The conflict occurred in database "ProjectServer_Reporting", table "dbo.MSP_EpmResource", column 'ResourceUID'. The statement has been terminated.'.
    ReportingProjectChangeMessageFailed (24006) - The INSERT statement conflicted with the FOREIGN KEY constraint "FK_MSP_EpmAssignment_ResourceOwnerUID". The conflict occurred in database "ProjectServer_Reporting", table "dbo.MSP_EpmResource", column 'ResourceUID'.
    The statement has been terminated.. Details: id='24006' name='ReportingProjectChangeMessageFailed' uid='0d7421f6-2579-4656-b956-d50ecc7f5f1c' QueueMessageBody='Project UID='2668bb26-5c23-42ce-843a-fa49feadba05'. PublishType='ProjectPublish'' Error='The INSERT
    statement conflicted with the FOREIGN KEY constraint "FK_MSP_EpmAssignment_ResourceOwnerUID". The conflict occurred in database "ProjectServer_Reporting", table "dbo.MSP_EpmResource", column 'ResourceUID'. The statement has been terminated.'.
    ReportingProjectChangeMessageFailed (24006) - The INSERT statement conflicted with the FOREIGN KEY constraint "FK_MSP_EpmAssignment_ResourceOwnerUID". The conflict occurred in database "ProjectServer_Reporting", table "dbo.MSP_EpmResource", column 'ResourceUID'.
    The statement has been terminated.. Details: id='24006' name='ReportingProjectChangeMessageFailed' uid='3456b70e-fe16-4b3a-ab66-f2a5237fbaeb' QueueMessageBody='Project UID='2668bb26-5c23-42ce-843a-fa49feadba05'. PublishType='ProjectPublish'' Error='The INSERT
    statement conflicted with the FOREIGN KEY constraint "FK_MSP_EpmAssignment_ResourceOwnerUID". The conflict occurred in database "ProjectServer_Reporting", table "dbo.MSP_EpmResource", column 'ResourceUID'. The statement has been terminated.'.
    ReportingProjectChangeMessageFailed (24006) - The INSERT statement conflicted with the FOREIGN KEY constraint "FK_MSP_EpmAssignment_ResourceOwnerUID". The conflict occurred in database "ProjectServer_Reporting", table "dbo.MSP_EpmResource", column 'ResourceUID'.
    The statement has been terminated.. Details: id='24006' name='ReportingProjectChangeMessageFailed' uid='fc78474a-bf5c-422c-a209-cb79e3201e38' QueueMessageBody='Project UID='2668bb26-5c23-42ce-843a-fa49feadba05'. PublishType='ProjectPublish'' Error='The INSERT
    statement conflicted with the FOREIGN KEY constraint "FK_MSP_EpmAssignment_ResourceOwnerUID". The conflict occurred in database "ProjectServer_Reporting", table "dbo.MSP_EpmResource", column 'ResourceUID'. The statement has been terminated.'.
    ReportingProjectChangeMessageFailed (24006) - The INSERT statement conflicted with the FOREIGN KEY constraint "FK_MSP_EpmAssignment_ResourceOwnerUID". The conflict occurred in database "ProjectServer_Reporting", table "dbo.MSP_EpmResource", column 'ResourceUID'.
    The statement has been terminated.. Details: id='24006' name='ReportingProjectChangeMessageFailed' uid='d2f4b313-0c21-4a2c-b8a7-f6bd7aef13fe' QueueMessageBody='Project UID='2668bb26-5c23-42ce-843a-fa49feadba05'. PublishType='ProjectPublish'' Error='The INSERT
    statement conflicted with the FOREIGN KEY constraint "FK_MSP_EpmAssignment_ResourceOwnerUID". The conflict occurred in database "ProjectServer_Reporting", table "dbo.MSP_EpmResource", column 'ResourceUID'. The statement has been terminated.

  • Project Server 2010 Web services access with Client Certificate Authentication

    We switched our SharePoint/Project Server 2010 farm to use client certificate authentication with Active Directory Federation Services (AD FS) 2.0, which is working without issue. We have some administrative Project Server Interface (PSI)
    web service applications that no longer connect to server with the new authentication configuration.  Our custom applications are using the WCF interface to access the public web services.
    Please let us know if it is possible to authenticate with AD FS 2.0 and then call
    Project Server web services. Any help or coding examples would be greatly appreciated.

    what is the error occurred when the custom PSI app connects?
    can you upload the ULS logs here for research?
    What is the user account format you specified in the code for authentication?
    For proper authorization, the “user logon account” in PWA for the user needs to be changed from domain\username to the claims token (e.g.
    'I:0#.w|mybusinessdomain\ewmccarty').
    It requires you to manually call the UpnLogon method of
    “Claims to Windows Token Service”. if (Thread.CurrentPrincipal.Identity is ClaimsIdentity)  
    {  var identity = (ClaimsIdentity)Thread.CurrentPrincipal.Identity;  }  
    if (Thread.CurrentPrincipal.Identity is ClaimsIdentity)
    var identity = (ClaimsIdentity)Thread.CurrentPrincipal.Identity;
    Than you need to extract UPN-Claim from the identity.
    Upload the verbose log if possible.
    Did you see this?
    http://msdn.microsoft.com/en-us/library/ff181538(v=office.14).aspx
    Cheers. Happy troubleshooting !!! Sriram E - MSFT Enterprise Project Management

  • Project Server 2010 Migratet from one farm to another farm

    Hi ,
    I need to migrate existing Project server 2010 farm one server to another server.
    Kindly suggest me what is the best way we need to fallow.
    Existing Environment two server:
    1.  App server(SharePoint 2010 +Project Server 2010)- Existing PWA site is running
    2.Database server(with DNS instance name)
    New Environment:
    1.App server (fresh installed SharePoint + project server 2010)
    2.DB server fresh server with sql 2008
    Hasan Jamal Siddiqui(MCTS,MCPD,ITIL@V3),Sharepoint and EPM Consultant,TCS
    |
    | Twitter

    Event viewer Error:
    Failed to provision site PWA with error: Microsoft.Office.Project.Server.Administration.ProvisionException: Membership synchronization failed. ---> System.UnauthorizedAccessException: Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED))
       at Microsoft.SharePoint.Library.SPRequest.RemoveRoleDef(String bstrUrl, Int32 lRoleID)
       at Microsoft.SharePoint.SPRoleDefinitionCollection.Delete(SPRoleDefinition roleDefinition)
       at Microsoft.Office.Project.Server.BusinessLayer.SharePointSecurityHelper.DeleteRoleByName(SPWeb web, String roleName)
       at Microsoft.Office.Project.Server.BusinessLayer.SharePointSecurityHelper.DeleteRoles(SPWeb web)
       at Microsoft.Office.Project.Server.BusinessLayer.SharePointSecurityHelper.ConfigureDefaultPWAWSSSecurityModel(SPSite topSite, SPWeb web)
       at Microsoft.Office.Project.Server.BusinessLayer.Admin.<>c__DisplayClass18.<QueueUpdateUsersAddRemoveStatusOnPwaRootsAndWorkspaces>b__17()
       at Microsoft.SharePoint.SPSecurity.<>c__DisplayClass4.<RunWithElevatedPrivileges>b__2()
       at Microsoft.SharePoint.Utilities.SecurityContext.RunAsProcess(CodeToRunElevated secureCode)
       at Microsoft.SharePoint.SPSecurity.RunWithElevatedPrivileges(WaitCallback secureCode, Object param)
       at Microsoft.SharePoint.SPSecurity.RunWithElevatedPrivileges(CodeToRunElevated secureCode)
       at Microsoft.Office.Project.Server.BusinessLayer.Admin.QueueUpdateUsersAddRemoveStatusOnPwaRootsAndWorkspaces(Dictionary`2 deletedUserUidsLoginNames, Guid[] addedUserUids, Boolean isFullSync, Boolean syncWorkspaces)
       at Microsoft.Office.Project.Server.BusinessLayer.Admin.SynchronizeMembershipForPwaAppRootSite()
       at Microsoft.Office.Project.Server.Administration.PsiServiceApplication.SynchronizePwaMembership(ProjectProvisionSettings provset, ProjectSite projectSite)
       --- End of inner exception stack trace ---
       at Microsoft.Office.Project.Server.Administration.PsiServiceApplication.SynchronizePwaMembership(ProjectProvisionSettings provset, ProjectSite projectSite)
       at Microsoft.Office.Project.Server.Administration.PsiServiceApplication.CreateSite(ProjectProvisionSettings provset
    Hasan Jamal Siddiqui(MCTS,MCPD,ITIL@V3),Sharepoint and EPM Consultant,TCS
    |
    | Twitter

  • Project Server 2010 PWA Provisioning Error - System.UnauthorizedAccessException: Access is denied.

    Hi,
    When migrating from a Prod Environment to a Test Environment using the Project Server 2010 5 Database backup and restore process (actually 6 DB's with the Project Sites DB), upon encountering a failure during provisioning the PWA Instance, we get the errors listed
    at the base of this posting in our Event Logs.
    To clarify what we have done already, we have:
    1. Backed up the 6 databases from the Source Environment.
    2. Removed the existing PWA_Content and PWS_Content (Project Sites) databases from the Target Environment Farm.
    3. Restored the 6 databases in the Target Environment.
    4. Given the SP Farm Service Account 'db_owner' rights to each of the 6 restored databases.
    5. Added the PWA_Content and PWS_Content databases  (exact same names) to the Target Environment.
    6. Locked down (offline/stopped), all of the SharePoint Content databases in the Farm except for the PWA_Content database.
    7. Run the PWA Provisioning process from the 'Project Server' SharePoint Service in Central Admin.
    It is during the PWA provisioning that we encounter these errors.
    As the Target Environment is for Test/Dev purposes, the SP Farm Service Account is setup to support all of the SharePoint Farm Services, is in the Local Admin Group of each of the Servers (App, WFE and DB), and is actually in the sysadmin
    role on the DB Server.
    Any suggestions on what is causing this denied access situation would be most appreciated.
    Cheers,
    Wayne
    Event Log Entries:
    ============================================
    Log Name:      Application
    Source:        Microsoft-SharePoint Products-Project Server
    Date:          1/22/2014 2:47:34 PM
    Event ID:      6971
    Task Category: Provisioning
    Level:         Error
    Keywords:     
    User:          ACCOUNTS\svc_psfarm
    Computer:      SERVER.accounts.domain.com
    Description:
    Failed to provision site PWA with error: Microsoft.Office.Project.Server.Administration.ProvisionException: Membership synchronization failed. ---> System.UnauthorizedAccessException: Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED))
       at Microsoft.SharePoint.Library.SPRequest.AddRoleDef(String bstrUrl, String bstrName, String bstrDescription, Boolean bHidden, Int32 lRoleOrder, UInt64 iPermMask, Byte iType, Int32 lRoleDefID)
       at Microsoft.SharePoint.SPRoleDefinitionCollection.AddCore(SPRoleDefinition role)
    etc....
    Failed to create the Report Center web (Exception: PSI Entry Point:
    Project User: DOMAIN\svc_psfarm Correlation Id: c0a30b18-46e4-4447-b469-f8fd3bb1490a
    PWA Site URL: http://pstest2010/PWA
    SSP Name: Project Server
    PSError: NoError (0))
    Failed to grant 'DOMAIN\svc_psfarm' access to web application 'SPWebApplication Name=Portal'.
    Error: System.Security.SecurityException: Access denied.  Only machine administrators are allowed to create administration service job definitions of type: Microsoft.SharePoint.Administration.SPUpdateWorkerProcessGroup, Microsoft.SharePoint, Version=14.0.0.0,
    Culture=neutral, PublicKeyToken=71e9bce111e9429c.
       at Microsoft.SharePoint.Administration.SPAdministrationServiceJobDefinition..ctor(String name, SPService service, SPServer server, SPJobLockType lockType)
       at Microsoft.SharePoint.Administration.SPUpdateWorkerProcessGroup..ctor(SPTimerService timerService, String[] loginsToAdd, String[] loginsToRemove)
       at Microsoft.SharePoint.Administration.SPWebApplication.GrantAccessToProcessIdentity(String username, SPPolicyRoleType policyRole)
       at Microsoft.Office.Project.Server.Administration.PsiServiceApplication.GrantAccessToWebApp(List`1 webApps, String userName) The Zone of the assembly that failed was: MyComputer

    Is the Test and Production in the same domain. If they are not, then the SIDs associated with the SQL accounts may look the same but they are not.  At times, I have had to recreated accounts when in different domains.
    I would also use PowerShell cmdlets and see if it finds any issues, such as Test-SPContentDatase.. Validate the SharePoint content databases, because if not setup properly the Provisioning will fail.
    Also check these properties.
    $web=get-spweb http://prodproj01/pwa
    $Web.AllProperties[“PWAURL”] ### see what the value is.. you may have to blank it out, specially if it is pointing to a different URL
    Here is how to fix.
    $Web.AllProperties[“PWAURL”]=””
    $web.Update()
    Michael Wharton, MVP, MBA, PMP, MCT, MCTS, MCSD, MCSE+I, MCDBA
    Website http://www.WhartonComputer.com
    Blog http://MyProjectExpert.com contains my field notes and SQL queries

  • Project Server 2010 - Applying CUs after SP2?

    I am taking over support of a development environment for Project Server 2010 and would like to update it to a more recent level of CU. We have one DB server, and all other components are on one additional server.
    Current levels from the Control Panel: MS Proj Server 2010 14.0.7015.1000, MS Sharepoint Server 2010 14.0.7015.1000, Service Pack 2 KB2687452 applied.
    Farm Info: Config DB version: 14.0.6134.5001.
     1. Can I apply the April CU and it will include all the previous CUs since SP2? Do I need to install the CUs one at a time?
     2. For each CU, do I install the Sharepoint component first, then Project?
     3. I keep reading information about problems with SP1 but I don't see it in my Control Panel as installed (just SP2.) Can I install Feb or April 2014 CU and avoid whatever issues were happening with July 2013 CU and SP1?
     4. Any advice on next steps is greatly appreciated.

    Hi LD2009,
    here are the answers to your questions:
    Q1: The CU April 2014 has included all fixes since SP2. So you don't need to install older CUs.
    Q2: You don't need seperate packages for SharePoint and Project Server. There is a Rollup-Package which updates both SharePoint
    and Project Server together. You can find it
    here.
    Q3: You must enshure that SP2 was installed and deployed correctly. In the Central Administration check if all databases were upgradet to the latest Level. If not, run psconfig.
    If you have the BCS Service configured then you have to run the following PS script (otherwise the BCS database would remain in the compatibility mode):
    (Get-SPDatabase | ?{$_.type -eq “Microsoft.SharePoint.BusinessData.SharedService.BdcServiceDatabase”}).Provision()
    For all other issues we need more details.
    For more informations read the blog posts from
    Brian Smith and
    Stefan Goßner.
    I hope this helps.
    Regards
    Bernhard Fischer
    Bernhard Fischer [MVP] | www.wodey.de

  • Project Server 2010 Jobs All 'Waiting To Be Processed'

    Hello,
    We have installed Project Server 2010 for evaluation and are running into an issue when creating new projects in the Project Center.  The installation included SharePoint 2010 and is a single-machine install (i.e. DB and WFE on same machine). 
    We can access the site without any problem and when accessing the Project Center and electing to create a new project from Basic Project Plan template, the interface processes the request and then informs us that the request was taking a long time to process
    and to check the Manage Queue Jobs interface for status.
    Reviewing the queued jobs reveals four queued tasks for Project Create, Project Publish Notifications, Project Publish and Start Workflow, all with a Job State of 'Waiting To Be Processed'.  When we originally ran into this issue, we realized that the
    User Profile Synchronization Service was configured to run with the Network Service account and that the two relevant ForeFront Identity Manager services were not running.  We had read that this may cause the queue to not process requests, so we reconfigured
    the system to use a domain account and started the User Profile Synchronization Service Application (which in turn started the ForeFront Identify Manager services).
    However, this did not help and the jobs (as well as new jobs) are still waiting to be processed.  We don't see any errors listed in the queue and can't really find relevant errors in the SharePoint logs or event viewer.
    Has anyone else run into this problem who can provide some insight?  Thanks.
    John

    Another thing to check John, and you may well find evidence in the ULS logs, is that the queue service is really running.  Just looking in Services isn't enough.  When the queue service starts it will check for the presence of PWA sites within
    each and every (probably just one) Project Service Application you have running.  It will then spawn an extra process for each Service Application it finds that has one or more PWA instances.  So you should always see at least two Microsoft.Office.Project.Server.Queuing.exe
    processes running within Task Manager -and if you just see one the looking in the ULS logs should give an indication why it didn't start up (re-starting will give you a fresh entry in the log - which will be easier than searching through lots of logs.
    Best regards,
    Brian.
    Blog |
    Facebook | Twitter | Posting is provided "AS IS" with no warranties, and confers no rights.
    Project Server TechCenter |
    Project Developer Center |
    Project Server Help | Project Product Page

  • Project Server 2010 : Webapp - tasks - "An Unknown Error has occured"

    Software used
    Project server 2010
    SharePoint 2010 RTM
    Sql Server 2008 R2
    Steps taken
    new project server 2010 setup on a virtual machine
    importing/publishing 2 projects from projectcentral 2000 to project server 2010.
    a user has 122 tasks (in project central 2000 he only gets 15 tasks in his view)
    unable to view the detail of the tasks --> unkown error.
    there is a sql time out in the log files, from the following query  (when i run it in SQL management studio it takes > 5 minutes)
    declare @ResUid UniqueIdentifier; set @ResUid = '9ffd71a7-c94a-44f5-b3b1-6d27eb17f541';
    declare @ViewUid UniqueIdentifier; set @ViewUid = 'a20480ef-c755-4da7-a36f-5fe92fed0c68'; 
    declare @P0 UniqueIdentifier; set @P0 = '9ffd71a7-c94a-44f5-b3b1-6d27eb17f541'; 
    SET NOCOUNT ON
    SELECT      MAS.ASSN_UID ,      MAS.PROJ_UID   INTO #T0 
    FROM dbo.MSP_ASSIGNMENTS_SAVED AS MAS    
          INNER JOIN dbo.MSP_PROJECTS AS MP ON MP.PROJ_UID = MAS.PROJ_UID    
          INNER JOIN dbo.MSP_TASKS_SAVED AS T ON T.PROJ_UID = MAS.PROJ_UID AND T.TASK_UID = MAS.TASK_UID    
          INNER JOIN dbo.MSP_PROJECT_RESOURCES AS R ON R.PROJ_UID = MAS.PROJ_UID AND R.RES_UID = MAS.RES_UID    
          INNER JOIN dbo.MSP_RESOURCES AS R2 ON R2.RES_UID = R.RES_DEF_ASSN_OWNER    
          LEFT JOIN dbo.MSP_RESOURCES AS R3 ON R3.RES_UID = MAS.RES_UID_OWNER    
          LEFT JOIN dbo.MSP_RESOURCES AS R4 ON R4.RES_UID = MAS.WRES_UID_MANAGER 
    WHERE MAS.WASSN_LOCKDOWN_BY_MANAGER = 0AND T.TASK_IS_ACTIVE = 1 AND ( (MAS.RES_UID_OWNER = @P0) )  
    CREATE CLUSTERED INDEX PK_#T0 ON #T0 (ASSN_UID, PROJ_UID)  
    SET NOCOUNT OFF  
    SELECT      MAS.ASSN_UID ,      MAS.PROJ_UID ,      MAS.TASK_NAME ,      MAS.ASSN_START_DATE ,      MAS.ASSN_FINISH_DATE ,     
    ASSN_REM_WORK ,      MAS.ASSN_PCT_WORK_COMPLETE ,      ASSN_WORK ,      ASSN_ACT_WORK ,      MAS.TASK_UID ,      PROJ_NAME ,     
    WASSN_IS_NEW_ASSN ,      MAS.WASSN_REMOVED_BY_RES ,      case when exists ( select * from MSP_ASSIGNMENT_TRANSACTIONS t where MAS.ASSN_UID = t.ASSN_UID and t.ASSN_TRANS_STATE_ENUM = 1) then 1 else 0 end AS
    ASSN_RESPONSE_PENDING ,      MAS.WASSN_MGR_UPDATED ,      MAS.WASSN_ACTUALS_PENDING ,      MAS.WASSN_SEND_UPDATE_NEEDED ,      MAS.WASSN_LOCKDOWN_BY_MANAGER
    ,      MAS.WASSN_DELETED_IN_PROJ ,      MAS.WASSN_COMMENTS ,      R.RES_NAME ,      T.TASK_IS_MILESTONE ,      WASSN_UPDATE_TRACKING_MODE
    ,      T.TASK_NOTES ,      T.TASK_IS_MANUAL ,      T.TASK_HIERARCHY ,      T.TASK_DUR_TXT ,      T.TASK_FINISH_TXT ,     
    T.TASK_START_TXT ,      MAS.TASK_IS_SUMMARY ,      WO.WOBJ_UID ,      MP.PROJ_OPT_MINUTES_PER_DAY ,      MP.PROJ_OPT_MINUTES_PER_WEEK ,     
    MP.PROJ_OPT_DAYS_PER_MONTH ,      MP.PROJ_OPT_CURRENCY_CODE ,      MAS.ASSN_STOP_DATE ,      T.TASK_IS_SUBPROJ ,      T.TASK_IS_ACTIVE ,     
    T.TASK_START_DATE ,      T.TASK_FINISH_DATE ,      T.TASK_DUR ,      MAS.RES_UID ,      R.RES_MATERIAL_LABEL ,      R.RES_TYPE ,     
    ASSN_UPDATE_NEEDED  
    FROM dbo.MSP_ASSIGNMENTS_SAVED AS MAS     
        INNER JOIN dbo.MSP_PROJECTS AS MP ON MP.PROJ_UID = MAS.PROJ_UID    
        INNER JOIN dbo.MSP_TASKS_SAVED AS T ON T.PROJ_UID = MAS.PROJ_UID AND T.TASK_UID = MAS.TASK_UID    
        INNER JOIN dbo.MSP_PROJECT_RESOURCES AS R ON R.PROJ_UID = MAS.PROJ_UID AND R.RES_UID = MAS.RES_UID    
        INNER JOIN dbo.MSP_RESOURCES AS R2 ON R2.RES_UID = R.RES_DEF_ASSN_OWNER    
        LEFT JOIN dbo.MSP_RESOURCES AS R3 ON R3.RES_UID = MAS.RES_UID_OWNER    
        LEFT JOIN dbo.MSP_RESOURCES AS R4 ON R4.RES_UID = MAS.WRES_UID_MANAGER   
        INNER JOIN #T0 AS keys ON keys.ASSN_UID = MAS.ASSN_UID AND keys.PROJ_UID = MAS.PROJ_UID    
        LEFT JOIN dbo.MSP_WEB_OBJECTS AS WO ON WO.WOBJ_PROJ_UID = T.PROJ_UID AND WO.WOBJ_TASK_UID = T.TASK_PUBLISHED_UID AND WO.WOBJ_TYPE = 2 
    WHERE MAS.WASSN_LOCKDOWN_BY_MANAGER = 0AND T.TASK_IS_ACTIVE = 1   
    DROP TABLE #T0;
    This query creates a tempory table -- when ran seperately = fast
    The query does a selection joining the temporary table.
    When running the second query without the join on the temp it takes 8 seconds and result in 826 records (all assignements in the db)
    After looking at the join and where clauses used in the first and second query i see they are almost identical and with only adding "AND ( (MAS.RES_UID_OWNER = @P0) ) " and not using a temp table, I get the wanted result (122) only taking half
    a second.
    So
    Suggestions how to fix, circumvent the problem?

    Exact same problem, took me hours to trace it, but i get the exact same behavior, some people can open the tasks view normally, some other people get timeouts.
    Tried multiple browsers, logging different users on different machines, different hours in the day with different loads and capacities, verified that SQL Server and SharePoint Servers and Project Servers are not over utilitized.
    There just seems to be something wrong with this query, i tried running it in SQL Server Management Studio, and it does indeed take alot of time to generate results, about 5 mins or so for some users.
    Please can anyone suggest a solution other than contacting support, this is heavily impacting our business.

  • Project Server 2010 Task page - An unknown error has occurred

    Hi All,
    I have searched inside the forum for similar problems but i didn't find any solution.
    We have Project Server 2010 with December CU installed and
    we are
    experiencing
    a serious
    problem with two enterprise resources.
    They can login to pwa succesfully but when they enter in the Task page the following error is raised:
    An unknown error has occurred
    There are no errors reported in the event viewer while in the ULS Log I found only this entry but i don't know if it's related with this issue:
    Detected use of SPRequest for previously closed SPWeb object. Please close SPWeb objects when you are done with all objects obtained from them, but not before. Stack trace:
    at Microsoft.SharePoint.SPWeb.get_CurrentUser()
    at Microsoft.Office.Project.PWA.PJContext.get_RegionalSettings()
    at Microsoft.Office.Project.PWA.PJContext.get_LocaleCulture()
    at Microsoft.Office.Project.PWA.WCFContext.AuthenticateUser(Message message, WCFContext& wcfContext, String userName, Boolean isWindowsUser)
    at Microsoft.Office.Project.PWA.WCFContext.GetContext(Message message, String userName, Boolean isWindowsUser, Boolean newCookie, Uri originalTargetUri)
    at Microsoft.Office.Project.Server.ProjectServerRouter.Microsoft.Office.Project.Server.IProjectServerRouter.ProcessMessage(Message message)
    at SyncInvokeProcessMessage(Object , Object[] , Object[] )
    at System.ServiceModel.Dispatcher.SyncMethodInvoker.Invoke(Object instance, Object[] inputs, Object[]& outputs)
    at System.ServiceModel.Dispatcher.DispatchOperationRuntime.InvokeBegin(MessageRpc& rpc)
    at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage5(MessageRpc& rpc)
    at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage4(MessageRpc& rpc)
    at System.ServiceModel.Dispatcher.MessageRpc.Process(Boolean isOperationContextSet)
    at System.ServiceModel.Dispatcher.ChannelHandler.DispatchAndReleasePump(RequestContext request, Boolean cleanThread, OperationContext currentOperationContext)
    at System.ServiceModel.Dispatcher.ChannelHandler.HandleRequest(RequestContext request, OperationContext currentOperationContext)
    at System.ServiceModel.Dispatcher.ChannelHandler.AsyncMessagePump(IAsyncResult result)
    at System.ServiceModel.Diagnostics.Utility.AsyncThunk.UnhandledExceptionFrame(IAsyncResult result)
    at System.ServiceModel.AsyncResult.Complete(Boolean completedSynchronously)
    at System.ServiceModel.Channels.InputQueue`1.AsyncQueueReader.Set(Item item)
    at System.ServiceModel.Channels.InputQueue`1.EnqueueAndDispatch(Item item, Boolean canDispatchOnThisThread)
    at System.ServiceModel.Channels.InputQueue`1.EnqueueAndDispatch(T item, ItemDequeuedCallback dequeuedCallback, Boolean canDispatchOnThisThread)
    at System.ServiceModel.Channels.InputQueueChannel`1.EnqueueAndDispatch(TDisposable item, ItemDequeuedCallback dequeuedCallback, Boolean canDispatchOnThisThread)
    at System.ServiceModel.Channels.SingletonChannelAcceptor`3.Enqueue(QueueItemType item, ItemDequeuedCallback dequeuedCallback, Boolean canDispatchOnThisThread)
    at System.ServiceModel.Channels.SingletonChannelAcceptor`3.Enqueue(QueueItemType item, ItemDequeuedCallback dequeuedCallback)
    at System.ServiceModel.Channels.HttpChannelListener.HttpContextReceived(HttpRequestContext context, ItemDequeuedCallback callback)
    at System.ServiceModel.Activation.HostedHttpTransportManager.HttpContextReceived(HostedHttpRequestAsyncResult result)
    at System.ServiceModel.Activation.HostedHttpRequestAsyncResult.BeginRequest()
    at System.ServiceModel.Activation.HostedHttpRequestAsyncResult.OnBeginRequest(Object state)
    at System.ServiceModel.PartialTrustHelpers.PartialTrustInvoke(ContextCallback callback, Object state)
    at System.ServiceModel.Activation.HostedHttpRequestAsyncResult.OnBeginRequestWithFlow(Object state)
    at System.ServiceModel.Channels.IOThreadScheduler.CriticalHelper.WorkItem.Invoke2()
    at System.ServiceModel.Channels.IOThreadScheduler.CriticalHelper.WorkItem.Invoke()
    at System.ServiceModel.Channels.IOThreadScheduler.CriticalHelper.ProcessCallbacks()
    at System.ServiceModel.Channels.IOThreadScheduler.CriticalHelper.CompletionCallback(Object state)
    at System.ServiceModel.Channels.IOThreadScheduler.CriticalHelper.ScheduledOverlapped.IOCallback(UInt32 errorCode, UInt32 numBytes, NativeOverlapped* nativeOverlapped)
    at System.ServiceModel.Diagnostics.Utility.IOCompletionThunk.UnhandledExceptionFrame(UInt32 error, UInt32 bytesRead, NativeOverlapped* nativeOverlapped)
    at System.Threading._IOCompletionCallback.PerformIOCompletionCallback(UInt32 errorCode, UInt32 numBytes, NativeOverlapped* pOVERLAP)
     It's not a task related errors because i have alredy done an analysis of the resorce's assignments.
    I have also verified IIS authentication settings as described in this
    post but all had been alredy correctly configured.
    We have a farm installation with two physical server:
    Application Server with Windows 2008 R2, SharePoint 2010 Enterprise, Project Server 2010
    Database Server with Windows 2008 R2 and SQL Server 2008 SP2
    Any help would be greatly appreciated!
    Thanks in advance.
    Raffaele

    Hi,
    I faced exactly the same problem: some resources try to connect to My Tasks, and get an Unknown error. No error message in ULS or Eventlog.
    I hope I solved the problem, and want to share the experience here.
    First, by reading this article,
    http://www.projectserverexperts.com/ProjectServerFAQKnowledgeBase/Unknown%20Error%20My%20Tasks%20Page.aspx: even if the SQL Query returns me no records, it gives me the idea to delete (unpublish) some tasks (i managed to identify some tasks which raised
    the problem, by assigning a test account on them, and see that the pb happened).
    So I decided to delete my project from the Published Database (and keep it in the Draft of course). Than in Project Pro, I opened and Published: the problem seem to be solved.
    I don't know the root cause of the pb: maybe some SQL data were corrupted for an unknown reason.
    Hope it could help some one ! Don't hesitate to give feedback if you solved this pb with this solution, or workaround.
    Sylvain

  • Project Server 2010: PWA Removing Default Project Site Security Groups When Creating a New Project

    I looked for this specific issue with Project Server 2010/PWA/SharePoint and could not find an exact answer... hopefully someone can help.
    We are currently using Project Server 2010 and have a number of project site templates that are used dependent upon the enterprise project type selected. Each of these project site templates have unique permissions which should create the default security
    groups on the project site upon publishing/syncing:
    <Project Name> Members
    <Project Name> Owners
    <Project Name> Visitors
    <Project Name> Project Managers (Project Web App Synchronized)
    <Project Name> Team Members (Project Web App Synchronized)
    Web Administrators (Project Web App Synchronized)
    Whether a user creates a project through PWA or Project Pro 2010 and imports the project into PWA, we get a weird result in the Site Permissions of the newly created project site. PWA will remove all default security groups from the project site template
    and add a whole list of users in the Site Permissions list without groups. 
    Once the project is published and the project site is created, we can then go back and add those default security groups back in the project Site Permissions and even add a couple of custom groups without them being removed on all subsequent project syncs
    or publishing. 
    How do we get PWA to not overwrite the project site templates' security groups and place each user in the proper default security groups? At the same time, how is PWA adding a number of users into the Project Site Permissions?
    Thanks in advance.

    Paul,
    Thanks for that information. Right now we are using the Test environment to turn the Auto-sync feature back on. I suspect that the reason this is happening is due to PWA groups/categories/security templates. There may be more than one PWA group that is "overwriting"
    the default project site groups upon initial creation of the project. We will look further into the security settings to tighten up the policies. 

  • Project Server 2010 / Sharepoint 2010 Permissions not syncing to Project Site

    Project Permissions not syncing to Project Site
    Project Manager Group
    New project is created and published project server sends permissions to Sharepoint which puts users into the following groups:
    <dir><dir></dir></dir><dir><dir>
    Web Administrator (Microsoft Project Server)
    Project Managers (Microsoft Project Server)
    Team members (Microsoft Project Server)
    Readers (Microsoft Project Server)
    At this time the creator/owner, owner’s management, portfolio managers, and executives should all have Project Manager rights on the sharepoint site, and Admins will have Web Admin permissions.
    Issue #1: Only the Web Admin permissions and creator/owner permissions are being added to the Sharepoint permission groups
    Workaround #1: Going into the project site permissions and adding the
    Project Managers (Microsoft Project Server) group manually and the sync will keep the permissions
    Workaround #2: Going into the Server Settings, Manager Groups then removing or add all users to the No Permission Group, which forces an sync to all workspaces. Con: This workaround can only be down at night when users are not active since it will
    block the queue for at least an hour.
    Project Owner Transfer
    Previously created project has owner change, once saved and published project server sends permissions to update user’s permission to
    Project Managers (Microsoft Project Server) on Sharepoint project site.
    Issue #2: When Project owner is changed and project is published the owner is not getting permissions to the Sharepoint project site. However, if owner is also added to the team using the Build Team Feature the sync will give the owner Project
    Manager permissions on the Project Site.
    Workaround #1: Going into Server Settings, Project Sites, select project and Synchronize. Once this is done, the owner will have Project Manager Permissions without being added to the team.
    Users who have been added to this project in Project Server 2010, but not assigned to tasks. Users who have assignments in this project in Project Server 2010 and are contributors to the project workspace site,
    meaning that they can create and edit documents, issues, and risks. Users who have published this project or who have
    Save Project permission in Project Web App and are contributors to the project workspace site, meaning that they can create and edit documents, issues, and risks. Users who have
    Manage SharePoint Foundation permission in Project Web App and are contributors to the project workspace site, meaning that they can create and edit documents, issues, and risks.</dir></dir>

    By default when you create project build team add users in the task and publish the project plan then All the User which are available in the project plan including Project owner will go to below mentioned group in project site:
    1. creator/owner, owner’s management, portfolio managers, and executives should all have Project Manager will get access to Project Managers (Microsoft Project Server)
    2. User who are having team member access to PWA will get Team members (Microsoft Project Server) access if they are assigned to the project task.
    3. User who are having team member access to PWA will get Readers (Microsoft Project Server) access if they are not assigned to the project task.
    4. Only PWA Administrator will get the access to Web Administrator (Microsoft Project Server)
    Sharepoint permission you have to use when you want to give permission manually to users on project site  
    In the Project Site provisioning setting under Server setting if you have Check to automatically synchronize Project Web App users with Project Sites when they are created, when project managers publish projects, and when user permissions change in Project
    Server.
    Then all the user get access as per describe above and if you will give access manually to any of the user either in project server group or in Sharepoint group once you will publish the project next time all the manually given permission will go away.
    IF you want to give permission to user manually to sharepoint group or project server group then uncheck automatically synchronize Project Web App users with Project Sites when they are created, when project managers publish projects, and when user permissions
    change in Project Server.
    You check PWA site setting --> Site permission then member of Sharepoint group user who will have access to sharepoint group in PWA site setting site permission will have access to all the project site sharepoint group as Project site inherit permission
    from PWA root site.
    Both the issue which you have described is behavior of project site.
    For issue 2 when first time project owner create and publish the project and projectsite is getting created then porject owner name gets access  in the porject manager (project server group) nect time if you will change the owner and publish the project
    until he will not present in the project plan will not get the permission.
    If you want to give sharepoint permission to users then uncheck automatically synchronize Project Web App users with Project Sites when they are created, when project managers publish projects, and when user permissions change in Project Server and give
    the permission manually. 
    Project site in 2010 has some issue and not full filling customer need some time ,Ms has came up with 2013 which is having tight integration with project sites .
    Project workspace security groups are equal to the SharePoint Server 2010 security groups.
    Web Administrator equals Full Control
    Project Managers equals Design
    Team members equals Contribute
    Readers equals Read
    Users who have Manage
    SharePoint Foundation permission in Project Web App and are contributors to the project workspace site, meaning that they can
    create and edit documents, issues, and risks will get access to Web Administrator (Microsoft Project Server)
    http://technet.microsoft.com/en-us/library/cc197668(v=office.14).aspx
    kirtesh

Maybe you are looking for