Project Server PFE Team Blog https://docs.microsoft.com/archive/blogs/projectserverpfeteamblog/feed.xml This is the Project Server PFE Team Blog. Premier Field Engineers who support Project Server around the globe contribute to this blog. Tue, 16 Apr 2019 06:15:12 GMT en-US hourly 1 You are about to reach the limit of 2000 Project Sites. Now what? https://docs.microsoft.com/archive/blogs/projectserverpfeteamblog/you-are-about-to-reach-the-limit-of-2000-project-sites-now-what Sat, 05 Jan 2019 01:06:16 GMT https://blogs.technet.microsoft.com/projectserverpfeteamblog/?p=1245 article). This situation requires multi-solution approach. It requires;
  • Deleting the unwanted sites.
  • Disabling the Auto Creation of the sites (optional),
  • Creation of the new Site Collection, modification of the EPT, so that all the new Sites will be created under a new Site Collection,
  • Creation of new the Project Site Template, in case you have any custom templates,
  • And permission management.
Above steps are provided in detail here, and have worked well with my customers.
  1. Delete Project Sites which are not required anymore.
  2. Disable Project Site Creation at the EPT level. This setting will turn off the new site creation at the EPT level.In case the new sites are required to be created, you can setup a manual approval process to create Project Sites when they are really required to be created.
2. Create a new Site Collection using Project Site template. You can do it by following the steps mentioned in this reference article. While creating a new Site Collection, ensure that you select a Project Site template . 3. Once the new Site Collection is created, copy the URL of a new Site Collection. 4. Open Enterprise Project Type(s) and paste the newly created Site Collection URL in "Site Creation Location" section of the EPT. It should look something like this;   5. Once the new Site Collection URL has been updated in the Enterprise Project Type, all the new Project Sites will be created under a new Site Collection. It will in-turn help in not creating any new sites under the existing Site Collection and it will keep an environment in a recommended state as far as the number of Project Sites limitations are concerned. 6. You can also move some of the existing Project Sites to a new Site Collection. You might need to create a script or use the tool to move the sites to a new Site Collection. Please note that above steps definitely help in creating new sites under a new Site Collection and prevent creation of the sites in an existing Site Collection, however you will be required to configure all the Project Site Templates once again (in case you had configured them in your previous Site Collection) and required to configure them in such a way so that they can work in a newly created Site Collection. You might also need to manage the permissions at a Project Site level manually, and above steps can also be followed for more than one Enterprise Project Types if required. I hope above steps help to handle the situation when you are about reach the limit of 2000 Project Sites.]]> Resource Center in Project Online doesn't show any data related to resource availability https://docs.microsoft.com/archive/blogs/projectserverpfeteamblog/resource-center-in-project-online-doesnt-show-any-data-related-to-resource-availability Mon, 12 Nov 2018 04:37:06 GMT https://blogs.technet.microsoft.com/projectserverpfeteamblog/?p=1175 Scenario
  • In the screen capture below, please note that the Test Resource has a lot of assignments made against it.
   
  • While looking at the Resource Center Page, a resource in question does not show any assignments.
   
  • Similar thing can also be noticed in the Remaining Availability/Capacity Planning page.
    Cause This behavior is noticed when the Timephased Data option is selected as 'Never' under Server Settings (PWA Settings) -> Enterprise Data -> Reporting section.       Resolution Under Server Settings (PWA Settings) -> Enterprise Data -> Reporting, change this option to 'Daily', 'Weekly', 'Monthly' or 'By fiscal period' and click on Save.     Once it is Saved, ensure that you Publish a Project in question (or all the Projects) and check the behavior. To know more about this feature you can go through a very informative blog of Brian Smith here. I hope this post helps to see the Resource Availability data in Resource Center/Capacity Planning page of Project Online. ]]> Make Advanced Search option available in SharePoint Online or in Project Online Site. https://docs.microsoft.com/archive/blogs/projectserverpfeteamblog/advanced-search-doesnt-appear-in-sharepoint-online-or-in-project-online Wed, 11 Oct 2017 04:07:41 GMT https://blogs.technet.microsoft.com/projectserverpfeteamblog/?p=1025 Advanced Search option in SharePoint Online as well as in Project Online site. Advanced Search Option isn't available in a default view. There are a few steps which need to be followed to make Advanced Search available on the desired page. This is how the default Search Option looks like.   The output of the Search page returns like this, after searching for a text.     As you can see, there is no option of Advanced Search available on this page     Steps to get the Advanced Search page available on any SharePoint Online or Project Online page Find a default Search URL of the tenant. There are two ways to find it.
  • Find the Tenant Admin Page and Search for the URL
Click on Admin Centers -> SharePoint -> Find the URL which ends with Search. See below example for more information  
  • Modify the Suffix of your URL.
E.g your tenant URL start with https://yourtenant.sharepoint.com/  You can look for the default Search URL by adding suffix to it. For e.g. https://yourtenant.sharepoint.com/Search

     1. Once you have identified your tenant Search URL, access the URL. It should look like the screenshot below.

      2. Try searching something in the Search URL and get an Advanced Search option

     3. Click on Advanced Search. It should  look something like this https://yourtenant.sharepoint.com/search/Pages/advanced.aspx.

     4. Copy the Advanced Search URL.

     5. Open a page where you want to display the Advanced Search option. In my case, I am going to display it on the home page of Project Online. It can be displayed on any SharePoint Online page as well.

     6. Click on the Right Top Gear and Click on Edit Page.

   7. Click on Add a Web Part.

   8. Select Search and Search Box and Click on Add.

   9. Edit the Search Web Part.

   10. Select Use This Site's Search Settings.

   11. Expand Settings, and Check Show Advanced link.

  12. Paste the URL which was copied in the Step No. 3 and replace Advance.aspx under Advanced Search Page URL. For       e.g. https://yourtenant.sharepoint.com/search/Pages/advanced.aspx

  13. Click on OK and then click on Stop Editing.

Now the Advanced Search link will appear along with the Search Box on the page you have used to follow the above steps.

I hope this post helps to bring Advanced Search feature/option on your SharePoint Online or on your Project Online page.

]]> Project Online/Server Custom field with People Picker https://docs.microsoft.com/archive/blogs/projectserverpfeteamblog/project-onlineserver-custom-field-with-people-picker Fri, 04 Aug 2017 20:16:45 GMT https://blogs.technet.microsoft.com/projectserverpfeteamblog/?p=1015 Requirement One of my customers recently came up with a requirement, where my customer wanted to get the People Picker Option while working with the Project Entity custom field using Project Online. Based on my experience, it required a great amount of effort in order to customize the custom field to achieve this requirement. In addition, my customers have always configured it in Project Server on-premises product and not in Project Online application. After doing a lot of research to achieve this requirement to configure People Picker for the Project Entity Custom Field, I learned that it can be done fairly easily using Project Details Pages and using a small Java Script. Thanks to Laksh for sharing this information. Steps to achieve the requirement Below TechNet Gallery has the steps by step information, which is prepared and shared by James. https://gallery.technet.microsoft.com/projectserver/Use-SharePoint-people-cc8289de I hope this information helps you configuring People Picker in Project Online/Server easily.]]> Project Server 2016 - Save engagements did not succeed https://docs.microsoft.com/archive/blogs/projectserverpfeteamblog/project-server-2016-save-engagements-did-not-succeed Thu, 04 May 2017 13:27:01 GMT https://blogs.technet.microsoft.com/projectserverpfeteamblog/?p=975 Issue - Project Managers get below error, while saving Project Plan in Project Professional 2016. It affects users who are using Project Professional with Project Server 2016. Project Publish process should complete just fine. Please note that this issue is noticed after upgrading Project Server to Project Server 2016. Errors -  Save Engagements did not succeed. Please make sure you are online and try again.  first-error or An unexpected error occurred during command execution.  Try the following:
  • Verify that all argument names and values are correct and are of the correct type. 
  • You may have run out of memory. To free up available memory, close programs, projects, or windows that you aren't using.
second-error Potential cause - Project Server 2013 doesn't support Engagement feature as it was introduced in Project Server 2016. Resolution - Modify global permission in existing groups (such as Project Managers) and allow 'View Resource Plan" permission. Or create a new group allow "View Resource Plan" permission and add all the affected users into the newly created group. resoltuon-permissions  ]]> Invalid version of project database: 4.0.0.0. The supported version is '15.0.347.0' or higher. https://docs.microsoft.com/archive/blogs/projectserverpfeteamblog/invalid-version-of-project-database-4-0-0-0-the-supported-version-is-15-0-347-0-or-higher Fri, 14 Apr 2017 15:59:01 GMT https://blogs.technet.microsoft.com/projectserverpfeteamblog/?p=965 Issue While upgrading Project Server database from Project Server 2013 to Project Server 2016, below error message is noticed.   Migrate-SPProjectDatabase : Invalid version of project database: 4.0.0.0. The supported version is '15.0.347.0' or higher.     Use Project Server 15 to upgrade the database and then retry the migration command At line:1 char:1 + Migrate-SPProjectDatabase + ~~~~~~~~~~~~~~~~~~~~~~~~~     + CategoryInfo          : InvalidArgument: (Microsoft.Offic...ProjectDatab    ase:PSCmdletMigrateSPProjectDatabase) [Migrate-SPProjectDatabase], SPExcep   tion     + FullyQualifiedErrorId : Microsoft.Office.Project.Server.Cmdlet.PSCmdletM    igrateSPProjectDatabase   Potential Cause Project Server database was attempted to upgrade as the content database first. In other words, the content database upgrade command was used, instead of the Project Server database upgrade command.   Resolution Restore the Project Server database and attempt the migration again.]]> Periodic Tasks for Project Managers https://docs.microsoft.com/archive/blogs/projectserverpfeteamblog/periodic-tasks-for-project-managers Tue, 22 Mar 2016 09:49:11 GMT https://blogs.technet.microsoft.com/projectserverpfeteamblog/2016/03/22/periodic-tasks-for-project-managers/

Periodic Tasks for Project Managers 

? 

Daily 

  1. Check the queue for Failed and Blocking jobs related to your plan in Server Settings > My Queued Jobs. 

  1. Review the errors related to failed and blocking jobs to troubleshoot. 

  1. Cancel Failed and Blocking jobs and/or re-submit them if required. 

  1. Check email notifications for the resources for undue or upcoming tasks (if the notification feature is turned-on).  

Weekly 

  1. Review task updates for accuracy in Approvals > Task Update. 

  1. Review the impact of the task updates on your plan using Preview Update. 

  1. https://technet.microsoft.com/en-us/library/hh767481(v=office.14).aspx  

  1. Accept or reject task updates and publish your plan.  

  1. https://technet.microsoft.com/en-us/library/hh767481(v=office.14).aspx  

  1. Update resource RBS values for new users.? Newly synched users from Active Directory won’t have an RBS. Note: This may be the job of the PMO. 

  1. https://technet.microsoft.com/en-us/library/cc197354.aspx#section5  

Monthly 

  1. Ensure that new team members get timesheet training. Your PMO may handle this task. 

  1. Best practices for submitting and reporting on actual work https://technet.microsoft.com/en-us/library/hh694531(v=office.14).aspx  

  1. Close completed tasks on your plan to updates.  

  1. Project Online and Project Server 2013 https://blogs.technet.microsoft.com/brookswhite/2015/11/13/where-did-close-tasks-to-updates-go-in-project-server-2013project-online/ 

  1. Project Server 2010 https://technet.microsoft.com/en-us/library/gg597618(v=office.14).aspx  

  1. Review plans to ensure all tasks you know are complete show as complete. If they are not 100%, drill into assignments and figure out the resource who has remaining work to clear. 

  1. Close out all the project plans which are already completed and notify Project Server Administrator to archive them. Retention policies may require the project be maintained in the Project Server but hidden from view to regular users.  

 

You can see Periodic Tasks for Project Server Administrators here: https://blogs.technet.microsoft.com/brookswhite/2015/01/30/periodic-tasks-for-project-server-administrators/

Originally posted at https://blogs.technet.com/b/brookswhite.]]> Project Server 2010, 2013 and 2016 March 2016 PU Announcement https://docs.microsoft.com/archive/blogs/projectserverpfeteamblog/project-server-2010-2013-and-2016-march-2016-pu-announcement Mon, 21 Mar 2016 07:57:39 GMT https://blogs.technet.microsoft.com/projectserverpfeteamblog/2016/03/21/project-server-2010-2013-and-2016-march-2016-pu-announcement/ Brian Smith has posted the March 2016 PU announcement for Project Server on the Project Support blog!

Project Server 2010, 2013 and 2016 March 2016 PU Announcement

https://blogs.technet.microsoft.com/projectsupport/2016/03/09/project-server-2010-2013-and-2016-march-2016-pu-announcement/

Originally posted at https://blogs.technet.com/b/brookswhite.]]> Project Server 2016 upgrade error - "The project schema has not been provisioned in Content database" https://docs.microsoft.com/archive/blogs/projectserverpfeteamblog/project-server-2016-upgrade-error-the-project-schema-has-not-been-provisioned-in-content-database Tue, 15 Mar 2016 12:07:16 GMT https://blogs.technet.microsoft.com/projectserverpfeteamblog/2016/03/15/project-server-2016-upgrade-error-the-project-schema-has-not-been-provisioned-in-content-database/ Upgrade to Project Server 2016 environment fails with below error message.

 

Migrate-SPProjectDatabase : The project schema has not been provisioned in

Content database '2013_ProjectWebApp'.

    Use the Upgrade-SPContentDatabase command to upgrade the Content database

and then retry the migration command

At line:1 char:1

+ Migrate-SPProjectDatabase

+ ~~~~~~~~~~~~~~~~~~~~~~~~~

    + CategoryInfo          : InvalidArgument: (Microsoft.Offic...ProjectDatab

   ase:PSCmdletMigrateSPProjectDatabase) [Migrate-SPProjectDatabase], SPExcep

  tion

    + FullyQualifiedErrorId : Microsoft.Office.Project.Server.Cmdlet.PSCmdletM

   igrateSPProjectDatabase

 This is what you see in the PowerShell Cmdlet

Potential causes

=============

 1. The farm was created using PowerShell (and not using GUI), or

 2. The first release of Project/SharePoint Server 2016 binaries are installed.

 

Resolution

========= 

This is what you will see once the issue is fixed 

]]> Tell the Product Group what you want to see! https://docs.microsoft.com/archive/blogs/projectserverpfeteamblog/tell-the-product-group-what-you-want-to-see Thu, 04 Feb 2016 07:35:50 GMT https://blogs.technet.microsoft.com/projectserverpfeteamblog/2016/02/04/tell-the-product-group-what-you-want-to-see/ The Product Group wants to know how Microsoft can improve SharePoint Server, SharePoint Online, Project Desktop, Project Server, and Project Online. You can lend your voice to the SharePoint and Project Server product group’s choices for functionality!

 

Here are the links to provide feedback at UserVoice.com:

For Project: https://microsoftproject.uservoice.com/

For SharePoint: https://sharepoint.uservoice.com/

 

 

Blogs for SharePoint:

https://blogs.office.com/sharepoint/

https://blogs.msdn.com/b/spblog/

 

Blogs for Project:

https://blogs.office.com/project/

https://blogs.technet.microsoft.com/projectsupport/.

Originally posted at https://blogs.technet.com/b/brookswhite.]]>