function readOnly(count){ }
Starting November 20, the site will be set to read-only. On December 4, 2023,
forum discussions will move to the Trailblazer Community.
+ Start a Discussion
bryanobryano 

Flex toolkit - "Security error accessing url"

I have a Flex application that is hosted on our server and is accessed by clicking on a web tab.  The web tab points to the .html file which in turn loads the .swf.

I have a client who can't load the application.  When he clicks on the web tab he gets the following error:

(mx.messaging.messages::ErrorMessage)#0
  body = (null)
  clientId = "DirectHTTPChannel0"
  correlationId = "326CBB94-1327-9170-3836-DFD447FED461"
  destination = ""
  extendedData = (null)
  faultCode = "Channel.Security.Error"
  faultDetail = "Destination: DefaultHTTPS"
  faultString = "Security error accessing url"
  headers = (Object)#1
    DSStatusCode = 0
  messageId = "00F9E634-16FD-BADE-8F6B-DFD448BA55C1"
  rootCause = (flash.events::SecurityErrorEvent)#2
    bubbles = false
    cancelable = false
    currentTarget = (flash.net::URLLoader)#3
      bytesLoaded = 0
      bytesTotal = 0
      data = (null)
      dataFormat = "text"
    eventPhase = 2
    target = (flash.net::URLLoader)#3
    text = "Error #2170"
    type = "securityError"
  timestamp = 0
  timeToLive = 0

Client is seeing this error in both IE 8 and Firefox 4 with the latest version of Flash player installed.
 
Now, if I log into his instance, click on the web tab, I'm able to load the application just fine in both IE and Firefox and with the same exact version of Flash installed.

I can also access the application in every other salesforce instance where our applicaiton is installed.

Anybody have an idea why he's the only one getting this security error?

 

sfdcfoxsfdcfox

It's obviously something with their machine. Have them try the optimal browser settings for their browser (in Help), and go to http://www.macromedia.com/support/documentation/en/flashplayer/help/settings_manager07.html to clear their website storage, and try again. A cursory search suggests that their machine isn't reading the crossdomain.xml file correctly for the domain, and so is giving an error message. Clearing the cache should clear this right up.