Error #2046

[amyjocoleman]

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?

[amyjocoleman]

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?

[Guest]

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]

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.

[johnnyy51050398]

Hi Amyjocoleman,

I am facing same issue with you today. Cloud you tell me which kind of updated versions you use is work well now? Please tell me the answer thanks very much!

[Guest]

Could you kindly help us with the download link for the updated 4.1 SDK files ?

Thanks.

[Guest]

Same problem here.  Is it possible to specify the link with the updated 4.1 SDK files please!

[johnnyy51050398]

Hi DESmirnov

You mentioned "using complementary SWF files (with debug info) instead of SWZ". I use textLayout_1.1.0.604.swz, framework_4.1.0.16076.swz, spark_4.1.0.16076.swz and rpc_4.1.0.16076.swz. Do you mean use textLayout.swc, framework.swc, spark.swc and rpc.swc to replace them? Thanks very much.

[Guest]

I meant SWF files from Flex SDK.
But at the moment using updated SWZ (as said by amyjocoleman) looks better.
Anyway, there is no 100% solution yet, all are working on it...

[jimb7174]

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?

[Guest]

We faced exactly the same issue today.

Have you identified a solution ?

[johnnyy51050398]

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

[FlexAirWow]

Same problem here.

I am facing same issue with you today.

[amyjocoleman]

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]

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.

[larry_e]

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.  

[stakezaki]

Right. it works without rebuilding my application swf.

I just put SWZ files on the App Server's directory the same as swf file.

These files are with a new signature expiration date, I think.

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

And we tested with Chrome and Firefox. I just did a normal browser cache clear.

Also,I tested build using complementary SWF files (with debug info) instead of SWZ.

[stakezaki]

It works HTTPS only.

[sky470]

Ok it works with all browser (IE, Chrome, Firefox)

Just,  we need to clear data browser and flash cache

"You can also manually accomplish this task by deleting the contents of the following folders:

Windows (tip: copy and paste these paths into the path bar in an Explorer window)

%appdata%\Adobe\Flash Player

%appdata%\Macromedia\Flash Player

"

[WernerE]

Congratulations!

We still have the problem described above: Since early this morning our customers cannot login any more into our complex FLEX based application installed by WAR files an different servers. Any attempts to delete swz-files in different folders on client computers did not work.

What exactly belongs to YOUR solution? Was it sufficient to delete all files in the directores "%appdata%\Adobe\Flash Player"  and "%appdata%\Macromedia\Flash Player" or did you also add swz-files to one of your application-folders?

[larry_e]

For what its worth I just figured out how to get it working for our clients.  

1.)   put the following swz files in App Server's directory, the same location as swf file.

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

2.)   to get ie and firefox working, just had to clear the cache, using the browsers built in cache clearing.  

3.)  to get chrome working, which is what most of our clients use,  the browser built in clear cache did NOT work.  had to manually delete all the swz files from the following folder

C:\Documents and Settings\Administrator\Local Settings\Application Data\Google\Chrome\User Data\Default\Pepper Data\Shockwave Flash\CacheWritableAdobeRoot\AssetCache\......

Now I just am trying to think of an easy way, or at least a process,  to do this across multiple versions and 100's of clients

Does anyone understand why this problem existed?  What was the point of having expiring certificates in these flex swz files?   It feels like for whatever reason more up to date chrome browsers with more up to date flash player plugins were not affected at least for us, but I don't understand why that is the case either.  Was there something special about May 5 2015?

Thanks to everyone on this board for helping to save the day.   

[larry_e]

I am thinking that maybe going to this link from a chrome client you could delete those swz files also.  Can anyone confirm that?   None of our clients are on the internet so they do not have access to this link?   Is there a way to access this link locally, or just do what I ended up doing. 

Adobe - Flash Player : Settings Manager - Global Storage Settings Panel

[larry_e]

Also does anyone know if these new swz files have an expiration date, or do our future selves many years from now have another bad day to look forward to?   Is there a way to find out?   

[WernerE]

Hi,

our system included also following file:

  textLayout_4.1.0.16076.swz

Does anybody know, where to find a new version of this file with a new certificate - if neccessary.

Would be grateful for any help!

[WernerE]

Hi,

all problems resolved: System login is possible again!

We had to replace the file  textLayout_4.1.0.16076.swz with the result of http://fpdownload.adobe.com/pub/swz/tlf/1.1.0.604/textLayout_1.1.0.604.swz and rename it to textLayout_4.1.0.16076.swz

Thank you all very much for your work on this issue!

Regards,

Werner