Project server 2013 olap database remains in processing state

Hi,
In an attempt to restore the Reporting Database in Project Server 2013, I did an archive and restore of Custom fields. Both of these events were successful, however, the Reporting database refresh kept on hanging in "Waiting to be processed status".
Before this was noticed, the OLAP Database was configured and a build was initiated. Now the status of the PWAOLAPDatabase build just remains in the "Processing..." status. What am I to do here? Thanks!

Hi Jaco,
It seems like your reporting database refresh has failed, so the OLAP DB cannot be generated either. It could be due to a large resource pool.
See reference below:
http://social.technet.microsoft.com/Forums/projectserver/en-US/7ac3bb1b-6621-46f0-a6c5-d9a04f770418/reporting-database-refresh-project-server-2010?forum=projectserver2010general
http://blogs.msdn.com/b/brismith/archive/2011/07/14/project-server-2010-reporting-database-refresh-failing-with-large-resource-pools.aspx
Note also that you can click on "processing" (as per your screenshot) to have the OLAP DB creation log in order to have more information on the status.
Hope this helps,
Guillaume Rouyre, MBA, MCP, MCTS |

Similar Messages

Project Server 2013 reporting database change in Schema from Project Server 2010

I have a current Project Server 2010 implementation, I am planning to migrate to Project Online.
We have Customized Reports that consume from the PS 2010 Reporting DB.
Are there differences in the Reporting DB schema between PS 2010 and Project Online?
My Question is: if we migrated to Project Online, will the reports crash?
Another question is that, is PS 2013 Reporting DB schema the same as Project Online?

Hi Atia,
IN project server 2013 we have only one database instead of 4, it means draft, archive, published and reporting with in one database.Project Server 2013 reporting database schema tool that can be downloaded.
http://blogs.msdn.com/b/project_programmability/archive/2013/01/28/project-server-2013-reporting-database-rdb-schema-reference.aspx
There are differences in reporting of on-premises vs. Project Online
The Project Server 2013 reporting schema includes three new tables, 27 new views, and a total of 33 tables and views that include new fields.
Answer-1 : Yes there are some differences between PS 2010 and project Online.
Answer-2 : Reports will crash as In Project Online you have to use ODATA to create report. You can not query project online data for reporting directly you have to have use ODATA.
http://msdn.microsoft.com/en-us/library/jj163015.aspx
Answer-3 : NO, PS 2013 Schema and Project online Schema is different.
kirtesh

Project Server 2013 OLAP cube build error

When I try to build the OLAP cube I receive the below error:
[2/26/2014 12:36 PM] Failed to build the OLAP cubes. Error: The attempt to build the OLAP database on server SQL_Server_Name failed, the SQL Server Analysis Services Analysis Management Objects (AMO) client software may not be installed on this server, please
install/update the client on this server and retry. The underlying exception was: Could not load file or assembly 'Microsoft.AnalysisServices, Version=10.0.0.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91' or one of its dependencies. The system cannot
find the file specified.
I did some search and found that Analysis Management Objects (AMO) client software is not installed on my servers, I downloaded and installed the AMO client software , restarted the Project Server Service application to the 4 Servers. I rebooted the
4 servers, tried to build the cube, but I got the same error. I checked the assembly on the 4 servers and they contain the dll Microsoft.AnalysisServices.
Any help?
I read that AMO client software tools must be installed during the farm setup, after installing the SharePoint Prerequisites and before installing SharePoint. Is that correct?

Hello,
Even with SQL 2012, the 2008 SQL AMO component is required on the Project Server servers. See the post from Brian for more details:
http://blogs.msdn.com/b/brismith/archive/2012/11/12/project-server-2013-requirements-to-build-an-olap-cube.aspx
Paul
Paul Mather | Twitter |
http://pwmather.wordpress.com | CPS

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 Olap Data Connection Problem

I have created a number or Excel 2013 reports which use OlapPortfolioAnalyser data connection. Typically creating a pivot table. I can select any dimensions and measures and excel works as expected. However if I include the Project list or Resource
list it does not. I have tried this in two separate instances but do not have a separate environmnent availabale but would appreciate confirmation or othrewise of the misbehaviour.
Steps are: (Assuming cube is built and permissions set correctly and using Excel 2013 client)
In PWA\Bi\Data connections navigate to cube folder
Double click on OlapPortfolioAnalyser – opens in Excel 2013 (warning about data connections being blocked)
Click Enable
In pivot select project list from pivottable fields
Save file (locally or to sharepoint)
Close file
Now re-open file
Excel displays warning - "We found a problem with some content in "xxx.xslx". Do you want us to try and recover as much as we can? If you trust the source of the workbook, click Yes.
Click Yes
Another warning is displayed (Repairs to xxxx.xslx)
Removed Part: /xl/pivotCache/pivotCacheDefinition1.xml part with XML error. (PivotTable cache) Load error. Line 2, column 0.
Removed Feature: PivotTable report from /xl/pivotTables/pivotTable1.xml part (PivotTable view)
Click Close - you now see data but pivottable functionality is gone.
Note: this also happens with Resource list data.
How do I resolve this?
Thx
Mike
Mike Mahoney

More research and KB 2817339 appears to have the fix - see
http://blogs.technet.com/b/projectsupport/archive/2013/07/30/excel-2013-error-opening-saved-pivottable-reports-from-pwa-bi-center.aspx
As I mention in the blog - the fix will not recover a broken xlsx as the break appeared to be on save rather than open.
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
Unfortunately the blog post you linked is in error - it reports that the issue is fixed in build
15.0.4517.1001. However I am running 15.0.4517.1504 and still hit the problem. The only workaround is the one post by
adrian_rho, above, which solved my problem. Thanks Adrian for the workaround, and to Brian for the great job tracking and assisting people on this issue, even though it is Excel and not Project - much appreciated!
Mike

Failed to build the OLAP cubes (Project Server 2013)

We are receiving errors when attempting to build our OLAP cubes. We've attempted to install the 2008 version of the SQL server native client 2008 but still the error appears. Please advise.
Configuration:
Project Server 2013
SharePoint 2012
SQL Server 2012
Error Message:
===== Initiating OLAP database build process =====
[1/7/2014 2:00 AM] Cube build request message has been added to the Project Server queue ===== Verifying and running pre-build server event handler =====
[1/7/2014 2:00 AM] Verifying and running pre-build server event handler ===== Determining database and OLAP database structure =====
[1/7/2014 2:00 AM] Cube build initialization started ===== Building database and cubes =====
[1/7/2014 2:00 AM] Cube build session started ===== Verifying and running post-build server event handler =====
[1/7/2014 2:00 AM] Verifying and running post-build server event handler ===== Processing OLAP database =====
[1/7/2014 2:00 AM] Process OLAP database session started ===== Process Completed =====
[1/7/2014 2:00 AM] Failed to build the OLAP cubes. Error: Failed to process the Analysis Services database OLAP_FTF on the XYZ server. Error: Errors in the back-end database access module. The provider 'SQLNCLI10' is not registered.
The following system error occurred: Class not registered Errors in the high-level relational engine. A connection could not be made to the data source with the DataSourceID of 'Project Reporting data source', Name of 'Project Reporting
data source'.
Errors in the OLAP storage engine: An error occurred while the dimension, with the ID of 'Project List', Name of 'Project List' was being processed.
Errors in the OLAP storage engine: An error occurred while the 'Start Date' attribute of the 'Project List' dimension from the 'OLAP_FTF' database was being processed.
Internal error: The operation terminated unsuccessfully.
Server: The current operation was cancelled because another operation in the transaction failed.

Hi Importek,
Please have a look to a similar threads that has been answered.
http://social.msdn.microsoft.com/Forums/en-US/a2696e29-e68e-45a8-8dae-fa8fa5640575/receive-the-following-error-when-trying-to-build-cube-errors-in-the-highlevel-relational-engine?forum=sqlanalysisservices
http://social.technet.microsoft.com/Forums/projectserver/en-US/420958bd-4613-451c-ac06-a1f149f64da9/problem-when-trying-to-build-the-cube?forum=projectserver2010general
Finally an article by Brian Smith:
http://blogs.msdn.com/b/brismith/archive/2007/07/16/yet-another-olap-error-message-the-longest-yet.aspx
This might be an issue of the SQL instance alias.
Hope this helps.
Guillaume Rouyre - MBA, MCP, MCTS

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 - Workflow Execution " Submit button is grayed out. "

Dear All,
As i was in progress to making workflows in sharepoint designer this is my first project of implementing project server 2013 and executing the workflows,in the continuation of this i followed below mentioned link to go through the process of WORKFLOWS but
got some issue
LINK: http://msdn.microsoft.com/en-us/library/office/jj163494(v=office.15)
ISSUE: Is that the SUBMIT Button is grayed out after saving initial proposal plan. Snapshot is attached.
I have checked in/out process along with this gone through re-executed the whole process same result occurred.
Suggestion/Help needed...
REGARDS DANISH DANIE

Hi Danish,
Its a common thing which users are experiencing.
When you create project from workflow click on Submit it take time for transition before transition it check all the condition which you have set for workflow stage. As per your screenshot it is waiting for details in PDP (Provide details of the proposed project)
when you click on submit it push data into the database,sometimes it send e mails to stakeholder then it use exchange and take times to send e-mails and for transition too.
When you/user face this issue ask them to wait for some time or close the file then reopen.
In the screen workflow is waiting for Project detail information in PDP that is why it is still in process and not going to next stage.
kirtesh

Problem after installation Project Server 2013 CU September 9, 2014

Dear All,
I have some problems after installation
Project Server 2013 CU September 9, 2014 (Hotfix 2883072) on 3 level farm
Before installing CU, I have installed
SP1 for Project Server 2013, installation and configuration was successful.
Then I have installed CU and I have not get any errors during installation process. Then I have restarted servers and in SharePoint health analyzer got an error about patch/installation status
on WFE server.
I checked in Windows installed updates and hotfix is installed. I checked in SharePoint Update and Upgrade history and there were no errors during installation. But when I checked in Manage
Patch Status list I found an information:
Language Pack for SharePoint and Project Server 2013 - Russian
Microsoft Project Server Russian Language Pack 15.0.4420.1017 Installed
Hotfix for Microsoft Project Server 2013 (KB2883072) 64-Bit Edition
15.0.4649.1001 Missing/Required
Microsoft Project Server 2013
Microsoft Project Server English Language Pack 15.0.4571.1502 Installed
Hotfix for Microsoft Project Server 2013 (KB2883072) 64-Bit Edition
15.0.4649.1001 Missing/Required
Service Pack 1 for Microsoft Project Server 2013 (KB2880553) 64-Bit Edition
15.0.4571.1502 Installed
Microsoft Project Server Web Front End Server
15.0.4571.1502 Installed
Hotfix for Microsoft Project Server 2013 (KB2883072) 64-Bit Edition
15.0.4649.1001 Missing/Required
Service Pack 1 for Microsoft Project Server 2013 (KB2880553) 64-Bit Edition
15.0.4571.1502 Installed
If I run installation again I get message that nothing will be updated - no update needed.
Please help, how I can install missed packages?

The problem was solved !
I solve it using two ways:
1. I have installed the hotfix for Project Server - Hotfix for Project Server 2013 October 14, 2014 KB 2889959 (Projectserverwfe-x-none.msp, Projectservermui-Language-Code.msp)
2. using command
Psconfig -cmd upgrade -inplace b2b -force -cmd applicationcontent -install -cmd installfeatures -cmd installcheck -noinstallcheck
After two actions I was able to run SharePoint Configuration Wizard and upgrade database. Configuration completed successful.

Unable to edit the Project details from PWA in Project server 2013

I am Migrating the project from MS Project 2007 to MS Project 2013.In that i save the project as a file first in 2007 and then open that file in MS Project 2013 And publish it.But in some Project when i am Trying to change the projects details from
PWA in Project server 2013 and then trying to save then the projects are not saving and are generating the error as shown below
•GeneralQueueException:◦GeneralQueueException (9131). Details: id='9131' name='GeneralQueueException' uid='f7bb5d93-20e9-e411-b302-005056ae159c' messageID='2' exception='System.TimeoutException: This request operation sent to net.pipe://localhost/pscalc_13c43af4a7d34a2c8145b776b325a865
did not receive a reply within the configured timeout (00:05:00). The time allotted to this operation may have been a portion of a longer timeout. This may be because the service is still processing the operation or because the service was unable to send a
reply message. Please consider increasing the operation timeout (by casting the channel/proxy to IContextChannel and setting the OperationTimeout property) and ensure that the service is able to connect to the client. Server stack trace: at System.ServiceModel.Dispatcher.DuplexChannelBinder.Request(Message
message, TimeSpan timeout) at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout) at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage
methodCall, ProxyOperationRuntime operation) at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message) Exception rethrown at [0]: at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg) at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData&
msgData, Int32 type) at Microsoft.Office.Project.Server.Interfaces.ICalcService.OpenProjectRemappedProject(CalcServiceCallState callState, Guid realProjectGuid, Guid remappedProjectGuid, EngineSessionState& sessionState, EngineSessionType sessionType,
PSError& psError) at Microsoft.Office.Project.Server.BusinessLayer.CalcServiceChannel.OpenProjectRemappedProject(CalcServiceCallState callState, Guid realProjectGuid, Guid remappedProjectGuid, EngineSessionState& sessionState, EngineSessionType sessionType,
PSError& psError) at Microsoft.Office.Project.Server.BusinessLayer.CalcServiceProxy.<>c__DisplayClass2.<OpenProjectRemappedProject>b__1(ICalcServiceChannel calcServiceChannel, PSError& localPsError, EngineSessionState& localSessionState)
at Microsoft.Office.Project.Server.BusinessLayer.CalcServiceProxy.<>c__DisplayClass6e`1.<RunCalcServiceOperation>b__6c() at Microsoft.Office.Project.Server.Base.IdentityUtilities.<>c__DisplayClass1`1.<RunWithAccessToAppTierServices>b__0()
at Microsoft.SharePoint.SPSecurity.<>c__DisplayClass5.<RunWithElevatedPrivileges>b__3() at Microsoft.SharePoint.Utilities.SecurityContext.RunAsProcess(CodeToRunElevated secureCode) at Microsoft.SharePoint.SPSecurity.RunWithElevatedPrivileges(WaitCallback
secureCode, Object param) at Microsoft.SharePoint.SPSecurity.RunWithElevatedPrivileges(CodeToRunElevated secureCode) at Microsoft.Office.Project.Server.Base.IdentityUtilities.RunWithAccessToAppTierServices[T](Func`1 action) at Microsoft.Office.Project.Server.BusinessLayer.CalcServiceProxy.RunCalcServiceOperation[T](CalcServiceOperation3`1
func, EngineSessionState& sessionState, String scopeName) at Microsoft.Office.Project.Server.BusinessLayer.CalcServiceProxy.OpenProjectRemappedProject(Guid realProjectGuid, Guid remappedProjectGuid, EngineSessionState& sessionState, EngineSessionType
sessionType) at Microsoft.Office.Project.Server.BusinessLayer.ProjectEngineUpdate.OpenProject() at Microsoft.Office.Project.Server.BusinessLayer.ProjectEngineUpdate.HandleUpdate() at Microsoft.Office.Project.Server.BusinessLayer.ProjectQueueDispatch.HandleProject2(MessageContext
mContext, ProjectMain project, ServerEventManager sem, ProjectDataSet dataset, Guid projectUid, Guid sessionUid) at Microsoft.Office.Project.Server.BusinessLayer.ProjectQueueDispatch.InternalDispatchMessage(IPlatformContext context, Message msg, Group messageGroup,
JobTicket jobTicket, MessageContext mContext)'.
•Queue:◦GeneralQueueJobFailed (26000) - ProjectUpdate.ProjectUpdate2Message. Details: id='26000' name='GeneralQueueJobFailed' uid='f8bb5d93-20e9-e411-b302-005056ae159c' JobUID='a6fa36de-1fe9-e411-b302-005056ae159c' ComputerName='1af8030b-7714-4c8f-8738-903b73e87a82'
GroupType='ProjectUpdate' MessageType='ProjectUpdate2Message' MessageId='2' Stage='' CorrelationUID='0a4aff9c-dd6b-7015-87a8-29d876e1540c'. For more details, check the ULS logs on machine 1af8030b-7714-4c8f-8738-903b73e87a82 for entries with JobUID a6fa36de-1fe9-e411-b302-005056ae159c.
What will i do .Please help.

Hi Jeremy,
Thanks for the reply .I try the steps that is given in link above but its not working.Please suggest something.What
should i do.

Help needed Regarding Project Server - 2013 Workflow

Hi All,
I am new to Project server 2013 Workflow, hence please help me regarding this. Pardon me if this question is too trivial.
I have created a project type associated with a workflow and my workflow is as follows :
So I am not doing anything here, I am just testing the workflow as mentioned by technet site : http://technet.microsoft.com/en-us/library/dn458865(v=office.15).aspx
But it is mentioned that, after a minute or 2, the workflow state will change, also they have mentioned to press the Submit button.
But in my case, the workflow is not moving to next stage [It just says 'The workflow is still processing - which never changes after hours] or I am getting the submit button (Submit button is disabled on the ribbon). Below is the state of my workflow :
PS : I have made the user added to Portfolio managers group as well. But still I am having this same issue.
The Workflow manager is installed properly, and it is working fine in case of List workflow. I am facing the issue only wrt Site workflow for Project server 2013.
Please help me to solve this issue.
Thanks,
shanky

Hi Kiran,
I am now facing issue while assigning a task to a person in the workflow.
I am having a person named say 'John' , who is included in Project Manager as well as Portfolio Manager.
And I am using a workflow as :
Stage : Conceptual
Assign a task to John (Task outcome to Variable: Outcome5 | Task ID to Variable: TaskID3 )
Transition to stage
Go to Approval
But this is again giving issue as :
Workflow Internal status : Cancelled
Details: System.ApplicationException: HTTP 401 {"error":{"code":"-2147024891, System.UnauthorizedAccessException","message":{"lang":"en-US","value":"Access denied. You do not have
permission to perform this action or access this resource."}}}
PS : I have used the same Sharepoint admin account for 'Account Name' in ‘User Profile Sync' , Is this causing the issue? Please let me know.
Thanks,
Shanky

Saving Error in Project Server 2013, Need Help!

Hey All,
I am running into issues with a Projects saving from Project Pro 2013 to our Project Server 2013 Farm.
It is strange, when someone tries to save a project out of Project Pro 2013 to Project Server, it will run through the "Synchronizing Data to the Server", and then bombs out with error
Job Type: Save
Error ID:9000(0x2328)
The project could not be saved to the server, Etc..
My understanding is that this is a generic save error that could mean many things.
In the ULS logs under "Active Cache Save" , I am getting:
"Cancelling correlation 1339927b-e9e5-e311-941d-00155d2bc10d as save is an overwrite or resubmit"
What is strange at this point is if I check the project back in, and re-open/re-checkout the project, and try to save again, it is successful in saving.
Just a few details about the environment:
Project Server Version: 2013 RTM (In the process of upgrading)
SharePoint Version: 2013 RTM (In the process of upgrading)
Project Structure: One Master Project with all other projects being subprojects of the master
Published Status: All Published
SQL Version: SQL Server 2012 SP1
User Count: About 5 currently
Deployment: 1 WFE, 1 APP Server, 1 SQL Server
It is just odd, as it seems to be completely random. We have tried clearing caches out to see if that resolves it but it did not. It is just odd that it takes two saves for it to actually work correctly, and is problematic as the many times they are saving
from the master and it bombs out there.
I am not sure how it could be an issue as it is usually just a single user working on the individual subprojects.
Maybe it is an issue in the RTM? I couldn't find any info in any of the CU's or SP's that addresses this directly
Has anyone seen this, or have any suggestions?
MS Support has not been any help at all.
Thanks all

I have heard of issues with Master and Sub-Projects and both being published to Project Server, as a rule it is a feature I learnt to avoid as a result of bad experiences with earlier versions of Project Server.
Whilst this will not resolve the issue you have encountered the following suggestion may help you avoid pain in the future and leverages the potential of Project Server to represent common attributes for projects.
Typically a Master/Sub Project environment is intended to reflect projects that are commonly aligned - it is not unusual for a Master Project to represent a programme and for there to be multiple sub-projects forming the programme - there can be programme
level events that have multiple predecessors from multiple sub-projects.
Rather than create a master and sub-project situation I would suggest looking to define two Enterprise Custom Project fields to assist with such situations. The first being a Project Field called Programme that has a look up table with a list of current
programmes you can select from. The second Project Field would be a Programme Status Field with an associated lookup table with 3 values, Master, Sub-Project, Standalone.
You can have a project represent the Master (Programme) project and open it and all sub-projects in the programme (albeit this would have to be a one by one action to begin with). With all the projects open go and open a New Window in Project Professional
and elect to include all the open projects in the new window - this will create a new project with all the selected projects showing as
"embedded objects" and then create dependencies from sub-projects to programme level events in the Master Project (I would suggest what I call
"one way traffic" when creating "cross project dependencies" to avoid further headaches). Close the project, you will be prompted to save changes which you should do but do not save the new window
"container" project. The dependencies across the projects will persist - in each project you will be able to see external successors - tasks in the master project. In the master project you will be able to see external predecessors.
In PWA you can create Project Centre Programme views that filter to exclude projects that ARE Standalone and group them by Programme and sort by Programme Status Field - this will ensure that the "Master" sits at the top of the pile for each programme grouping.
Just a suggestion - I hope the issue you have encountered is resolved soon.
Dominic Moss | MAPM Microsoft Certified Technology Specialist | Our Newsletter:
PM News Project Server Specialists
Project Server PRIME | Twitter:
@Twitter | Facebook:
@Facebook | Linkedin:
Wellingtone

Workflow in Project server 2013 online not going particular stage after Approval

Hi All,
i have created workflow using sharepoint designer 2013 for project server 2013 online. and i have also set the approver after the first stage. when i create a project using this workflow, project is created successfully and the approval task also go for
a approval to specific user. and i have set the property that after approval it has to go on specific stage. but the problem is when user approve the task it shows approved but my stage in workflow is remain same. it is not going to any stage.
i don't know why this type of problem is occur.
FYI, i have created same workflow for Project server 2013 on premise(Which is installed in my server) and
it is working fine but when i want to deploy this workflow in
project server 2013 online its giving error.
so please help me to solve this type of issue.
Thanks

I am also experiencing issues with this. After the approval task is completed, the Workflow gets cancelled with the following message
RequestorId: 60d96368-4cb4-b059-8086-604972a92e60. Details: System.Collections.Generic.KeyNotFoundException: The given key was not present in the dictionary. at Microsoft.Activities.Hosting.Runtime.Subroutine.SubroutineChild.Execute(CodeActivityContext context)
at System.Activities.CodeActivity.InternalExecute(ActivityInstance instance, ActivityExecutor executor, BookmarkManager bookmarkManager) at System.Activities.Runtime.ActivityExecutor.ExecuteActivityWorkItem.ExecuteBody(ActivityExecutor executor, BookmarkManager
bookmarkManager, Location resultLocation)
All other desired workflow actions work as expected. Emails are sent, project is moved from stage to stage, however as soon as the workflow approval task is completed, either Approved or Rejected, the Internal Status is changed to Canceled and the
workflow fails.
What is interesting is when the Approval task is completed, the approver will receive an email notification that the task was CANCELLED or DELETED....
not COMPLETED, which is what would be expected.
Has anyone seen this - any potential resolution?

How to make the entire project in the project server 2013 reschedule؟

How to make the entire project in the project server 2013 reschedule ?
Because item %compelet related to reschedule
In this photo it is known there are no items update project

Hi,
In PWA, you do not have the feature to update the project plan in one click, meaning marking as completed the work before the status date or reschedule after the status date the remaining work. Either you have to use Project Pro, or edit individually the
assignments with the actual work (if not comming from timesheets) and remaining work.
Hope this helps,
Guillaume Rouyre, MBA, MVP, P-Seller |

Project server 2013 olap database remains in processing state

Similar Messages

Maybe you are looking for