Error #2046

Report · May 05, 2015

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?

Report · May 06, 2015

Same problem here .

Thanks

Report · May 06, 2015

We've replaced the files, but it seems does not work..

Report · May 06, 2015

First. Delete All files in Chrome.

C:\Users\????????\AppData\Local\Google\Chrome\User Data\Default\Pepper Data\Shockwave Flash\CacheWritableAdobeRoot\AssetCache\?????\???.swz

Report · May 06, 2015

Thank you for your advice, I'll take a try.

Report · May 06, 2015

Hello,

Same pb. no swz in cache folder (cache cleared).

But it does not work 😞

Report · May 06, 2015

[FLEX-34833] Error #2046 appearing on custom application - preventing users from logging in - ASF JI...

Report · May 06, 2015

I use IE9 and delete all history and cache, but still can't work...

Report · May 06, 2015

Success here.

Replaced the swz files in our original war-file with the new swz files, as described by amyjocoleman
Redeployed the war-file to the application server

On the client PC:

In the browser, clear the browser cache (history, temp files etc)
In the browser go to: http://www.macromedia.com/support/documentation/en/flashplayer/help/settings_manager03.html#117498
Uncheck the 2 checkboxes:

Allow third party Flash content to store data on your computer
Store common Flash components to reduce download time

Close the browser
Reopen the Browser
Test you URL

(If everything works works in the browser you can reenable the check boxes in the Global Settings Storage panel above)

Report · May 06, 2015

Our clients are not on the internet, they are intranet kiosk machines. Is there a way to do this process below

In the browser go to: http://www.macromedia.com/support/documentation/en/flashplayer/help/settings_manager03.htm l#117498
Uncheck the 2 checkboxes:

without being on the internet, maybe manually deleting certain files?

Report · May 06, 2015

It seems that everyone has the general idea of how to resolve the problem, which is great. We are close to rolling out instructions for the fix to our clients. We have been on calls with Adobe over the last couple of hours and have asked them to confirm that the resolution we have been discussing here is in fact the official solution from Adobe. We have also asked for any ideas for a solution which is a bit simpler for our clients to deploy. So, we hope to have this info from Adobe in the next few hours and will share it with you then. Good luck everyone.

Report · May 06, 2015

To answer the question about the expiration date in the new files: Based on what we see in the new files, the date is 1-Nov-2025. Hopefully Adobe will confirm.

Report · May 06, 2015

Thank you to everyone that contributed to this thread. I'm still in the process of going through all of the .swz files hosted on fpdownload.adobe.com to determine their expatriation date, but we believe they are all valid until at least 2025. Once we finish this, we'll move to the flex sdk's still hosted on adobe and determine which are now out of date.

As noted previously, the .swz signatures supplied in the flex 4.1.0.16076 SDK's expired this morning (5/6/2015). Customers are now being advised to point their apps (or download) the .swz files hosted on fpdownload.adobe.com. The files hosted on fpdownload have 15 year certificates, expiring on November 1st, 2025 or later. The exact dates for the set of files lists on this thread are:

datavisualization_4.1.0.16076.swz November 1st, 2025

framework_4.1.0.16076.swz November 1st, 2025

framework_4.1.0.21490.swz July 24th, 2026

osmf_flex.4.0.0.13495.swz November 1st, 2025

rpc_4.1.0.16076.swz November 1st, 2025

spark_4.1.0.16076.swz November 1st, 2025

sparkskins_4.1.0.16076.swz November 1st, 2025

Thank you again for all your help and investigation. Your comments here were able to bring our west cost folks up to speed very fast this morning.

Report · May 07, 2015

And what about 4.6 swz ? When will we have the same issue ?

Report · May 07, 2015

The 4.6.0.23201 SDK hosted on Adobe.com contains SWZ's that expire in 2026. The 4.6 SWZ's on fpdownload.adobe.com also expire in 2026.

Path	Expiration
http://fpdownload.adobe.com/pub/swz/flex/4.6.0.23201/advancedgrids_4.6.0.23201.swz	10/31/2026
http://fpdownload.adobe.com/pub/swz/flex/4.6.0.23201/charts_4.6.0.23201.swz	10/31/2026
http://fpdownload.adobe.com/pub/swz/flex/4.6.0.23201/framework_4.6.0.23201.swz	10/31/2026
http://fpdownload.adobe.com/pub/swz/flex/4.6.0.23201/mx_4.6.0.23201.swz	10/31/2026
http://fpdownload.adobe.com/pub/swz/flex/4.6.0.23201/osmf_1.0.0.16316.swz	10/31/2026
http://fpdownload.adobe.com/pub/swz/flex/4.6.0.23201/rpc_4.6.0.23201.swz	10/31/2026
http://fpdownload.adobe.com/pub/swz/flex/4.6.0.23201/spark_4.6.0.23201.swz	10/31/2026
http://fpdownload.adobe.com/pub/swz/flex/4.6.0.23201/spark_dmv_4.6.0.23201.swz	10/31/2026
http://fpdownload.adobe.com/pub/swz/flex/4.6.0.23201/sparkskins_4.6.0.23201.swz	10/31/2026
http://fpdownload.adobe.com/pub/swz/flex/4.6.0.23188/advancedgrids_4.6.0.23188.swz	10/31/2026
http://fpdownload.adobe.com/pub/swz/flex/4.6.0.23188/charts_4.6.0.23188.swz	10/31/2026
http://fpdownload.adobe.com/pub/swz/flex/4.6.0.23188/framework_4.6.0.23188.swz	10/31/2026
http://fpdownload.adobe.com/pub/swz/flex/4.6.0.23188/mx_4.6.0.23188.swz	10/31/2026
http://fpdownload.adobe.com/pub/swz/flex/4.6.0.23188/osmf_1.0.0.16316.swz	10/31/2026
http://fpdownload.adobe.com/pub/swz/flex/4.6.0.23188/rpc_4.6.0.23188.swz	10/31/2026
http://fpdownload.adobe.com/pub/swz/flex/4.6.0.23188/spark_4.6.0.23188.swz	10/31/2026
http://fpdownload.adobe.com/pub/swz/flex/4.6.0.23188/spark_dmv_4.6.0.23188.swz	10/31/2026
http://fpdownload.adobe.com/pub/swz/flex/4.6.0.23188/sparkskins_4.6.0.23188.swz	10/31/2026
http://fpdownload.adobe.com/pub/swz/flex/4.6.0.23188/textLayout_2.0.0.232.swz	10/31/2026

Report · May 07, 2015

Hi,

Our customers have experienced the same issue.

Our Flex application was isolated from the Internet and could not update the SWZ files from the Adode websites.

The Flex cache contained the old SWZ files, which were expired. Because the application could not reach the Internet, the cache was not updated even if our server application (in a war) had the new SWZ files.

We have to delete manually the Flex cache on each physical client to allow them to download the new SWZ files hosted in the WAR file of the server application.

In our situation, if we have got enough time, we could also have modified the Flex builder to update the URL of the SWZ files to make our own SWZ file provider inside our DMZ : <runtime-shared-library-path> <path-element>libs/textLayout.swc</path-element> <rsl-url>http://fpdownload.adobe.com/pub/swz/tlf/1.1.0.604/textLayout_1.1.0.604.swz</rsl-url> <policy-file-url>http://fpdownload.adobe.com/pub/swz/crossdomain.xml</policy-file-url> <rsl-url>textLayout_1.1.0.604.swz</rsl-url> <policy-file-url></policy-file-url> </runtime-shared-library-path>

Report · May 17, 2015

If we have a group of Windows computers being affected with this 2046 error, do we have a tool in place that end users can use to fix this automatically rather than performing manual steps which might not be simple for less computer literate users ?

Report · May 07, 2015

Hi Chris,

we exchanged all files from your list that are included in our system.

Our system did not include osmf_flex.4.0.0.13495.swz and framework_4.1.0.21490.swz

We still receive the Error #2046 message even with brand new browser clients without any cache files.

Do you have any suggestion?

The build process includes also directories with swc-files. Could this cause a problem? (however the War file includes a "rsl" directory with the new swz-files)

Best regards,

Werner

Report · May 07, 2015

Hi Chris,

Is there a way to check the Expiration Date of the new swz-files?

Of course, I believe the Expiration date on which you've described above.

However, my customer has requested the evidence.

Best regards,

Keiichi

Report · May 08, 2015

恵一玉山 wrote:

Hi Chris,

Is there a way to check the Expiration Date of the new swz-files?

Of course, I believe the Expiration date on which you've described above.

However, my customer has requested the evidence.

Best regards,

Keiichi

We’re investigating coming up with a more official / automated way for customers to accomplish this.

In the meantime, here’s how I did this:

Open each SWZ file up in binary mode, scroll towards the bottom of the file, and look for a set of numbers to find the yymmdd format for the certification applied and expired date

Look at the pattern with the red box around it. The top one is the cert creation date, the bottom is the cert expiration date (in the form YYMMDD). You may see several similar patterns like this in the file, but look for the one which has an accurate description wrt. the particular RSL you’re looking at (alternatively, you can look for the closest expiration date)

Report · May 10, 2015

I urgently need working copies for these files. Can you advise?

http://fpdownload.adobe.com/pub/swz/flex/4.5.1.21328/framework_4.5.1.21328.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.5.1.21328/spark_4.5.1.21328.swz

http://fpdownload.adobe.com/pub/swz/flex/4.5.1.21328/sparkskins_4.5.1.21328.swz

http://fpdownload.adobe.com/pub/swz/flex/4.5.1.21328/rpc_4.5.1.21328.swz

http://fpdownload.adobe.com/pub/swz/flex/4.5.1.21328/mx_4.5.1.21328.swz

Thank you.

Report · May 10, 2015

Valentin Manthei wrote:

I urgently need working copies for these files. Can you advise?

http://fpdownload.adobe.com/pub/swz/flex/4.5.1.21328/framework_4.5.1.21328.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.5.1.21328/spark_4.5.1.21328.swz

http://fpdownload.adobe.com/pub/swz/flex/4.5.1.21328/sparkskins_4.5.1.21328.swz

http://fpdownload.adobe.com/pub/swz/flex/4.5.1.21328/rpc_4.5.1.21328.swz

http://fpdownload.adobe.com/pub/swz/flex/4.5.1.21328/mx_4.5.1.21328.swz

Thank you.

These files are valid to the dates below:

framework_4.5.1.21328.swz expires 05/29/2026

mx_4.5.1.21328.swz expires 05/29/2026

rpc_4.5.1.21328.swz expires 05/29/2026

spark_4.5.1.21328.swz expires 05/29/2026

sparkskins_4.5.1.21328.swz expires 05/29/2026

textLayout_1.1.0.604.swz expires 11/01/2025

Report · May 10, 2015

Thanks very much for your response.

I have confirmed the expiration date of swz files in that way.

Report · May 07, 2015

Hi,

I was getting the same error and after relaced swz files and cleared cache i am having error #2034.

Thank you in advance for your help.

Med.

Report · May 08, 2015

Mohamed Bassami wrote:

Hi,

I was getting the same error and after relaced swz files and cleared cache i am having error #2034.

Thank you in advance for your help.

Med.

If you haven't already, can you try restarting the system?

Report · May 12, 2015

Hi guys,

I have meet the similar issue, after follow these steps, 1. replace all SDK swz file with the new one. 2. restart the service (in fact, I restart the machine). 3. clear client cache by use the "Delete Data" button in flash player global setting panel. reopen the safari or firefox, what I get is Error #2034.