none
Project Server 2019 Error RRS feed

  • Question

  • Good Morning SharePoint Experts.

    I am deploying a new Project Server site with the PWA template. However I'm getting the error below when browsing to the site /myprojectsite/default.aspx. I've spend at least a week trying to find the root cause with no luck :(. Any help is very much appreciated.

    • SharePoint Version: 2019 Enterprise
    • SQL Version:
    • 2016 Farm: 3 tier (App, FE, SQL)

    I created the Project Web App Site as per the the instructions below:

    1. Enabled PWA site collection features
    2. Created a PWA site in an existing site collection

    The site creates successfully and if I go to the parent site collection "site content" I see my site. And if I click on the ellipsis for my PWA subsite I can browse to it's site content as well and all pages display except "default.aspx" where the PWA should show. I get the error message below when I go to https://mysitecollection.domain.com/projects/default.aspx:

    Server Error in '/' Application.

    The SELECT permission was denied on the object 'objects', database 'mssqlsystemresource', schema 'sys'.

    Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

    Exception Details: System.Data.SqlClient.SqlException: The SELECT permission was denied on the object 'objects', database 'mssqlsystemresource', schema 'sys'.

    Source Error:

    The source code that generated this unhandled exception can only be shown when compiled in debug mode. To enable this, please follow one of the below steps, then request the URL:

    1. Add a "Debug=true" directive at the top of the file that generated the error. Example:

      <%@ Page Language="C#" Debug="true" %>

    or:

    2) Add the following section to the configuration file of your application:

    <configuration>
       <system.web>
           <compilation debug="true"/>
       </system.web>
    </configuration>

    Note that this second technique will cause all files within a given application to be compiled in debug mode. The first technique will cause only that particular file to be compiled in debug mode.

    Important: Running applications in debug mode does incur a memory/performance overhead. You should make sure that an application has debugging disabled before deploying into production scenario.

    Stack Trace:
    [SqlException (0x80131904): The SELECT permission was denied on the object 'objects', database 'mssqlsystemresource', schema 'sys'.]
       System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction) +3306108
       System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose) +736
       System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady) +4061
       System.Data.SqlClient.SqlDataReader.TryConsumeMetaData() +90
       System.Data.SqlClient.SqlDataReader.get_MetaData() +99
       System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString, Boolean isInternal, Boolean forDescribeParameterEncryption, Boolean shouldCacheForAlwaysEncrypted) +604
       System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async, Int32 timeout, Task& task, Boolean asyncWrite, Boolean inRetry, SqlDataReader ds, Boolean describeParameterEncryptionRequest) +3303
       System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, TaskCompletionSource`1 completion, Int32 timeout, Task& task, Boolean& usedCache, Boolean asyncWrite, Boolean inRetry) +667
       System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method) +83
       System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior, String method) +301
       System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior) +105
       Microsoft.Office.Project.Server.Data.SqlSession.ExecuteReader(SqlCommand command, CommandBehavior behavior, SqlQueryData monitoringData, Boolean retryForDeadLock) +1073
       Microsoft.Office.Project.Server.Data.SqlSession.ExecuteReader(SqlCommand command, CommandBehavior behavior) +134
       Microsoft.Office.Project.Server.DataAccessLayer.SqlSessionAdapter.ExecuteCommandDataReader(SqlCommand command, CommandBehavior behavior) +52
       Microsoft.Office.Project.Server.DataAccessLayer.<>c__DisplayClass9.<ReadDatabaseInfoFromVersionTable>b__8() +85
       Microsoft.Office.Project.Server.Security.SecurityContext.RunAsProcess(CodeToRunElevated secureCode) +194
       Microsoft.Office.Project.Server.DataAccessLayer.DatabaseVersionManager.ReadDatabaseInfoFromVersionTable(IProjectServerSqlSession session) +318
       Microsoft.Office.Project.Server.DataAccessLayer.DatabaseVersionManager.GetDatabaseVersion(IProjectServerSqlSession session) +59
       Microsoft.Office.Project.Server.DataAccessLayer.DatabaseVersionManager.IsUpgradeInstalled(IProjectServerSqlSession session, Version upgraderVersion) +14
       Microsoft.Office.Project.Server.DataAccessLayer.<>c__DisplayClass1.<IsUpgradeInstalled>b__0(IProjectServerSqlSession session) +20
       Microsoft.Office.Project.Server.DataAccessLayer.DatabaseVersionManager.IsUpgradeInstalled(IProjectServerSqlSessionProvider sessionProvider, Version upgraderVersion) +112
       Microsoft.Office.Project.Server.DataAccessLayer.AuthDal.AuthenticateUserByAccount(String account, ISet`1 encodedClaims) +2568
       Microsoft.Office.Project.PWA.PJContextIdentityAuthenticator.AuthenticateUser() +132
       Microsoft.Office.Project.Server.SecurityAuthorization.Authenticate() +132
       Microsoft.Office.Project.PWA.PJContext.Authenticate(IIdentity identity) +123
       Microsoft.Office.Project.PWA.PJContext.GetContext(Boolean isWebServiceCall, Boolean ignoreCachedContext, SPWeb web) +257
       Microsoft.Office.Project.PWA.PJContext.GetContext(Boolean isWebServiceCall, Boolean ignoreCachedContext) +76
       Microsoft.Office.Project.PWA.PJBaseWebPartPage..ctor() +53
       ASP.DEFAULT_ASPX__1676264446..ctor() +16
       __ASP.FastObjectFactory_app_web_default_aspx__1676264446_5mwbuuym.Create_ASP_DEFAULT_ASPX__1676264446() +31
       System.Web.Compilation.BuildManager.CreateInstanceFromVirtualPath(VirtualPath virtualPath, Type requiredBaseType, HttpContext context, Boolean allowCrossApp) +152
       System.Web.UI.PageHandlerFactory.GetHandlerHelper(HttpContext context, String requestType, VirtualPath virtualPath, String physicalPath) +47
       System.Web.MaterializeHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +624
       System.Web.HttpApplication.ExecuteStepImpl(IExecutionStep step) +213
       System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +131
    


    Version Information: Microsoft .NET Framework Version:4.0.30319; ASP.NET Version:4.7.3429.0 

    Other errors and fixes I have applied:

    


    OT

    Friday, September 13, 2019 1:32 PM

All replies

  • Seems like an access issue from your SQL end. Go to SQL Server and click on this mssqlsystemresource and Select Schema for this Database and provide Dbo access for the account you are trying and then give it a try.

    Thanks & Regards,



    sharath aluri

    Friday, September 13, 2019 1:44 PM
  • Hi Oliver_Tech,

    To troubleshoot the issue, you could check the permission of the schema “sys” on the database “mssqlsystemresource”.

    And then you also check if the schema “sys” has denied privileges on the database “mssqlsystemresource”.

    Best regards,

    Sara Fan


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    SharePoint Server 2019 has been released, you can click here to download it.
    Click here to learn new features. Visit the dedicated forum to share, explore and talk to experts about SharePoint Server 2019.

    Monday, September 16, 2019 7:58 AM
    Moderator

  • Hi Oliver_Tech,

    How is everything going?

    Is there anything update about this issue?

    If the reply is helpful to you, you could mark the reply as answer. Thanks for your understanding.

    Best regards,

    Sara Fan

    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    SharePoint Server 2019 has been released, you can click here to download it.
    Click here to learn new features. Visit the dedicated forum to share, explore and talk to experts about SharePoint Server 2019.

    Wednesday, September 18, 2019 9:18 AM
    Moderator