Project Server splits project data across two areas: Project Server holds the plan data (Tasks, Milestones) & resourcing data (Resources, Timesheets), and then SharePoint (WSS or MOSS) holds the Risks, Issues, Documents and other custom data.
When a project is initially published in Project Server, PWA (Project Web Access) will attempt to provision a new SharePoint subweb. This means Project Server creates a Project Workspace in SharePoint.
The problem I’m witnessing? That even manually creating the workspace results in a single dialog box in which the only text is “Error”.
Continue reading ‘Error when provisioning a Project Workspace’
Apparently this isn’t as simple as it should be.
The environment:
Project Server 2007 with SharePoint v3. Each Project has a SharePoint subweb as a “Project Workspace”. The Project workspaces are provisioned automatically by Project Server. Project Server applies a template to the new workspaces. The template can be customised but must be derived from the one Project Server originally shipped.
The scenario:
Put workflow into the template so that each provisioned Project workspace starts with a number of pre-defined processes
Shouldn’t be hard right? Well, it was.
Continue reading ‘Workflow in SharePoint Project Server templates’
Contrary to the current MSDN documentation here:
http://msdn2.microsoft.com/en-us/library/websvcproject.project.readprojectstatus.aspx
The ReadProjectStatus web method requires two sets of permission to return Projects for a given user:
- ViewProjectCenter
- OpenProject
Recent Comments