Skip to main content

*FIXED* #ProjectServer2013 bug? - cannot close in progress timesheet periods

Timesheet periods cannot be closed "bug"(?):

 ** UPDATE:  THIS IS NOW FIXED WITH THE JUNE 2013 CUMULATIVE UPDATE FOR PROJECT SERVER 2013 **
http://support.microsoft.com/kb/2817341

 The following has been repro'd on 
- an Project Server 2013 (RTM) - next step is June CU
- project online

 Repro:
- Create a number of resources/users
- Set up timesheet periods
- Test 1: TS periods can be closed
- Create a timesheet (one user)
- Save timesheet
- Test 2: Close timehseet period (same period as timesheet created in) = Result - TS period cannot be closed 

 Note:  you can also note a javascript error in IE at line 1409.  When you look at the source code, this appears to point to a page with the URL /pwa/_Layouts/15/pwa/admin/PeriodCloseConfirmation.aspx
Now I don't know if this is a legacy page or not, but if you navigate to this page you see this (which is exactly what I want to see when closing a period)
So what this means if this means is:- if you are running timesheets it is impossible to exempt some users from timesheets submission as periods wont be able to be closed!! 

 Another fail in this is that the Timesheet Status flag is extremely unreliable. I have seen many examples where a timesheet returns to 0 State (not submitted) event when it is approved. This will also trigger this failure to close timesheet periods.

 It's my belief that this is not by design behavior due to the existence of this page, which suggests it is an override to allow periods to be closed:
Labels:

Comments

Post a Comment

Popular posts from this blog

Issues update on #projectserver2013 - Timesheets and Publishing

Reporting Publish ** updated with links to other related discussions, and a VBA macro ** the following issue has been noted on publish since June 13 CU was applied: ReportingProjectChangeMessageFailed (24006) - Object reference not set to an instance of an object.. Details: id='24006' name='ReportingProjectChangeMessageFailed' uid='4d869e56-f625-e311-bb41-005056b90052' QueueMessageBody='Project UID='e3f49977-b2bc-e211-8559-005056b90052'. PublishType='ProjectPublish'' Error='Object reference not set to an instance of an object.'. I have seen this noted previously on a similar issue: http://nearbaseline.com/blog/2013/06/ms-reporting-project-publish-jobs-failed-after-aprilcu/comment-page-1/#comment-14741 This is  caused by Baselined Milestones having NULL Baseline Cost values Original bug note with potential workaround is here: http://blogs.msdn.com/b/brismith/archive/2012/05/23/project-server-2007-reporting-project-pu...
4 comments
Read more

#projectserver2013 VIEW FAILURE: The view failed to load. Press OK to reload this view with the default settings. Press cancel to select another view.

** UPDATE ** includes notes relating to secondary bug where Timesheet is created without Administrative tasks. Does this ring any bells? This has been bugging me for months, but finally I have a repro for this: Issue Summary:  When a task is deleted from a plan that is approved into a previous or current timesheet - even when there are no actuals on the task - you can no longer view the timesheet The following repro has been proven: - Setup system with Single Entry Mode, with enforced Status Approval before Timesheet Approval - Create resource as own timesheet manager - Create new project - Create two tasks in the same week, starting monday with 5 days duration:  1) Task to assign actuals, 2) Task to delete post submission - Assign Resource to tasks - publish project - as Timesheet User, go to the appropriate timesheet period for the tasks created - Assign actual work to one task (task 1), leaving task 2 with no actual work - Submit timesheet - as Project ...
6 comments
Read more

Restoring PWA Site to another Web App in the same Farm

The scenario is this: SharePoint 2016 Farm with Project Server Two Web Apps Development UAT One PWA on Development Web App. I want to copy the PWA Site on Development web app to UAT to support a testing cycle. As far as I knew there were two options: 1) Content Database Restore and Attach Process would be backup your Dev Content Database, Restore to a new Content Database for QA, then mount the database on the appropriate web app and your off.... Problem:  Although you can do this with the -AssignNewDatabaseID switch in Powershell (to avoid two content db's having the same database id) the Site Collection (PWA) in the db still retains its SiteID which means there is a duplicate SiteID in the Configuration Database.  This stops the PWA site being created and alllocated correctly and becomes essentially orphaned. This method is only any good for MOVING not COPYING Back to the drawing board... 2) Backup-SPSite / Restore-SPSite I didn't believe this ...
1 comment
Read more