Sign in
 
Windows > Windows Forms Forums > ClickOnce and Setup & Deployment Projects > ClickOnce Error Message
Ask a questionAsk a question
Search Forums:
 

QuestionClickOnce Error Message

  • Tuesday, August 22, 2006 11:05 PMCassieC Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote
    Hi, I'm getting the following error message & detailed report:

     'Cannot download the application. The application is missing required files. Contact application venfor for assistance.'




    PLATFORM VERSION INFO
        Windows             : 5.1.2600.131072 (Win32NT)
        Common Language Runtime     : 2.0.50727.42
        System.Deployment.dll         : 2.0.50727.42 (RTM.050727-4200)
        mscorwks.dll             : 2.0.50727.42 (RTM.050727-4200)
        dfdll.dll             : 2.0.50727.42 (RTM.050727-4200)
        dfshim.dll             : 2.0.50727.42 (RTM.050727-4200)

    SOURCES
        Deployment url            : file://(PATH)/SerialSNMPWinApp.application
        Deployment Provider url        : file://(PATH)/SerialSNMPWinApp/bin/Release/SerialSNMPWinApp.application

    ERROR SUMMARY
        Below is a summary of the errors, details of these errors are listed later in the log.
        * Activation of \\(SERVER/PATH)\SerialSNMPWinApp.application resulted in exception. Following failure messages were detected:
            + The Deployment Provider specified in the manifest cannot be reached. Maybe due to network error and/or the deployment provider is not responding correctly.
            + Exception reading manifest from file://(SERVER/PATH)/SerialSNMPWinApp/SerialSNMPWinApp/bin/Release/SerialSNMPWinApp.application: the manifest may not be valid or the file could not be opened.
            + Manifest XML signature is not valid.
            + No signature was present in the subject.


    COMPONENT STORE TRANSACTION FAILURE SUMMARY
        No transaction error was detected.

    WARNINGS
        There were no warnings during this operation.

    OPERATION PROGRESS STATUS
        * [8/22/2006 3:37:15 PM] : Activation of \\(PATH)SerialSNMPWinApp.application has started.

    ERROR DETAILS
        Following errors were detected during this operation.
        * [8/22/2006 3:37:15 PM] System.Deployment.Application.InvalidDeploymentException (Manifest)
            - The Deployment Provider specified in the manifest cannot be reached. Maybe due to network error and/or the deployment provider is not responding correctly.
            - Source: System.Deployment
            - Stack trace:
                at System.Deployment.Application.DownloadManager.FollowDeploymentProviderUri(SubscriptionStore subStore, AssemblyManifest& deployment, Uri& sourceUri, TempFile& tempFile, IDownloadNotification notification, DownloadOptions options)
                at System.Deployment.Application.DownloadManager.DownloadDeploymentManifestBypass(SubscriptionStore subStore, Uri& sourceUri, TempFile& tempFile, SubscriptionState& subState, IDownloadNotification notification, DownloadOptions options)
                at System.Deployment.Application.ApplicationActivator.PerformDeploymentActivation(Uri activationUri, Boolean isShortcut)
                at System.Deployment.Application.ApplicationActivator.ActivateDeploymentWorker(Object state)
            --- Inner Exception ---
            System.Deployment.Application.InvalidDeploymentException (ManifestParse)
            - Exception reading manifest from file://(PATH)/SerialSNMPWinApp/SerialSNMPWinApp/bin/Release/SerialSNMPWinApp.application: the manifest may not be valid or the file could not be opened.
            - Source: System.Deployment
            - Stack trace:
                at System.Deployment.Application.ManifestReader.FromDocument(String localPath, ManifestType manifestType, Uri sourceUri)
                at System.Deployment.Application.DownloadManager.DownloadDeploymentManifestDirect(SubscriptionStore subStore, Uri& sourceUri, TempFile& tempFile, IDownloadNotification notification, DownloadOptions options, ServerInformation& serverInformation)
                at System.Deployment.Application.DownloadManager.FollowDeploymentProviderUri(SubscriptionStore subStore, AssemblyManifest& deployment, Uri& sourceUri, TempFile& tempFile, IDownloadNotification notification, DownloadOptions options)
            --- Inner Exception ---
            System.Deployment.Application.InvalidDeploymentException (SignatureValidation)
            - Manifest XML signature is not valid.
            - Source: System.Deployment
            - Stack trace:
                at System.Deployment.Application.Manifest.AssemblyManifest.ValidateSignature(Stream s)
                at System.Deployment.Application.ManifestReader.FromDocument(String localPath, ManifestType manifestType, Uri sourceUri)
            --- Inner Exception ---
            System.Security.Cryptography.CryptographicException
            - No signature was present in the subject.

            - Source: System.Deployment
            - Stack trace:
                at System.Deployment.Internal.CodeSigning.SignedCmiManifest.Verify(CmiManifestVerifyFlags verifyFlags)
                at System.Deployment.Application.Manifest.AssemblyManifest.ValidateSignature(Stream s)

    COMPONENT STORE TRANSACTION DETAILS
        No transaction information is available.



    I've tried the digital certification (checking the "Sign the ClickOnce manifests"), but it hasn't changed the error message any; is this because my certificate is untrusted?  I've also tried using the mageui.exe, but it didn't seem to do anything.

    Thanks in advance,
    Cassie
     

All Replies

  • Wednesday, August 23, 2006 1:35 PMdbcuser Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote
    In your project do you see [project]_TemperaryKey.pfx? This file will be created by VS2005 for you for testing purposes. Make sure the file is there.If it is not there then they option you choose to sign is not correct and if the file is there try deleting file and try again.
     
  • Wednesday, August 23, 2006 11:03 PMCassieC Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote
    I have tried deleting the temporary key, but the same log pops up.  I can paste the new one over now:

    PLATFORM VERSION INFO
        Windows             : 5.1.2600.131072 (Win32NT)
        Common Language Runtime     : 2.0.50727.42
        System.Deployment.dll         : 2.0.50727.42 (RTM.050727-4200)
        mscorwks.dll             : 2.0.50727.42 (RTM.050727-4200)
        dfdll.dll             : 2.0.50727.42 (RTM.050727-4200)
        dfshim.dll             : 2.0.50727.42 (RTM.050727-4200)

    SOURCES
        Deployment url            : file://francium/ENG/puma/RegressionTest/cassie/SerialSNMPWinApp.application
        Deployment Provider url        : file://francium/ENG/puma/RegressionTest/VBNetapps/SerialSNMPWinApp/SerialSNMPWinApp/bin/Release/SerialSNMPWinApp.application

    ERROR SUMMARY
        Below is a summary of the errors, details of these errors are listed later in the log.
        * Activation of file://\\francium\ENG\puma\RegressionTest\cassie\SerialSNMPWinApp.application resulted in exception. Following failure messages were detected:
            + The Deployment Provider specified in the manifest cannot be reached. Maybe due to network error and/or the deployment provider is not responding correctly.
            + Exception reading manifest from file://francium/ENG/puma/RegressionTest/VBNetapps/SerialSNMPWinApp/SerialSNMPWinApp/bin/Release/SerialSNMPWinApp.application: the manifest may not be valid or the file could not be opened.
            + Manifest XML signature is not valid.
            + No signature was present in the subject.


    COMPONENT STORE TRANSACTION FAILURE SUMMARY
        No transaction error was detected.

    WARNINGS
        There were no warnings during this operation.

    OPERATION PROGRESS STATUS
        * [8/23/2006 4:01:52 PM] : Activation of file://\\francium\ENG\puma\RegressionTest\cassie\SerialSNMPWinApp.application has started.

    ERROR DETAILS
        Following errors were detected during this operation.
        * [8/23/2006 4:01:55 PM] System.Deployment.Application.InvalidDeploymentException (Manifest)
            - The Deployment Provider specified in the manifest cannot be reached. Maybe due to network error and/or the deployment provider is not responding correctly.
            - Source: System.Deployment
            - Stack trace:
                at System.Deployment.Application.DownloadManager.FollowDeploymentProviderUri(SubscriptionStore subStore, AssemblyManifest& deployment, Uri& sourceUri, TempFile& tempFile, IDownloadNotification notification, DownloadOptions options)
                at System.Deployment.Application.DownloadManager.DownloadDeploymentManifestBypass(SubscriptionStore subStore, Uri& sourceUri, TempFile& tempFile, SubscriptionState& subState, IDownloadNotification notification, DownloadOptions options)
                at System.Deployment.Application.ApplicationActivator.PerformDeploymentActivation(Uri activationUri, Boolean isShortcut)
                at System.Deployment.Application.ApplicationActivator.ActivateDeploymentWorker(Object state)
            --- Inner Exception ---
            System.Deployment.Application.InvalidDeploymentException (ManifestParse)
            - Exception reading manifest from file://francium/ENG/puma/RegressionTest/VBNetapps/SerialSNMPWinApp/SerialSNMPWinApp/bin/Release/SerialSNMPWinApp.application: the manifest may not be valid or the file could not be opened.
            - Source: System.Deployment
            - Stack trace:
                at System.Deployment.Application.ManifestReader.FromDocument(String localPath, ManifestType manifestType, Uri sourceUri)
                at System.Deployment.Application.DownloadManager.DownloadDeploymentManifestDirect(SubscriptionStore subStore, Uri& sourceUri, TempFile& tempFile, IDownloadNotification notification, DownloadOptions options, ServerInformation& serverInformation)
                at System.Deployment.Application.DownloadManager.FollowDeploymentProviderUri(SubscriptionStore subStore, AssemblyManifest& deployment, Uri& sourceUri, TempFile& tempFile, IDownloadNotification notification, DownloadOptions options)
            --- Inner Exception ---
            System.Deployment.Application.InvalidDeploymentException (SignatureValidation)
            - Manifest XML signature is not valid.
            - Source: System.Deployment
            - Stack trace:
                at System.Deployment.Application.Manifest.AssemblyManifest.ValidateSignature(Stream s)
                at System.Deployment.Application.ManifestReader.FromDocument(String localPath, ManifestType manifestType, Uri sourceUri)
            --- Inner Exception ---
            System.Security.Cryptography.CryptographicException
            - No signature was present in the subject.

            - Source: System.Deployment
            - Stack trace:
                at System.Deployment.Internal.CodeSigning.SignedCmiManifest.Verify(CmiManifestVerifyFlags verifyFlags)
                at System.Deployment.Application.Manifest.AssemblyManifest.ValidateSignature(Stream s)

    COMPONENT STORE TRANSACTION DETAILS
        No transaction information is available.


     
  • Thursday, September 14, 2006 6:28 AMimakalic Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote
    Hi, I'm having the same problem, but with mandatory profiles. .NET 2 seems to think that it is the same a guest profile. Any ideas on how I can get the application to run?

    Thank you.
     
  • Friday, December 15, 2006 3:53 PMinvalid display name Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote
    Is there any solution to this? I am also experiencing the same problem while using mandatory profiles on a terminal server.
     
  • Friday, January 05, 2007 4:26 PMinvalid display name Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote
    Are there any thoughts on this?
     
  • Wednesday, January 17, 2007 5:08 PMinvalid display name Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote
    -bump-
     
  • Monday, January 29, 2007 6:01 PMinvalid display name Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote

    see http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=773794&SiteID=1

     
  • Monday, February 05, 2007 4:04 PMinvalid display name Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote
    nothing ?
     
  • Monday, February 12, 2007 4:00 PMinvalid display name Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote
    no acknowledgment from ms on this issue ?
     
  • Monday, February 19, 2007 4:06 PMinvalid display name Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote
    tock
     
  • Tuesday, February 27, 2007 3:24 PMinvalid display name Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote
    tick
     
  • Wednesday, February 28, 2007 7:22 PMCOBrien Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote
    We're having the same issue and I can't seem to find any work-around or resolution from Microsoft regarding this.  It also seems like this has been an issue for a LONG time and I'm concerned that Microsoft hasn't addressed this yet.
     
  • Monday, March 05, 2007 8:27 PMinvalid display name Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote
    no repsonses yet...
     
  • Monday, March 12, 2007 3:52 PMinvalid display name Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote
    100% reproducable BUG
     
  • Monday, March 19, 2007 3:34 PMinvalid display name Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote
    or is this a feature?
     
  • Friday, March 23, 2007 4:35 PMkryzchek Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote
    Do you get the same error if you try to run the following from the RUN box?

    rundll32.exe dfshim.dll,ShOpenVerbApplication http://www.yourserver.com/yourproject/yourapp.application
     
  • Monday, March 26, 2007 3:35 PMinvalid display name Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote

    I tried the command line and still not working. It generated the same error log as if the user had launched via the browser

    Here is the error log:

    PLATFORM VERSION INFO
     Windows    : 5.2.3790.65536 (Win32NT)
     Common Language Runtime  : 2.0.50727.42
     System.Deployment.dll   : 2.0.50727.42 (RTM.050727-4200)
     mscorwks.dll    : 2.0.50727.42 (RTM.050727-4200)
     dfdll.dll    : 2.0.50727.42 (RTM.050727-4200)
     dfshim.dll    : 2.0.50727.42 (RTM.050727-4200)

    SOURCES
     Deployment url   : http://deploy/ClickOnce/testapp/testapp.application

    ERROR SUMMARY
     Below is a summary of the errors, details of these errors are listed later in the log.
     * Activation of http://deploy/ClickOnce/testapp/testapp.application resulted in exception. Following failure messages were detected:
      + Exception reading manifest from http://deploy/ClickOnce/testapp/testapp.application: the manifest may not be valid or the file could not be opened.
      + Manifest XML signature is not valid.
      + The profile for the user is a temporary profile.


    COMPONENT STORE TRANSACTION FAILURE SUMMARY
     No transaction error was detected.

    WARNINGS
     There were no warnings during this operation.

    OPERATION PROGRESS STATUS
     * [3/26/2007 11:27:01 AM] : Activation of http://deploy/ClickOnce/testapp/testapp.application has started.

    ERROR DETAILS
     Following errors were detected during this operation.
     * [3/26/2007 11:27:01 AM] System.Deployment.Application.InvalidDeploymentException (ManifestParse)
      - Exception reading manifest from http://deploy/ClickOnce/testapp/testapp.application: the manifest may not be valid or the file could not be opened.
      - Source: System.Deployment
      - Stack trace:
       at System.Deployment.Application.ManifestReader.FromDocument(String localPath, ManifestType manifestType, Uri sourceUri)
       at System.Deployment.Application.DownloadManager.DownloadDeploymentManifestDirectBypass(SubscriptionStore subStore, Uri& sourceUri, TempFile& tempFile, SubscriptionState& subState, IDownloadNotification notification, DownloadOptions options, ServerInformation& serverInformation)
       at System.Deployment.Application.DownloadManager.DownloadDeploymentManifestBypass(SubscriptionStore subStore, Uri& sourceUri, TempFile& tempFile, SubscriptionState& subState, IDownloadNotification notification, DownloadOptions options)
       at System.Deployment.Application.ApplicationActivator.PerformDeploymentActivation(Uri activationUri, Boolean isShortcut)
       at System.Deployment.Application.ApplicationActivator.ActivateDeploymentWorker(Object state)
      --- Inner Exception ---
      System.Deployment.Application.InvalidDeploymentException (SignatureValidation)
      - Manifest XML signature is not valid.
      - Source: System.Deployment
      - Stack trace:
       at System.Deployment.Application.Manifest.AssemblyManifest.ValidateSignature(Stream s)
       at System.Deployment.Application.ManifestReader.FromDocument(String localPath, ManifestType manifestType, Uri sourceUri)
      --- Inner Exception ---
      System.Security.Cryptography.CryptographicException
      - The profile for the user is a temporary profile.

      - Source: System.Deployment
      - Stack trace:
       at System.Deployment.Internal.CodeSigning.SignedCmiManifest.VerifyPublicKeyToken()
       at System.Deployment.Internal.CodeSigning.SignedCmiManifest.Verify(CmiManifestVerifyFlags verifyFlags)
       at System.Deployment.Application.Manifest.AssemblyManifest.ValidateSignature(Stream s)

    COMPONENT STORE TRANSACTION DETAILS
     No transaction information is available.

     

     
  • Saturday, April 07, 2007 8:19 AMMunirul Abedin Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote
    This is a known issue, fix will be available in the next release. If this is a blocking issue for you consider filing a bug for QFE.
     
  • Thursday, April 12, 2007 7:08 PMinvalid display name Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote
    is this something that is fixed in the .net 3.0 framework?
     
  • Wednesday, May 23, 2007 8:28 PMrabidrobot417 Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote
    Also getting this very error and it is maddening.  No key is good enough. bump
     
  • Wednesday, May 23, 2007 9:58 PMMunirul Abedin Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote
    Thanks a lot for your feedback. It was a great help, based on the forum posts we have already resolved this issue. Unfortunately fix is not available in 3.0, you will get it in Orcas (3.5) beta2 release and later in RTM release.
     
  • Thursday, October 18, 2007 3:13 PMjkaater Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote
    IMPORTANT NOTE: The current version of ClickOnce will only work properly in Internet Explorer. In particular if you try to download using Firefox the following error message will appear:

    "Cannot Start Application. Cannot download the application. The application is missing required files. Contact application vendor for assistance."

    Microsoft are working on cross browser support for ClickOnce - if you're interested read more here.
    A patch for Firefox that will enable it to run ClickOnce properly is available here.
     
  • Wednesday, March 11, 2009 10:15 PMBill2010 Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote
    Hmmmm.... interesting. We are running Visual Studio 2008 and the ClickOnce WinForm is using .NET Framework 3.5.... and this just cropped up on some of our machines today for the first time.

    Not encouraging. :(
     
  • Thursday, March 12, 2009 5:05 PMRobinDotNetMVP, ModeratorUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote
    If you want help with this, you are going to have to give details.

    RobinS.
    GoldMail.com
    Ts'i mahnu uterna ot twan ot geifur hingts uto.
     
  • Thursday, May 28, 2009 7:39 PMStorm Bringer Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote

    Hello,

     

                    We are having a similar problem.  After dozens of successful installs globally, we have a user who cannot install the application via our click-once deployment.  They receive the following error message:

     

    PLATFORM VERSION INFO

                    Windows                                            : 5.0.2195.262144 (Win32NT)

                    Common Language Runtime     : 2.0.50727.832

                    System.Deployment.dll                               : 2.0.50727.832 (QFE.050727-8300)

                    mscorwks.dll                                    : 2.0.50727.832 (QFE.050727-8300)

                    dfdll.dll                                                : 2.0.50727.42 (RTM.050727-4200)

                    dfshim.dll                                           : 2.0.50727.42 (RTM.050727-4200)

     

    SOURCES

                    Deployment url                                               : http://sgofgridapp06/GRIDClient/GRID.Client.application

     

    ERROR SUMMARY

                    Below is a summary of the errors, details of these errors are listed later in the log.

                    * Activation of http://sgofgridapp06/GRIDClient/GRID.Client.application resulted in exception. Following failure messages were detected:

                                   + Exception reading manifest from http://sgofgridapp06/GRIDClient/GRID.Client.application: the manifest may not be valid or the file could not be opened.

                                   + Manifest XML signature is not valid.

                                   + O sistema não pode encontrar o arquivo especificado.

     

     

    COMPONENT STORE TRANSACTION FAILURE SUMMARY

                    No transaction error was detected.

     

    WARNINGS

                    There were no warnings during this operation.

     

    OPERATION PROGRESS STATUS

                    * [5/28/2009 11:46:14 AM] : Activation of http://sgofgridapp06/GRIDClient/GRID.Client.application has started.

     

    ERROR DETAILS

                    Following errors were detected during this operation.

                    * [5/28/2009 11:46:37 AM] System.Deployment.Application.InvalidDeploymentException (ManifestParse)

                                   - Exception reading manifest from http://sgofgridapp06/GRIDClient/GRID.Client.application: the manifest may not be valid or the file could not be opened.

                                   - Source: System.Deployment

                                   - Stack trace:

                                                   at System.Deployment.Application.ManifestReader.FromDocument(String localPath, ManifestType manifestType, Uri sourceUri)

                                                   at System.Deployment.Application.DownloadManager.DownloadDeploymentManifestDirectBypass(SubscriptionStore subStore, Uri& sourceUri, TempFile& tempFile, SubscriptionState& subState, IDownloadNotification notification, DownloadOptions options, ServerInformation& serverInformation)

                                                   at System.Deployment.Application.DownloadManager.DownloadDeploymentManifestBypass(SubscriptionStore subStore, Uri& sourceUri, TempFile& tempFile, SubscriptionState& subState, IDownloadNotification notification, DownloadOptions options)

                                                   at System.Deployment.Application.ApplicationActivator.PerformDeploymentActivation(Uri activationUri, Boolean isShortcut)

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

                                   --- Inner Exception ---

                                   System.Deployment.Application.InvalidDeploymentException (SignatureValidation)

                                   - Manifest XML signature is not valid.

                                   - Source: System.Deployment

                                   - Stack trace:

                                                   at System.Deployment.Application.Manifest.AssemblyManifest.ValidateSignature(Stream s)

                                                   at System.Deployment.Application.ManifestReader.FromDocument(String localPath, ManifestType manifestType, Uri sourceUri)

                                   --- Inner Exception ---

                                   System.Security.Cryptography.CryptographicException

                                   - O sistema não pode encontrar o arquivo especificado.

     

                                   - Source: System.Deployment

                                   - Stack trace:

                                                   at System.Deployment.Internal.CodeSigning.SignedCmiManifest.VerifyPublicKeyToken()

                                                   at System.Deployment.Internal.CodeSigning.SignedCmiManifest.Verify(CmiManifestVerifyFlags verifyFlags)

                                                   at System.Deployment.Application.Manifest.AssemblyManifest.ValidateSignature(Stream s)

     

    COMPONENT STORE TRANSACTION DETAILS

                    No transaction information is available.

     

                    For those of you not fluent in Portuguese, "O sistema não pode encontrar o arquivo especificado" translates to "The System could not find the file specified."

     

                                   I'm not sure what the problem could possibly be or what to do next.

     

    Please give me any advice you have.

    Storm Bringer

    WCF the next frontier
     
  • Friday, October 23, 2009 8:09 PMVern DeMille Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote
    Ok all, here is what I found that fixed this problem for me:


    Clean your solution.
    Delete all files and folders from your drop site.
    Rebuild all.
    Republish.
    On the client side, remove all previous versions of the deployment.
    Then reinstall. This fixed it for my team.
     
  • Friday, November 06, 2009 3:22 PMMr. Javaman Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote
    Ouch! If that was the fix this is a bug....
    Javaman