*** Update 4/3/2014 - as a precaution both the SharePoint and Project Server SP1 downloads have been temporarily made unavailable - more information when I have it. The KB articles have been updated with:We have recently uncovered an issue with this Service Pack 1 package that may prevent customers who have Service Pack 1 from deploying future public or cumulative updates. As a precautionary measure, we have deactivated the download page until a new package is published.***
Busy day in Project Blog land – SP1 for Project 2013 and Project 2013 is out – see http://blogs.technet.com/b/projectsupport/archive/2014/02/25/project-2013-and-project-server-2013-service-pack-1.aspx
A couple of points to note – if you updated the sproc mentioned in KB 2933444 then you will need to update it again after applying SP1 as we re-write the sprocs (double checking this (thanks Corrie!)) – and if you didn’t – perhaps you should?
And the other point – the SP1 Server side scheduling engine reports a lower version number than the client – so if you want to control the allowed version of Project Professional that can connect then just go for 15.0.4569.1000 and all will be good!
Hi : I´m going to instal Project server 2013 , but I have a question The Project server 2013 it is compatible with IE9?
I believe there may be a bug in Project client SP1 with baselines.
1) Create task of 1d
2) Add a resource with a cost rate
3) Set Task Usage at bottom window
4) Add Baseline 0 Cost, Baseline 10 cost, baseline 4 cost (or some others too)
5) Add some Timephased costs into Cost timephased field
6) Set baseline
7) All baselines are set with a value *ERROR
8) Edit Baseline0 Cost TImephased entry
9) All Baseline Values change *ERROR
Hi Carl, thanks for the feedback. Can you clarify step 5) Add some Timephased costs into Cost timephased field? With a work resource the costs come from the work. Do you mean adding more work elsewhere - or some other cost. And exactly where are you entering it. Feel free to mail me if that would help with screenshots etc.
And for Marian - yes, IE9 is supported. We support the same browser set as SharePoint - see technet.microsoft.com/.../cc263526.aspx
Actually it is an easier repro:
- Firstly create split view with task usage on the bottom and gantt at the top
- add Cost, baseline Cost, Baseline1 cost, other baseline cost fields to the Task Usage Timephased section
1) Create a task (any duration)
2) assign a resource to the task that has a standard rate so we see costs timephased in task usage pane
3) Now set Baseline0
BUG: See that Baseline 1-10 Cost values in timephased data now all have a value, not just the baseline0cost value
4) Now edit an element of the timephased baseline0 cost data
BUG: All Baseline Cost Values change in that time segment to the value you edited
5) Now try edit a timephased segement for basline 1 cost
BUG: Notice the edit wont set
6) now try settings Baseline 1 (or another >0)
BUG: Timephased BaselineX Cost Values NOT Created
It appears that timephased data for Baseline1-10 Cost are linked to the Timephased values of Baseline0Cost. This did not occur before SP1 was applied.
Note: This doesn't occur on Baseline Work timephased values, or any of the tabular fields, only TIMEPHASED BASELINE COST 0-10
I will email you the screenshots over
I have a farm consisting of 2 servers:
1. SharePoint Server 2013 + Project Server 2013;
2. SQL Server 2012.
After installing SP1 for Project Server 2013 (and previously for SharePoint Foundation 2013 and SharePoint Server 2013) I have errors, when run my PowerShell-scripts, that update projects:
1. Update Project error:
<?xml version="1.0" encoding="utf-16"?>
<error id="9131" name="GeneralQueueException" uid="4e24adbf-29aa-e311-93fb-005056b86b77" messageID="2" exception="System.NullReferenceException: Object reference not set to an instance of an object. at Microsoft.Office.Project.Server.BusinessLayer.ProjectEngineUpdate.HandleSSPUpdates() 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)" />
<error id="26000" name="GeneralQueueJobFailed" uid="4f24adbf-29aa-e311-93fb-005056b86b77" JobUID="14ed62a0-f9ec-437c-88df-5124226f12c8" ComputerName="71a7fe7a-8c66-4dec-8f87-e4e6dc92b25b" GroupType="ProjectUpdate" MessageType="ProjectUpdate2Message" MessageId="2" Stage="" CorrelationUID="6ea47c9c-ff30-f037-2b25-b9047c2bb543" />
2. Publish Project error:
Exception calling "QueuePublish" with "4" argument(s): "ProjectServerError(s) LastError=ProjectPublishEnqueueFailure Instructions: Pass this into PSClientError constructor to access all error information"
3. CheckIn Project error:
Exception calling "QueueCheckInProject" with "5" argument(s): "ProjectServerError(s) LastError=ProjectCheckinFailed Instructions: Pass this into PSClientError constructor to access all error information"
All errors associated with the execution of queue tasks.
I work with PSI. Fragment of program code:
# New GUID for session
$SessionId = [System.Guid]::NewGuid()
# New GUID for job
$JobId = [System.Guid]::NewGuid()
Write-log "Update Project..."
$SvcPSProxy_Projects.QueueUpdateProject2($JobId, $SessionId, $Project, $false)
Write-log "Publish Project..."
$SvcPSProxy_Projects.QueuePublish($JobId, $Project.Project.PROJ_UID, $true, $EmptyString) | Out-Null
Write-log "CheckIn Project..."
$SvcPSProxy_Projects.QueueCheckInProject($JobId, $Project.Project.PROJ_UID, $false, $SessionId, $SessionDescription_CheckIn)
If the same operation (Save/Publish/CheckIn) to perform on the PWA-site or from client (Project Professional), errors do not occur! Problem is only with PSI! Before installing SP1 everything was Ok!
What do you think?
Thanks Carl, I will take a look.
Ronni - not aware of any issues with PSI post SP1 - I'll take a look with ProjTool - the 2010 version certainly still worked prior to SP1.
after installing the SP1 for Project Server 2013 (and SharePoint Server 2013) we are experiencing the issues like Ronni also when using CSOM.
-GeneralQueueException (9131). Details: id='9131' name='GeneralQueueException' uid='9bc746d4-77b2-e311-93fc-00155d350205' messageID='2' exception='System.NullReferenceException: Object reference not set to an instance of an object. at Microsoft.Office.Project.Server.BusinessLayer.ProjectEngineUpdate.HandleSSPUpdates() 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)'.
-GeneralQueueJobFailed (26000) - ProjectUpdate.ProjectUpdate2Message. Details: id='26000' name='GeneralQueueJobFailed' uid='9cc746d4-77b2-e311-93fc-00155d350205' JobUID='8e6ca9d3-77b2-e311-93fc-00155d350205' ComputerName='d220335d-5209-4b3d-ad09-ff0eec096759' GroupType='ProjectUpdate' MessageType='ProjectUpdate2Message' MessageId='2' Stage='' CorrelationUID='5b0b809c-0ead-a00a-9675-91074aca04a3'. For more details, check the ULS logs on machine d220335d-5209-4b3d-ad09-ff0eec096759 for entries with JobUID 8e6ca9d3-77b2-e311-93fc-00155d350205.
The issue seems to be related to DraftProject class or it's methods after SP1?
I think you can repro the issue with the LimitTest example; msdn.microsoft.com/.../microsoft.projectserver.client.draftproject.update_di_pj14mref.
- an example code executes just fine but the "Project Update from PSI" job fails in the Queue and a project is not checked-in as it should be.