Skip to main content
amyjocoleman
amyjocoleman
Participating Frequently
May 6, 2015
Question

Error #2046

  • May 6, 2015
  • 16 replies
  • 50806 views

We are receiving Error #2046 when loading the flash component (delivered as a.SWF) for one of our products. We may have a problem with the certificate that was used to sign the component.  While we work on fixing the certificate, is there any way to avoid the error by making a change on the browser?

    This topic has been closed for replies.

    16 replies

    Show previous replies
    P
    PienAcude
    Participant
    May 6, 2015

    Same problem here .

    Thanks

    amyjocoleman
    amyjocolemanAuthor
    Participating Frequently
    May 6, 2015

    Latest update for everyone:

    We are trying to contact Adobe but we are not having any luck.  It looks like they have updated the problematic SWZ files with a new signature expiration date.

    Here are the quick instructions that we are currently testing.  We are still seeing some issues after following these steps, so we may be missing a necessary step or two.

    1.       Delete all deployed SWZ files

    2.       Replace with files downloaded from the adobe site.  For example, we need to replace these:

     

    http://fpdownload.adobe.com/pub/swz/flex/4.1.0.16076/spark_4.1.0.16076.swz

    http://fpdownload.adobe.com/pub/swz/flex/4.1.0.16076/datavisualization_4.1.0.16076.swz

    http://fpdownload.adobe.com/pub/swz/flex/4.1.0.16076/rpc_4.1.0.16076.swz

    http://fpdownload.adobe.com/pub/swz/flex/4.1.0.16076/framework_4.1.0.16076.swz

    http://fpdownload.adobe.com/pub/swz/flex/4.1.0.16076/osmf_flex.4.0.0.13495.swz

    http://fpdownload.adobe.com/pub/swz/tlf/1.1.0.604/textLayout_1.1.0.604.swz

    http://fpdownload.adobe.com/pub/swz/flex/4.1.0.16076/sparkskins_4.1.0.16076.swz

     

    then, clear the Flash cache and restart the app server.

    BE SURE TO TEST THOROUGHLY.  RESULTS SEEM TO VARY BY BROWSER AND BY APP SERVER.

      stakezaki
      stakezaki
      Participant
      May 6, 2015

      It works. I just did the following steps.

      1. Place the SWZ files(as said by amyjocoleman) on the App Server's directory(same as swf).

      2. Clear the Flash(browser) cache.

      It seems that if the SWZ files form Adobe site occurs expiration error, then it looks into the App Server and

      SWZ files with a new signature expiration date are taken.

      L
      larry_e
      Participating Frequently
      May 6, 2015

      I could not get that to work swz copy and cache clear solution to work.  It sounds like you did not have to rebuild you application swf, is that accurate?   Did you just do a normal browser cache clear, and did you manually go in and delete things?  What browser did it work on?   Thanks for the help.  

      F
      FlexAirWow
      Participant
      May 6, 2015

      Same problem here.

      I am facing same issue with you today.

        A
        Anonymous
        May 6, 2015

        We faced exactly the same issue today.

        Have you identified a solution ?

        J
        johnnyy51050398
        Participant
        May 6, 2015

        Not yet. I just wait for someone who can give the solution now.

        J
        jimb7174
        Inspiring
        May 6, 2015

        Hi - We are seeing exactly same issue here.  Is there anyone from Adobe.com that can comment on this issue and when a fix will be made live?

        amyjocoleman
        amyjocolemanAuthor
        Participating Frequently
        May 6, 2015

        Update.  We have discovered that the error is specifically caused by the expiration of the digital signature on multiple Adobe SWZ files that are part of the Flex 4.1 SDK.  Apparently the signature was set to expire at the end of the day yesterday.

        What we need:

        1. We need immediate developer level support to help us find a work-around.  For example, is there a browser setting or flash setting that we could change that would allow the .SWZ file to load even if the signature is not valid?
        2. We need assistance with selecting the best possible solution.  For example, can we get updated versions of any files with expired signatures?

        Can someone from Adobe please provide us with assistance or contacts that can help?

        A
        Anonymous
        May 6, 2015

        We faced exactly the same issue today. And our analysis results are similar.
        As quick workaround we suggest using complementary SWF files (with debug info) instead of SWZ.
        Please share better solution if you will find it.

          amyjocoleman
          amyjocolemanAuthor
          Participating Frequently
          May 6, 2015

          Thanks very much for your response.  Updated versions of the 4.1 SDK files with corrected signatures are available on Adobe.com.  We are now testing with these versions.  Unfortunately, we believe that using either these new SWZ files or the alternate SWF files may require us to rebuild all of our applications and supply updated versions to all of our clients...which is a huge undertaking given the number of apps and the multiple versions that our clients have deployed on-premise around the world.  So, we are also testing whether there is a way to merely "drop" the updated SWZ files onto a previously deployed site.

          Terms & ConditionsAccessibility statement
          Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices