Project Server technical bits

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:Pro...

** WARNING ** following this post may kill your already sickly farm.... Imagine the scenario: - during some troubleshooting, someone deletes some EPM databases that they believe no longer point to a PWA Site (but actually do) or - when deleting a PWA Site, some environmental issue interrupts the process before it completes or - an issue occurred during PWA Site provisioning or - who knows what, sometimes bad things happen...... what you will see: Sharepoint will continually report events such as : An exception occurred while running the job scheduler.   Reason: Cannot open database "ProjectServer_Published" requested by the login. The login failed.  Login failed for user xxxxxxxxxxxxxxxxx.  Technical Details: System.Data.SqlClient.SqlException: Cannot open database "ProjectServer_Published" requested by the login. The login failed.  Login failed for user xxxxxxxxxxxxxx     at System.Data.SqlClient.SqlInternalConne...

** UPDATE2:  OK so I didn't reboot before that previous note.  This has now resolved the issue.  Reboot WAS tried prior to June CU * UPDATE:  After installing June CU2011 Server Rollups (SPF & SPS+PS) I am still seeing the same issues as before.  More research to do..... Since my rig had Project Server 2010 SP1 packages installed I have seen PWA provisioning fail when creating a brand new PWA Site with clean DB names etc. Note:  This is NOT a restore scenario: Firstly I see the following, which is what I would expect: 09/19/2011 15:45:59.32 OWSTIMER.EXE (0x0C30)                   0x05C4 Project Server                 Provisioning                   6974 Information Provisioning 'zzzzzzzzzzzzzzzzz': Server versions: Primary 10.50.1600.1, Reporting 10.50.1600.1. 47871661-d3d4-46fa-9c73-f5faf328a37d ...