Project Server 2010 - Auto publish projects in Project Center

Hi,
We checked that we can make rules and auto publish the task updates. However we want to auto publish the projects in project center (Project Server 2010). Is there any way to do this?
Your help is appreciated.
Thanks,
Anuja

Hello,
Not quite from the project center but you could have a windows scheduled task that bulk published the projects over night or each week etc. See the PowerShell script below:
https://gallery.technet.microsoft.com/Server-2010-Publish-all-45ba385b
if you want to publish specific projects you could look at this script:
https://gallery.technet.microsoft.com/Server-2010-Publish-537857d8
Paul
Paul Mather | Twitter |
http://pwmather.wordpress.com | CPS |
MVP | Downloads

Similar Messages

Need to send a email alert to Projectmanger when publishing a project in project server 2010 PWA site

Hi All
When creating and publishing a project in PWA(server 2010) need to send a mail alert to the concerned project manager.
How can i achieve this..
I have configured the outgoing mail sending in sharepoint and its working fine now.
Please help me..
Thanks Advance
SharePoint Module Lead Assyst International Private Ltd Cochin India

Nothing is built in Project Server to do this for you automatically.
They way I have done this in the past is to create a SQL job using SSIS. It runs every hour and when it sees a project schedule that has a recent PUBLISHED date then this is a trigger to send an email to project manager.
Cheers!
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 Professional 2010 Not Publishing to Project Server 2010

I am having trouble publishing a project from Project Professional 2010 to the Project Server 2010 (PWA). What I am trying to publish is a master project which is contains many enterprise projects as subprojects. When I press publish, it prompts me
to save and if I click yes then it goes through and saves all the subporjects and then just stops there and doesn't publish the changes to the master project. If I press publish and click no to the save prompt then it gives me the status "sychronizing
data to server" for around 15 seconds and then just does nothing after the sychonization finishes.
It usually should be giving a "publishing job done 0%" or "publishing job completed" when it publishes, but it gives nothing like that. I also check the project through the PWA and it has not updated yet, but when I open it for editing in the client it has
everything updated and up to date, meaning that the save is working properly and just not the publishing.
All my subprojects are able to publish correctly, it's just this master project that is not working.
Does anyone know why this is happening? Is the publishing process timing out for some reason? Or is it something else?
Please help.
EDIT: The progress notification at the bottom of Project Professional just stops at "save completed sucessfully" whenever I try to publish

To check the queue, navigate to Server Settings > Manage Queue and view the jobs that are present. If there is an error when publishing you should see it in the queue.
Alex Burton
www.epmsource.com |
Twitter
Project Server TechCenter |
Project Developer Center |
Project Server Help | Project Product Page

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 permissions granted through RBS are not flowing through to Project Sites.

Hi,
I have configured RBS as "The Project Owner is a descendant of the user via RBS" its working fine for Projects.
But users are facing access denied issue when working with project sites RBS is not working for project sites.
Can any one Help me How can i grant permissions Automatically for project sites also as same like projects is it possible ?
The Members in Executives group can see all projects in organization but same like can they see all project sites ?
I have found one blog of
RaymondRis he is recommending to do it manually as its not possible to grant Project site permissions Automatically.
http://blogs.technet.com/b/raymond_ris/archive/2013/05/09/project-server-2010-permissions-granted-through-rbs-are-not-flowing-through-to-project-sites.aspx
Thank You, Kumar KSV

Kumar,
The permissions to project sites is not cotrolled by the RBS, as you have discovered. It is controlled by the Security Category permisisons, and the settings if the permssions are auto synced. The permissions work like this:
Project managers who have published a project or who have Save Project permissions on a project are added to the Project Managers (Microsoft Project Server) site group.
Team members with assignments in a project are added to the Team members (Microsoft Project Server) site group.
Other Project Server users who have View Project Site permission on a project are added to the Readers (Microsoft Project Server) site group.
As long as you use the Auto Sync of permisisons for project sites, i do not think there is any work around.
Cheers,
Prasanna Adavi, Project MVP
Blog:
Podcast:
Twitter:
LinkedIn:

Project Server 2010 - Modification date and name of the person who made the last change in the project

Hello everybody
I'm with a doubt.
I got in the business
environment Project Server 2010 and
would like to get the publication date,modification
date and name
of the person who made
the last change in
the project. It is possible
to doby the native
resources or is
there any query in
SQL Server to perform a
query of this information.
Thank you.
Obrigado por contactar o fórum Microsoft Technet!

Hi Hezequias,
You can get the ProjectModifiedDate column in MSP_EPMProject_userView in the Reporting DB where you can
get the data based on the projectUID.
The "last saved" date in the draft DB (be aware that querying in the draft DB is not supported by MS).
For the "last modified by", I think it is not stored in any place.
But you can develop custom code upon publishing the project (Event BeforePublish), writing the current
date and username automatically into a custom enterprise field.
Hope this helps,
Guillaume Rouyre, MBA, MCP, MCTS |

Project Server 2010 - Error 20010 with a master project and 3 sub-projects during publication

Hi,
Here is the situation :
One master project with three sub projects.
Sub projects are really similar (Same ressources and nearly same tasks but only the first contain real work for now).
Sub projects got no sub projects nor links between projects.
The owner of the master project got read rights through projects permissions on sub projects.
Sub projects are link in "read only".
We applied Project Server 2010 SP2 last week end and the issue appeared monday.
Here are the symptoms :
When we link only one sub project (Doesn't matter which one), the owner can publish, no problems.
With 2 sub projects, the error may occur.
With 3 sub projects, the error always occurs.
With admin rights, the error doesn't occur.
Here is the error :
ID : 20010 (0x4E2A)
Description : You don't have required permissions to perform the action (Average traduction)
Detail : <detail><errinfo><general><class name="Project"><error id="20010" name="GeneralSecurityAccessDenied" uid="19515c1d-2624-466f-953a-b7fc67337b81"/></class></general></errinfo></detail>
I'm unable to determine which sub project is the culprit, if there is one, as it's working when I link only one of them.
Thanks for your time !

Fylim --
If the project manager in question does not need to edit any of the three projects, the PM does not need to have Read/Write access to any of the three projects. Because you said that the PM needs to set links in all three projects, this means that
the PM will be editing all three projects. In order to edit the three projects, the PM must have Read/Write access to all three. Setting cross-project links constitutes editing of the projects, which is why the PM must have Read/Write permission.
Make sense?
Regarding SP2, I am not aware that this would change anything, but I could be wrong. The reality is that regardless of which SP you have applied to Microsoft Project and Project Server 2010, the PM in this situation MUST have Read/Write access to the
projects that he/she needs to edit with cross-project links. Hope this helps.
Dale A. Howard [MVP]

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 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 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.

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

Project Server 2010 - Auto publish projects in Project Center

Similar Messages

Maybe you are looking for