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

Labels:

Comments

Post a Comment

Popular posts from this blog

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

SP2 released

Office Project Server 2007 Sp2 has now been released.  see the details here - http://blogs.msdn.com/chrisfie/archive/2009/04/28/announcing-service-pack-2-sp2-for-microsoft-project-2007-and-microsoft-project-server-2007.aspx .  see teh webcast here http://blogs.msdn.com/brismith/archive/2009/04/28/project-server-2007-service-pack-2-sp2-is-now-available.aspx Blogged with the Flock Browser
Post a Comment
Read more

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  LEFT OUTER JOIN         ...
Post a Comment
Read more