Pages

Thursday, 21 November 2013

Error 18003 and 26000 when publishing a Project to create associated SharePoint Workspace/Site

Recently a user encountered the following error when publishing a project. The project was created using a custom EPT with custom SharePoint Site Template.

-----------------------------

The errors returned from the queue are as follows:
Error ID: 18003
Error ID: 26000

Detailed error below - send it to the administrator for more detailed troubleshooting.

<?xml version="1.0" encoding="utf-16"?>
<errinfo>
<general>
<class name="Web is not a child of the default site collection">
<error id="18003" name="WSSWebIsNotUnderDefaultCollection"

----------------------------------

Steps taken to Test (replicate) Issue;

1) Test the project creation using default and custom EPT and publish from PWA.

2) Check/Validate Message Queues i.e. no issue with the Project Server Queue service and that the jobs are they draining/being processed as expected.

3) Test the custom EPT with default Microsoft Site Template.

4) Test the creation of SharePoint site manually via PWA site collection > Site Settings > Sites and Workspaces using both the default Project Site Template and Custom Site Template.

What I Encountered – My Findings

The site creation failed with project creation and manual process. Issue with both default and custom templates. Creating the site manually gave the following error message. See fig below. It was related to a missing Site Collection  feature.

image

Next, use Powershell to get the name of the feature it is referencing:

Get-SPFeature -Identity <GUID>

image

This feature should be enabled or disabled on both the site collections.

In my case it was OpenInClient. This was found to deactivated. The issue was resolved by activating this feature at PWA Site Collection level.

List of all the Features and Associated Correlation ID

Refer to: <I will add to the following post>

Lessons learned

  1. Keep a note of all configuration changes and review impact i.e. feature enabled and disabled.
  2. If features are modified at PWA Site Collection level, reset your site template and associate with the appropriate EPTs. 

Hope this helps.

Wednesday, 20 November 2013

Overwriting Existing Enterprise Project Schedule/Plan with Externally Provided Plan

So you are using Microsoft Project Server and you have a need to regularly show updated external project schedule in your portfolio of Enterprise Projects. How can we do this whilst maintaining continued use of Project related artefacts such as documents, workflow, risks, issues etc?

image

You can do this by importing the external project schedule/plan and saving this with the SAME name as the existing Enterprise Project. Doing this retains the internal project GUID and, hence, maintains its links to Workflow, SharePoint Workspace and other artefacts.

Here are the general steps;

  1. Make a note of the EXACT name of the Enterprise Project Plan to be replaced. You can do this either from Project Centre or Project Pro > File Open dialog box.
  2. Using Project Professional, open the external project schedule/plan provided by your external contractor or consultant.
  3. Review and modify plan if necessary.
  4. File > Save As > Choose SAVE option in the ‘Save to Project Server’ dialog box.
  5. You will then be prompted the option to overwrite existing project in the server. Choose OK. See example figure below.

image

image

Hope this Helps. Enjoy project….ing!!

Thursday, 7 November 2013

Web UI to Build Windows PowerShell Commands for SharePoint

How cool is this!! Web UI for building any Windows PowerShell command you may need!

Simple and easy to use! And, no need to keep file away a big list of commands only to loose it and spend time searching for it. Give it a try….

http://www.microsoft.com/resources/TechNet/en-us/Office/media/WindowsPowerShell/WindowsPowerShellCommandBuilder.html 

image

Applies: SharePoint 2010/2013 and online services

Enjoy SharePoint…ing!!