Update for Microsoft Project Server 2013 (KB2768001)

Applies: Project Server 2013; SharePoint Server 2013

Due to a change in the package configuration introduced after SharePoint 2013 RTM the March Public update is a mandatory requirement in order to install subsequent SharePoint Updates.

EPM2010 – Error ‘Project Web App cannot connect to Project Sever’ (After Upgrade)

I recently came across this error message after upgrading from 2003 > 2007 > 2010.

Note: SP/PS2010 version is at June 2012 CU (v6123) patch level.

Resolution;

1. Ensure Project Server Service is running. Check within SP Central Admin.
2. Run the SharePoint configuration wizard to ensure all the DBs in the farm are upgraded correctly and are at the same version/patch level.
3. Re-boot the server(s)

Voila!! Your system will up and running.

Office 2013 Quick Start Guides

If you’re new to Office 2013, you can download free Quick Start Guides from Microsoft. These printable guides contain useful tips, shortcuts, and screenshots to help you find your way around.

http://office.microsoft.com/en-us/support/office-2013-quick-start-guides-HA103673669.aspx

EPM2010 – User with ‘Manage Cube Building Service’ Permission does not have access to ‘OLAP Database Management’ within Server Settings

If a user (say sub administrator) needs to be provided access to ‘OLAP Database Management’ within Server Settings, you will need to ensure that a dependent global permission ‘Manage Site Services’ is enabled as well.

Note: This dependency is not mentioned in the technical documentation.

Hope this helps.

Create SharePoint sites by using cross-site publishing in SharePoint Server 2013

Find resources for learning how to use cross-site publishing to make published content available to users in SharePoint Server 2013.

What is cross-site publishing: Cross-site publishing is a new publishing method that lets you create and maintain content in one or more authoring site collections and publish this content in one or more publishing site collections by using Search Web Parts. Cross-site publishing complements the already existing publishing method, author-in-place, where you use a single site collection to author content and make it available to readers of your site.

Why would I use this scenario: You should use cross-site publishing when you want to store and maintain content in one or more authoring site collections and display this content in one or more publishing site collections. Using cross-site publishing provides the following benefits:

• Separates content authoring from branding and rendering.
• Can be used across site collections, web applications, and also across farms.
• Allows for a mix of authored pages and list content.

Learn more>>>

EPM2010 – issue with Project Workspaces Links showing in Quick links

Ever come across this issue where all the SharePoint Project Workspaces start showing in the PWA quick links?

The resolution is simple.

1. Navigate to PWA > Server Settings > Quick Launch
2. un-check the option for ‘Show menu items from Microsoft SharePoint Foundation’. See fig below.
3. Save changes.
4. Close browser session and navigate to PWA.
5. Voila!! the links have one.

Hope this helps.

Migration Issue - Content Database is in compatibility range and upgrade is recommended?

Applies: SharePoint 2010, Project Server 2010

So you have migrated Project Server and Content DB from one environment to another. You attached the content DB (containing the PWA Site Collection) and then attach the four restored PS databases to the PWA instance. You might think that this would be sufficient and that all the restored databases would be successfully upgraded ok by the DB attach operations.

You might then subsequently run the SharePoint configuration wizard, to resolve any issues. Looking at the ‘Upgrade Status Check’ in Central Admin shows all is ok.

Not the case for one of the sites!! When the user started to use the system, strange things started to happen. Project Workspaces where not being created when publishing a project. Same issue occurred if you manually created a site using one of your site templates.

On close examination it turn out that the Project Server (PS) databases upgraded just fine but the content DBs did not. This was evident from ‘Database Review Status’ page within Central Admin.

To resolve this issue we needed to upgrade the affected content databases using the Power Shell command (Run as Administrator).

Upgrade-SPContentDatabase -Identity YourDatabaseName

Depending on your data/content/customisation, you may encounter some errors which you will need to review and resolve. The issues may relate to missing features that need to be enabled etc.

Finally, the ‘Database Review Status’ page within CA will indicate that all the databases are ok and do not require any update.

Hope this helps.