Skip to main content

Order Enterprice Project Types (EPT) in Project Server 2013

In Project Server 2013 I experienced a strange problem today. When trying to order the Enterprise Project Types (EPT) by choosing a new value in the "Choose the type before which the current type should be positioned" dropdown nothing happened in Project Center. The EPT's were just visible in the order they were created in.



This is an error in the current version of Project Server 2013 (SP1, CU1). I could not find any workaround except to delete all the EPT's and create them in the correct order, this would just have been alot of work as we have more than 10 EPT's.
I have never experienced this problem in Project Server 2010, so it must have been introduced in the new version.

To solve the issue i found tracked down the stored procedure which loads the EPT's. By adding a order statement to this stored procedure the list got sorted correctly.
This solution is not supported by Microsoft and might be overwritten in a future hotfix/CU/SP of Project Server.

To install the solution log on to the SQL server where the ProjectWebApp database resides.
Start SQL Server Management Studio and create a new query.
Copy-paste the below script and execute it by pressing F5.
If the ProjectWebApp database has a different name then the standard name replace the "use ProjectWebApp" with the name of the database.

------------------------------------------------------------------------------------------------------------
USE [ProjectWebApp]
GO
/****** Object:  StoredProcedure [pub].[MSP_WORKFLOW_ReadEnterpriseProjectTypes]    Script Date: 5/30/2014 6:53:33 PM ******/
SET ANSI_NULLS ON
GO
SET QUOTED_IDENTIFIER ON
GO
ALTER PROCEDURE [pub].[MSP_WORKFLOW_ReadEnterpriseProjectTypes]
   @layoutsFolder nvarchar (15)
AS
BEGIN

   SELECT
      ept.ENTERPRISE_PROJECT_TYPE_UID,
      ept.ENTERPRISE_PROJECT_TYPE_NAME,
      ept.ENTERPRISE_PROJECT_TYPE_DESCRIPTION,
      ept.WORKFLOW_ASSOCIATION_UID,
      ept.WORKFLOW_ASSOCIATION_NAME,
      ept.IS_DEFAULT_PROJECT_TYPE,
      ept.ENTERPRISE_PROJECT_PLAN_TEMPLATE_UID,
      ept.ENTERPRISE_PROJECT_WORKSPACE_TEMPLATE_NAME,
      ept.ENTERPRISE_PROJECT_TYPE_ORDER,
      ept.IS_MANAGED_PROJECT,
      Replace(ept.ENTERPRISE_PROJECT_TYPE_IMAGE_URL, '$LAYOUTS', @layoutsFolder) as ENTERPRISE_PROJECT_TYPE_IMAGE_URL
   FROM
      pub.MSP_ENTERPRISE_PROJECT_TYPES ept
   ORDER BY ENTERPRISE_PROJECT_TYPE_ORDER

   SELECT
      eptd.ENTERPRISE_PROJECT_TYPE_UID,
      eptd.DEPARTMENT_UID
   FROM
      pub.MSP_ENTERPRISE_PROJECT_TYPE_DEPARTMENTS eptd

   SELECT
      eptp.ENTERPRISE_PROJECT_TYPE_UID,
      eptp.PDP_UID,
      eptp.PDP_ID,
      eptp.PDP_NAME,
      eptp.IS_CREATE_PDP,
      eptp.PDP_POSITION
   FROM
      pub.MSP_ENTERPRISE_PROJECT_TYPE_PDPS eptp

END

Comments

Popular posts from this blog

Install DLL in GAC - Windows 2008/2012 (Using Powershell, No GacUtil.exe)

If you want to install a DLL in the GAC and do not have the GACUtil.exe available. Powershell is properly the easiest way to procede.

Before Powershell you would properly just drag the DLL file into the C:\Windows\Assembly but this option is usually not available anymore.

Powershell - Add DLL to GAC So to install a DLL file in the GAC simply execute the below Powershell script. Remember you migth want to run the Powershell prompt as an administrator.
[System.Reflection.Assembly]::Load("System.EnterpriseServices, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a")$publish=New-ObjectSystem.EnterpriseServices.Internal.Publish$publish.GacInstall("c:\temp\MyDllFile.dll")iisreset
The first line adds a reference to the assembly we need to be able to mange the GAC.
The second and third lines retrives the GAC object and publish a new DLL file to it.
The last line resets the Internet Information Services. This is only needed if your DLL file is used in a websi…

Error occurred in deployment step 'Add Solution': Attempted to perform an unauthorized operation.

Received this error today when trying to create a SharePoint solution against a newly created site.


My first problem was the site was configured to use a port which was already used by another web site. Therefore the site could not start at all.

In my case both Default Web Site and SharePoint - 2000 was both using port 2000. Changing the port of Default Web Site and I was able to start the site.

However now I still received the same error message. When browsing the site I realized I did not have access to the site.

Giving access to my user and I was able to deploy the solution.

To sum up this post:
 - Check the site can start
 - Check the site can be browsed
 - Check your user have access to the site

SharePoint 2013 : Cannot connect to the targeted site.

On my Contoso environment I was trying to create a sandboxed solution. I have already configured my app domain and app management services. But when I tried to validate the site I got the following error message.
Error

Cannot connect to the targeted site. This error can occur if the specified site is not hosted on the local system. SharePoint solutions work only with locally-installed versions of SharePoint Foundation or SharePoint Server. Remote development is supported only for apps for SharePoint 2013.
If you search around the internet you will find many people suggesting to change your host file from 127.0.0.1 to the actual IP.

Solution However the solution, at least on a Contoso environment, is to type in the actual IP address in the host file.
(the IP 192.168.150.1 is the special IP for Contoso, I have 2 network adapters)
And do not forget to clear/flush the DNS cache. Now the solution can be created and validates.