none
Geeting a message "An unexpected error has occured" !! RRS feed

  • Question

  • Hi , 

    I am a project server admin but i have been getting a message "an unexpected error has occurred". i was delegating some resources but suddenly the PWA started throwing this error. I checked the logs and here is what i found:



    Entering monitored scope (InitializeWcfServerOperation)  
    09/13/2013 08:44:38.68 w3wp.exe (0x092C)                       0x2108 SharePoint Foundation         Topology                       e5mb Medium   WcfReceiveRequest: LocalAddress: 'http://XXXXXXXXXXXXX.com:32843/65d3eeb195df4463a52520d7d3e33d5d/PSI/authentication.svc' Channel: 'System.ServiceModel.Channels.ServiceChannel' Action: 'http://schemas.microsoft.com/office/project/server/webservices/Authentication/GetUserByName' MessageId: 'urn:uuid:fd53cca6-9fae-4b32-8e20-433cc8eb9d8d' d28fc896-b319-439d-ac82-540edca12ea5
    09/13/2013 08:44:38.68 w3wp.exe (0x092C)                       0x2108 SharePoint Foundation         Monitoring                     b4ly Verbose Leaving Monitored Scope (InitializeWcfServerOperation). Execution Time=0.191608988948111 d28fc896-b319-439d-ac82-540edca12ea5
    09/13/2013 08:44:38.68 w3wp.exe (0x092C)                       0x2108 SharePoint Foundation         Monitoring                     nass Verbose ____Execution Time=0.191608988948111 d28fc896-b319-439d-ac82-540edca12ea5
    09/13/2013 08:44:38.68 w3wp.exe (0x092C)                       0x2108 SharePoint Foundation         Monitoring                     nasq Medium   Entering monitored scope (ExecuteWcfServerOperation) d28fc896-b319-439d-ac82-540edca12ea5
    09/13/2013 08:44:38.68 w3wp.exe (0x092C)                       0x2108 SharePoint Foundation         Monitoring                     nasq Verbose Entering monitored scope (ExecuteStoredProcedureDataReader -- MSP_AUTH_GETUSERBYNAME) d28fc896-b319-439d-ac82-540edca12ea5
    09/13/2013 08:44:38.70 w3wp.exe (0x092C)                       0x2108 SharePoint Foundation         Monitoring                     b4ly Verbose Leaving Monitored Scope (ExecuteStoredProcedureDataReader -- MSP_AUTH_GETUSERBYNAME). Execution Time=13.6985800457521 d28fc896-b319-439d-ac82-540edca12ea5
    09/13/2013 08:44:38.70 w3wp.exe (0x092C)                       0x2108 SharePoint Foundation         Monitoring                     nass Verbose ____Execution Time=13.6985800457521 d28fc896-b319-439d-ac82-540edca12ea5
    09/13/2013 08:44:38.70 w3wp.exe (0x092C)                       0x2108 SharePoint Foundation         Monitoring                     nasq Verbose Entering monitored scope (CleanUpWcfServerOperation) d28fc896-b319-439d-ac82-540edca12ea5
    09/13/2013 08:44:38.70 w3wp.exe (0x092C)                       0x2108 SharePoint Foundation         Usage Infrastructure           d0hz Verbose Starting write trace for type Microsoft.SharePoint.Administration.SPRequestUsageEntry with correlationID 166fd5f4-335d-4fb7-8c20-82472aa201d0 d28fc896-b319-439d-ac82-540edca12ea5
    09/13/2013 08:44:38.70 w3wp.exe (0x092C)                       0x2108 SharePoint Foundation         Usage Infrastructure           d0i0 Verbose Successful wrote trace for type Microsoft.SharePoint.Administration.SPRequestUsageEntry with correlationID 166fd5f4-335d-4fb7-8c20-82472aa201d0 d28fc896-b319-439d-ac82-540edca12ea5
    09/13/2013 08:44:38.70 w3wp.exe (0x092C)                       0x2108 SharePoint Foundation         Monitoring                     b4ly Verbose Leaving Monitored Scope (CleanUpWcfServerOperation). Execution Time=0.399672948321154 d28fc896-b319-439d-ac82-540edca12ea5
    09/13/2013 08:44:38.70 w3wp.exe (0x092C)                       0x2108 SharePoint Foundation         Monitoring                     nass Verbose ____Execution Time=0.399672948321154 d28fc896-b319-439d-ac82-540edca12ea5
    09/13/2013 08:44:38.70 w3wp.exe (0x092C)                       0x2108 SharePoint Foundation         Monitoring                     b4ly Medium   Leaving Monitored Scope (ExecuteWcfServerOperation). Execution Time=14.6270060437278 d28fc896-b319-439d-ac82-540edca12ea5
    09/13/2013 08:44:38.70 w3wp.exe (0x092C)                       0x2108 SharePoint Foundation         Monitoring                     nass Verbose ____SPRequest Objects=0 d28fc896-b319-439d-ac82-540edca12ea5
    09/13/2013 08:44:38.70 w3wp.exe (0x092C)                       0x2108 SharePoint Foundation         Monitoring                     nass Verbose ____SQL Query Count=0 d28fc896-b319-439d-ac82-540edca12ea5
    09/13/2013 08:44:38.70 w3wp.exe (0x092C)                       0x2108 SharePoint Foundation         Monitoring                     nass Verbose ____Execution Time=14.6270060437278 d28fc896-b319-439d-ac82-540edca12ea5
    09/13/2013 08:44:38.70 w3wp.exe (0x092C)                       0x2108 SharePoint Foundation         Monitoring                     nass Verbose ____Current User= d28fc896-b319-439d-ac82-540edca12ea5
    09/13/2013 08:44:38.70 w3wp.exe (0x092C)                       0x2108 SharePoint Foundation         Monitoring                     nass Verbose ____WebPart Events Offsets=0 d28fc896-b319-439d-ac82-540edca12ea5
    09/13/2013 08:44:38.70 w3wp.exe (0x092C)                       0x2108 SharePoint Foundation         Monitoring                     nass Verbose ____Service Calls=0 d28fc896-b319-439d-ac82-540edca12ea5
    09/13/2013 08:44:38.70 w3wp.exe (0x092C)                       0x2108 SharePoint Foundation         Monitoring                     nass Verbose ____Page Checkout Level=Published d28fc896-b319-439d-ac82-540edca12ea5
    09/13/2013 08:44:38.70 w3wp.exe (0x092C)                       0x2108 SharePoint Foundation         Monitoring                     nass Verbose ____Current SharePoint Operations=0 d28fc896-b319-439d-ac82-540edca12ea5
    09/13/2013 08:44:38.70 w3wp.exe (0x092C)                       0x2108 SharePoint Foundation         Monitoring                     nass Verbose ____Critical Events=0 d28fc896-b319-439d-ac82-540edca12ea5
    09/13/2013 08:44:38.70 w3wp.exe (0x092C)                       0x2108 SharePoint Foundation         Monitoring                     nass Verbose ____Log Correlation Id=166fd5f4-335d-4fb7-8c20-82472aa201d0 d28fc896-b319-439d-ac82-540edca12ea5
    09/13/2013 08:44:38.71 w3wp.exe (0x092C)                       0x2108 SharePoint Foundation         Monitoring                     nasq Verbose Entering monitored scope (SPCertificateValidator.Validate)  
    09/13/2013 08:44:38.71 w3wp.exe (0x092C)                       0x2108 SharePoint Foundation         Monitoring                     b4ly Verbose Leaving Monitored Scope (SPCertificateValidator.Validate). Execution Time=1.12625130908431  
    09/13/2013 08:44:38.71 w3wp.exe (0x092C)                       0x2108 SharePoint Foundation         Monitoring                     nass Verbose ____Execution Time=1.12625130908431  
    09/13/2013 08:44:38.71 w3wp.exe (0x092C)                       0x2108 SharePoint Foundation         Monitoring                     nasq Verbose Entering monitored scope (SPTrustedIssuerNameRegistry.GetIssuerName)  
    09/13/2013 08:44:38.71 w3wp.exe (0x092C)                       0x2108 SharePoint Foundation         Monitoring                     b4ly Verbose Leaving Monitored Scope (SPTrustedIssuerNameRegistry.GetIssuerName). Execution Time=0.0859315122190954  
    09/13/2013 08:44:38.71 w3wp.exe (0x092C)                       0x2108 SharePoint Foundation         Monitoring                     nass Verbose ____Execution Time=0.0859315122190954  
    09/13/2013 08:44:38.71 w3wp.exe (0x092C)                       0x2108 SharePoint Foundation         Monitoring                     nasq Verbose Entering monitored scope (SPSaml11BaseTokenHandler.ProcessAttributeStatement)  
    09/13/2013 08:44:38.71 w3wp.exe (0x092C)                       0x2108 SharePoint Foundation         Monitoring                     b4ly Verbose Leaving Monitored Scope (SPSaml11BaseTokenHandler.ProcessAttributeStatement). Execution Time=0.11116246687066  
    09/13/2013 08:44:38.71 w3wp.exe (0x092C)                       0x2108 SharePoint Foundation         Monitoring                     nass Verbose ____Execution Time=0.11116246687066  
    09/13/2013 08:44:38.71 w3wp.exe (0x092C)                       0x2108 SharePoint Foundation         Monitoring                     nasq Verbose Entering monitored scope (SPClaimsAuthenticationManager.Authenticate)  
    09/13/2013 08:44:38.71 w3wp.exe (0x092C)                       0x2108 SharePoint Foundation         Monitoring                     b4ly Verbose Leaving Monitored Scope (SPClaimsAuthenticationManager.Authenticate). Execution Time=0.0398575950292825  
    09/13/2013 08:44:38.71 w3wp.exe (0x092C)                       0x2108 SharePoint Foundation         Monitoring                     nass Verbose ____Execution Time=0.0398575950292825  
    09/13/2013 08:44:38.71 w3wp.exe (0x092C)                       0x2108 SharePoint Foundation         Monitoring                     nasq Verbose Entering monitored scope (SPIisWebServiceAuthorizationManager.CheckAccessCore)  
    09/13/2013 08:44:38.71 w3wp.exe (0x092C)                       0x2108 SharePoint Foundation         Monitoring                     b4ly Verbose Leaving Monitored Scope (SPIisWebServiceAuthorizationManager.CheckAccessCore). Execution Time=0.514857741295686  
    09/13/2013 08:44:38.71 w3wp.exe (0x092C)                       0x2108 SharePoint Foundation         Monitoring                     nass Verbose ____Execution Time=0.514857741295686  
    09/13/2013 08:44:38.71 w3wp.exe (0x092C)                       0x2108 SharePoint Foundation         Database                       7t61 Verbose DatabaseConnectionString acquired.  Data Source=xxxxxx;Initial Catalog=xxxxxxxxx_Published;Integrated Security=True;Enlist=False;Connect Timeout=15  
    09/13/2013 08:44:38.71 w3wp.exe (0x092C)                       0x2108 SharePoint Foundation         Database                       7t61 Verbose DatabaseConnectionString acquired.  Data Source=xxxxxxxx;Initial Catalog=xxxxxxxxxx_Archive;Integrated Security=True;Enlist=False;Connect Timeout=15  
    09/13/2013 08:44:38.71 w3wp.exe (0x092C)                       0x2108 SharePoint Foundation         Database                       7t61 Verbose DatabaseConnectionString acquired.  Data Source=xxxxxxxxx;Initial Catalog=xxxxxxxxxx_Draft;Integrated Security=True;Enlist=False;Connect Timeout=15  
    09/13/2013 08:44:38.71 w3wp.exe (0x092C)                       0x2108 SharePoint Foundation         Database                       7t61 Verbose DatabaseConnectionString acquired.  Data Source=xxxxxx;Initial Catalog=xxxxxxxxx_Reporting;Integrated Security=True;Enlist=False;Connect Timeout=15  
    09/13/2013 08:44:38.71 w3wp.exe (0x092C)                       0x2108 SharePoint Foundation         General                       6t8j Verbose Site lookup by id found the typical site /PWA.  
    09/13/2013 08:44:38.71 w3wp.exe (0x092C)                       0x2108 SharePoint Foundation         Monitoring                     nasq Verbose Entering monitored scope (InitializeWcfServerOperation)  
    09/13/2013 08:44:38.71 w3wp.exe (0x092C)                       0x2108 SharePoint Foundation         Topology                       e5mb Medium   WcfReceiveRequest: LocalAddress: 'http://xxxxxxxxxxxx.com:32843/65d3eeb195df4463a52520d7d3e33d5d/PSI/PWA.svc' Channel: 'System.ServiceModel.Channels.ServiceChannel' Action: 'http://schemas.microsoft.com/office/project/server/webservices/PWA/SecurityCheckUserPagePermission' MessageId: 'urn:uuid:82f9a774-0c9f-41ae-ad09-9184ecc3c895' d28fc896-b319-439d-ac82-540edca12ea5
    09/13/2013 08:44:38.71 w3wp.exe (0x092C)                       0x2108 SharePoint Foundation         Monitoring                     b4ly Verbose Leaving Monitored Scope (InitializeWcfServerOperation). Execution Time=0.14334107570164 d28fc896-b319-439d-ac82-540edca12ea5
    09/13/2013 08:44:38.71 w3wp.exe (0x092C)                       0x2108 SharePoint Foundation         Monitoring                     nass Verbose ____Execution Time=0.14334107570164 d28fc896-b319-439d-ac82-540edca12ea5
    09/13/2013 08:44:38.71 w3wp.exe (0x092C)                       0x2108 SharePoint Foundation         Monitoring                     nasq Medium   Entering monitored scope (ExecuteWcfServerOperation) d28fc896-b319-439d-ac82-540edca12ea5
    09/13/2013 08:44:38.71 w3wp.exe (0x092C)                       0x2108 SharePoint Foundation         Monitoring                     nasq Verbose Entering monitored scope (ExecuteStoredProcedureNoResultWithOutputParameters -- MSP_WEB_SP_SEC_CheckSPGlobalPermission) d28fc896-b319-439d-ac82-540edca12ea5
    09/13/2013 08:44:38.71 w3wp.exe (0x092C)                       0x2108 SharePoint Foundation         Monitoring                     b4ly Verbose Leaving Monitored Scope (ExecuteStoredProcedureNoResultWithOutputParameters -- MSP_WEB_SP_SEC_CheckSPGlobalPermission). Execution Time=0.844322815803792 d28fc896-b319-439d-ac82-540edca12ea5
    09/13/2013 08:44:38.71 w3wp.exe (0x092C)                       0x2108 SharePoint Foundation         Monitoring                     nass Verbose ____Execution Time=0.844322815803792 d28fc896-b319-439d-ac82-540edca12ea5
    09/13/2013 08:44:38.71 w3wp.exe (0x092C)                       0x2108 Project Server                 Security                       8tid Verbose PWA:http://xxxx/PWA, ServiceApp:ProductionProjectServerService, User:xxxxx\xxxxx, PSI: Permission Check Failed: User e410b33a-9c0d-4498-8cf9-c3e90bb2cd80 does not have global permission 7c40a2c2-fd15-44e3-8fd3-11b3e0a4e441. d28fc896-b319-439d-ac82-540edca12ea5
    09/13/2013 08:44:38.71 w3wp.exe (0x092C)                       0x2108 Project Server                 General                       ukhl Verbose Error is: GeneralSecurityAccessDenied. Details: . Standard Information: PSI Entry Point:   Project User: xxxxx\xxxxx Correlation Id: 513a6af1-d57b-4d71-b4f2-3913bd3a4ba7  PWA Site URL: http://xxxxxxx/PWA  SSP Name: ProductionProjectServerService  PSError: GeneralSecurityAccessDenied (20010) d28fc896-b319-439d-ac82-540edca12ea5
    09/13/2013 08:44:38.73 w3wp.exe (0x092C)                       0x2108 SharePoint Foundation         Monitoring                     nasq Verbose Entering monitored scope (CleanUpWcfServerOperation) d28fc896-b319-439d-ac82-540edca12ea5
    09/13/2013 08:44:38.73 w3wp.exe (0x092C)                       0x2108 SharePoint Foundation         Usage Infrastructure           d0hz Verbose Starting write trace for type Microsoft.SharePoint.Administration.SPRequestUsageEntry with correlationID 34defccc-5b70-4e49-b229-3e6a0ac3e870 d28fc896-b319-439d-ac82-540edca12ea5
    09/13/2013 08:44:38.73 w3wp.exe (0x092C)                       0x2108 SharePoint Foundation         Usage Infrastructure           d0i0 Verbose Successful wrote trace for type Microsoft.SharePoint.Administration.SPRequestUsageEntry with correlationID 34defccc-5b70-4e49-b229-3e6a0ac3e870 d28fc896-b319-439d-ac82-540edca12ea5
    09/13/2013 08:44:38.73 w3wp.exe (0x092C)                       0x2108 SharePoint Foundation         Monitoring                     b4ly Verbose Leaving Monitored Scope (CleanUpWcfServerOperation). Execution Time=0.382486645877335 d28fc896-b319-439d-ac82-540edca12ea5
    09/13/2013 08:44:38.73 w3wp.exe (0x092C)                       0x2108 SharePoint Foundation         Monitoring                     nass Verbose ____Execution Time=0.382486645877335 d28fc896-b319-439d-ac82-540edca12ea5
    09/13/2013 08:44:38.73 w3wp.exe (0x092C)                       0x2108 SharePoint Foundation         Monitoring                     b4ly Medium   Leaving Monitored Scope (ExecuteWcfServerOperation). Execution Time=4.36824614880559 d28fc896-b319-439d-ac82-540edca12ea5
    09/13/2013 08:44:38.73 w3wp.exe (0x092C)                       0x2108 SharePoint Foundation         Monitoring                     nass Verbose ____SPRequest Objects=0 d28fc896-b319-439d-ac82-540edca12ea5
    09/13/2013 08:44:38.73 w3wp.exe (0x092C)                       0x2108 SharePoint Foundation         Monitoring                     nass Verbose ____SQL Query Count=0 d28fc896-b319-439d-ac82-540edca12ea5
    09/13/2013 08:44:38.73 w3wp.exe (0x092C)                       0x2108 SharePoint Foundation         Monitoring                     nass Verbose ____Execution Time=4.36824614880559 d28fc896-b319-439d-ac82-540edca12ea5
    09/13/2013 08:44:38.73 w3wp.exe (0x092C)                       0x2108 SharePoint Foundation         Monitoring                     nass Verbose ____Current User= d28fc896-b319-439d-ac82-540edca12ea5
    09/13/2013 08:44:38.73 w3wp.exe (0x092C)                       0x2108 SharePoint Foundation         Monitoring                     nass Verbose ____WebPart Events Offsets=0 d28fc896-b319-439d-ac82-540edca12ea5
    09/13/2013 08:44:38.73 w3wp.exe (0x092C)                       0x2108 SharePoint Foundation         Monitoring                     nass Verbose ____Service Calls=0 d28fc896-b319-439d-ac82-540edca12ea5
    09/13/2013 08:44:38.73 w3wp.exe (0x092C)                       0x2108 SharePoint Foundation         Monitoring                     nass Verbose ____Page Checkout Level=Published d28fc896-b319-439d-ac82-540edca12ea5
    09/13/2013 08:44:38.73 w3wp.exe (0x092C)                       0x2108 SharePoint Foundation         Monitoring                     nass Verbose ____Current SharePoint Operations=0 d28fc896-b319-439d-ac82-540edca12ea5
    09/13/2013 08:44:38.73 w3wp.exe (0x092C)                       0x2108 SharePoint Foundation         Monitoring                     nass Verbose ____Critical Events=0 d28fc896-b319-439d-ac82-540edca12ea5
    09/13/2013 08:44:38.73 w3wp.exe (0x092C)                       0x2108 SharePoint Foundation         Monitoring                     nass Verbose ____Log Correlation Id=34defccc-5b70-4e49-b229-3e6a0ac3e870 d28fc896-b319-439d-ac82-540edca12ea5






    I am not able to go into the PWA but surprisingly i am able to go through child sites in same collection. What needs to be done , please help.

    Thanks

    Monday, September 16, 2013 6:27 AM

All replies

  • Looks like a straight permission issue.

    Assuming 2010/2013 - Can you try going to the Project Server Service in Central Admin and 'viewing' the PWA instance.  This should show you the Admin account of the Project Instance - try logging into this account to regain access to your instance.


    James Boman - http://www.boman.biz Software Consultant for IPMO - http://www.ipmo.com.au

    Monday, September 16, 2013 6:45 AM
  • Hi James,

    Thanks for reply , but what you showed is the site collection admin account but i am working using a account that has been created as a user in PWA with admin access to everyhting , this what you shown is usually the prod id which we do not use. Think me of as a user who has admin rights and can perform all the tasks of the admin but cannot logon now because of this error.

    Thanks

    Monday, September 16, 2013 10:31 AM
  • Hey there,

        The error message says the account you are using doesn't have the "7c40a2c2-fd15-44e3-8fd3-11b3e0a4e441" permission - which is the "Log On" right.  So you need to find another account that does, and then use it to investigate what has happened with security.  The most privileged account in Project Server is the one I pictured above which could be used to achieve this.  (This is not the same as Site Collection Administrator).

    BTW - What usually causes this kind of thing is Active Directory Synchronisation comes along and deactivates a bunch of users because someone has made a change in AD.

    Good luck,

       James.


    James Boman - http://www.boman.biz Software Consultant for IPMO - http://www.ipmo.com.au


    • Edited by James Boman Monday, September 16, 2013 11:41 AM
    Monday, September 16, 2013 11:38 AM
  • Hi James,

    Thanks for the reply, but can you tell me one very straight method to approach this problem, do i have to write some query or something ? there is mention of one procedure MSP_AUTH_GETUSERBYNAME in there too , could it be causing some issues ? please help me out here .

    Thanks

    Tuesday, September 17, 2013 9:29 AM
  • Unfortunately I don't know how else to say it.

    The user account you are attempting to use has lost the "Log On" global right in Project Server (not SharePoint)

    You need to use a different account to log into Project Server and rectify the problem.

    The account I pictured in the screenshot above would be the account I would use.

    Good luck,

       J.


    James Boman - http://www.boman.biz Software Consultant for IPMO - http://www.ipmo.com.au

    Wednesday, September 18, 2013 3:17 AM