I sure hope someone can give me a definitive answer about how to get rid of this error. I had completed an application in Flash Builder 4, put the updated executables on my Linux Server (where previous revs had been working fine), and when i tried it, I got a blank screen (in Firefox, Opera, Safari, Chrome and IE ...all of which had been working fine before). The only change in the interim was an update to Flash Player 10.1, but curiously my app still works fine if I run it on any browser from my Windows (Apache2.2/MySQL5.1/PHP5) server. Thankfully, I at least got an error message "Error #2046" on my new litl webbook. The debug Flash Player logged the error message, "Warning: Ignoring 'secure' attribute in policy file from http://fpdownload.adobe.com/pub/swz/crossdomain.xml. The 'secure' attribute is only permitted in HTTPS and socket policy files. See http://www.adobe.com/go/strict_policy_files for details."
By my bad luck, this happened on the day i was about to deploy to my client. I've spent two days since looking for a solution, but found NOTHING but complaints from others with similar problems and no responses (no solution). Yes, my app uses RSLs.
PLEASE HELP, I am desperate. This was my first Flex app, and I was hitting stride until this. Honestly, my faith in the stability/reliability of the Flex Framework is severely shaken. I am close to jettisoning a month's work if Flex is this flakey. I sure hope someone tells me I don't have to, because I was starting to really like FB4.
Regards,
bob
Stack Trace? I wish I had one! On any browser, the screen is blank. All that shows is my app's background color, whether I load the html-wrapper or swf.
The server is running Ubuntu Server 10.4
BTW, I have since tried "merging into the code" at compile-time to avoid using RSL's, but still get nothing but a blank screen. The only difference is on my litl, the Error #2046 does not appear anymore.
Thanks,
bob
Clearing the local Flash Player Cache can help - visit the page http://www.macromedia.com/support/documentation/en/flashplayer/help/se ttings_manager03.html and uncheck the option to "Store common Flash components to reduce download times" and click the Confirm button.
Then click the "Store common Flash components to reduce download times" check box again to re-enable the cache.
Thanks for the suggestion. I uninstalled 10.1 and installed Flash 10,0,12,36 and SAME RESULTS (still blank screens on all browsers).
Ach! I was blaming the 10.1 player "upgrade", but apparently that's not the cause.
Unfortunately, it doesn't tell me what *is* the cause yet, but at least its narrowed down to either a changes I made in the code (of which there were many last week between updates to try on the Linux server), or something about the server.
Thanks,
bob
Yes, and that's only on my litl webbook (see http://litl.com) and only when I use RSLs (i.e., when I do not "merge with code"). The error message I mentioned in my first post appeared in the logfile from a debug version of the Flash Player, again only when I used RSLs. Hence, #Error 2046 is only half the problem.
A new development might be relevant: My Linux server was apparently hacked, because SSH and MySQL services are blocked. Shortly before this happened, my SSH client noted that my server's signature had changed. Don't know what these possibilities might imply however, since after that I re-installed Linux, starting with new partitions, and it worked the same.
The thing that kills me most about this is that my app continues to work fine on Windows Apache/MySQL/PHP., which is not what i care about. I would love to hear an explanation of what's happening "behind the curtain", whatever that curtain is, that's causing it to color the background, but fail to load at all.
Thanks,
bob
I did a second complete re-installation of my (Ubuntu) Server w/o exposure to the Internet (to keep the creepy crawlers out) and got it working again.
Conclusion: The only one for sure is, its real important to harden your web server if its on the big bad Internet.
As far as Error #2046 and blank screen from a loading swf (that doesn't load), they remain a lingering, irritating mystery.
Thanks,
bob
North America
Europe, Middle East and Africa
Asia Pacific