PWA permissions

We’re in the process of setting up our first PWA site and subsites.
We’ve created several new Enterprise Projects and assigned owners.
The owners can navigate to the subsite but they cannot edit their projects, and the option to open the project in Microsoft Project is greyed out.
I’ve tried every permission group available and the only one that works is the default ‘Administrators for Project Web App’.
If they are assigned to that group everything is fine.
None of the other built in groups work, or even the custom groups I’ve created.
The subsites inherit permissions from the main PWA site.
Each project Manager has a Project Online and a Project Pro for Office 365 license.
If we create sites using the ‘SharePoint Tasks List’ option, then permissions seem to be fine.
But these sites don’t offer all the functionality we need.
Does everyone really need to be a member of the ‘Administrators for Project Web App’ to edit an Enterprise Project?
That seems like way too much access.
Thanks,
Joe

Hi again Joe,
You actually answered my question while I was writting... Is there any particular reason (except because it is the default permission mode) why you choose the SharePoint permission mode. This mode is much more tedious since it is all manual and not sync
with your project plan. Unless you manage a small organization with a low number of users and projects, I'd strongly advice to switch to the Project permission mode. Be aware that you'll oose any access to sites given with the previous mode.
For the issue about the "track your work" webpart, did you try to edit the page, remove and insert again the webpart?
Hope this helps,
Guillaume Rouyre, MBA, MVP, MCP |

Similar Messages

Project Server 2013 - Remove user from resource pool via sync

Hello everyone,
has anyone managed to configure their Project Server 2013 box with a resource pool sync that will actually remove user from the resource pool (disable "User can be assigned as resource" or deactivate users) when the user is removed from the AD
group(s)?
Setup: Single box, SQL 2012 SP1, SharePoint/Project Server 2013 + PU March + CU April. 2 PWA instances, 1 in SharePoint and 1 in Project permission mode. Tried on 2 different machines (different setup, accounts, domains).
Proceedings:
Create AD user U, AD group G. Add U to G.
Go to PWA, setup resource pool sync with G, sync.
U is now in the resource pool, has no PWA permissions.
Remove U from G. Resync resoure pool.
U is still in resource pool, still a resource, still active, can still be assigned as resource.
Adding U back to G an repeating the whole spiel with a resource pool and a PWA group sync of G will result in U being added and removed from the user list (as expected), and U being added but not removed from the resource pool.
Having read
http://technet.microsoft.com/en-us/library/gg982985.aspx and
http://technet.microsoft.com/en-us/library/gg750243.aspx, there does not seem to be an omission on my part.
The first article states:
Note:
The corresponding Project Server User Account is not deactivated based on this synchronization. If the same Active Directory user is configured to synchronize with a Project Server security group, the Project Server user account will be inactivated when
that synchronization occurs. For more information, see
Best practices to configure Active Directory groups for Enterprise Resource Pool synchronization in Project Server 2013.
Unfortunately, this deactivation either does not seem to occur even with a PWA group sync or I misunderstood the article.
So, did anyone manage to setup their resource pool sync in a way, that new resource will be added, but also be removed from the resource pool?
Kind regards,
Adrian

Hi Adrian,
you tried to sync the same AD group that you used for the resource pool sync also with a Project Server permission group?
And on removal of the user of the AD group the project user/resource is not deactivated? Only removed from the group
Regards
Christoph
Hi Christoph,
even though I might have tried that before, I tried it again in several constellations. It didn't change anything. The the user will be properly added to and removed from the PWA group whenever I remove them from the AD group, the use will also stay active
(but cannot logon without permissions). However, the user will always remain in the resource pool, i.e. the "User can be assigned as resource." checkbox will remain unless it is cleared manually.
Having re-read the technet articles, none of the scenarios actually seem to descibe or address the process that I require, or maybe I'm just misunderstanding. Let me just try to outline the core issue:
Add user to AD group. Sync AD group with resource pool. User is now a PWA resource and PWA user.
Remove user from AD group, but do not deactivate/delete user from AD.
(Magic happens!)
User cannot be assigned as ressource in PWA.
So, is there anything to make this step 3 happen, or is it just not possible to sync users out of the resource pool anymore unless they are deleted/deactivated in AD?
Kind regards,
Adrian

Interpreting the Check Effective Rights Category Permission - Project Grid

I am seeking clarification - I was advised that a user could not access projects so I checked their Effective Rights and noticed a RED cross against the Project Heading at the top of the list of rights for the Category Permission - Project when I selected
any project in the drop down list.
I assumed that a RED Cross at the very top indicated an Overall Block on those permissions, however using Delegation as the afflicted user I found that I could do things that they had reported they were unable to do.
There was one permission that had been removed - PWA Permissions "Delete Project" which I reinstated and this resulted in there being a Grey Cross at the Project heading for the list. Reinstating this did not appear to enhance the users permissions
and reinstating it did not appear to diminish them. The only evident difference being the RED cross against the Project Heading at the top of the list of rights for the Category Permission - Project when any project was selected.
Looking at permissions when a person belongs to more than one security group and there is an allowed permission for one group and a not allowed permission for the other group the permission level itself tends to show a grey cross in such circumstances so
in effect green ticks are negated by red crosses at the group level when viewing the permission level that they are listed beneath.
Am I right to assume that this RED cross simply indicates that at some point there is a permission that is denied?
Dominic Moss | MAPM Microsoft Certified Technology Specialist | Our Newsletter:
PM News Project Server Specialists
Project Server PRIME | Twitter:
@Twitter | Facebook:
@Facebook | Linkedin:
Wellingtone

I have investigated a bit further and from what I can deduce if there is a Red Cross at the Project level in the Category
Permission - Project list it would appear that it is simply indicating that there is a Deny or Unavailable permission at some point in the list. Can anyone confirm this?
Dominic Moss | MAPM Microsoft Certified Technology Specialist | Our Newsletter:
PM News Project Server Specialists
Project Server PRIME | Twitter:
@Twitter | Facebook:
@Facebook | Linkedin:
Wellingtone

Error Message when opening Project Plan on Project Professional from PWA 2013 using either Google Chrome or Firefox

Dears,,
One of our clients uses Google Chrome
as their standard navigator to open PWA 2013 that we have deployed for them.
Every thing went fine until we tried to open a project plan using Project Professional 2013 from PWA using the Edit in Project Professional option, we had the below error:
"Project Web App was unable to find the specified Project.
the project was not found on Project Web App. some possible reasons include:
The Project has not yet been saved successfully to the server.
The Project has been deleted on the server.
you don’t have adequate permissions to open this project.
if the project is available in the local cache, you can click the globe in the status bar and select "Work offline", and then open the project, if the problem continues, contact
your administrator."
Please note that IE is working fine with this scenario,
the belwo screenshot shows the error that appears to the users.
Ibrahim Al-Masri Technology Manager at MethodCorp

Hi All,
As Gary and Guillaume suggested, have you tried to install IE tab extension for chrome?
See the link below:
http://www.ietab.net/
and also im with what Dale has posted
(why don't you just tell the PM to use Internet Explorer instead of Google Chrome?
I suspect that this problem reveals that PWA does not work perfectly in browsers other than the Internet
Explorer,
so I would simply mandate that all PMs and TMs need to use Internet Explorer for Project Server.
Just a thought. Hope this helps.)
from my side , i have tested it and it works perfect.
Karim El Zarka, MCTS Sharepoint 2010 , MCITP SharePoint Administrator 2010 Whenever you see a reply and if you think is helpful, click "Vote As Helpful"! And whenever you see a reply being an answer to the question of the thread, click "Mark
As Answer

Unable to open/edit project in project professional form PWA(project server 2010)

i have been working perfectly and opening my projects with project professional from PWA
All of a sudden,i get this error: no permission to read enterprise global file when trying to edit my projects in project professional from the PWA
i have also tried opening the project from project professional directly and it says (you do not have sufficient permissions to perform the requested action)
please what is the cause of this issue and what can i do to resolve it?

Hello kehinde,
The cause of this problem is somebody changed something.
To resolve, I would clear out the cache to see if that resolves anything.
Then, I would reboot system and see if that resolves.
If still no go, then I would look into security settings, and start doing some detective work. I keep a version of project server in a separate instance, that is completely out of the box, so I can have a reference point for settings.
If still not solution, then I would resave the global file settings.
Cheers!
Michael
Michael Wharton, MBA, PMP, MCT, MCSD, MCSE+I, MCDBA
www.WhartonComputer.com

Project Server 2010 PWA - attempting to move folders from root to document library subfolder does not work

Hello all,
We have an issue whereby attempting to move documents from the top level folder to a subfolder in a PWA site appears to work initially, but within a few minutes the documents are moved back to the top level folder with no error message.
Uploading a document has the same effect.
Permissions are granted at all levels in the document folder.
Only some users seem to be affected.
Only some project sites are affected.
As an admin user I can successfully upload and move documents without issue.
Any thoughts on what might cause this ? I've actually never seen this before (and I have worked on a lot of SharePoint/Project Server deployments) so interested to know if anyone out there has a bright idea on how this might get fixed ?
Many Thanks

Hi,
I understand you encountered the issue when save document from Office client application to SharePoint 2010 site.
Is there any Proxy settings in networking side? Please bring up IE > Internet options > Connections > Lan settings. If so, please uncheck options in Proxy server and test the issue again.
If you have deploy GPO to add SharePoint site into Trusted sites, please check if there is any other GP associated with trusted sites that might affect the issue. You could also remove it from Trusted sites via IE options and test the issue again.
In addition, please provide more error message to help narrow down the issue, you could locate error information in Event log at least.
Regards,
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
[email protected] .
Rebecca Tu
TechNet Community Support

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

Is it possible to link data across different/multiple PWA sites leveraging Master Project with the Subprojects feature?

A couple different questions /similar scenarios
1) Is it possible with Project Server 2010 to have several sites (http://server/pwa1 and
http://server/pwa2 for example) communicate and build a Master Project at a third (or X) site (http://server/pwa3)
2) Is it possible with Project Server 2010 to have several sites (http://server/pwa1 and
http://server/pwa2 for example) communicate and build a Master Project at one of the original sites (http://server/pwa1 (for example))
OR is there a better way to do this/more preferred way to do this.
We found this (http://social.technet.microsoft.com/Forums/projectserver/en-US/2379c3f2-6c80-46d7-8eac-3bc2ccb2d908/master-projectsubproject-with-sites-in-pwa-2010?forum=projectserver2010general)
but its not what we're looking for
3a) Issue/Example -
We want to set up a site (http://server/pwa100) for just the president of the company - all the schedules of the subsites (/pwa99 + /pwa98) create a feed into an integrated master schedule/master project with subprojects(located
in /pwa100).
3b-1) We also want to set up sub sites (http://server/pwa99 and
http://server/pwa98) for each division VPs (and specific other people). These two sites would only allow specific user's project files to be viewed by each other...
Can their project files have linkages between the two project sites (/pwa99 and /pwa98)? Meaning if user1 logs in to /pwa99 can he see a project file (given that they have permission) from /pwa98 in the same instance?
3b-2) Can they see the project file in ProjPro and/or PWA ???
3c) is it possible to have:
+ /pwa100 (pres)
++/pwa99 & /pwa98 (two vps)
+++/pwa97 & /pwa96 & /pwa95 & /pwa-etc (minions)
each rolling up to the next level (level 3 rolls up to level 2 which can roll up to level 1)

kbwrecker,
I agree with Dale. Having multiple sites will make this difficult to set up.
Not knowing how your Custom Groups/Categories have been set up, have you looked into using the "Project Permissions" feature to share projects. These permissions are 'additive' to the category permissions, so you could start out with people looking at the
projects they are authorized to via categories, and then let them share/add people as needed basis. This will also satisfy the requirement of not-loading the projects with resources..
And finally, the department and categories need not align, except that when projects from one dept are shared t another dept resource, the visibility of custom fieds will be affected.
Hope I did not go off on a tangent there :)
Prasanna Adavi,PMP,MCTS,MCITP,MCT TWitter: @prasannaadavi Blog: http://www.prasannaadavi.com
Meant to get back to this earlier - your answer is close (because its what we currently do..sort-of)
From my understanding of this issue the users are separated by department and can only see specific projects; however, when they try to share departments between users (so they can see their projects (dept a sees dept b projects)) this works - but there
is a bigger issue/main issue.
main issue: when dept B adds a new project dept. A cannot see the new project in dept B.
This can be eliviated by removing the user/s and re-adding them to the permission structure of the deptment but overall doing this several times based on user/s and projects being added it gets to be cumbersome and just plain annoying.
Any help/additional thoughts would be great

TF244069: An error occurred while checking the provisioning status of the reporting database schema for a PWA instance.

The command TfsAdmin ProjectServer /RegisterPWA causes next error:
TF244069: An error occurred while checking the provisioning status of the reporting database schema for a PWA instance.
Project Server returned the following error: "Server was unable to process request. ---> The request failed with HTTP status 401: Unauthorized.".
(type ProvisionException)
Exception Stack Trace:    at Microsoft.TeamFoundation.Sync.Provisioning.ProvisionPwaDBSchema.HandleSoapException(SoapException soapException, String errorResourceString)
   at Microsoft.TeamFoundation.Sync.Provisioning.ProvisionPwaDBSchema.IsDBSchemaProvisioned()
   at Microsoft.TeamFoundation.Sync.Provisioning.ProvisionManager.Provision()
I installed SharePoint 2013 and Project Server 2013 as farm and TFS 2012 and my account has permissions everywhere. I read article
http://msdn.microsoft.com/en-us/library/gg412653.aspx and gave full permissions for TFS account to SQL and Project, Project app pool account to SQL, but still have an error.
How can I find out what exactly permissions are not enough???

The problem was in claims authentication. Changed to Windows and all worked out.

Issue in Custom Filter in PWA of Ms Project Server 2010

Hi,
i am facing an issue on setting a cutom filter in the Project Center view of PWA. I am setting a custom filter and it works fine.
Projects are filtered as per the filter. However, on selecting the filter for editing, I get a message viz. "Failure. There was an error processing the request".
I am looking for pointers and guidance to resolve this issue. Any helpin this regard will be appreciated.

Hi,
Evenif you already checked this out, it is likely to be a security issue. This functionality is managed by permissions in PWA server settings and not in the Central Admin.
Check this article :
http://msprojectnow.com/Blog/tabid/142/entryid/556/Enabling-Task-Sheet-functionality-to-Add-Yourself-to-a-Task-in-Project-Server-2010-PWA.aspx
Check if you're not belonging to multiple categories that might have the given permission disabled.
Hope this helps,
Guillaume Rouyre, MBA, MCP, MCTS |

Permissions for connected SharePoint sites

hello forum members,
can someone please explain to me how do permissions work for connected SharePoint sites if Project Server set up to use Project permissons instead of SharePoint ?
Another question I have is that our environment was once set to use SharePoint permissions , then changed to use Project server permission mode. I checked on one user who could not login to Project Server and when i clicked on "Checked Permissions"
on a ribbon - it showed that this person had full rights, but when i went to check on Project security group - he was missing there. It was very confusing.
Does "Check Permissions" actually works when environment set up to use Project server mode permissions?
tatiana

On top of the very good Paul's explanation, here is what happens behind the scene:
case 1: you assign a resource to a project task, you save and publish project:
A hard coded job will parse assignment table and will put :
Project manager (MS office project synched) role to the project owner
Team member (MS office project synched) role to resources with assignments
In addition, 2 additional jobs will give suitable permissions to the resources part of security groups of PWA:
1 gives access to PWA site (to access my tasks, time sheets...)
the other one gives proper access to the resources who have dynamic rights(ie: if they are part of a PWA group that has a category, for instance, giving read to anyone who has Same RBS as project owner
Case2: you add a resource in PWA as part of a security group
1 job for PWA top site + 1 job for each project of server will give suitable rights to the new resource.
Case3: you change the permissions of an existing security group (more exactly to the category set to the group )
1 job for PWA site + 1 job by project will populate on each project site the new permissions. Mind to do that out of peak hours or you'll have a big slow down.
Case4: you add manually permissions directly in the project site. In this case one should never add people in an synched group or rights will Be overwritten during the next project publish.
note there are known bugs for large data set when many synch jobs stay in the queue: we can have jobs conflict and a general permissions loss. On top of that, a sync job including people whose active directory accounts are bad (having left the company
for instance) can block permissions syncs.... We demonstrated this fact to Microsoft and we are working on that with them...
hope this helps
Jeff

Failed to provision site PWA with error: Microsoft.Office.Project.Server.Administration.ProvisionException: To create databases we need dbcreator and securityadmin server roles on servers.

I'm getting the following errors while trying to provision a PS 2010 PWA on our SharePoint 2010 farm. Our PS instance has been working for a while now, and houses two other PWAs. But today,
when trying to create this one, I get "Failed - see the Application event Log" and the following in the Event Viewer:
Log Name: Application
Source: Microsoft-SharePoint Products-Project Server
Date: 4/2/2014 2:09:08 PM
Event ID: 6980
Task Category: Provisioning
Level: Error
Keywords:
User: DOMAIN\DB_Access
Computer: server
Description:
Provisioning 'PWA/SDN': To create databases we need dbcreator and securityadmin server roles on servers 'DB1' and 'DB1'.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-SharePoint Products-Project Server" Guid="{b2178104-1b5b-4c20-8c8f-960678ced9e5}" />
<EventID>6980</EventID>
<Version>14</Version>
<Level>2</Level>
<Task>20</Task>
<Opcode>0</Opcode>
<Keywords>0x4000000000000000</Keywords>
<TimeCreated SystemTime="2014-04-02T19:09:08.225Z" />
<EventRecordID>1676727</EventRecordID>
<Correlation ActivityID="{90131653-B0A4-4FAF-A43C-7DF07CBC3332}" />
<Execution ProcessID="11040" ThreadID="12384" />
<Channel>Application</Channel>
<Computer>sharepoint</Computer>
<Security UserID="S-1-5-21-2280669542-4145173436-3058324265-4222" />
</System>
<EventData>
<Data Name="string0">PWA/SDN</Data>
<Data Name="string1">DB1</Data>
<Data Name="string2">DB1</Data>
</EventData>
</Event>
Log Name: Application
Source: Microsoft-SharePoint Products-Project Server
Date: 4/2/2014 2:09:08 PM
Event ID: 6993
Task Category: Provisioning
Level: Error
Keywords:
User: DOMAIN\DB_Access
Computer: sharepoint
Description:
Provisioning 'PWA/SDN': Failed to provision databases. An exception occurred: To create databases we need dbcreator and securityadmin server roles on servers..
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-SharePoint Products-Project Server" Guid="{b2178104-1b5b-4c20-8c8f-960678ced9e5}" />
<EventID>6993</EventID>
<Version>14</Version>
<Level>2</Level>
<Task>20</Task>
<Opcode>0</Opcode>
<Keywords>0x4000000000000000</Keywords>
<TimeCreated SystemTime="2014-04-02T19:09:08.225Z" />
<EventRecordID>1676728</EventRecordID>
<Correlation ActivityID="{90131653-B0A4-4FAF-A43C-7DF07CBC3332}" />
<Execution ProcessID="11040" ThreadID="12384" />
<Channel>Application</Channel>
<Computer>sharepoint</Computer>
<Security UserID="S-1-5-21-2280669542-4145173436-3058324265-4222" />
</System>
<EventData>
<Data Name="string0">PWA/SDN</Data>
<Data Name="string1">To create databases we need dbcreator and securityadmin server roles on servers.</Data>
</EventData>
</Event>
Log Name: Application
Source: Microsoft-SharePoint Products-Project Server
Date: 4/2/2014 2:09:08 PM
Event ID: 6958
Task Category: Provisioning
Level: Error
Keywords:
User: DOMAIN\DB_Access
Computer: sharepoint
Description:
Provisioning 'PWA/SDN': Database provisioning failed.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-SharePoint Products-Project Server" Guid="{b2178104-1b5b-4c20-8c8f-960678ced9e5}" />
<EventID>6958</EventID>
<Version>14</Version>
<Level>2</Level>
<Task>20</Task>
<Opcode>0</Opcode>
<Keywords>0x4000000000000000</Keywords>
<TimeCreated SystemTime="2014-04-02T19:09:08.225Z" />
<EventRecordID>1676729</EventRecordID>
<Correlation ActivityID="{90131653-B0A4-4FAF-A43C-7DF07CBC3332}" />
<Execution ProcessID="11040" ThreadID="12384" />
<Channel>Application</Channel>
<Computer>sharepoint</Computer>
<Security UserID="S-1-5-21-2280669542-4145173436-3058324265-4222" />
</System>
<EventData>
<Data Name="string0">PWA/SDN</Data>
</EventData>
</Event>
Log Name: Application
Source: Microsoft-SharePoint Products-Project Server
Date: 4/2/2014 2:09:08 PM
Event ID: 6971
Task Category: Provisioning
Level: Error
Keywords:
User: DOMAIN\DB_Access
Computer: sharepoint
Description:
Failed to provision site PWA/SDN with error: Microsoft.Office.Project.Server.Administration.ProvisionException: Failed to provision databases. ---> Microsoft.Office.Project.Server.Administration.ProvisionException: To create databases we need dbcreator and
securityadmin server roles on servers.
at Microsoft.Office.Project.Server.Administration.PsiServiceApplication.EnsureDatabases(ProjectProvisionSettings provset, SPSite pwaSite, String adminName, String adminEmail, ProjectDatabaseStateType& originalDatabaseState, Guid& adminGuid)
--- End of inner exception stack trace ---
at Microsoft.Office.Project.Server.Administration.PsiServiceApplication.EnsureDatabases(ProjectProvisionSettings provset, SPSite pwaSite, String adminName, String adminEmail, ProjectDatabaseStateType& originalDatabaseState, Guid& adminGuid)
at Microsoft.Office.Project.Server.Administration.PsiServiceApplication.CreateSite(ProjectProvisionSettings provset)
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-SharePoint Products-Project Server" Guid="{b2178104-1b5b-4c20-8c8f-960678ced9e5}" />
<EventID>6971</EventID>
<Version>14</Version>
<Level>2</Level>
<Task>20</Task>
<Opcode>0</Opcode>
<Keywords>0x4000000000000000</Keywords>
<TimeCreated SystemTime="2014-04-02T19:09:08.226Z" />
<EventRecordID>1676730</EventRecordID>
<Correlation ActivityID="{90131653-B0A4-4FAF-A43C-7DF07CBC3332}" />
<Execution ProcessID="11040" ThreadID="12384" />
<Channel>Application</Channel>
<Computer>sharepoint</Computer>
<Security UserID="S-1-5-21-2280669542-4145173436-3058324265-4222" />
</System>
<EventData>
<Data Name="string0">PWA/SDN</Data>
<Data Name="string1">Microsoft.Office.Project.Server.Administration.ProvisionException: Failed to provision databases. ---> Microsoft.Office.Project.Server.Administration.ProvisionException: To create databases we need dbcreator and securityadmin
server roles on servers.
at Microsoft.Office.Project.Server.Administration.PsiServiceApplication.EnsureDatabases(ProjectProvisionSettings provset, SPSite pwaSite, String adminName, String adminEmail, ProjectDatabaseStateType& originalDatabaseState, Guid& adminGuid)
--- End of inner exception stack trace ---
at Microsoft.Office.Project.Server.Administration.PsiServiceApplication.EnsureDatabases(ProjectProvisionSettings provset, SPSite pwaSite, String adminName, String adminEmail, ProjectDatabaseStateType& originalDatabaseState, Guid& adminGuid)
at Microsoft.Office.Project.Server.Administration.PsiServiceApplication.CreateSite(ProjectProvisionSettings provset)</Data>
</EventData>
</Event>
Anybody ever get any events like this before? I'm not finding much or nothing on Google or on other forums, so I thought I would run it past and see if anyone has experienced anything of a similar
nature. And yes, the farm account obviously has creator/secadmin permissions, at this point of our deployment....
I look forward to any and all feedback. Thanks and good afternoon!

I figured out the answer to this myself. For those few who might run into something akin to my error...
During the off-hours of where I work, I re-applied the farm account credentials to all dB server VM SQL services that had the account for a log-on (i.e., MSSQLSERVER, SQLSERVERAGENT, etc.) as well as all SharePoint services on our WFE/App Server VM (a two
server farm is what we host), in that order. Then I rebooted the dB server first, followed by the SharePoint server. Upon coming back, everything was working fine again. I was able to provision a site, no probelm, and it seemed to even be a little snappier
when doing so.
One note: doing this procedure gave me a "One or more services have started or stopped unexpectedly" error in the Health Analyzer, for the SPTimerV4 service. When you get this, simply enter into the item and click on "Reanalyze Now;" this will quickly clear
the error out of the Analyzer, and all should be right with the world! :)

Security Groups when in 'Project Server Permissions Mode' - Project Online

Hi All,
We have Project Online up and running, by default the PWA instance we added to O365 was in "SharePoint Permissions" Mode, we changed to "Project Server Permissions" Mode because of some complex security we need to configure. For some
reason (different from Project Server 2013) Project Online creates a number of Security Groups by default that seem to be duplicates. For example for Administrators there are:
- Administrators
- Administrators for Project Web App
- Web Administrators (Project Web App Synchronized)
For Project Managers:
- Project Managers
- Project Managers (Project Web App Synchronized)
- Project Managers for Project Web App
And there is something similar for all the groups (compared to Project Server 2013):
I have looked online, with no luck, for some guidance on what all these groups are and if I can delete some of them without causing PWA to crash.
If anyone out there can point me in the right direction / send me some documentation or links it will be greatly appreciated!
Thanks!
Jorge

Hi Jorge, I had the same thing on two different tenants within the last week - one today. I will just clean up the SharePoint groups manually. The ones with the descriptions are the correct Project Server permission mode groups... Hopefully Microsoft will
fix this soon, you could raise a support ticket on your office 365 tenant - support is pretty quick! Paul
Paul Mather | Twitter |
http://pwmather.wordpress.com | CPS

Project Server 2013 administrator account unable to access PWA site

I've just finished installing and configuring all the appropriate pieces to get PS2013 up and running along with a pwa site. The problem I'm running into is that my designated administrative account for the pwa site is unable to login at all. I receive
the "Sorry this site hasn't been shared with you." error. The domain account has all the appropriate permissions according
to the PS2013 guide, the services are all up and running, and the pwa site is provisioned. I'm at a loss as to what to change to access the pwa site.

Using SharePoint Central admin navigate to PWA site provisioning page
Hover the mouse point over provisioned PWA site and select view.
Review Primary administrator's field.
Let me know if this does not help, we can also find out using querying database but only with SELECT query.
Since this is brand new PWA, you can delete the PWA site make sure to uncheck the check box delete site collection and re-provision PWA site using same name and database but this time you can either use old account or use new account
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.

PWA permissions

Similar Messages

Maybe you are looking for