Skip to main content

#ProjectServer2013 Issues with Views

Project Server 2013 Issues Summary

Over the last few weeks I've been implementing a number of Project Server 2013 systems, and have found a couple of application issues that are worthy of note:

Views Issue #1 - Project Center / Resource Center - "The View Failed to Load"

This error, followed by "You do not have permissions to view" message appear to relate to a failure of the webpart to select a view from the list available to me.

One example of how this can happen is that if I selected View A the last time I accessed Project Centre, but since then View A has been removed/taken away, then this error will occur.

Another example MAY (awaiting repro) be if you delete/rename/remove the default Project Centre view.

The fix is three clicks of a mouse but is really not good.

- Open the ribbon
- Select a new view from the available list
- F5 Refresh

This should be a simple code fix to ensure that if the cached last view is no longer available, enumerate through to find the first available view and display that.

Note:  This has also been noted on Resource Centre although the second error you get is Access Denied


Views Issue #2 - Phantom Project Schedule views
This is a very new one.  we removed a pile of the default schedule views from all categories as we had replaced them with our own custom views.
Strangely any projects created PRIOR to this change being made still display the views as available, however if you select them they return "There is no data available" (as you would expect as they are not attached to a category)

Any new projects do not display these phantom views.

Again, this is very early warning, and I will be aiming to repro this in a few weeks time.

Views Issues #3 - Timesheet creation failure
Again this is initially noted by the generic "The view failed to load" but this time there are no options to workaround this.  The issue was noted for a specific resource, so I worked on the basis that it was a data issue.

I looked in the tasks.aspx view for the resource while delegating and found one assignment with a NULL value in the Work field.

Upon reviewing this in the plan, this task was a Milestone.

Of course we all know that you shouldn't put resouces on milestones, but as this is supported by Tasks.aspx and you cannot stop it, the timesheet task population job SHOULD account for this and at least either exclude the assignment or add it in as read only.

The ULS error we saw was:

Error is:  GeneralUnhandledException.  Details: General Unhandled Exception in _Timesheet.CreateTimesheet_ Attributes: System invaldcastexception: Cannot cast DBNull.Value to type 'System.Byte'. Please use a nullable type.

Removing these resources from milestones, and publishing, resolved the issue.

more to follow once i've repro'd!

Carl

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