Project Server 2010 CU Update

Hi,
Currently we have February 2013 Update http://support.microsoft.com/kb/2767794 14.0.6134.5000 available in the farm. Can we directly install April 2014 Release?
Thanks
srabon

Yes, you can. While there is no "CU" for Project Server in April 2014, there are two hotfixes:
http://support.microsoft.com/kb/2878259
http://support.microsoft.com/kb/2878266
Note under the Prerequisites section, they just require SP1 or SP2.
Trevor Seward
Follow or contact me at...
&nbsp&nbsp
This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

Similar Messages

Project Server 2010 - PDP updates not triggering Project Server Events

Hello,
We're experiencing an issue whereby when a user updates a Project PDP, no update is triggered and reflected in the reporting database.
My question is, which Server Side Event Handler is responsible for picking up PDP changes (i.e. Changes to Enterprise Custom Fields)?
Can someone please assist?
Thanks in advance.
What we have configured and is working as expected...
Event: Reporting
Event Name: ProjectChanged, ProjectCreated, ProjectDeleted

There may be multiple reasons for this.
1. SharePoint timer Job is malfunctioning:
For this try restarting SharePoint timer Job. through SP Powershell:
Stop SPTimerv4 , Start SPTimerv4
2: SharePoint Cache is full:
Reset SharePoint Cache by deleting all XML files ( except cache.ini
) in SharePoint Cache located in System Drive\ProgramData\Microsoft\SharePoint\Config\<GUID>
3: Check if Microsoft Project Server Event Service is running in Services.msc, try restarting it.

Updating custom fields in project server 2010/2013 using psi

Hi,
I have two custom fields . Lets call them A and B.
A has some content. Now i want B to have the same content as A . B is a formula custom field wher b=[A] .
now b is empty data and A has data.
how do i get column in B be populated.
i tried manual publish. IT worked but i have several projects.so iam looking for a script to do bulk publish so that data in B can be populated with data in A
a) i checked out project (CheckOutProject)
b) published project (QueuePublish())
c) checked in project (QueueCheckInProject())
however i donot get the value of A reflected in B using. Am i doing something wrong?
Pls help.Any pointers towards a script would behighly appreciated.
i am using project server 2010
Thanks
Su

Hello,
You probably want to use Project Pro to do the publish so the calculation happens and updates field B. For bulk publish using project pro use VBA to automate project pro to open each project then do save and publish etc.
Paul
Paul Mather | Twitter |
http://pwmather.wordpress.com | CPS |
MVP | Downloads

Project Server 2010 Site Template Update

Hi,
I have a Project Server 2010 environment in which there are several site templates created and there are about 500 projects.
Now, I have the requirement of changing some templates (add a list, some fields in a existing Risks and Issues lists, etc.)
How Can I update current template?
If I update current template, Will the sites created be updated with the new lists and fields? Or Should I do these additions by hand?
Thanks!
José Quinto Zamora SharePoint and Search Specialist MCITP and MCPD in SharePoint 2010
http://joSharePoint.com

Hi,
Another related question,
We have created custom Web Template by saving as a template one site. Later we have created 20 sites using that Web Template. And now we want to update this template to "Site Template v2". We create other Web Template and now we have two
"Site Template v1" and "Site Template v2". Should we remove "Site Template v1" from Solutions Gallery? Or it is neccesary while exists sites created with version 1?
José Quinto Zamora SharePoint and Search Specialist MCITP and MCPD in SharePoint 2010
http://joSharePoint.com

Project Server 2010 - Updated User Profile - Display Name is Old Name

Similar to question"It shows the Domain\Logon account instead the User Name (up right corner)" but not quite the same. I also checked on the related topics list and could not find a solution.
We have a Resource in Project Server 2010 whose name changed. This included a change to her loginID as well as her email address. I went in to PWA > Server Settings > Security > Manage Users and changed the
Name, Email Address, and User Login Account fields accordingly. When the user goes into Project Server or any of the Project Sites, her old User Name is reflected. If she accesses any other SharePoint site (not associated with Project Server) her
new name shows up in the upper right hand corner of the screen.
We do not have AD Synchronization turned on.
How can we edit the name that appears in the upper right corner of the screen?

Hi,
Use Display name shown on right hand site is not from PWA, its from SharePoint User profile. When we make change to user display name, sometime SharePoint Still retain the old account and also add new account. To fix the issue we have to remove the user
profile from PWA root site.
Open PWA and navigate to following path
Site Actions>>Site Settings>>People and Groups
Click on More from left hand site list of groups
Select appropriate group, belongs to the user
Select the user and from Actions tab remove the user. (you may see two entries old and new), Either you can delete both or click on each account to validate correct user ID.
Once again navigate to PWA>>Server Settings>>Manage User
Edit affected user and click on Save
Have user log on to PWA and validate the result.
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.This can be beneficial to other community members reading the thread.

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

Project Server 2010 - Change Status Manager

End Goal: We would like to perform this change via SQL statement - which I believe I have I feel like I am missing something and not sure what it is.
Background: We migrated from a different product to Project Server 2010, while our team members were assisting users to move their projects from the old application to Project 2010 they did not realize their names would appear as status
managers.
The quick solution would be to tell the owners of the projects to change the information themselves (republish or go in themselves and change every line); however we feel this can be cumbersome and too much work due to having hundreds of projects and there
are thousands of fields that need to be modified. I can quickly accomplish what I want with an UPDATE command and be done with it (no user involvement).
What I am running into in my test environment is that I can modify the fields (query below) to the appropriate status manager, but I cannot get the changes to appear in Project Professional - it still shows the old value.
I have used the following command to change the Status Manager to the Project Owner (I'm new to SQL, and we no longer have a DBA - so if my code isnt the greatest...I'll fix it)
USE ProjectServer_ReportingUPDATE MSP_EpmTaskSET TaskStatusManagerUID = MSP_EpmProject.ProjectOwnerResourceUIDFROM MSP_EpmProjectWHERE MSP_EpmTask.ProjectUID = MSP_EpmProject.ProjectUID
This modifies all the values correctly - Project Owners become the Status Manager in SQL
Question: Is there something I am missing or can do OR I am not doing to make this new value show up? Is there a better way to do this from an administrative point of view, with no customer/user interaction?
Your help is greatly appreciated
Thank You
kbwrecker

Merely my personal opinion having been a Project Server 2010 admin in a medium-sized corporation:
I think you are going to seriously do some damage if you go about trying to modify SQL tables behind Project Server's back. There are a LOT of operations that go into a simple "publish" and I doubt that the minor changes you want to make will account for
all of them. Are you confident you're adjusting all of the values necessary? You may have a detrimental impact on in-flight approvals, timesheets, projects, tasks, assignments.. There is just far too much IMO.
Believe me, I know it is not an ideal solution to have the business make their own adjustments. However sometimes it is just what has to be done. My vote is to craft brief instructions and send them out to the PMs. It's easy to do, they can change one row
and then drag the field down like in Excel to edit all the rest; it's a 1-minute operation, max.
Due to the nature of the field, (not being something you can edit via PWA, and even in Project Pro it only allows you to change it to yourself or another current Status Mgr) I think you'll have a hard time scripting this one via macro etc.. However if you
do find a way, seriously keep in mind your scope and don't edit them all at once, it will need to kick off publishes and check-ins for all the affected projects.
Good luck!

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 , Project Center, Resource Center, My Work not loading

Hi,
We have Project Server 2010 SP-2 env
Yesterday one of my Project Manager told me that he is not able to access any of the following page Project Center, Resource Center, My Work in our Quality env. Issue is it shows page is loading infinitely long and on botton it shows some script error mentioned
below
Webpage error details
User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.1; WOW64; Trident/4.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; .NET4.0C; .NET4.0E)
Timestamp: Tue, 21 Oct 2014 13:55:19 UTC
Message: 'null' is null or not an object
Line: 217
Char: 4
Code: 0
URI: http://XXXXXXXXXXX/_layouts/inc/pwa/library/webmethodmanager.debug.js?rev=BtnvMSOtt14tg%2FnfhDTJpA%3D%3D
Also I have checked event logs in shows WebHost failed error with Event ID 3 , complete detail mentioned below.
Event Log Error
WebHost failed to process a request.
Sender Information: System.ServiceModel.ServiceHostingEnvironment+HostingManager/45523402
Exception: System.ServiceModel.ServiceActivationException: The service '/_vti_bin/PSI/ProjectServer.svc' cannot be activated due to an exception during compilation. The exception message is: Could not load file or assembly 'FirePoint.SharePoint.RssViewerWebPart,
Version=1.4.7.12, Culture=neutral, PublicKeyToken=e891f27e2edd24d0' or one of its dependencies. The system cannot find the file specified.. ---> System.IO.FileNotFoundException: Could not load file or assembly 'FirePoint.SharePoint.RssViewerWebPart, Version=1.4.7.12,
Culture=neutral, PublicKeyToken=e891f27e2edd24d0' or one of its dependencies. The system cannot find the file specified.
File name: 'FirePoint.SharePoint.RssViewerWebPart, Version=1.4.7.12, Culture=neutral, PublicKeyToken=e891f27e2edd24d0'
   at System.Reflection.Assembly._nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, Assembly locationHint, StackCrawlMark& stackMark, Boolean throwOnFileNotFound, Boolean forIntrospection)
   at System.Reflection.Assembly.InternalLoad(AssemblyName assemblyRef, Evidence assemblySecurity, StackCrawlMark& stackMark, Boolean forIntrospection)
   at System.Reflection.Assembly.InternalLoad(String assemblyString, Evidence assemblySecurity, StackCrawlMark& stackMark, Boolean forIntrospection)
   at System.Reflection.Assembly.Load(String assemblyString)
   at System.ServiceModel.Activation.ServiceHostFactory.CreateServiceHost(String constructorString, Uri[] baseAddresses)
   at System.ServiceModel.ServiceHostingEnvironment.HostingManager.CreateService(String normalizedVirtualPath)
   at System.ServiceModel.ServiceHostingEnvironment.HostingManager.ActivateService(String normalizedVirtualPath)
   at System.ServiceModel.ServiceHostingEnvironment.HostingManager.EnsureServiceAvailable(String normalizedVirtualPath)
WRN: Assembly binding logging is turned OFF.
To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
Note: There is some performance penalty associated with assembly bind failure logging.
To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].
   --- End of inner exception stack trace ---
   at System.ServiceModel.ServiceHostingEnvironment.HostingManager.EnsureServiceAvailable(String normalizedVirtualPath)
   at System.ServiceModel.ServiceHostingEnvironment.EnsureServiceAvailableFast(String relativeVirtualPath)
Process Name: w3wp
Process ID: 5052
Also I have checked Brian Smith blog to resolve WebHost error with Event ID 3, but that didn't help.
So kindly help me to get this issue resolve and do let me know in case need further details.
Thanks

Hi,
From error log it seems you have some custom or thrid party web part activated in your application and that web part is not able to load which might causing those pages to get corrupt.
As a fix can suggest you below to two thing to check
1) Remove that "FirePoint.SharePoint.RssViewerWebPart" from your environment and try to access those PWA pages again.
2) Even after removing above web-part solution does not fix this issue, as it is quality env can you try to disconnect and reconnect the share-point farm . Then try to access those pages again.
Share us the latest update and your finding on this issue.
Regards
Sachin Vashishth MCTS

Project Server 2010 Active Directory Synchronization - duplicate Windows Name - Event ID 7734

Environment: SharePoint Server 2010, Project Server 2010, SP2, DEC 2013 CU (Farm Build number: 14.0.7113.5001)
Scenario:
Domain user has been added to the Active Directory group being synchronized with Project Server for the Team Members group.
That user has participated as a team member in numerous projects, added documents, been assigned tasks, typical project stuff...
Employee quits.
AD account is deleted. (NOT deactivated or moved into another OU)
Time passes...
Employee gets rehired. NEW AD account is set up: same display name, SamAccountName, email address, different GUID of course.
Daily Active Directory job runs again and throws event ID 7734 and the sync ends with a partial fail.
I understand why this is happening. Solutions I've found point me to deleting the Enterprise Object resource in Project Server and then rerunning the sync. Sure, this works BUT won't all of the previous documents, tasks,
etc. be disassociated from that user? If so, this is not ideal.
2 questions:
Is there a better way to deal with the fixing of the resource in Project Server to somehow link the old resource to the new resource allowing the sync to run successfully while still leaving the association to all old content intact?
How are other organizations dealing with rehires when they have been added as resources in Project Server? What is the best practice guidance from Microsoft on this? Are other companies not actually deleting AD accounts when users leave organizations
or are they putting them into a "ARCHIVE" OU or something like that? This happens at least half a dozen times a year at my company. We would like to keep our AD as clean as possible, but this appears to change our approach.
Any suggestion/guidance is appreciated.

For the question to relink the new account to the account which is already available in Project Server. You will have to update the WRES_AD_GUID to Null for the the Resource in MSP_RESOURCES table in the published database.
Whenever a users gets synchronized to the PWA his ADGUID, SAMAccountName, Display Name, Email Address and DepartmentName is Synchronized from AD to Project Server. When the user was deleted and recreated the ADGUID got changed. During the next sync, project
found the user with similar properties but different ADGUID which was updated in WRES_AD_GUID column in MSP_RESOURCES table. Hence it says that there is a duplicate account in the table with the same properties but a different ADGUID
Nullifying the WRES_AD_GUID column value in MSP_RESOURCES table should get the user synchronized to Project server in the next sync.
Cheers! Happy troubleshooting !!! Dinesh S. Rai - MSFT Enterprise Project Management Please click Mark As Answer; if a post solves your problem or Vote As Helpful if a post has been useful to you. This can be beneficial to other community members reading
the thread.

Error Message while Approving Tasks in Project Server 2010

Hi All,
While performing Tasks approvals in MS Project 2010 I am getting below error message:
An Error Occured while processing one or more items. This was caused by one of the following:
A timesheet job is failed and blocking coorelation in the queue.
The approval item no longer exists or has already been approved
The host server is unreachable.
Following are the details of the error message found in Event Viewer:
Standard Information:PSI Entry Point:
Project User: <domain>\<windowsuserid>
Correlation Id: 417dce51-740f-46f0-8f1e-182b4e0c635c
PWA Site URL: http://<servername>/<projectserver>/
SSP Name: spsusfiprojwebappservice
PSError: GeneralQueueCorrelationBlocked (26005)
Operation could not completed since the Queue Correlated Job Group is blocked. Correlated Job Group ID is: 2ae5d5f9-b554-4a44-93f0-f815d36976cd. The job ID of the affected job is: 82dce1fb-be71-4c4a-8d16-4516ea8c887d. The job type of the affected job is:
TimesheetReview. You can recover from the situation by unblocking or cancelling the blocked job. To do that, go to PWA, navigate to 'Server Settings -> Manage Queue Jobs', go to 'Filter Type' section, choose 'By ID', enter the 'Job Group ID' mentioned in
this error and click the 'Refresh Status' button at the bottom of the page. In the resulting set of jobs, click on the 'Error' column link to see more details about why the job has failed and blocked the Correlated Job Group. For more troubleshooting you can
look at the trace log also. Once you have corrected the cause of the error, select the affected job and click on the 'Retry Jobs' or 'Cancel Jobs' button at the bottom of the page.
In Server Settings>Manage Queues>Erro Details following information is listed
General
Timesheet:
TimesheetIncorrectMode (3204). Details: id='3204' name='TimesheetIncorrectMode' uid='e53139e1-66cb-4b4a-a948-cbeda21340b8' mode='1'.
Queue:
GeneralQueueJobFailed (26000) - TimesheetSubmit.SubmitTimesheetMessage. Details: id='26000' name='GeneralQueueJobFailed' uid='4c09d375-cad0-4b61-be16-49abbdc149e4' JobUID='b3737c2a-11f4-4799-9fd7-1d018e4c73d1' ComputerName='JSIDBWPRJA02' GroupType='TimesheetSubmit'
MessageType='SubmitTimesheetMessage' MessageId='1' Stage=''. For more details, check the ULS logs on machine JSIDBWPRJA02 for entries with JobUID b3737c2a-11f4-4799-9fd7-1d018e4c73d1.
Background:
We are gearing up to upgrade our Project Server from 2003 to 2010; as part of this process we have installed MS Project Server 2010 on our dev environment. We created Test Project plans and assigned ourselves (we admins) to these plans and all of us have
admin privileges.

Hi, Can you give a bit more detail on how your generating the task approval. Are you going into myTasks and doing self assignment to your test project plans or are you generating these approvals via outlook or are you updating a timesheet and sending status?
If you're using your timesheet have you created all your timesheet periods within server settings, time and task management...Donald R. Landry

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

Need solution to make changes in existing project sites in Project Server 2010 environment

Dear Folks,
Hope you all are doing good and ready to give a way for this requirement. :)
In project server 2010 environment, I am using InfoPath documents library, Issues, Risks etc in each and every project sites.
Say, after creation of 100 projects/project sites, I have got a requirement to make some changes in the InfoPath document library and in Issues, Risks list, so I have decided to use the following solution which is actually weird:
Make the changes in InfoPath document library, Issues/Risks list for 1 of the project site and save that site as template and associate it with running EPT.
Then, delete the existing project sites (after taking backup) and start recreating it from PWA/Server Settings/ Operational Policies/ Project Sites, so that it will take the latest template. But, seems like it is time taking and handy and actually it's not
working for some of the projects.
Request all of you to provide some solution for this.
Ask more, if my explanation is not clear.
Regards,
Shravan

Hello,
Regarding mass deleting and recreating Project Sites via the PSI, firstly delete the project sites then run the following PowerShell script to bulk create project sites:
https://gallery.technet.microsoft.com/Bulk-create-Server-Sites-784f7b29
I have got a script that bulk deletes projects but this is not published as this could be a dangerous script to run if you did know what to update etc. To give you an idea of how to delete project sites via the PSI see a code snippet below:
$EPMTYGUID = [system.guid]::empty
$projectOwnerID = 'd6a0a720-12ac-e211-93f9-00155d153dd4'
$ProjectList = $svcPSProxy.ReadProjectStatus("$EPMTYGUID","PublishedStore","", "0").Project | format-table proj_uid -hidetableheaders | out-string -stream
foreach ($projectUid in $projectList)
if ($projectUid -ne "")
$projectsforDeletions = $svcPSProxy.ReadProject($projectUid, "PublishedStore").Project | where {$_.projectOwnerID -eq $projectOwnerID} | format-table proj_uid -hidetableheaders | out-string -stream
foreach ($projUid in $projectsforDeletions)
if ($projUid -ne "")
$svcWSSProxy.DeleteWSSSite($projUid)
Write-host 'Project UID for deleted site' $projUID
That particular example deletes the project sites for a particular project owner, you could easily modify that to remove the project owner filter if needed.
Regarding your query about having to delete the project sites to get the changes to take affect, there is no easy option to get the issues and risks list changes to filter though, this would either be manual on each existing site or using code to iterate
through each existing site and apply the changes programmatically. Depending on if you used site collection content types to set up the Issues and Risks lists, it might be simple to add a new column etc. as you could do this centrally and it will cascade
down. If you didn't use content types and or its view changes etc. this is a per site change that can be manual or programmatically done. The same applies to the document library, if this was set up using a site collection content type, the changes can
be modified on the content type and cascaded down. If the library was set up with just a library that used local columns / templates then it will be a per site change - the same as the issues and risks.
The company I work for (CPS) does have a site sync tool that will programmatically update existing sites based on a specified site so I know it is all possible to do in code!
Paul
Paul Mather | Twitter |
http://pwmather.wordpress.com | CPS |
MVP

PerformancePoint Services of Project Server 2010

Hi guys. Now I am using Business Intelligence Feature in Project Server 2010. I did build a report show all Project by Dashboard Designer. In report i use Analysis Services type of Data Connection. I did build a Analysis Services Project by SQL Server
Business Intelligence Development Studio in Server. Everything ok, I see all project. But when I add more Project and refresh page, data not updated. Please help me to find out

With the cube you will need to rebuild it in order to refresh the data, if you are using cube you will need to schedule the cube build time, in order for cubes to be updated it can be scheduled and frequency of update can be set, however depending upon the
frequency impact on servers should be considered accordingly as cube build take quite a bit of resource while building
On a side note, curios to understand why are you not using the reporting DB which has nearly real time data and doesn't requires a refresh or update, though it may not have all the prebuilt measures & dimensions along with data, as in cube, but i am
sure you can manipulate them to show whatever you want
Thanks | Sunil Kr Singh | http://epmxperts.wordpress.com

Project Server 2010 CU Update

Similar Messages

Maybe you are looking for