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!



Popular posts from this blog

#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 Status Manager, approve the time on task 1 …

What to do when your application server goes bang

What happens when someone kills your Application Server?
So imagine the scenario:
Three Server Solution - SQL - SharePoint 2010 and Project Server 2010 Application Server (Central Admin Host) - Wfe/ReportServer
We wake one bleary Monday morning to find that some numpty has killed the application server and the users are baying for blood.
Well surprisingly SharePoint handles this disaster recovery scenario particularly well.  Well.  Better than I thought it would to be honest.
Rough steps:
- quick SQL backup to be safe - Rebuild your application server - reinstall pre-reqs - reinstall SP, PS, SPFSP1, SPS+PSSP1, Cumulative Update and other stuff you usually put on there. - Run your configuration wizard to reattach to the Farm, and select Host CA Site
The last step was what I was VERY wary of.  Would the server simply reattach to the Farm, even when there is no CA server available?  
Bingo your back.... almost.... you are going to get errors a-gogo in your event log as things just aren't quite back…

Reporting from Project Server 2016 - multiple sites and userviews

Just a quickie...
I've been interested in how MS have handled the "multiple PWA sites in a Content DB" thing since I read that this was their new approach.  Most of my reporting is via SSRS so i am reliant (still... in 2016) on DB queries rather than OData feeds (tsk) and this "querying a PWA DB with more than one PWA site in it is unsupported" quote was worrying me.

So it looks like what is happening is this.

When you create the first PWA site in a Content DB it hard-codes the SiteID into the _Userview view design elements.  This means that your first PWA Site is the default.  All the data for subsequent sites are still held in the tables against separate SiteID's but you cannot utilise the OOTB _Userview components (see below)

SELECT        ProjectFields....
FROM            pjrep.MSP_TVF_EpmProject('FF19B767-CA6D-4C4C-B123-C0B5AE5354D6') AS MSP_EpmProject