Tags: MSOffice, Project 2010, Project Server 2010, Project Server 2013, PS2010, PS2013
There have been several requests for publishing projects listed in a text file, this follows on from my post / publish all projects script found below:
****Update – this also works for Project Server 2013****
This script allows you to specify a list of projects in a text, then only those projects will be sent for publishing. For the purpose of this post I have a text file called projectstobepub.txt that contains a list of my test projects to be published:
The PowerShell script will need to be updated to reference the text file containing the list of projects that you wish to publish and also update the Project Server PWA URL. Comments have been added in the screen shot below to show what lines need to to be updated:
The script has my test PWA instance URL as highlighted below:
New-WebServiceProxy -uri “
The strikethrough text will need to be updated with the correct URL for your environment.
The script can be downloaded from the Script Center following the link below:
Once the script has been executed, the projects listed in the text file will be sent for publishing.
The script can either be executed on demand or set on a schedule using Windows Tasks Scheduler. Execute the script with an account that has access to the projects listed in the text file.
Tags: Office 2013, Office365, Project 2013, Project Server 2013, SharePoint 2013, SP2013
Quick post to highlight that Office 2013 has reached RTM! For more details see:
Tags: Project 2010, Project Server 2010, PS2010
I had a recent query from a colleague regarding the bulk update project site functionality in Project Server 2010. In this scenario my colleague had taken pre-configured databases from an environment at our offices and restored these 5 databases to the clients production environment. They then created some test projects / updated configuration etc. A test environment was also created for this client, part of this assignment was to rollover production to test, this included running the bulk update project sites functionality to update the test project sites. When looking at the list of previous site path web applications they could not see the clients web application in the list. All that was present were URLs from various test machines from the CPS environment, this can be seen below:
Bulk Update Project Sites:
Having seen this myself before but never had the opportunity to investigated it, I decided to look into the issue further.
Firstly I executed the MSP_Web_PWS_ReadProjectSiteBaseURLS stored procedure which I believe is called to populate the drop down menu above. This reads data from the MSP_Web_Applications table and MSP_Projects table.
Project Site Base URLs:
As you can see, the SQL output above matches the URLs displayed in the previous path drop down in the first screen shot. Notice 3 different URLs, these PWA databases have been linked to various PWA sites.
I then checked the WSTS Server UID for the project sites in the database, the test site server UID matched the http://vm662 server UID in the MSP_Web_Applications table:
I then checked the PWA site collection ID in the content database:
PWA site ID:
So this all linked up as expected but with the incorrect URL, http://vm662 and not the clients server URL. http://vm662 was the VM that was used at the CPS office to create this clients initial config.
I believe the reason for this issue with the URL is that when using the 5 database restore process the PWA site is not recreated. The provisioning process just links to the existing PWA site collection in the restored content database. The URL doesn’t get updated in the MSP_Web_Applications tables as the site ID remains the same so Project Server doesn’t think there is a new URL. If you take only the 4 PWA databases and create a new PWA site, the URL is displayed correctly in the scenario described above. This is just a display issue, all functionality works correctly once the bulk update project site process has run.
Hopefully that will help to explain why you might be experiencing the same issue as seen / described above.