Project General Data Access Layer error connecting to database


Applies to: Project Server 2013, Project Server 2010

Topic Last Modified: 2013-12-18

Element ID / Rule Name:   Project_General_Data_Access_Layer_Error_Connecting_To_Database

Summary:   This message indicates that the Data Access Layer on a Microsoft Project Server application server tried but could not connect to one of the four Project Server databases that hold the data for a Microsoft Project Server site. The effect that this problem has on the Project Server deployment varies, depending on whether the problem is caused at the server or the database level, and whether a database is affected. The following list describes how the effect on the Project Server deployment varies, depending on which database the error originated from:

  1. Draft Database   Project managers will be unable to save edits to data. However, some Microsoft Project Web App functionality will be available, although typically read-only. All Reporting database read-only functionality should be available. Limited Archive database functionality will be available, but no project archive or restore functions will be available.

  2. Published Database   Most system functionality will be impaired because the security data that is used for authorization is stored in this database. All Reporting database functionality should be available. However, no Archive database functionality will be available.

  3. Archive Database   Most system functionality will be available except for archive and restore functions that are either scheduled or performed manually.

  4. Reporting Database   Most system functionality will be available except for relational reporting.


If either the Published database or the Draft database is unavailable, the Project Server queue service will degrade over time as queued actions either fail or are blocked.

Cause:   Possible causes include the following:

  • Network connectivity issues that prevent the Project Server application servers from connecting to the one or more computers that are running Microsoft SQL Server.

  • Invalid service account credentials caused by account lockouts or failure to propagate changes.

  • Database availability issues caused by hardware problems, such as failed hard disk drives or controllers.

  • Data access issues caused by an administrator who changes database permissions, which results in the account that is used to access data being denied authorization.

Possible resolutions include the following: