Editing Main Page

==Existing Documentation==
Before you add an error to this page, please check out the existing error-code documentation. It may be covered already:
*[http://livedocs.macromedia.com/flex/201/langref/compilerWarnings.html Compiler warnings]
*[http://livedocs.macromedia.com/flex/201/langref/compilerErrors.html Compiler errors]
*[http://livedocs.macromedia.com/flex/201/langref/runtimeErrors.html Run-time errors]


===Run-time errors===

<table width="90%" border="1" cellspacing="2" cellpadding="2">
  <tr>
    <th scope="col" width="20%">Error code</th>
    <th scope="col" width="40%">Description</th>
    <th scope="col" width="40%">Solution or workaround</th>
  </tr>

<tr>
  <td>1000</td>
  <td>Error: 1000: No bitrate match</td>
  <td>This error occurs when the application is unable to locate an flv file that it has been asked to play. Usually that means a filename is incorrect, but some people using asp have needed to set the correct MIME type for flv files. 
</td>
</tr>

<tr>
  <td>1009</td>
  <td>TypeError - Cannot access a property or method of a null object reference</td>
  <td>When using modules, be careful using shared code between modules that share the same classes or assets.   If those modules share managers, then the developer must be careful. One common mistake is to accidentally bring in Managers (PopUpManger, DragManager) in a module and use from another module.  For more information, see http://thanksmister.com/?p=54.

If you get this error from clicking a cell an ItemRenderer, add the following line to the renderer's "override public function set data(...)":

super.data = value;
</td>
</tr>
<tr>
   <td>1030</td>
   <td>VerifyError</td>
   <td>Make sure you are running the current version of the player.</td>
</tr>
<tr>
   <td>1034</td>
   <td>TypeError: Type Coercion failed: cannot convert <i>class</i> to <i>class</i>.</td>
   <td>This is a common error when two modules or SWFs try to share a class across ApplicationDomains.<br/>
Another possibility is that two events have the same name ("click", "result", etc), and events bubble or there is ambiguity as to which event you are listening for. In this case, the listener will be coded to receive the wrong type of event and you'll get this error.
</td>
</tr>
  <tr>
   <td>1067</td>
   <td>Implicit coercion of a value of type Class to an unrelated type mx.core:Container.<i>classname</i></td>
   <td>happens when try to assign mxml page to viewStack.selectedChild</td>
  </tr>
  <tr>
  <tr>
   <td>1068</td>
   <td>VerifyError: <i>classname</i> and <i>classname</i> Cannot be reconciled</td>
   <td>One developer who experienced this error reports that restarting the application 
        server fixed the problem.</td>
  </tr>
  <tr>
   <td>1151</td>
   <td>A conflict exists with definition <i>definition</i> in namespace <i>namespace</i></td>
   <td>The declaration of a variable of a certain type cannot be overridden to a different type in the same scope.</td>
  </tr>
  <tr>
   <td>1502</td>
   <td>A script has executed for longer than the default timeout period of 15 seconds.</td>
   <td>For Flex Charting, ensure that you're using unique category names in the category axis.</td>
  </tr>
   <tr>
    <td>2032</td>
    <td>HTTP request error</td>
    <td>The referenced resource does not exist or the swf is trying to access a file across a restricted domain. Or, possibly something went wrong on the sever side of a WebService (or HTTPService) call.</td>
  </tr>
  <tr>
    <td>2082</td>
    <td>Connect failed because the object is already connected.</td>
    <td>If your application dies unexpectedly, it can leave the history LocalConnection in a hung state:
<ul>
<li>One workaround is to shut down all instances of the Flash Player, including all browsers, and Yahoo IM, then you should be all set. 
</li>
<li>A code-based workaround is as follows:<br/>

If connecting to a named LocalConnection "A" fails, you can try setting up a temporary callback LocalConnection and then invoke a send() to connection "A". If the owning instance is running it receives the call to connection "A" and should ping back over the temporary connection and you'll know that the connect failure is legitimate because the owning player instance is running. If you don"t hear back after 5 seconds (magic number) the Player assumes that connection "A" is orphaned and cleans up the shared memory, and at this point you can retry your connect() and it should succeed.
</li>
</ul>

Another cause of this error is using managers (or other singletons) within a module before they're loaded by the main application. There's a lengthy thread on this topic in flexcoders here: http://tech.groups.yahoo.com/group/flexcoders/message/63829
     </td>
  </tr>
  <tr>
    <td>2137</td>
    <td>Sandbox security violation</td>
    <td>Possible solutions include:
<ul>
<li>You are accessing a remote asset but the remote web server does not have a crossdomain.xml file or the crossdomain.xml file's allow-access-from domain attribute doesn't allow access from your domain. For more information, see http://livedocs.adobe.com/flex/201/html/05B_Security_176_04.html</li>
<li>You did not specify the appropriate value for the use-network compiler option. For more information, see http://livedocs.adobe.com/flex/201/html/compilers_123_24.html</li>
</ul>

</td>
  </tr>
  <tr>
    <td>&nbsp;</td>
    <td>SWF is not a loadable module</td>
    <td>If you load modules across domains, the target domain must implement a crossdomain.xml file with the appropriate permissions.</td>
  </tr>
</table>