Project Server 2013 SP1 only

Hi,
Can Project Server be updated to SP1 and leave SharePoint without it? it seems there is some kind of trouble
http://social.technet.microsoft.com/Forums/en-US/45b56c00-b894-445d-9e4b-c44b158f0531/after-project-server-2013-sp1-update-without-updating-sharepoint-server-2013?forum=projserv2010setup
Thanks

Hi,
We need SharePoint Server SP1 installed first and then install Project Server SP1

Similar Messages

Project server 2013 sp1

Hi,
What is sequence for installing-SP1 on Project Server 2013 ?
1.SP1 for sharepoint 2013
2.Windows updates (is it required ?)
3.PSConfig Wizard (is it required ?)
Recent CU needed ?
4. SP1 for project Server 2013
5.Windows updates (is it required ?)
6.PSConfig Wizard (is it required ?)
Recent CU needed ?
Regards

Hi Mafab,
You can refer to this link for PS2013 CUs:
http://blogs.technet.com/b/projectsupport/p/ps13cu.aspx
Hope this helps,
Guillaume Rouyre, MBA, MVP, P-Seller |

After Project Server 2013 SP1 update (without updating Sharepoint Server 2013)

I get this error entering the PWA root:
Derived method
'RequiresWebPartClientScript' in type
'Microsoft.Office.Project.PWA.WebParts.PWAPart' from assembly
'Microsoft.Office.Project.Server.PWA, Version=15.0.0.0, Culture=neutral,
PublicKeyToken=71e9bce111e9429c' cannot reduce access
SharePoint Server 2013 version: 15.0.4420.1017
Project Server 2013 version: 15.0.4569.1506
There is no SP1 uninstall process? Totally lost!

Hi Ximet,
If you go to Central Administration > System Settings > Manage Servers in this Farm. Do you see Upgrade Available for the servers.
If they show Upgrade Available, can you run the SharePoint Config Wizard one more time or you can also try running the command "psconfig -cmd upgrade -inplace b2b -wait -force"
Just curious to know if the issue is because the binaries have not been updated properly.
In case the issue persists and is impacting your business, I would suggest that you raise a support ticket with Microsoft so that we can further assist you on the case.
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.

Problems installing Project Server 2013 SP1

Hi,
I have an issue installing Project Server SP1 (KB2880553). The history of this installation is as follows below:
I have one App Server and one Web Server (test environment)
On February I installed the mistaken SharePoint 2013 SP1, Project Server SP1 and Language Pack SP1 in both servers, followed by SharePoint Config Wizard. No problem here, other than the mistaken SP1's
The current week I've installed SharePoint SP1 (KB2880552) in both servers, followed by SharePoint Config Wizard. No problem here.
Then I installed Project Server SP1 (KB2880553) in both servers, it got installed in both servers apparently, but when I run the SharePoint Config Wizard in the APP server I get the error below and I can't continue:
If I try to install Project Server SP1 in the Web Server it tells me that the product is alteady installed there, if I try to install the Language Pack SP1 KB2880554, it tells me that there is nothing to be installed in that Web server.
If I check the Patch Status in Central Admin, this is what I get regarding the Web server, the APP server is apparently ok:
So the problem is that I can do nothing, as it doesn't allow me to install anything anywhere.
Please, do you know what to do in this case?
Thank you for your help and regards,
José Espases

Hi,
thank you for your answer.
Maicco, I've already tried to follow the links but as I said initially there is nothing that I can install, as you can see in the second picture that I sent before, the KB2880553 is installed partially (last line) but missing/required in other lines, so
when I try to install it again it keeps saying that it has been already installed, but when I execute the Config Wizard it says that it is missing and required.
The Uninstallation/installation is what I try to avoid.
Raymundo, regarding the post http://www.maadarani.com/Blog/Lists/Posts/Post.aspx?ID=12&mobile=0 it
doesn't work, probably something is missing in the link, please, can you send it again?
Thank you and regards,
José Espases

Project Server 2013: Set-SPProjectPermissionMode error

Hi,
In our environment, we need to use Project Server permission mode to fine tune permissions. According to documents, we need to run the Set-SPProjectPermissionMode command. However, when I ran it, I got the following error:
Set-SPProjectPermissionMode : There is a version mismatch between the Web server and the content databases, and connections to the data have been blocked to avoid data loss. This can happen when a service pack is not completely installed. Notify your server
administrators so that they can
upgrade the Web server and the databases to the same version. For more information about installing service packs and updates, see the Microsoft Web site (http://go.microsoft.com/fwlink?LinkID=177163).
The linked document does not offer any help. It talks about changes in Project Server 2010, while we're configuring permission mode in Project Server 2013.
Thanks for any information.
By the way, we've installed both SharePoint 2013 SP1 and Project Server 2013 SP1 (currently only one server in the farm). In Central Admin's Upgrade and Migration section, neither the content database nor the service packs (or any other updates) report any
errors.

Hello,
If you go to Central Admin check the following two pages:
Manage Servers in this Farm (in System Settings) - on this page what does the status show for each server in the farm, "Action Required" or "No Action Required". If any action is required, please resolve this before attempting
this PowerShell command again.
Review Database Status (in Upgrade and Migration) - do any of the farm databases status display action required or are they all "No Action Required"? If any of them require action, please resolve this before attempting this PowerShell command
again.
Paul
Paul Mather | Twitter |
http://pwmather.wordpress.com | CPS |
MVP | Downloads

Task custom field and formula custom field don't correspond Project Server 2013

Hi people, I have an interesting case in Project Server 2013 SP1 CU Apr:
I have a custom task number field called AM. This field get's filled by a PSI action with actual material costs from an external system.
I also have a custom task cost formula field that is called AM*. This field is a formula field that has the formula [AM]. And summary tasks use the formula field as well.
As soon as I create a project, assign costs in the external system and let PSI fill the values within AM I get correct values in AM. But nothing is calculated on AM*. If I edit the project in the browser and publish, check in and revisit the project
AM* still isn't filled.
If I open the project in MS Project Pro the calculation comes through nicely, however I do not want to use MS project Pro to see correct data in browser.
Some tests I have already done:
I have noticed that when I create a new calculated task field AM2*, this get's calculated correctly on the already existing task.
I have also noticed that opening the custom field in server settings and just saving the field creates correct values on AM*.
What is going on? I don't want to save the custom formula field every day... There are 11 custom formula fields in the environment at the moment.

Hi Gary,
Thank you for the quick response. Please note that the fieldnames are [AM] and [AM*]. There is a difference in field name due to the astrix. However I did think about the situation and changing one of the field names all together didn't do anything for the
situation at hand.
It looks like some kind of refresh thing, because without changing anything in the custom field just saving the field in server settings will turn op good values. However, values already turned up good in Project Professional 2013. And that suggest
that there is a calculation error on the PWA side wouldn't you say?
Anyway, thank you for taking time to look into this matter.
Erik

Project Server 2013 - Approved Tasks not applied to Project Schedule

Environment Details: Microsoft Project Server 2013 SP1
When an Resource completes a tasks within the Task or Timesheet page at the end of each day, the tasks is routed to the Project Owner for approval. The Project Owner (Project Manager) approves the task. During this process no errors are displayed.
When the Project Owner (Project Manager) goes into the Project Professional 2013 client to view how the project is progressing, and update the project completion date, the updates is not applied to the project.
This worked for some time, but has recently stopped working with no changes made to the environment. Any help would be great, as our project manager's are manually updating the tasks prior to approving them so they can report back on the project each week.

Hello ProjMgrMatt
Sounds pretty serious, but I think something is missing somewhere.
Make sure that the Status Manager field is the same as the Project Owner.
Check to queue to be sure that nothing is stuck and waiting.
Create a new project, publish, submit, approve, etc and see if it still happens.
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

Connecting "ms project pro 2007" to "project server 2013"?

Hello, Is there a way to connect "ms project pro 2007" to "project server 2013"? Do we have a "backward compatibility mode" in this context? Thankx

If I understood correctly, you are asking for whether the MS Project Professional 2007 is supported in Project Server 2013. The answer is
no.
Project Server 2013 supports only Project Professional 2013 version.
http://technet.microsoft.com/en-us/library/ff603505(v=office.15).aspx

After installing Project Server 2013 (without updating SharePoint Server 2013 SP1))

I am facing the problem while opening project web app. I configured the SharePoint 2013 and project server 2013. Here is the detail what I performed the steps:
OS Server 2012 R2, SQL Server 2012, SharePoint server 2013 version
15.0.4420.1017, Project Server 2013 version
15.0.4454.1000. SharePoint configured and running successfully. After project web app site provisioning successfully completed. I got the below error.
Microsoft.Office.Project.PWA.WebParts.PWAPart' from assembly 'Microsoft.Office.Project.Server.PWA, Version=15.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c' cannot reduce access.
I run this psconfig -cmd upgrade -inplace b2b -wait -force. But still getting same error.
Previous steps:
Earlier I had also tried to install SharePoint Server 2013 SP1 "3823428". After the installation SP1 some of sharePoint site features suddenly stopped e.g: Cannot browse "Service Applications -->
Manage service applications" option even after re-start the server. This was previous error after upgrading SP1
"Method 'get_IsClientValid' in type 'Microsoft.SharePoint.WorkflowServices.WorkflowServiceApplicationProxy' from assembly 'Microsoft.SharePoint.WorkflowServices,
Version=15.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c' does not have an implementation"
Anyone can help me!!! Thanks...
Faisal Numan

hello,
For SP2013 and PS2013 to work properly on Windows Server 2012 R2 you need to use the SP1 install media for both, download SharePoint 2013 with SP1 and Project Server 2013 with SP1
http://support.microsoft.com/kb/2891274
http://blogs.technet.com/b/office_sustained_engineering/archive/2014/03/03/announcing-availability-of-slipstreamed-office-2013-and-sharepoint-server-2013-with-sp1.aspx
http://blogs.technet.com/b/projectsupport/archive/2014/02/25/project-2013-and-project-server-2013-service-pack-1.aspx
Paul
Paul Mather | Twitter |
http://pwmather.wordpress.com | CPS

Project Server 2013 - Out of Office Sync - Only two months in future?!?

Hello there guys,
after Long Long search for the problem, I've found out that our Project Server 2013 only syncs the out of Office time from our Exchange Calendar for the next two months.
But for our Project planning we Need of course a more longtime synchronization, at least 6 or better 12 months.
I didnt find any Option where I could set it to sync more then 2 months of the out of Office times in the calendars.
I've spent already so much time on this Problem... When I set the Project Server time 2 weeks(!) in the future, then the sync will also sync two more weeks in the future, but not more.
The timesheet periods are also set for the next 12 month.
Does anybody have an Information/help regarding this Problem for me?
How can I set the Out of Office sync to synchronize more then just 2 months?
THANK YOU VERY MUCh!!
Regards
Lukas Meyer
PS: Using the current October 2013 CU.

I've searched the Verbose Log and found the following:
12/17/2013 14:38:16.32 Microsoft.Office.Project.Server (0x0928) 0x1A6C Project Server Exchange Sync aaubf Verbose PWA:https://servername/PWA, ServiceApp:Project Server-Dienstanwendung, User:PROJECTSERVER\system,
PSI: Calling service.GetUserAvailability() for user:2c3909bc-d6fb-e211-b239-000c296be823 for period:12/17/2013 00:00:00-02/17/2014 00:00:00, LogLevelManager Warning-ulsID:0x00014045 has no entities explicitly specified. 3a2f619c-f4a0-f018-b62b-b2d1299a489f
So the Project Server is only asking for two months of User Availability on the Exchange. Where can I Change this Setting so that the Project Server syncs more then 2 months?
Otherwise this functionality is quite useless in my view as we are planning our Projects longer then only 2 months...
Thank you!

SP1 files for Project Server 2013

Hi,
Where can we found the true SP1 files for SharePoint Server, Project Server and Project Pro 2013,
after the withdraw of first SP1 ?
Thanks

Hello,
SharePoint Server 2013:
http://support.microsoft.com/kb/2880552
Project Server 2013: http://support.microsoft.com/kb/2880553
Project 2013: http://support.microsoft.com/kb/2817433
Paul
Paul Mather | Twitter |
http://pwmather.wordpress.com | CPS

Project Server 2013: Project progress task available to only assigned resources.

I have a project in project server 2013. In that I am preparing the project plan. Now I want that only the respective person to whom I have assigned the task can modify the % complete. Not even the owner can edit it.
Shruti Vyas
Advaiya Solutions Pvt. Ltd.
Associate Development Services.

Project owner can modify the the plan either from PWA or from MPP.
As far as % complete is concerned for assignment only Resource who will be assigned to the task can fill the actual for the task either from Task page or from Timesheet page if Single Entry Mode is enabled. No one else can fill the actual for the task from
Timesheet page and task page. AS assignment will be available to the only that resource who is assigned to the task.
But Project owner can do the modify the project plan any time either from MPP or from PWA you can not restrict him/her. But as far as % complete is concerned do the setting
To prevent the project manager from updating a team member's actual time worked, select the Only allow task updates via Tasks and Timesheets check box. it will be
available on server setting --> Task setting and display
http://technet.microsoft.com/en-us/library/gg982960(v=office.14).aspx
kirtesh

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

Publication of the big-sized Enterprise projects from Project Professional 2013 to Project Server 2013 takes about 60+ minutes.

Dear Sirs,
I need your support over the following MS EPM 2013 issue:
Publication of the big-sized Enterprise projects from Project Professional 2013 to Project Server 2013 takes about 30+ minutes. We
need to reduce this total publication time down to acceptable working values 10+- minutes.
Environment information:
Single App Server (Virtual): 16 Gb RAM, x64 4xCPU, HDD > 50 GB free disk space, OS Windows Server 2012 Standard Edition x64 Service
Pack 1, MS SharePoint Server 2013 and MS Project Server 2013 with CU December 2013 (KB 2850024) applied.
Single RDBMS MS SQL Server (Virtual): 8 Gb RAM, x64 4xCPU, HDD > 200 GB free space, OS Windows Server 2012 Standard Edition x64 Service
Pack 1, MS SQL Server 2012 x64 SP 1 Enterprise Edition.
We have 1Gbit LAN between APP, DB server and 1Gbit LAN between APP and Proj Prof Client.
Yes, we are on the way of migrating to the Prod environment
with 3-tiered architecture (with SP1 slipstream and CU December 2014 applied), but this issue also
presents there.
Project’s file information:
Tasks in the file: [~4900], resources in the file [~396] enterprise task’s custom fields used in the file [~23].
Project save procedure for this new project would last about 7 minutes. Project publication would last about 47 minutes. We noticed that
tasks synchronization process took about 1 second for each ~2,5 tasks, to add them to the sharepoint tasks list. So for all 5148 tasks it took about 5148/3/60 = 34 minutes. Other 13 min was used for reporting database publication and other tasks relevant
for new sharepoint site creation.
Case 1: Issue description:
During the Enterprise project’s file save and publication we have the following sharepoint 2013 log messages:
07.31.2014 12:43:17.22 Microsoft.Office.Project.Server (0x0358) 0x3D5C SharePoint Foundation Monitoring b4ly High Leaving Monitored Scope
(Persisting list changes). performing time =376.068676326181 22dca99c-4696-70f1-e9e2-06851d0bcffd
07.31.2014 12:43:17.69 Microsoft.Office.Project.Server (0x0358) 0x3D5C SharePoint Foundation Monitoring b4ly High Leaving Monitored Scope
(Persisting list changes). performing time =361.652807828928 22dca99c-4696-70f1-e9e2-06851d0bcffd
It shows that sharepoint spend at least ~350 milliseconds (or 0,35 sec*4900 tasks = 1715 sec, or 28,5 min) for each task update during
project publication. And we also have another log file that shows that about 0,7 sec (or 0,7 sec*4900 tasks = 3430 sec, or 57 min) sharepoint spend for save each task in project file to project server. So total save and publication time more then 60+ minutes
for that project file. The same result we have even if user didn’t do any changes at the project file.
We use only enterprise projects (dbo.MSP_EpmProject_UserView.projectvisibilitymode = «False»), and do not use sharepoint tasks lists,
but the synchronization between MSP Plan and SharePoint tasks list works at any case.
Case 2: Issue description:
- For the second test we created a new project with new sharepoint project’s site on basis of our «issue» project, with total amount
of tasks in it of 5148 (yes, we increased the tasks list default limit at the sharepoint site up to 6000 items in it – standard limits for sharepoint view list – 5000 items).
- Project save procedure for this new project would last about 7 minutes. Project publication would last about 47 minutes. We noticed
that tasks synchronization process took about 1 second for each ~2,5 tasks, to add them to the sharepoint tasks list. So for all 5148 tasks it took about 5148/3/60 = 34 minutes. Other 13 min was used for reporting database publication and other tasks
relevant for new sharepoint site creation.
-Then we deleted the
tasks list for that new test project from the sharepoint site and republish the project plan one more time. This time project save procedure took about 7 minutes, project publication about 2 minutes and 3 minutes for other relevant queue jobs. So total time
is 12 minutes.
As a conclusion: yes, we have determined
the exact problem - during synchronization process (from Project Server to SharePoint) it perform copying all tasks and related data from Project to SharePoint in spite of fact that you changed only ONE task or ALL of them. At any case, synchronization will
copy ALL of them from Project Server to SharePOint task’s list.
Our workaround is to disable the task’s synchronization for such big-sized project plans:
– to delete the SharePoint «tasks» list at the SharePoint site tied with project plan.
- or deattach the SharePoint site from the project plan.
Thank you for reading this topic, please if you also forced with such issue provide us any known workaround or maybe any official response
\ feedback from MS about it.
Thank you in advance,
Best Regards, Andrey

Regarding my topic, I also said that every time when sync works it updates All items from project’s plan at Project Server to corresponded task’s list at SharePOint server. Inspire of the fact that you changed only One task or group /
all of them at your project’s plan.
And it seems to me and my colleagues that it’s probably (maybe) a “bug” at the product. Here is what we have if looked a little bit closer to the code:
Share Point determines what task to sync from Project’s plan to sharepoint list. To do that sharepoint needs to know was that task changed or not, based on the following fileds (check SQL stored procedure “[MSP_READ_TASKS_FOR_SYNCRONIZATION]”):
TASK_UID    TASK_NAME    TASK_START_DATE    TASK_FINISH_DATE    TASK_PCT_COMP    TASK_PARENT_UID    TASK_OUTLINE_NUM
WSS_LISTITEM_UID   TASK_ID    TASK_IS_ACTIVE
We noticed that at any case synchronization performs for all tasks, EXCEPT the ROOT one. Then we looked at the comparison of TASK_PARENT_UID field. So sharepoint compares TASK_PARENT_UID with ParentID (this is internal name for lookup
field “Tasks” at the Sharepoint, and it stores their values at the format "ID;#Title").
And comparison performs like following:
SharePoint looks for Task at the Tasks’s list corresponded to Project’s plan with ID represented at the TASK_PARENT_UID field. Then it takes SharePoint ListItem ID (“int” type) and store it to the “num” parameter;
num = this.GetCachedListItemByUniqueId(listItem.ParentList, nullable.Value).ID;
2.Then it compares “num” with task’s “ParentID” at SharePOint as follow with operator “!=”:
((SPItem) listItem)["ParentID"] != (System.ValueType) num
3. If comparison was success (true) – then it tell us that values (at the Project’s plan for tasks) was changed, then it need to be synchronized. Corresponded Method setup “true” flag, and then returns it.
The “bug” is that this expression at the Step 2 will always return “true”, because in fact it compares “string” (see above – that this is lookup field at SharePoint side)
with “number”. For example if the parant task ID is “55”, then we get:
"55;#Task 1" != 55
And by the rules of .Net the “string” will never equal “number”
Furthermore this is approved by the SharePoint logs:
In that case we always get the note “Setting ParentID to” at the logs (we see it if turns on Verbose for “Project Server” -> “Sharepoint Integration” category).
So at any case of publishing project’s plan we always get that note at the logs for tasks that have Parent task, and we have Parent for all of them EXCEPT the ROOT one, exact logs represented further:
10/15/2014 02:37:32.26    Microsoft.Office.Project.Server (0x07D8)    0x06E8    Project Server    Sharepoint Integration    ado0d
Verbose    Setting ParentID to 1    bf2fc29c-7727-b00d-fa4a-34f22ea9ec1d 10/15/2014 02:37:32.62    Microsoft.Office.Project.Server (0x07D8)    0x06E8
Project Server    Sharepoint Integration    ado0d    Verbose
Setting ParentID to 1    bf2fc29c-7727-b00d-fa4a-34f22ea9ec1d 10/15/2014 02:37:32.63    Microsoft.Office.Project.Server (0x07D8)    0x06E8    Project Server
Sharepoint Integration    ado0d    Verbose
Setting ParentID to 1    bf2fc29c-7727-b00d-fa4a-34f22ea9ec1d 10/15/2014 02:37:32.67    Microsoft.Office.Project.Server (0x07D8)    0x06E8    Project Server
Sharepoint Integration    ado0d    Verbose
Setting ParentID to 1    bf2fc29c-7727-b00d-fa4a-34f22ea9ec1d 10/15/2014 02:37:32.69    Microsoft.Office.Project.Server (0x07D8)    0x06E8    Project Server
Sharepoint Integration    ado0d    Verbose
Setting ParentID to 5    bf2fc29c-7727-b00d-fa4a-34f22ea9ec1d
The following is the complete Method’s code from the corresponded reflector:
private bool UpdateParentID(DataSet taskDS, DataRow row, SPListItem listItem, Dictionary<Guid, SPListItem> redoEntries)
bool flag = false;
int index = taskDS.Tables[0].DefaultView.Find((object) DataRowExtensions.Field<Guid>(row, "TASK_PARENT_UID"));
if (index >= 0)
Guid? nullable = DataRowExtensions.Field<Guid?>(taskDS.Tables[0].DefaultView[index].Row, "WSS_LISTITEM_UID");
int num = -1;
if (listItem.Fields.ContainsField("ParentID"))
if (nullable.HasValue)
try
// STEP 1
num = this.GetCachedListItemByUniqueId(listItem.ParentList, nullable.Value).ID;
catch (ArgumentException ex)
if (redoEntries != null)
if (!redoEntries.ContainsKey(DataRowExtensions.Field<Guid>(row, "TASK_UID")))
redoEntries.Add(DataRowExtensions.Field<Guid>(row, "TASK_UID"), listItem);
//STEP 2
if (num != -1 && ((SPItem) listItem)["ParentID"] != (System.ValueType) num)
((SPItem) listItem)["ParentID"] = (object) num;
ULS.SendTraceTag(845443U, (ULSCatBase) ULSCat.msoulscat_PS_ProjectSharepointIntegration, ULSTraceLevel.Verbose, "Setting ParentID to {0}", new object[1]
((SPItem) listItem)["ParentID"]
//STEP 3
flag = true;
else if (((SPItem) listItem)["ParentID"] != null)
((SPItem) listItem)["ParentID"] = (object) null;
ULS.SendTraceTag(2495056U, (ULSCatBase) ULSCat.msoulscat_PS_ProjectSharepointIntegration, ULSTraceLevel.Verbose, "Resetting ParentID to null");
flag = true;
return flag;
Any thoughts about it would be much appreciated!

Project Server 2013 - OLAP Cube Build Issues

Hi,
I have a Project Server 2013 environment with SQL Server 2012 SP1. My cube built successfully and Report Authors group (including me) were accessing the templates and Data Connections from BI centre successfully.
I re-built the cube and suddenly we all cannot access templates or data connection as it says 'Access denied'!
Went to server hosting Analysis Services and checked the role ProjectServerViewOlapDataRole and didn't see any of the check box ticked for database permissions like it was when I initially built the cube and added Report Authors group and account
that is used by Secure Store app. Membership has both account and group.
Has anyone come across this issue?
Thank you,
SJ

SJ,
The access of the BI Center, templates and data connections are handled by SharePoint permissions and are usually inherited from PWA.
The ProjectServerViewOlapDataRole simply provides the ability to view the data from the OLAP database. It sounds like the issue isn't with the OLAP but rather with PWA itself. An OLAP error would have only precluded you from retrieving data.
Did someone modify the BI Center site permissions recently such as breaking inheritance?
Treb Gatte, Project MVP |
@tgatte | http://AboutMSProject.com

Project Server 2013 SP1 only

Similar Messages

Maybe you are looking for