Extract logs from #SharePoint ULS logs #ProjectServer #PS2013 #SP2013

July 30, 2012 at 12:14 pm | Posted in Administration, Customisation, Functionality, Information, PowerShell | 1 Comment
Tags: , , , , , , ,

This post follows on from my previous post regarding the new log level manager functionality in Project Server 2013: https://pwmather.wordpress.com/2012/07/26/projectserver-ps2013-log-level-manager-sp2013-sharepoint-msproject-powershell/

Once configured, all activity on the farm for that particular entity, depending on the logging level set, is logged in the SharePoint ULS logs.

As mentioned in my last post, I said that I would create a simple PowerShell script that will extract the Project Server 2013 log level manager logs into a custom file to make it easier for viewing.

The script is available from the Microsoft Script Center below:


The script can be seen below with comments for configuration options:

# set the required date, below will set today, other days / dates can be
# used. For example, to get yesterdays logs use
# $Date = get-date -format "yyyyMMdd" (get-date).AddDays(-1)

$Date = get-date -format "yyyyMMdd"

# if you want logs from a specified date, remove the $Date variable from the where object
# and specify the string, for example for 27/07/2012 use:
# where-object {$_ -like "*20120727*"}

$files = Get-ChildItem "C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\15\LOGS" | where-object {$_ -like "*$Date*"}
foreach ($file in $files)
    # this script will copy any row that contains LogLevelManager!, to copy other
    # logs, update the string in the where object, for example you could use the entity UID
    get-content -path "C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\15\LOGS\$file" | where-object { $_ -match ‘LogLevelManager!’} | Out-File C:\PSLog$Date.txt -append

Running the script:


Creates a new text file in the specified location, in this example, the root of the C drive:


Whilst this script is aimed at extracting the Project Server log level manager logs, it could also be used to extract logs for other SharePoint applications. For example, you might have an issue with Excel Services and may want all of the Excel Services logs into a separate file while you investigate the issue.

#ProjectServer #PS2013 Log Level Manager #SP2013 #SharePoint #MSProject #PowerShell

July 26, 2012 at 8:15 pm | Posted in Administration, Configuration, Functionality, Information, PowerShell | 3 Comments
Tags: , ,

There is new feature in Project Server 2013 called the Log Level Manager that enables you to track certain entities such as Projects, Resources and Tasks etc. Once configured, all activity on the farm for that particular entity, depending on the logging level set, is logged in the SharePoint ULS logs. 

More details can be found here:


The log level manager is configured using PowerShell, the Project Server 2013 preview PowerShell commands can be found here:


For the purpose of this blog post I have enabled logging for one test project, the project is called PMPSTest1 and the project GUID is 35cafba6-38d6-e111-9923-4c809328175b. Below you can see the PowerShell commands used to set up the logging for this one project:


Notice the refresh command, this is required to update the cached list of entities to watch.

As mentioned above the log level manager writes the logs into the SharePoint ULS logs, an example can be seen below:


An example entry:

LogLevelManager!PWA:http://vm657/PWAClassic, ServiceApp:Project Server Service Application, User:i:0#.w|cps\paulmather, PSI: Start checkout of project ’35cafba6-38d6-e111-9923-4c809328175b’ by resource ‘f8a06617-38d6-e111-bf72-00155d1463b9’ to store ‘WorkingStore’. Project:35cafba6-38d6-e111-9923-4c809328175b Original TraceLevel:Medium    9f6fbd9b-85f6-e003-5b7a-17f60ec5f059

The SharePoint ULS logs aren’t the nicest of log files to look through at the best of times, never mind trying to look for logs regarding the specific Project Server entities that you are tracking. I will create a simple PowerShell script to take all of the log level manager entries from the ULS logs and place these into a new text file/s. This will enable you to view all of the Project Server log level manager entries without the other SharePoint entries.

The log level manager is very useful for auditing / tracking activity for a certain project, task or timesheet etc. It would not be recommended to enable verbose logging for all entities in Project Server though!

#SharePoint #SP2013 Project Site visibility in #ProjectServer 2013 #Office365 #PS2013

July 25, 2012 at 5:52 pm | Posted in Configuration, Functionality, Information, Reporting, T-SQL | 4 Comments
Tags: , , ,

In this post I will look at the new functionality that allows you to have visibility of the SharePoint 2013 project sites / SharePoint sites that have a Task list in Project Server 2013. I mentioned this functionality in a previous post last week: https://pwmather.wordpress.com/2012/07/19/first-look-at-projectserver-online-office365-ps2013-sp2013/

The SharePoint 2013 Project Site template by default has a Task list so these will be available to add to Project Server, if you add the Task list to other SharePoint 2013 sites in the PWA site collection these will also be available to add to Project Server 2013.

For the purpose of this post I have a couple of test projects that are managed by Project Server, these are called PMPSTest1 and PMPSTest2. I also have 2 SharePoint Project Sites that contain tasks ready to be added to Project Server, these are called PMSharePointTest1 and PMSharePointTest2.

Firstly lets take a look at the project centre, here we can see the two Project Server projects as mentioned above.


Below are the two SharePoint 2013 sites created from the Project Site template:

Project Site template:


Project Sites:


Notice one task is assigned to Lee Mather – he is not currently a resource in Project Server.


Lets take a look at the Project Server Project Sites, we will use PMPSTest1 for this. As you can see below the tasks from the project plan do not appear in the Tasks list on the associated project site as this project is managed via PWA:



Notice the message stating that this project is managed by Project Server Project Web App.

Before we add any SharePoint sites to Project Server I just want to show the projects in the reporting tables from the ProjectServer database:


Now we will look at adding a SharePoint site, see the steps below:

Navigate to the Project Centre, click the Projects tab > Add SharePoint Sites:



Notice the three SharePoint sites, two are created from the project site template the other site is a team site with the Task list added.

Select PMSharePointTest1 and click Add:


Click Close

Below is a screen shot of the Project Server queue showing all of the successful jobs for adding this SharePoint site task list to Project Server:


Once the jobs have completed successfully, refresh the Project Centre and you will see the SharePoint site:


Clicking the PMSharePointTest1 project takes you to the Task list on the site:


Notice the quick launch on the site now has a Project Details link, this gives you access to the Project Detail pages for this project:


As this is not an enterprise Project Server project you cannot edit the tasks from the PDP.

Looking at the resource centre, you can see that Lee Mather has been automatically added as a resource to Project Server as he was assigned the task SPTask3 on the SharePoint task list:


Looking at the Resource assignments for my account, you will see that all tasks (from both enterprise projects and the SharePoint task list) are displayed:


The SharePoint task list project (PMSharePointTest1) will also be available in Project Professional 2013:


Project Professional synchronises with the SharePoint task list, new tasks can be added using Project Professional and these are synched back to the SharePoint task list on the PMSharePointTest1 site:


Saving the project will sync the tasks back to the Task list:



Running the same SQL query against the Reporting tables / views in the ProjectServer database now includes the tasks from the SharePoint site that was added. This enables reports to be easily created using Excel / SSRS etc.:


Notice the ProjectVisibilityMode column, for the SharePoint project site the value is 1, for enterprise projects the value is 0.

The data is also available in the Project Server OLAP cube, example below looking at the MSP Portfolio Analyser cube:


The SharePoint task list can be removed from Project Server using the normal delete enterprise object functionality – if you want to keep the SharePoint site do not check the box “Delete the connected SharePoint sites”!

The SharePoint task list can be converted to fully managed enterprise project using the activate button on the Connected SharePoint Sites page:


After clicking Activate, the project will appear and function as a normal enterprise Project Server project and set the SharePoint task list to read only. Deactivating will set the project back to a SharePoint task list managed project.

Projects created in Project Server can also be deactivated and managed via the Task list.

This new functionality is great for organisations that want the visibility of lightweight projects in Project Server. This enables both types of projects, enterprise projects and task lists, to be visible in one central location and also make use of the full reporting capability of Project Server.

For more details see the links below:




#ProjectServer 2013 online change permission mode #Office365 #PS2013 #SP2013

July 19, 2012 at 8:15 pm | Posted in Administration, Configuration, Functionality, Information | 2 Comments
Tags: , , ,

Quick post to detail the steps to change permission mode for Project Server 2013 online. The default permission mode is the SharePoint permission mode, to change this to Classic permission mode (Project Server mode) see the steps below:

Open PWA and click Admin > Project:


Select the PWA site and click Project Web App > Settings from the ribbon:


Check the Classic permission management radio button, specify an administrator and click OK.


Please note, switching between permission modes deletes all security related settings.

First Look at #ProjectServer online #Office365 #PS2013 #SP2013

July 19, 2012 at 6:48 pm | Posted in Functionality, Information | 3 Comments
Tags: , ,

As you are probably all aware the preview for next version of Office was released earlier this week. https://pwmather.wordpress.com/2012/07/16/projectserver-2013-preview-sharepoint2013-msproject/

In this post I will give a brief intro to the new version of Project Server 2013. I will cover the look and feel and highlight some of the new features. The screen shots from the post are from the Project online version as I haven’t got around to installing the on-premise version yet. For this example I have created a simple example project called PM Test Project 1.

Firstly lets take a look at the default PWA homepage:


The reminders web part has been updated with the cool new metro style “Track your work” web part to summarise your work. Clicking one of the icons takes you to that page to see the details, for example the Tasks page:


This page looks the same as it did in 2010.

The project centre now has the timeline view available:


You will also see a new button on the Projects tab, Add SharePoint sites:


When you click this button a new window will pop up populated with a list of the SharePoint sites based on the SharePoint Project Site template, below you can see the example site I created on the PWA site collection.


Once these SharePoint project sites are added they are visible in Project server but I will create a separate post for this soon!

The Project sites have nice new Project Summary web part where you can switch between the timeline or upcoming and late tasks:



All the project task are visible but not editable on the project site in the Tasks list:


There is also a notebook on the project site, this uses OneNote:


Project 2013:


The built in reports have been updated, take a look at the Project Overview report:


The report is editable, with new charts and tables etc.



The existing charts are all editable:


These are just a few examples of the new features in Project Server 2013 and Project 2013. I will be posting more details in the coming weeks.

#ProjectServer 2013 preview #SharePoint2013 #MSProject

July 16, 2012 at 8:50 pm | Posted in Information | 3 Comments
Tags: ,

The next version of Project Server is now available as a preview, see the links below:

Project Server 2013 preview:


Project Professional 2013 preview:


Other links:




#ProjectServer Active Issues and Risks on PWA Reminders Web Part #PS2010 #SP2010 #SharePoint

July 13, 2012 at 11:05 am | Posted in Administration, Configuration, Customisation, Functionality, Issue, T-SQL | 1 Comment
Tags: , , , , ,

The Project Server reminders web part contains key information relating to all projects that the logged on user is involved in. This includes new task assignments, timesheet information, pending approvals and active issues and risks assigned to the logged on user. This post focuses on the issues and risks count as I have seen a number of queries relating to the issues and risks not showing on the reminders web part.

Firstly I will detail where this web part gets the data from and then show working / non working examples. This web part reads data from the Project Server Reporting database, two stored procedures create the dataset for the web part then the code on the web part counts how many of those issues and risks are active. The status value is key to the issues and risks count on the reminders web part, this will be shown in the examples later on. In the image below you can see that I have 3 active risks and 2 active issues assigned to me on my test system:


Lets now take a look what the two stored procedures return from the Reporting database. Firstly I need to get my ResourceUID to pass into the stored procedures using the simple query below against the Reporting database:


The two stored procedures are MSP_WSS_ReadResourceIssues and MSP_WSS_ReadResourceRisks. These two stored procedures require a RES_UID value, in this example I will use my ResourceUID C5733575-2C0A-4B40-A367-E33B82A1CB33 as shown below:


As you can see I have 3 risks and 4 issues assigned to me. Notice on the PWA reminders web part it shows 3 active risks which matches the SQL dataset and 2 active issues which doesn’t match the SQL dataset. The issues SQL dataset returns four issues, 3 of which are active in the lists and one which is postponed.

For active issues and risks to appear on the reminders web part it is key that the Status value is (1) Active, notice that the 4th issue has a value of Active without the (1).

If I change the issue list settings for the PM Testing Assn project site so that the Status choice value includes (1) Active then edit the item, the reminders web part will correctly show 3 active issues.

The current Status choice values on the PM Testing Assn project site are shown below:


Once this choice list has been updated to include the correct Active value and the issues edited the SQL dataset will contain the correct values and therefore so will the reminders web part. The choice values updated to the correct values shown below:


Now after editing the issue item the correct active Status value will appear:


The SQL stored procedures return the correct values after the Reporting (Project Sync) job has successfully completed in the Project Server queue:


Refreshing the PWA homepage now also shows the correct count on active issues and risks:


So the keys things to remember to make sure the reminders web part shows the correct counts for the active issues and risks are:

  • ensure the Issues and Risks list default status values are not updated
  • ensure the Reporting (Project Sync) jobs completed successfully

When updating the project site template it might be worth testing all default functionality, a useful project site smoke test can be found here:


Check all #SharePoint lists and libraries for specified column type in a site collection #SP2010 #PS2010 #ProjectServer #PowerShell

July 6, 2012 at 12:04 pm | Posted in Administration, Configuration, Information, PowerShell | 1 Comment
Tags: , , ,

Recently we were carrying out an internal review of our SharePoint 2010 intranet system at CPS and needed to see where the BCS applications were used in the site collection on all sites. Rather than clicking on the list or library settings for each list / library to check for the External Data type on the column settings, I wrote a simple PowerShell script to check this.

The script is available from the Microsoft Script Center below:


To run the script, update the $siteCollection variable with the correct site collection URL and specify the column type, in our case this was External Data.

Once executed, the script will output the data to a text file called sitelists.txt. An example output can be seen below:


Testing a new #ProjectServer project site template #PS2010 #MSProject #EPM #SP2010 #SharePoint

July 4, 2012 at 12:58 pm | Posted in Administration, Configuration, Customisation, Functionality, Information | 7 Comments
Tags: , ,

If you are not aware already, deleting or modifying the default lists and fields in Project Server 2007 and Project Server 2010 can break some default functionality on Project Server. For example updating the Issue and Risk Status field choices, particular the “(1) Active” value will prevent the active Issues and Risks displaying in the Reminders web part on the PWA homepage. Other changes can cause the Reporting WSS sync job to fail in the Project Server queue which causes the WSS Project Sites data not to be current in the Reporting database and OLAP Cube. If you do have any of these issues I did write about a fix around a year ago now, this can be found here: https://pwmather.wordpress.com/2011/06/20/project-server-2010-project-site-default-fields/

Below is a useful set of tests that can be used to test a new Project Server 2010 project site to confirm the default functionality with Project Server still works:

· Create a test project with a few tasks and a project site

· Check you can create a new Issue, set the status to Active and assign to a Project Manager account that has access to the Project Site

· Return to PWA homepage using the Project Manager account and ensure you see 1 active issue assigned

· Click on the new Issue and make sure all links function correctly and you can see the Issue on the Project Site

· Check you can create a new Risk, set the status to Active and assign to a Project Manager account that has access to the Project Site

· Return to PWA homepage using the Project Manager account and ensure you see 1 active risk assigned

· Click on the new Risk and make sure all links function correctly and you can see the Risk on the Project Site

· Edit an Issue and link it to a Project task

· Return to PWA Project Centre, does the Issue indicator appear

· View the Project Details page, does the Issue indicator appear next to the task

· Edit a Risk and link it to a Project task

· Return to PWA Project Centre, does the Risk indicator appear

· View the Project Details page, does the Risk indicator appear next to the task

· Can you upload a document

· Edit a Project Document and link it to a Project task

· Return to PWA Project Centre, does the Document indicator appear

· View the Project Details page, does the Document indicator appear next to the task

· Publish the Project Plan

· Check Reporting job is successful in the Project Server queue

· Build the Project Server OLAP Cube, create a report based on the OlapProjectSharePoint template and confirm the issues and risks appear

· Open the IssuesandRisks sample report and confirm the issues and risks appear

· Check you can delete workspace for the test project

· Check can create a new workspace for the test Project

· Publish the Project Plan

· Check the workspace synchronisation is successful – no errors in the queue

To test other functions in Project Server 2010, take a look at this TechNet link:


#ProjectServer and #SharePoint 2010 June 2012 Cumulative Update #PS2010 #SP2010 #MSProject

July 1, 2012 at 10:37 am | Posted in Administration, CU, Information | 6 Comments
Tags: , , , , ,

The Office 2010 June 2012 Cumulative Updates are now available, please see the links below:

Project Server 2010 Server Roll up package June 2012 CU (Recommended):

Project Server 2010 June 2012 CU (Included in the Server Roll up package):

Project 2010 June 2012 CU:

For more details please see: http://blogs.technet.com/b/projectadministration/archive/2012/06/29/microsoft-project-server-and-sharepoint-server-2007-and-2010-june-2012-cu-announcement.aspx

As always, test these updates on a test environment before deploying to production

Blog at WordPress.com.
Entries and comments feeds.