Skip to main content

Project Server 2010 PSI : Unhandled Communication Fault #projectserver




Environment
  • Two tier environment
  • -        2x NLB Servers operating in WFE/APP role
  • -        Active/Passive SQL Cluster
  • NLB Settings
  • -        Multicast
  • -        Single affinity / sticky sessions
  • Web App created against NLB Host
  • PWA site created on Host Header
  • PWA Site DNS Alias linked to NLB Hostname

Issue: 
Running a custom powershell PSI job failed.  

Exception calling "readuserlist" with "1" argument(s): "Unhandled Communication Fault Occurred"
At line: 1 char:25
CategoryInfo NotSpecified: (:) [], MethodInvocationException

I ran projtool and when attempting to log on I received “Unhandled Communication Fault occurred” 

Fiddler returned the following http 500 error

1a2
http://schemas.xmlsoap.org/soap/envelope/
">http://Microsoft.Office.Project.Server">a:ProjectServerFaultCodeUnhandled Communication Fault occurredhttp://schemas.microsoft.com/2003/10/Serialization/">Value cannot be null.
Parameter name: account

0

Resolution:
Disabling Anonymous Access in IIS on both WFE/APP Servers resolved the issue

  • Open IIS
  • Identify and select the website that is hosting the Project Web App Site(s)
  • Select Authentication 
  • Right click on Anonymous Access and Disable
  • Retest PSI Calls - should now be successful

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

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

SSRS 2016 Dashboard UX Part 1 - Slicers

Dashboard navigation is the phrase i am using to describe the process of being able to interrogate and drill down into reports without the necessity for using parameters.  Let's face it, parameters are really ugly in SSRS - even with the ability to now lay them out - and the world would be a happier place if there was such a concept as slicers and other report UI elements natively in the SSRS universe. Firstly a note:  yes, I know Power BI does a lot of this stuff.  However, for on-premise customers, this isn't necessarily a cost-effective solution.  Most of my customers are SharePoint and Project Server users and - lets face it - most Project Server environments don't end up sitting on SQL Enterprise Edition so Power BI requires $/£ on top of the existing customer investment, which just isn't gonna fly in most cases. So here are a few concepts I have played with in the last few weeks to spoof such navigation tricks. Part 1) Single-select slicers usi...
Post a Comment
Read more