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 12, 2015

If you haven't already, could you try restarting the system that is getting #2034? I've seen this come up before and a restart usually clears it up.

Report · May 13, 2015

I gave it a try but still get Error #2034, is it related to the flash player version I used? I used version is 16,0,0,305, BTW, the Flex SDK version we used before has the security patch which are provided by Adobe, the version is 4.1.0.16076A‌, not sure whether it has impact here.

Report · May 18, 2015

Hello Chris,

Thank you for your answer.

I am still getting the same error #2034 after rebooting and clearing cache.

For another application, i have not done any change and it is working fine with the old swz.

Regards,

Thank you for you help.

Med.

Report · May 18, 2015

Hello,

It is working for me now for the following scenarios:

Change made in EAR:

I have replaced the existing SWZ with the following:

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/framework_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/spark_4.1.0.16076.swz

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

To generate a new EAR:

I have replaced in \flex_sdk_4.1A\frameworks\rsls\ the following SWZ with the new ones.

osmf_flex.4.0.0.13495.swz

textLayout_1.1.0.604.swz

framework_4.1.0.21490.swz (delete the exiting one and rename framework_4.1.0.16076.swz to framework_4.1.0.21490.swz)

rpc_4.1.0.16076.swz

spark_4.1.0.16076.swz

sparkskins_4.1.0.16076.swz

Regards,

Report · May 08, 2015

Hi as an end user this has caused me a lot of problems on an embedded machine GUI. I tried deleting the cache on all my browsers and flash but the problem still persisted until I changed my PC date to a random date in 2014 then cleared the cache and flash again. Once done the next time you open the browser and attempt to log on to the device everything downloads as normal This is obviously just a work around until the fixed server files can be updated with a firmware update which is done by the GUI interface in my case. Built-in obsolecence brilliant.

Hope this gets you out of trouble too.

Report · May 14, 2015

I haven't made any of the changes to the .swz files and some desktop clients are able to log in and some can't. I'm reluctant to make any changes, because some are reporting getting error #2304 after making the changes. Any advice is appreciated.

Report · Jun 03, 2015

Hi,

We have resolved this issue for affected customers on Chrome & IE thanks to the helpful details however, users with Chromebooks are still reporting the problem. Please could someone advise what to do beyond simply clearing the browser cache for Chromebook as I do not have access to one of these devices? How / Where do I clear the swz from the local cache?

Many thanks!

Report · Jun 14, 2015

We ran into this very same issue today, although its an AIR app that is currently deployed to the field, making updates more problematic.

We run a mixed AIR/Java app, and the Java side launches the AIR app. When some of our products restarted in the field, the AIR app failed to load. Looking at the trace log, it was getting the same Error #2046 The loaded file did not have a valid signature. That search led me here. We're using Flex 4.5.1 and according Chris Campbell, 4.5.1 has valid expiration dates. We even looked our our local .swz files and compared. They also show the 2025/2026 dates. However, the app still failed to launch w/ the same error. Using strace on Linux, we could tell it was getting to the framework.swz and then stopping. So we're not sure if there is something else in those swz files that has dates. We did some testing by setting the local clock back and was able to get it to fail or work based on the date (I think between June 12 and June 13).

Our fix was to just bite the bullet and statically link in the framework SWC files. I'm still a little perplexed why the app was failing to load the RSLs when the expiration dates should be valid, but it was.

- John O

Report · Jun 15, 2015

Hi John,

I suspect you ran into a slightly different permutation of this issue. If you're using AIR, are you using HTMLLoader and loading swf content into the AIR application? Is this app using a shared runtime?

The issue over the weekend (on Jun 13 01:01:42 2015 GMT to be exact) was due to an older version of Flash Player (10.x) having it's 10 year root certificate expire. We updated Flash Player back in 2011 with a new 15 year cert, but it sounds like your app might not have access to this...

Chris

Report · Jun 15, 2015

Our AIR app is using Flex 4.5.1 and runtime-shared-library-path (specified in our Ant build using mxmlc). We are using local copies of the framework .swz files. Switching it over to not use the RSLs seemed to fix our issue, but we'd rather use the RSLs.

Do you think the issue is the Flash Player in the SDK itself? If so, how could we check this and/or fix the issue?

Thanks for any advice.

Report · Jun 15, 2015

Are you using an HTML control or loading swf's in your app via the built in webkit?

Report · Jun 15, 2015

We do have a HTML control, but its not a main piece of our app. We load in our "component" SWF files using Loader at app start-up, and one of those components is for displaying HTML content. This is a digital signage product that uses a Java backend, talking to an AIR UI via a socket.

Report · Jul 28, 2015

Greetings Chris,

I Have an iMac OS X 10.4.11 (Tiger) which uses the Flash 10.3 player & have been encountering problems this summer similar to those reported in this thread when trying to load Flex applications from websites that I have routinely visited successfully in the past. I have kept the copy of the Flash player dmg on my system for whenever I needed to reload it.

I am afraid that, as you point out, the 10 yr cert has expired which is the source of my difficulties.

If I go to the Adobe Archives will there be a Flash 10.3 Player that has the extended expiration so I may continue using this product that has served me well in the past ?

Report · Jul 07, 2015

Some of the products in our catalogue have the swz files bundled in SCORM packages intended to reside behind a firewall on an LMS. Updating the 4.1 Flex framework swz files sloved the problem with these products when hosted on the web, but the SCORM 1.2 zips still fail to launch in ADL test suite. (A client requirement.) We have tried all suggestions in this thread without success. Any idea why the updated frameworks are failing?

Report · Jul 07, 2015

What version of ADL/AIR is being used when you get this error code?

Report · Jul 09, 2015

- Sorry. The ADL I refer to is Advanced Distributed Learning TestSuite1.2.7 specifically for testing SCORM 1.2 conformant zip packages.