View Khurram Jamshed's profile on linkedin

Tuesday, September 23, 2014

Project Server 2013 More Symptoms to Lost Resource Issue #PS2013 #LostResources #ProjectServer

In relation to a famous Lost Resources issue in Project Server 2013, i would like to share few more symptoms that can help you to identify this issue and apply the relative fix. Also the purpose is to feed search engines with more relevant data to help us lead to right direction.

By the way if anyone has already applied April 2014 CU, or planning to apply, then note that the fix for this issue is available as part of this April 2014 CU. But the fix will not solve any existing affected projects, and you need to follow Brian's advise mentioned in his blog (URL available below) to fix it.

Also more details and immediate fix, in case you are not planning to apply CU, is available here at Brian Smith's blog: Blog and Fix

Following are my findings related to the same issue:

Error on Project Page in PWA:

The general error statement on PWA page is not so helpful :)

Queue Error:

You will find project stuck in queue with percentage completed less than 100%, and error details would be:

  • Microsoft.Office.Project.Server.BusinessLayer.Queue.Message:
    • ProjectPublishFailure (23000). Details: id='23000' name='ProjectPublishFailure' uid='187759d1-663f-e411-8b70-0050569b2beb' projectuid='1201772f-00b0-e311-baa9-782bcba8cb82' messagetype='Microsoft.Office.Project.Server.BusinessLayer.QueueMsg.PublishProjectMessage' messageID='16' stage='' blocking='Block'

Using JOB ID mentioned, searching ULS Log will help you find below details:

Wednesday, July 30, 2014

#ProjectServer2013 RollUp Formula field Calculation Issue #PS2013 #ProjectServer

OK this post is actually about sharing an issue i came across lately, with the hope to get a fix through any of the coming CUs. And the hope is high, with the recent news of getting scheduled CU more frequently now :)

Out of lot of improvements we are enjoying with Project Server 2013, one of them is having a scheduling capabilities built within  PWA, and now PWA schedule webpart do all the formula processing as well without open/publish the same project from Ms Project. Unlike its predecessor, where any formula field requires MS Project push to get populated, and hence we had dependency to Ms Project even in the presence of web client and it was nightmare sometimes to explain to end user that why they need to buy more Ms Projects licenses to cope up with web based client limitations.

But recently i found that 'Task level number type roll up formula field, if copied to Project level number type formula field - doesnt work' :(

Now let me try to illustrate above through an example to make it more clearer:
And before i start, note that my server is patched with SP1 (re-released) + Jul 2014 CU.

1. Create a task level number type field, lets name it: %Weight
2. Create a task level number type formula field, with roll up Sum calculation for summary rows:

           Lets name it:  %WeightedProgress = ([% Complete] * [%Weight]) / 100

Here %complete is a default field, and %Weight is the one we have created at step-1 and will be manually updated by users.

3. Create a project level number type formula field:

          Lets Name it %ProjectProgress =  %WeightedProgress

As you can see, i am only copying data of task level formula field to project level field in order to show the data in project center.

Using PWA web scheduler:

1. I have entered %Weight for following 2 tasks, %Weighted Progress is 0 for each task because %Complete is 0, and hence at project level roll up value is also 0.

2. Update %Complete of first task with 50%, and %Weighted Progress will be calculated using formula and became 10 at task level and Project roll up level. Publish project.

 3. Open Project Center and observe % Weighted Progress, its showing 0 which was the task roll up at project level before we have made any changes.

4. Open project, and update %Complete of 2nd task with 50% and that will change %Weighted Progress value to 25. Publish project.

5. Open Project Center, and observe %Weighted Progress, its showing 10 which was the task roll up at project level before we have made change to 2nd task.

By now you may have learnt that its following a unique pattern while updating project level custom field. That its showing you previous value at project center level once you publish your project, although at Project level it updates at the same time.

So the first time when at Project level it was 0, in Project Center it was appearing blank.
Second time when at Project level it was 10, in Project Center it was appearing 0.
Third time when at Project level it was 25, in Project Center it was appearing 10.

Lets update our project plan one more time to assure our conclusion.

6. Open project, and update %Complete of Task A with 100% and that will change %Weighted Progress value to 35. Publish project.

7. Open Project Center, and observe %Weighted Progress, its showing 25 which was the task roll up at project level before we have made change to Task A.

So Fourth time when at Project level it was 35, in Project Center it was appearing 25.

I hope an issue is clear, now a workaround to this is to open/publish using Ms Project and everything will work like a charm, just like old times (Project Server 2010).

Though its not workable in my current scenario because not all the end user have Ms Project on their PCs.

With the hope that we get fix to this issue soon :), see ya next time.

Tuesday, April 29, 2014

#ProjectServer and #SharePoint 2013 SP1 re-released #ps2013 #sp2013 #office2013

There is lot of noise over the web related to Service Pack 1 of MS Office 2013 products, it was released with much of an applaud then deactivated due to issue and then re-released with lot of clarifications :) because in between deactivation and re-release of SP1, April 2014 CU for Project Server and SharePoint 2013 was also released.

So let me kill all this unnecessary noise with the final announcement that Service Pack 1 is now available to download, and all the clarifications in a nut shell is that Just apply this SP1 to your environment even if you have applied the previously released SP, and also feel free to apply this SP1 if you have April 2014 CU in place.  don't forget to  run the configuration wizard in the end :)

Also do not forget that unlike old times, this SP1 is not a roll up package, which mean you should install SharePoint 2013 SP1 + Project Server 2013 SP1 and then run the configuration wizard in the end.

Download links for updated SP1:

For details please see Brian Smith post, you can find details of almost all the queries in your mind on his blog post.

Also see Stefan Bogner's post for details related to Service Pack 1 release announcement and clarifications.

As always try any patches in your test environment prior to apply to production.

Happy patching :D

Thursday, April 10, 2014

#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:
Project 2013 Apr 2014 CU:
SharePoint Server 2013 Apr 2014 CU:

Project Server 2010 individual Apr 2014 CU:
Project 2010 Apr 2014 CU:

For more details please see:

Tuesday, April 8, 2014

#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:
Happy updating SharePoint farm :)

Friday, April 4, 2014

#ProjectServer and #SharePoint 2013 #SP1 download deactviated

Update: Service Pack 1 is re-released now, find details in this post

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:

Sunday, March 2, 2014

#SharePoint 2013 SP1 on the way ... #SP2013 #Office2013

Thought of spreading this thrilling announcement recently published that SP1 for 2013 product is on its way and expecting to be released early next year.

Service Pack 1 (SP1) for the 2013 set of products including Office, SharePoint and Exchange.  SP1 will deliver performance enhancements, feature updates and improve compatibility with Windows 8.1. 

This will be applicable to both on-premises and online versions, and more details are expecting soon. Also i am trying finding any news related to Project Server, if SP1 is applicable to Project Server 2013 as well, and will update through my blog once i find something.

Update: 2nd March 2014
Service Pack 1 is released, and you can find the details here in this Blog Post.

Say hello to #Project and #ProjectServer 2013 Service Pack 1 #sp2013 #ps2013 #office2013

A quick note to spread the news that Service Pack 1 for SharePoint/Project Server 2013 and other 2013 office products is out now.

For Project Server 2013, you can download from below:

For Project 2013 client, 32bit or 64bit, you can download from below:

For SharePoint 2013 server, you can download from below:

Few important things to note here, that unlike previous versions, this time SP1 is not a roll-up version. Which means that Project Server SP1 doesn't include SharePoint side of update, and vice verse.

Also another important point, is that as part of lost resource fix if you have updated the required sproc, then you may need to update them again as SP1 will re-write those sprocs during installation/setup.

Also read the Project Client versioning details in Brians's post (same link as above).

And in the end as always, try all the updates in test environment prior to apply to production.

Happy patching.

Thursday, January 9, 2014

#SharePoint 2010 setup error: Cannot connect to database master at #sp2010 #ps2010 #sp2013

Lately i got a chance to help my customer with standard deployment of Project Server 2010, and as they say "you learn new things each day", i also learnt about an issue which could be seen as basic activity but could lead you to pull your hairs while troubleshooting.

The issue occurred while running SharePoint 2010 setup, after installing pre-requisites, and following first few initial screens of setup wizard. Once reached to the point where you can enter SharePoint database server name, and credentials which can be used to talk to database server. You may see this error:

Cannot connect to database master at SQL Server at <server_name>. The database might not exist, or the current user does not have permission to connect to it.

Now if you have followed the recommended technet article to setup service accounts and permission, this error might be little misleading at the start. But root cause of the issue is completely valid.

There is already a very detailed and helpful blog is available for you to follow to start troubleshooting:

The possible causes of that error are as follows, first 2 are available in this blog, and the 3rd is the one i found and is the reason of this post:

  1. Permissions of the account used to configure has correct permission within SQL based on technet article.
  2. SQL Server in windows firewall required port, by default its 1433, is allowed to receive traffic from SharePoint application server.
  3. Verify that user through which you are running setup has got permissions to login to SQL Server. Yes, its very common in production or customer environments that you use different credentials to login to server than to the one you use to for deployment. Now either allow that user login permission to SQL Server by going to SQL Server and adding that user under logins within security of SQL Server. Or, run the setup as an administrator. In fact a good practice, is to always run the setup as an administrator to avoid such glitches.

Have a good day at work.

Wednesday, January 1, 2014

Year 2013 Passed, A new to come..

At the start of new year 2014, when i turn back and see 2013, it seems like it passed with the speed of light. But then this is how it meant to be, as they says "time flies" ....

For me the year starts with some big fireworks display, as Dubai has plan to create a world record of biggest fireworks at new year. It was fun to witness such historic moment, at the same time a little guilt that this enormous amount of money could be used to something more useful.

On a personal side of my Year 2013, i have had a great time with my family. My son turned 2, and i now can understand exactly the meaning of terrible 2 :) He is occupying most of my time, and i love every minute spending with him, no matter how much frustrated i could be due to worldly matters, he brings smile to my face and my source to stay motivated.

Year 2013 was good for me in terms of learning, as Project 2013, online and on-premises versions, was released in this year, and i have got lot of new dimensions of a product to learn. 

Working as PPM/EPM specialist is my passion, and i got a chance to work with different aspects of PPM as a tool to help lay down project management methodology for organization. For some reason, i have got more chance to work on reporting part of a product, and i explored in detail the database level of a product. And here i learnt that how rite use of Top-Down and Bottom-Up approaches of reporting can help organizations to see their desired results.

Despite of being occupied with work and personal stuff, i have tried to be on my mark when its about gaining knowledge or information about the world of SharePoint/Project Server. And for this i found twitter as my best friend :) i am following some great people from around the world to learn about fact paced technology evolution. Also with the passage of time technology is really coming to palms of our hands now, and i am relying more on my mobile device to stay connected instead of laptop. 

During year 2013, i have also tried to be active through my blog and forums as well. My blog stats reached near to 100,000, and i have got 150+ visitors each day from around the world. So thank you everyone for visiting my blog, and i try to share more during the coming year.

Lets stay connected, keep visiting my blog, leave your comments, and have a great new Year 2014.