PerformancePoint 2013 Dashboard Designer fails to start after October 2013 CU

PerformancePoint 2013 Dashboard Designer fails to start after October 2013 CU

  • Comments 32
  • Likes

Issue:

After the SharePoint 2013 October 2013 cumulative update (CU) the PerformancePoint 2013 dashboard designer fails to start and gives error "Application cannot be started.  Contact the application vendor."

 

Cause:

The dashboard designer files were not signed correctly during the CU build process.

 

Workaround:

**This issue has been resolved in SharePoint 2013 Service Pack 1

Backup these files on all your SharePoint servers:

C:\Program Files\Common Files\Microsoft Shared\Web ServerExtensions\15\TEMPLATE\LAYOUTS\ppsma\1033\Designer.Application

C:\Program Files\Common Files\Microsoft Shared\Web ServerExtensions\15\TEMPLATE\LAYOUTS\ppsma\1033\DesignerInstall\Designer.exe.manifest

C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\15\TEMPLATE\LAYOUTS\ppsma\1033\DesignerInstall\Microsoft.SharePoint.Client.Runtime.dll

C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\15\TEMPLATE\LAYOUTS\ppsma\1033\DesignerInstall\Microsoft.PerformancePoint.Scorecards.Client.dll

C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\15\TEMPLATE\LAYOUTS\ppsma\1033\DesignerInstall\Microsoft.PerformancePoint.Scorecards.DesignerPlugins.dll

C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\15\TEMPLATE\LAYOUTS\ppsma\1033\DesignerInstall\Microsoft.SharePoint.Client.dll

Replace the files above with the files contained in the PPS.zip attached to this blog post.

 

Final Notes:

This issue has been resolved in SharePoint 2013 Service Pack 1

Attachment: PPS.zip
Comments
  • I have the same problem, When should we expect a hot fix to be available?

  • Still have issue after replaced files.  Please fix as soon as possible.

    ====

    ERROR DETAILS

    Following errors were detected during this operation.

    * [11/27/2013 9:36:40 AM] System.Deployment.Application.InvalidDeploymentException (HashValidation)

    - File, Microsoft.SharePoint.Client.Runtime.dll, has a different computed hash than specified in manifest.

    - Source: System.Deployment

    - Stack trace:

    at System.Deployment.Application.ComponentVerifier.VerifyFileHash(String filePath, Hash hash)

    at System.Deployment.Application.ComponentVerifier.VerifyFileHash(String filePath, HashCollection hashCollection)

    at System.Deployment.Application.ComponentVerifier.VerifyComponents()

    at System.Deployment.Application.DownloadManager.DownloadDependencies(SubscriptionState subState, AssemblyManifest deployManifest, AssemblyManifest appManifest, Uri sourceUriBase, String targetDirectory, String group, IDownloadNotification notification, DownloadOptions options)

    at System.Deployment.Application.ApplicationActivator.DownloadApplication(SubscriptionState subState, ActivationDescription actDesc, Int64 transactionId, TempDirectory& downloadTemp)

    at System.Deployment.Application.ApplicationActivator.InstallApplication(SubscriptionState& subState, ActivationDescription actDesc)

    at System.Deployment.Application.ApplicationActivator.PerformDeploymentActivation(Uri activationUri, Boolean isShortcut, String textualSubId, String deploymentProviderUrlFromExtension, BrowserSettings browserSettings, String& errorPageUrl)

    at System.Deployment.Application.ApplicationActivator.ActivateDeploymentWorker(Object state)

  • The fix doesn't work for other language packs likce 1031 German. Cause the resource dlls are different.

  • Still have issue after replacing the files, it does not work for some people and it work for some who are accessing for the first time and it does not work for other Languages.

  • Agreed. This fix does not work for my farm which is patched at this level. And I have replaced the files listed in this article

  • The latest files don't fix the problem

  • Following errors were detected during this operation.

    * [12/5/2013 4:19:35 AM] System.Deployment.Application.InvalidDeploymentException (HashValidation)

    - File, Microsoft.SharePoint.Client.Runtime.dll, has a different computed hash than specified in manifest.

    - Source: System.Deployment

    - Stack trace:

    at System.Deployment.Application.ComponentVerifier.VerifyFileHash(String filePath, Hash hash)

    at System.Deployment.Application.ComponentVerifier.VerifyFileHash(String filePath, HashCollection hashCollection)

    at System.Deployment.Application.ComponentVerifier.VerifyComponents()

    at System.Deployment.Application.DownloadManager.DownloadDependencies(SubscriptionState subState, AssemblyManifest deployManifest, AssemblyManifest appManifest, Uri sourceUriBase, String targetDirectory, String group, IDownloadNotification notification, DownloadOptions options)

    at System.Deployment.Application.ApplicationActivator.DownloadApplication(SubscriptionState subState, ActivationDescription actDesc, Int64 transactionId, TempDirectory& downloadTemp)

    at System.Deployment.Application.ApplicationActivator.InstallApplication(SubscriptionState& subState, ActivationDescription actDesc)

    at System.Deployment.Application.ApplicationActivator.PerformDeploymentActivation(Uri activationUri, Boolean isShortcut, String textualSubId, String deploymentProviderUrlFromExtension, BrowserSettings browserSettings, String& errorPageUrl)

    at System.Deployment.Application.ApplicationActivator.ActivateDeploymentWorker(Object state)

  • <publisherIdentity name="CN=REDMOND\brenwil"   ???

  • Replacing these with a CU EARIER than October (i.e. from another farm that did not yet have October CU on it) worked for me, my fellow SharePoint peeps... Quite lame that there isn't even a KB article on this problem. :/

  • Upon further inspection, it gets a bit further, but still does not work... :(

    + File, Microsoft.SharePoint.Client.dll, has a different computed hash than specified in manifest.

  • Replacing the 2 files does work, however, that will only work on machines that have never launched Dashboard Designer before or from the Server directly. To fix it on machines that have previously launched Dashboard Designer, you need to replace all the files below.

    C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\15\TEMPLATE\LAYOUTS\ppsma\1033\Designer.Application

    C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\15\TEMPLATE\LAYOUTS\ppsma\1033\DesignerInstall\Designer.exe.manifest

    C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\15\TEMPLATE\LAYOUTS\ppsma\1033\DesignerInstall\Microsoft.SharePoint.Client.Runtime.dll

    C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\15\TEMPLATE\LAYOUTS\ppsma\1033\DesignerInstall\Microsoft.PerformancePoint.Scorecards.Client.dll

    C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\15\TEMPLATE\LAYOUTS\ppsma\1033\DesignerInstall\Microsoft.PerformancePoint.Scorecards.DesignerPlugins.dll

    C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\15\TEMPLATE\LAYOUTS\ppsma\1033\DesignerInstall\Microsoft.SharePoint.Client.dll

    I new zip file with the corrected files will be uploaded soon.

  • Please upload the zip file as fast as possible

  • This posting has been updated

  • The zip is corrupted, could you please reupload it?

  • New Zip attached

Your comment has been posted.   Close
Thank you, your comment requires moderation so it may take a while to appear.   Close
Leave a Comment