Project Server technical bits

** 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 ...

Sometime over the last couple of weeks - whilst running some BI-focused EPM Demos - I have come to realise that sometimes no manner of demo will get people interested when they just want to jump to the good stuff, the charts and graphs, the decomposition tree, indicators and traffic lights and KPI's etc etc Sometime's they just want the shiny-shiny So with this in mind I've given my blog a spring clean and a spruce up.  Time is pushed at the moment but I intend to attempt to post as much as I can over the coming months.  As ever, there will be some trouble shooting and some how-to's that I hope people can get benefit from.

The other day I was tibnkering on my new demo rig (I love SSD's) and the whole OS Drive locked up on my, causing me to hard-crash the machine. Uh-ho i thought... my VM was running at crash point... better check it over. Lo and behold, my rig was dead on reboot.  Upon review my config_db was suspect - go figure - and I had to try and get it back (as I was going to lose quite a lot of work if i didn't). So after a little trawl around I found the following.  I hope it helps someone else in the future: Run this in SQL:                alter database “Sharepoint_config” set emergency Set DB to single user mode  Run this in SQL to find the SPID for the connection to the Config_DB                 sp_who2 disconnect from SQL ensure SQL Browser service started open SQL Mgt but dont connect to the server New Query                Kill SPID#...

Timesheet solutions in project server 2010 - #1 Security black holes and foibles This is my first outing into a full blown stand-alone timesheet solution.  Yes, I’ve done the full bottom-up and top-down configurations before but never JUST timesheets. The aim of this solution is to - minimise the administrative overheads associated to running an EPM solution - minimise “Project Owner” involvement in the process and thus minimise MS Project Pro licence needs - Capture historic data (actual work and cost) - A fixed list of “activities” per project, duplicated for work performed pre project and during the project - Allow anyone to work on any project within their particular group/team/dept - provide some insightful BI and reports off the back The entry point in for this solution is the [magical] new option of automated publishing via rules, delivered as part of SP1, without which we would not be moving forward with this. Voyage of discovery: During the first t...