#ProjectServer / #ProjectOnline Publish All projects #JavaScript #jQuery #SharePointOnline #Office365 #PS2013

April 17, 2014 Leave a comment
Paul Mather
I am a Project Server and SharePoint consultant but my main focus currently is around Project Server.
I have been working with Project Server for nearly five years since 2007 for a Microsoft Gold Certified Partner in the UK, I have also been awared with the Microsoft Community Contributor Award 2011.
I am also a certified Prince2 Practitioner.

This article has been cross posted from pwmather.wordpress.com (original article)

This post covers a new script I have written that publishes all projects the user has access to. I do have a PowerShell script that does this perfectly but only works for Project Server on-premise. This is detailed here:

http://bit.ly/RdsTp3

http://bit.ly/RQbZdq

The new script is JavaScript so will work for Project Server 2013 and Project Online. The publish all JavaScript file can be downloaded here:

http://bit.ly/1j8K4mL

To get the script to work you will need to download the following jQuery library:

jquery-1.8.3.min.js – jQuery download

A later version of this library may work but this was the one I used / tested with.

Upload this library to your PWA site collection then update the script file with the correct location. I uploaded this file to the site assets library as you can see in the code below:

image

Also note the references to the default SharePoint / ProjectServer JavaScript libraries.

Once the script is uploaded, save this to the PWA site collection. I uploaded the JavaScript file to the style library:

image

Now create a new page, I called mine PublishAll and saved this in the Site Collection Documents Library library. The name of the page and the location of the page can be changed, just make sure the users have access to it. Then add a content editor web part on the page and reference the publishallprojects.js file. After clicking save you should see the following load:

image

Clicking the Publish Projects button will fire of a publish job for all the projects you have access to. You will see the following pop disappear once all the projects have been sent to the queue for publishing:

image

There are several publish all type apps available in the app store but this method does not require you to install and configure the app store or download and install an app.

Categories: Paul Mather, Work Tags:

SharePoint 2013, Nintex 2013 Workflow

April 14, 2014 Leave a comment

Recently I have been working with the various Nintex products to create a few demos and prototypes.

Recently while working with a new VM recently I noticed that some of the actions were not performing correctly and the message templates were blank from site to farm level.

None of the normal things seemed to help (IIS Reset, Reboot, Deactivate / Reactivate, Reinstall), until I came across this post on the Nintex forum.

It turned out my VM had the currently withdrawn SharePoint 20103 SP1 applied. As soon I installed the fix normal Nintex service was resumed.

Categories: SharePoint 2013

Want to see Risks and Issues on a #ProjectOnline / #ProjectServer project detail page? #PS2013 #SharePointOnline #SP2013 #Office365 #JavaScript #jQuery

April 11, 2014 Leave a comment
Paul Mather
I am a Project Server and SharePoint consultant but my main focus currently is around Project Server.
I have been working with Project Server for nearly five years since 2007 for a Microsoft Gold Certified Partner in the UK, I have also been awared with the Microsoft Community Contributor Award 2011.
I am also a certified Prince2 Practitioner.

This article has been cross posted from pwmather.wordpress.com (original article)

Over the last few weeks when I have had a spare 5 minutes I have been playing with JavaScript /jQuery. It is something I have wanted to learn for a while and finally thought I would give it ago and see what I could do with SharePoint / Project data. After lots of reading and researching (lots of examples out there!) I came across some very useful jQuery libraries. This post covers the usage of a script I put together to display risks and issues on a project detail page from the associated project site. The full script can be downloaded from the Microsoft script gallery below:

http://bit.ly/1kARHI2

The script only uses default Project Server Issues and Risks columns so it will work as is but it can easily be updated to include other columns.

To get the script to work you will need to download the following jQuery libraries:

jquery-1.8.3.min.js – jQuery download

knockout-3.1.0.js – knockout jQuery download

ko.sp-1.0.min.Ex.js – knockout JS binder library – Extended Version (Includes Moment Js and numeral Js)

Later versions of these libraries may work but these were the ones I used / tested with.

Upload these to your PWA site collection then update the script file with the correct location. I uploaded these files to the site assets library as you can see in the code below:

image

Also note the references to the default SharePoint / ProjectServer JavaScript libraries.

Once the script is uploaded, save this to the PWA site collection. I uploaded the JavaScript file to the style library:

image

Now create a new PDP page, I called mine Risks and Issues. Then add a content editor web part on the page and reference the riskandissueonPDP.js file. After clicking save you should see the following message above the grids:

image

This is because the current page is not an actual projects project details page. Add the new PDP to the correct EPT/s. Now navigate to the Project Center and click on a project that contains risks and / or issues on the associated project site. Click the new Risks and Issues PDP and you will see the the risks and issues displayed:

image

The script is just an example I put together and should really be improved for a production environment  – error handling, update the displayed columns, visualise processing etc. Watch this space for more JavaScript examples as I dabble further! Smile

Categories: Paul Mather, Work Tags:

#Project, #ProjectServer and #SharePoint Server 2013/2010 April 2014 CU available #ps2013 #sp2013

This is to announce that April 2014 CU of Project, Project Server and SharePoint Server 2013/2010 is out now. The important point to note that April 2014 CU of Project Server 2013 includes the fixes of SP1 as well. Since SP1 is deactivated until further announcement from Microsoft, Apr 2014 CU can do the job for now.

Also Project Server 2013 CU is not a roll-up package, which means it doesn’t includes SharePoint server fixes.

Test the CU in your test environment first prior to apply to production.

Project Server 2013 individual Apr 2014 CU: http://bit.ly/1g8zmuj
Project 2013 Apr 2014 CU: http://bit.ly/1g8zmuk
SharePoint Server 2013 Apr 2014 CU: http://bit.ly/1hij6eG

Project Server 2010 individual Apr 2014 CU:http://bit.ly/1g8zmuo
Project 2010 Apr 2014 CU: http://bit.ly/1g8zkTe

via All about Enterprise Project Management (EPM) http://bit.ly/1hij6eH

Khurram Jamshed
The author of the blog has an extensive experience of working as an EPM Consultant. Currently he is located in Dubai, UAE and working for Microsoft partner organization as Project Server specialist. He has a thorough experience of providing Project Management technical/functional consultancy to all sort of organizations. He is a certified PMP, a Project Server MCITP, and also received a MS community contributor award 2011.

This article has been cross posted from khurramjamshed.blogspot.com/ (original article)

#ProjectServer and #SharePoint 2010 / 2013 April 2014 Cumulative Update #PS2010 #SP2010 #PS2013 #SP2013 #MSProject

Paul Mather
I am a Project Server and SharePoint consultant but my main focus currently is around Project Server.
I have been working with Project Server for nearly five years since 2007 for a Microsoft Gold Certified Partner in the UK, I have also been awared with the Microsoft Community Contributor Award 2011.
I am also a certified Prince2 Practitioner.

This article has been cross posted from pwmather.wordpress.com (original article)

The Office 2013 April 2014 Cumulative Updates are now available, please see the links below:

http://bit.ly/1lR8IgH

***There is no Project Server 2013 Server Roll up package for April 2014 CU***
Project Server 2013 April 2014 CU:
http://bit.ly/1g8zmuj
Project 2013 April 2014 CU:
http://bit.ly/1g8zmuk

Also worth noting, if you haven’t done so already, install the March 2013 Public update: http://bit.ly/1lR8IgK if installing the April 2014 CU.

The Office 2010 April 2014 Cumulative Updates are now available, please see the links below:

http://bit.ly/1g8zmul

***There is no Project Server 2010 Server Roll up package for April 2014 CU***
Project Server 2010 April 2014 CU:    
http://bit.ly/1g8zmuo & http://bit.ly/1lR8IgP
Project 2010 April 2014 CU:
http://bit.ly/1g8zkTe
Remember SP1 or SP2 is a pre-requisite for the Office 2010 April 2014 CUs.

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

For more details see:

http://bit.ly/1lR8JBq

Categories: Paul Mather, Work Tags:

#SharePoint Product Configuration Wizard Error: Unable to create a Service Connection Point in AD #SP2010 #PS2010

While updating one of my Project Server 2010 environment with language pack, the configuration wizard has thrown following error in the end at step 9:

An exception of type Microsoft.SharePoint.PostSetupConfiguration.PostSetupConfig
urationTaskException was thrown.  Additional exception information: The upgrade

command is invalid or a failure has been encountered.

Failed to upgrade SharePoint Products.
ULS logs digging helped me found a substantial clue and reminded me that i did come across to similar issue long time back as well. The issue is related to configuration to track any SharePoint production installation to farm of your organization, and tracking requires container in AD with appropriate user permissions to allow installation. If the account does not have permission to write to this container, the following warning will appear in the log file for the SharePoint Products Configuration Wizard and Wizard will fail at the last step:


Failed to add the service connection point for this farm
Unable to create a Service Connection Point in the current Active Directory domain. Verify that the SharePoint container exists in the current domain and that you have rights to write to it.”
To resolve this follow these steps:
  1. On the domain controller, click Start, point to Administrative Tools, and then click ADSI Edit, or use a remote administration tool to connect to ADSI Edit from another computer.
  2. On the Action menu, click Connect to, and connect to the domain that you want to use.
  3. In the console tree, expand the connection, expand the domain name, and then click CN=System.
  4. In the details pane, right-click in the white area, click New, and then click Object.
  5. In the Create Object dialog box, in the Select a class box, click container and then click Next.
  6. In the Value box, type Microsoft SharePoint Products as the container name, and then click Next.
  7. Click Finish.
    The container is created.
  8. Right click the container (CN=Microsoft SharePoint Products), and then click Properties.
  9. On the Security tab, click Add.
  10. In the Select Users, Computers, Service Accounts, or Groups box, add the users that you want to write to this container, and then click OK.
    Note that if a user who cannot write to this container installs SharePoint Server 2010, no new entry will be created. Consider giving all Authenticated Users the permission so that you can track all the objects.
  11. In the Group or user names box, select the names that you previously added, and then under the Permissions box, clickAdvanced.
  12. In the Permission entries box, select the names that you previously added, and then click Edit.
  13. In the Permission Entry for Microsoft SharePoint Products dialog box, in the Permissions box, select the Allow check box forCreate serviceConnectionPoint objects, and then click OK.
Now re-run the wizard and hopefully this time it will go through successfully.
The whole process, with powershell comands as well, can be found here: http://bit.ly/1eedeUt
Happy updating SharePoint farm :)

via All about Enterprise Project Management (EPM) http://bit.ly/1eeddjp

Khurram Jamshed
The author of the blog has an extensive experience of working as an EPM Consultant. Currently he is located in Dubai, UAE and working for Microsoft partner organization as Project Server specialist. He has a thorough experience of providing Project Management technical/functional consultancy to all sort of organizations. He is a certified PMP, a Project Server MCITP, and also received a MS community contributor award 2011.

This article has been cross posted from khurramjamshed.blogspot.com/ (original article)

#ProjectServer and #SharePoint 2013 #SP1 download deactviated

This is to spread the word that due to recently discovered issue, Microsoft Project Server and SharePoint Server 2013 SP1 have been temporarily unavailable for downloading.

“We have recently uncovered an issue with this Service Pack 1 package that may prevent customers who have Service Pack 1 from deploying future public or cumulative updates. As a precautionary measure, we have deactivated the download page until a new package is published.”

Download pages for Project Server and SharePoint are also updated with above reason.

For more details, check Brian Smith post: http://bit.ly/1fE43L8



via All about Enterprise Project Management (EPM) http://bit.ly/1q2IRSo

Khurram Jamshed
The author of the blog has an extensive experience of working as an EPM Consultant. Currently he is located in Dubai, UAE and working for Microsoft partner organization as Project Server specialist. He has a thorough experience of providing Project Management technical/functional consultancy to all sort of organizations. He is a certified PMP, a Project Server MCITP, and also received a MS community contributor award 2011.

This article has been cross posted from khurramjamshed.blogspot.com/ (original article)

Follow

Get every new post delivered to your Inbox.

Join 571 other followers

%d bloggers like this: