Project Active Directory Connection Failed Project Server

Element ID / Rule name:

Project_Active_Directory_Connection_Failed

Summary:

This monitor indicates that Microsoft Project Web App could not access the Active Directory directory service.

When an administrator browses to the “Active Directory Enterprise Resource Pool Synchronization” or “Add or Edit Group” page by using Project Web App, Project Web App checks the current availability of the Active Directory forests. This check determines whether the Find Group button on those pages is enabled.

If the Find Group button is available, administrators can use it to choose which Active Directory group to use for synchronization.

Cause:

One or more of the following situations might be the cause:

The Microsoft Project Server application server is using a SharePoint Service Account (SA) account that does not have read access to Active Directory.

The Project Server application server may no longer be joined to an Active Directory domain.

The Project Server application server does not currently have network access to the domain.

Ports required for Project Server and Active Directory to communicate are not open between the Project Server application server and the Active Directory store. This can occur if a firewall is configured to block a port described in the following list:

389/UDP – LDAP: LDAP is the Lightweight Directory Access Protocol that is designed to provide a standard way to access directory services. LDAP is the primary protocol used to access an Active Directory store.

636/TCP – LDAP over SSL: When Secure Sockets Layer (SSL) is enabled, the LDAP data that is transmitted and received is encrypted.

3268/TCP – Microsoft Global Catalog: Active Directory global catalogs listen on this port.

3269/TCP – Microsoft Global Catalog with LDAP/SSL: Microsoft global catalog SSL connections listen on this port.

Possible resolutions include:

Verify that the service account used by the SA used by the Project Server application server is a domain account that has read access to Active Directory.

Verify that the Project Server application server is joined to an Active Directory domain.

Verify that the Project Server application server has network access.

Verify that the ports listed in the previous section are open between the Active Directory store and the Project Server application server.

Advertisements
Project Server

News Project Server 2016: December 2016 Patch Update

December 2016

https://support.microsoft.com/en-us/kb/3128017

https://support.microsoft.com/en-us/kb/3128014

DB Version (C0ntent DB – 16.0.4471.1000)

This update includes the following improvements and fixes in Project Server 2016:

If you apply a new site theme, the timeline which is a part of the tasks app, may continue to use the default theme.For example, suppose that the new site theme displays a blue background. In this case, the timeline would still be displayed with the default white background.

An Active Directory group that’s used to synchronize users in Project Web App and that includes disabled accounts does not inactivate those users in Project Web App. Additionally, the Active Directory Sync job may show that it partly failed.

When you edit a project in Project Web App, the filter that has been associated to the view that you have applied doesn’t work if the filter uses the “Begins with” test.

Consider the following scenario:
* In Project Professional, you have several tasks, some of which are summary tasks.
* You have collapsed some detail tasks so that you only see the related summary tasks.
* You save, publish, close, and check in the project.
* In Project Web App, you go to the Project Center.
* You drill into the project so that you can see the details.
* You choose to edit the project in Project Web App.

In this situation, you see the expected summary tasks but you can’t expand them in order to see the sub tasks under them.

How to rename an MS Project file

1.In PWA, change project name to the new title and update project ID

2.From SharePoint site, Site Actions, Site Settings, Title, Description, and Icons setting, rename the Title and the URL name

3.In PWA from ‘Server Settings’, select ‘Project Sites’ and select the white space next to the project name. then at the top, edit site address

4.We then need to update the name in the excel file we are using for the business case displayed on the SharePoint sites and the URL code to link buttons from the SharePoint site to the new project ID

Clean MS Project Local Cache

Never open MS Project files directly from your cache, you should always open from the saved location (typically the MS Project Server) to get the most recent version.  You should periodically clean your cache, to prevent any issues opening or closing MS Project files from the server.

  1. Within MS Project, go to the File menu item on the ribbon and Click on options | Save | Cleanup cache…
  2. Look at both project filters (in the middle of the dialog, projects checked out to you and projects not checked out to you) and highlight the project you wish to remove from your cache and click the “Remove From Cache” button

To add the Cleanup Cache to your quick menu within MS Project (will add an icon to the MS Project ribbon toolbar to go directly to the cleanup cache:

  1. Go to File | Options | Quick Access Toolbar |
  2. Select “All Commands” in the “Choose Commands” combo box
  3. Select the “Cleanup Cache” command and add it to the Quick Access Toolbar.
  4. The Icon will show up on the toolbar next to the undo/redo buttons.

In some extreme cases, when files do not clean from the cache as above you may need to navigate to the folder where the cache resides on your local drive and delete files.  Here are the steps to accomplish that:

  1. Open MS Project, go to menu item Tools -> Local Project Cache -> Cache Settings
  2. Copy the Path given in the Cache Location field
  3. Close MS Project (you have to close MS Project before doing the next steps to release locked cache folders)
  4. Open Windows Explorer and browse to the folder given in the Cache Location, or alternatively you can Paste the path copied in step-2
  5. Delete all subfolders and files under the Cache Location; don’t delete the “Cache” folder itself
  6. Open MS Project again and check the lookup values.  The problem should be fixed.