Recently, I migrated the Microsoft Project Server 2013 databases from production environment to newly created development environment. I used the database attached method and it went well, however I was unable to open the Projects from Project Center and was getting below error message.

Error in IE window: “Sorry, something went wrong

The ULS log was showing below exception.

Error in ULS Log:

==========================

Watson bucket parameters: Microsoft Project Server 2013, ULSException14, 070f6ea0 “project server”, 0f001181 “15.0.4481.0”, 09d02580 “microsoft.workflow.client”, 01009cc3 “1.0.40131.0”, 52ef34cc “sun feb 02 22:18:52 2014”, 0000005e “0000005e”, 00000076 “00000076”, 8e5b5a5b “scopenotfoundexception”, 00101621 “aeby7”    52fea99c-5aba-a029-621f-59599d28ff58
[Forced due to logging gap, cached @ 07/31/2014 11:39:33.45, Original Level: Verbose] PWA:http://Servername/PWA, ServiceApp:ProjectServiceApplication, User:i:0#.w|username, PSI: EnsureWorkflowServicesProviders: ServiceCredentials {0} null Project:402a41ae-f2b5-e311-93fa-005056a212ba    52fea99c-5aba-a029-621f-59599d28ff58
Error is: GeneralUnhandledException. Details: General Unhandled Exception in _Workflow.GetProjectDrilldownInformation_ Attributes:  Microsoft.Workflow.Client.ScopeNotFoundException: Scope ‘/SharePoint/default/a2e1bb0c-01f9-4be3-8749-c64b3cff0b03/1bc6d678-b638-493f-af24-3c241680f02e’ was not found.  HTTP headers received from the server – ActivityId: 6ca3cefa-6239-4e2e-80f0-541b694f0de3. NodeId: Servername. Scope: /SharePoint/default/a2e1bb0c-01f9-4be3-8749-c64b3cff0b03/1bc6d678-b638-493f-af24-3c241680f02e. Client ActivityId : 52fea99c-5aba-a029-621f-59599d28ff58. —> System.Net.WebException: The remote server returned an error: (404) Not Found.     at Microsoft.Workflow.Common.AsyncResult.End[TAsyncResult](IAsyncResult result)     at Microsoft.Workflow.Client.HttpGetResponseAsyncResult…    52fea99c-5aba-a029-621f-59599d28ff58

===========================

I had workflow manager 1.0 installed and configured correctly and workflow service status was showing “Workflow is connected”. But still it was throwing workflow related errors while accessing projects from Project Center. Finally, I re-installed and configured the workflow manager 1.0 again using below steps and that helped to resolve the issue.

Uninstalled Workflow Manager 1.0 using below steps.

  1. Removed the workflow manager from the farm by running the Workflow Manager Configuration Wizard and then leaving the farm.
  2. Uninstalled below applications.
    • Service Bus 1.0
    • Workflow Manager 1.0
    • Workflow Manager Client 1.0
    • Windows Fabric
  3. Deleted the below databases from the SQL server
    • WfManagement
    • SbGatewayDatabase
    • SBContainer
    • WFInstanceManagementDB
    • WFResourceManagementDB
    • SBManagementDB

Installed Workflow Manager 1.0 using below steps

  1. Downloaded and installed the Workflow Manager 1.0 from http://msdn.microsoft.com/en-us/library/jj193448.aspx
  2. Ran the Workflow Manager Configuration Wizard and selected “Configure Workflow Manager with Default settings”
  3. Re-Registered the Workflow Service using below command. You cannot un-register the workflow service which is already registered and hence I had to use the –Force parameter to forcefully register the workflow service. You will get error “Failed to register because the farm or partition is already registered with a workflow service” if you don’t use the –Force parameter.

Register-SPWorkflowService -SPSite “http://Servername/pwa” -WorkflowHostUri “http://servername:12291″ -AllowOauthHttp –Force

If you need any additional information please contact us