none
CheckAndDownloadUpdateAsync - fails with catastrophic error

    Question

  • Our application seems to update itself fine using MSdev environment but once we deploy it to the production server we get a catastrophic error when there is a download available.

     

    We deployed to an IIS box, is there anything special we have to set?  This is quite frustrating since it give no clue on what is going wrong.

    Thursday, June 03, 2010 3:49 PM

Answers

  • I have the exact same problem. Any news on this problem?

     

    Update:

    I just changed the mime type from application/x-silverlight-app to application/octet-stream and e.Error in CheckAndDownloadUpdateAsync became "System.Security.SecurityException:Cannot update application, the installed application and update
    candidate differ in certificate/signature state."

    Then I found this thread:

    http://forums.silverlight.net/forums/p/166799/378510.aspx#378510

    Post by JoNaS:

    "Hi Jonathan, thanks for your concern. I have found out what the problem is. The Application is installed as full trust, but it is not signed and hence the error.

    So for all of you out there, if you have a full trust out-of-browser silverlight 4 app and want to check for updates, you need to sign your app."

    This should solve my problem.

    Wednesday, June 23, 2010 10:14 AM

All replies

  • Update on this,

     

    Tracing it with fiddler I see that the complete XAP file has been sent down to the client.  The failure must be somewhere in the client runtime.

     

    Question, does the client runtime use the description in any way to do a comparison check?  We put the version of the source in this description.

    Running out of options, any ideas would be great

    Friday, June 04, 2010 8:47 AM
  • r u using any web service or some thiing like that

    Webclient obj = new WebClient(uri);

    Friday, June 04, 2010 9:04 AM
  • http://msdn.microsoft.com/en-us/library/system.windows.application.checkanddownloadupdateasync(VS.95).aspx
    Friday, June 04, 2010 9:10 AM
  • Usama,

     Thanks for the reply.  Have been traveling so sorry for the slow response.

     

    No I am not using the webclient

    Doing exactly as the documentation states.  Moved the code from app.cs to MainWindow.cs to see if there was a threading issue or reentrant issue and no there is none.

    The application is being downloaded to the client but it seems to fail during the install process.  Quite frustrating.  Cant seem to get around this at all.

    Any other ideas?

    Wednesday, June 09, 2010 5:16 PM
  • Hi Cconner101,

    What does your "catastrophic error" really mean?  Do you mean that it throws an exception or just not work as desired?   Please clear your cache and have a test.

    Best regards,

    Jonathan

    Thursday, June 10, 2010 10:15 PM
  • This is the reply from CheckAndDownloadUpdateCompleted event

    e.error =

    System.Exception: Catastrophic failure (Exception from HRESULT:0x8000FFFF (E_UNEXPECTED))

    As stated before, using fiddler i can see the the application is downloaded from the server but seems to fail during installation.  This works fine in local dev mode but when an installed OOB application is running on a customer machine and there needs to be an update we get this message all the time

    Monday, June 14, 2010 11:51 AM
  • I have the exact same problem. Any news on this problem?

     

    Update:

    I just changed the mime type from application/x-silverlight-app to application/octet-stream and e.Error in CheckAndDownloadUpdateAsync became "System.Security.SecurityException:Cannot update application, the installed application and update
    candidate differ in certificate/signature state."

    Then I found this thread:

    http://forums.silverlight.net/forums/p/166799/378510.aspx#378510

    Post by JoNaS:

    "Hi Jonathan, thanks for your concern. I have found out what the problem is. The Application is installed as full trust, but it is not signed and hence the error.

    So for all of you out there, if you have a full trust out-of-browser silverlight 4 app and want to check for updates, you need to sign your app."

    This should solve my problem.

    Wednesday, June 23, 2010 10:14 AM
  • Hello

    Its SOS, help is really needed for Silverlight SL5 OOB application’s auto update

    I also have the same problem, my Silverlight SL5 OOB application’s auto update feature work perfectly with our development server. But when I upload to our client server, application is never get auto updated. Really strange!!!

    When I try to get download and install directly from the site, I always get the newer version but SL OOB  app does not get automatically updated using App.Current.CheckAndDownloadUpdateAsync() method

    Consider following points.

    1)    I have signed both the xap version (installed and the server update which require to be updated) with Verisign digital certificate “Microsoft Authenticode”.

    2)    OOB App Project property

    a.    Enable running application out of the browser – true

    b.    Require elevated trust when running in browser – true

    Following is my source code for version update:

    private void MainView_Loaded(object sender, RoutedEventArgs e) //It’s in MainView.cs not in App.cs

    {

    App.Current.CheckAndDownloadUpdateCompleted += newCheckAndDownloadUpdateCompletedEventHandler(Current_CheckAndDownloadUpdateCompleted);

    App.Current.CheckAndDownloadUpdateAsync();

               

    }

    void Current_CheckAndDownloadUpdateCompleted(object sender, CheckAndDownloadUpdateCompletedEventArgs e)

    {

                if (e.Error == null && e.UpdateAvailable)

                {

                    MessageBox.Show(“Application is updated, please restart”);

                }

    }

    Getting System.Exception: Catastrophic failure (Exception from HRESULT: 0x8000FFFF (E_UNEXPECTED))

    I also have posted the same in http://social.msdn.microsoft.com/Forums/en-US/silverlightarchieve/thread/41fd8511-f2ca-4716-96e9-85405a2e29d1/ forum 

    Thanks for everyone help in advance

    Friday, February 15, 2013 2:19 PM
  • I would like some more information about this as well. We have rarely had this problem in the past but now it seems to be happening all the time.

    I am starting to suspect that it is related to https because this is the first time we've used https on a live environment and changing the IIS settings in this area seems to have alleviated the problem

    Monday, September 01, 2014 6:15 AM
  • Hello

    I have the same problem, I use https mode with "Windows Authentication".

    I have solved it by adding "Anonymous Authentication" on ClientBin folder.

    Monday, February 06, 2017 5:05 PM