Facebook

Login

Support Sailonline

If you haven't already - join the SAILONLINE YACHT CLUB!

Please also consider making a donation - all amounts are greatly appreciated!

Board » Technical Support » Optimum Angles

Page: Previous 1 2 3 Next

Just logged in to see if there was any news about this problem, and boy, I'm happy to see that A2 is trying to get to the buttom of this.
Thanks for that, A2 :-)
Waiting in suspense for the outcome.
# 2032 [Stream Error]

This error indicates that the SWZ or SWF file is not being found.

The frequently occurs if the client is not able to download the signed framework RSL (Runtime Shared Library) from the Adobe web site, and you have not deployed a local signed framework RSL. If the client has limited or not internet connectivity, be sure to deploy the local framework RSL to a location that is accessible to the client. For more information, see Using the framework RSLs.

It can also occur if Flash Player tries to load a custom RSL that is not available. For example, if you specified only “mylib.swf” as the value of the rsl-url parameter to the runtime-shared-library-path option, but the SWF file is actually in a sub-directory such as /rsls, then you must either recompile your application and update the value of the rsl-url parameter to “rsls/mylib.swf”, or move mylib.swf to the same directory as the application’s SWF file.
---------------------------
# 2046

This error indicates that the loaded RSL was not signed properly. In the case of framework RSLs, the framework’s SWZ file that the application attempted to load at run time was not a properly signed SWZ file. You must ensure that you deploy an Adobe-signed RSL, or be sure to use the signed framework RSLs that are deployed on the Adobe web site.
---------------------------
# 2048

The cause of this error is that you do not have a crossdomain.xml file on the server that is returning the RSL. You should add a file to that server. For more information, see Using cross-domain policy files.

If you are loading signed framework RSLs from the Adobe web site, you should not get this error.

If you put the crossdomain.xml file at the server’s root, you do not have to recompile your application. This is because the application will look for that file at the server’s root by default, so there is no need to explicitly define its location.

If you cannot store a crossdomain.xml file at the remote server’s root, but can put it in another location on that server, you must specify the file’s location when you compile the application. On the command line, you do this by setting the value of the policy-file-url argument of the runtime-shared-library-path option.

In the following example, the RSL SWF file is located in the /rsls directory on www.domain.com. The crossdomain.xml file is located in the same directory, which is not the server’s root, so it must therefore be explicitly specified:

mxmlc
-runtime-shared-library-path=
../lib/mylib.swc,
http://www.mydomain.com/rsls/myrsl.swf,
http://www.mydomain.com/rsls/crossdomain.xml
Main.mxml
---------------------------
Requested Resource Not Found

You might find this error in your web server logs. If you deploy the RSL SWF file to a location other than that specified when you compiled the application, then you will get an error similar to this when the application tries to run.

The solution is to either recompile your application and correct the deployment location of the RSL SWF file or to move the RSL SWF file to the location that the application expects.
None so blind
Does the same thing happen when you load a race on http://beta.sailonline.org/? (other things might not work properly there, but the client should load)

--- Last Edited by kroppyer at 2015-07-10 11:06:21 ---
Yes it returns

[RSL 1 of 3]

error #2046
None so blind
I punched up the Classic Client & it does load correctly. I noticed that the Framework XXX.swz file loads directly from Sailonline.org and when it is complete the XXX.swf follows.

This is what is Not happening for the Beta Client.

SWZ does not begat SWF
None so blind
Attachments
avoid loading adobe.com's crossdomain.xml by hosting the swz files on your own server. Just copy the swz files to the same directory as your application and modify the RSL URLs.

The RSL URLs are modified by removing the URL pointing to the adobe hosted site and keeping the "framework_4.5.0.20967.swz" URL.
None so blind
The problem remains the same after several weeks.

--- Last Edited by A2 at 2015-07-26 01:41:25 ---
None so blind
I am not aware of any information being volunteered here by Sailonline NavSim AB relating to whether any files under their control has changed recently concurrent with the various difficulties under discussion in this thread nor to what extent if any they are able or willing to implement remedies as needed.

Adobe may be at the root cause of this perplexing dilemma as there are similarities found in their Forum https://forums.adobe.com/thread/723549 here.

Although being able to decipher such geeky stuff is above my pay grade.

Implied from what I can tell is that Adobe may have changed certain files without notice or some files may have an inherent expiration which is now out of date.

For Example here is one excerpt that caught my eye:

"two solutions, depending on how important are external libraries for your app(s), neither of which involves changing a single line of code.
1. Disable framework RSLs and deploy a "fat" app
2. Disable digest authentication for RSLs, and deploy the compiled framework SWFs along with your app. In this case, the old SWZ files are not interesting anymore, and you must deploy all the generated files, including the "framework.swf" etc."

Even if this proves not to be relevant in fixing the problem here I believe that it does emphasize the prudence of keeping all components involved in stasis locally and not at the whim of Adobe's future inclinations.

Anyone that is having this problem also please post your Operating System flavors & such so that it is possible to discern any pattern that may or may not exist from the User side.

--- Last Edited by A2 at 2015-07-26 01:39:56 ---
None so blind
Anyone that is having this problem also please post your Operating System flavors & such so that it is possible to discern any pattern that may or may not exist from the User side.
---

Yes. With only one or two people having this problem, it is almost bound to be a user side problem.
Possible explanations and solutions (as found by A2) don't seem to completely fit our problem, they don't explain why the client works without problems for almost everyone. I've cleared caches and all so that I would need to reload the RSLs the same way A2 does, and it works all fine here...
Well obviously my clumsy attempts to find useful information from the Adobe forums for this problem has not been successful, which raises the question why the cognoscenti has not done so directly. However I am at odds with the assumption that this is a User only circumstance. My suspicions are that Adobe may be arbitrarily curtailing access to Flash versions which they deem to be out of date even though no such limitation exists within the client itself.

The Classic client works because it does not access files from Adobe. What is needed from my point of view is a stand alone SWF version that does not require the SWZ precursor to test this hypothesis.

This might explain why only users with computers of a certain age are affected as long as they have not actually had to clear their caches of versions that are still functional before returning to Adobe for a reload.
None so blind

Page: Previous 1 2 3 Next

Please login to post a reply.

Races

Next Race: 00d 00h 00m


Current Races:

Melbourne to Hong Kong
After celebrating Christmas and New Year it is time for the second run in this year's Ocean Race Championship. After leaving Melbourne on this (about) 5.500 NM course, we will leave the Solomon Islands, Papua New Guinea and the Philippines, all to port. And remember, once again we'll have to choose the best way to cross the Doldrums
PRIZE: SMPF
Race #1658
INFOfrom brainaid.de
OD65v3 Particulars
WX Updates:
0430 / 1030 / 1630 / 2230
Ranking:
OCQ1-OCCH-SUPSOL-SYC
Race starts: Feb 04th 05:00 Registration Open!

▶ Flash
GO TO RACE

China Sea Dash 2023
The waters of the China Sea beckon for this short race around the cans. We'll be racing 128nm in our TP 52s as the local racers warm down as their sailing season closes.
Race #1551
INFO by brainaid.de
TP 52 PARTICULARS
WX Updates:
0430 / 1030 / 1630 / 2230
Ranking: SYC
Race starts: Feb 04th 02:15 Registration Open!

▶ Flash
GO TO RACE

Buenos Aires to Rio 2023

This year's second ARCH series race will run from Buenos Aires, Argentina to Rio de Janeiro, Brazil on a route designed by SOLer Vida_Maldita (under his former alias of zero) in 2013. This is a replica of a classic triennial race of 1200nm, first run in 1947. More information about this IRL race can be found here.
So, Bemvindo/Bienvenidos in this coastal classic and prepare your 90ft Monohulls well.
Race #1662
INFO by brainaid.de
90ft Monohull PARTICULARS
WX Updates:
0430 / 1030 / 1630 / 2230
Ranking:
ARQ1 - ARCH - SUPSOL - SYC
Race starts: Feb 01st 18:00 Registration Open!

▶ Flash
GO TO RACE

Up Helly Aa 2023
A-OI!!! The cry should soon be ringing out in the streets of Lerwick as the Guizer Jarl and his crew, along with the other teams in the Up Helly Aa parade complete their preparations for the biggest fire festival in Europe. As is Sailonline's tradition, we shall be racing the 383nm from Aberdeen to Lerwick to (virtually) take part in the Up Helly Aa festivities there which take place for the first time since 2020 on Tuesday, 31 January. SAILING NOTE: Gruney may be approached from any direction but must be passed for rounding purposes as indicated on the chart.
Race #1660
INFO by brainaid.de
Elan 410 PARTICULARS
WX Updates:
0430 / 1030 / 1630 / 2230
Ranking: SYC
RACE CLOSE: Friday,
3 February at 2300 UTC
Race starts: Jan 28th 11:00 Registration Closed

▶ Flash
GO TO RACE

Go to race archive

SYC Ranking

  1. Sailonline Yacht Club Member WRmirekd
  2. Sailonline Yacht Club Member Pit8008
  3. Sailonline Yacht Club Member FreyjaUSA
  4. Sailonline Yacht Club Member Vida_Maldita
  5. Sailonline Yacht Club Member Kipper1258
  6. Sailonline Yacht Club Member bonknhoot
  7. Sailonline Yacht Club Member Sax747
  8. Sailonline Yacht Club Member rafa
  9. Sailonline Yacht Club Member SlideRule
  10. Sailonline Yacht Club Member TarassBoulba

View full list

Series

Mobile Client

SYC members have the benefit of access to our mobile/lightweight web client!

The mobile client