Home / Products / FlashCom / Support / Release Notes
Macromedia Flash Communication Server MX 1.5 release notes
This document addresses issues, primarily for Macromedia Flash Communication Server MX developers, which are not discussed in the Macromedia Flash Communication Server MX documentation. This document may be updated periodically as more information becomes available.
System requirements
Known issues in Macromedia Flash Communication Server MX

Reporting a bug to the Macromedia Flash Communication Server MX team

  System Requirements
  • Pentium III 500 Mhz processor or better (dual Pentium 4 or faster recommended)
  • Windows XP, Windows 2000, Windows NT 4.0 SP6 or later, or RedHat Linux 7.3 or 8.0.
  • 64 MB Available RAM (512 MB Recommended)
  • 50 MB of available disk space
  • CD-ROM Drive (optional)
  • Macromedia Flash MX for Windows or Macintosh systems for application authoring.

Known issues in Macromedia Flash Communication Server MX 1.5

Installation on Windows

  • Running the Communication Server 1.5 installer more than once on the same system is not supported. If you want to reinstall the server after running the installer with upgrade options, remove the installation first, then run the installer again.
  • If you try to install with a version 1.5 upgrade serial key and you don't have version 1.0 of the server installed, the installation will abort. To use a 1.5 upgrade serial key, run the installer on a system that already has version 1.0 installed.
  • The Communication Server 1.5 installer does not update your Macromedia Dreamweaver MX installation with the latest support or ASC file editing. For more information, see the TechNote for Communication Server 1.5 and Dreamweaver MX ASC editing support.

Installation on Red Hat Linux

  • There is no option to modify an individual installation option. If needed, use Control+C to exit the installer and begin again.

Upgrades and Platform Migration

  • After upgrading to 1.5 and migrating to Linux the server reports an "Invalid" upgrade key error and runs in Developer Edition mode.

    Customers who purchase Macromedia Flash Communication Server MX 1.5 or upgrade to 1.5 from 1.0 have the option to choose the platform on which they would like to run the Communication Server — Windows or Linux. If you are upgrading from 1.0 to 1.5 and want to switch from the Windows platform to Linux, please locate the serial number for your Flash Communication Server 1.0 and the new serial number for your Flash Communication Server 1.5 Upgrade and contact Macromedia Customer Service.

Server: All Platforms

  • The SimpleConnect component has three new features: the onComponentsConnected event handler, the ability to load a server name from an XML file, and improved connection times for HTTP tunneling. For more information, see the TechNote for SimpleConnect 1.5.
  • When using the SetBandwidth component, note that you can set the up/down rates in the component using a programmatic call to the setRates() method, as shown in the following example:
    var up = 146; // up bandwidth of 146 kbit/sec
    var down = 0; // down bandwidth of unlimited kbit/sec
    setbw_mc.setRates( up, down ); // assume setbw_mc is an instance of FCSetBandwidth component

    A value of 0 represents unlimited bandwidth; the example shows an unlimited bandwidth for the down rate.

  • MP3 files that contain encoding errors might fail to play back through the server. The presence of encoding errors in the file will also cause Stream.length(streamName) to return 0. These errors might be caused by the software used to encode the MP3 file. If the server does not play back MP3 files, try encoding the files again or see the TechNote for supported MP3 encoders.
  • If your application uses components and you define a custom onAppStop method in your main.asc script, make sure that it returns either true or false. If your onAppStop method doesn't return anything, the onAppStop methods defined in the components' server-side scripts will not be invoked, and the components might not work properly.
  • The key_value argument of the setConfig method can be an XML hierarchy, but needs to be valid XML. The following example is valid, assuming "nc" is a NetConnection object:"setConfig", 0, "Hello", "<World><Tag1>value1</Tag1><Tag2>value2</Tag2></World>",    "/");

    and will result in deleting any tags already in the <Hello> hierarchy and replacing it with the values:


Server: Windows

  • StopServerService.bat (Stop Server from the Start menu) might display the following diagnostic message: "find: unable to access "Windows NT": The system cannot find the file specified." This error does not affect the server shutdown. The script will continue to run as normal.

Server: Red Hat Linux

  • Regardless of the capacity limits for Flash Communication Server, the server always accepts connections from administrators. However, when the operating system is under heavy load, an administrator attempting to connect to the server might not be able to connect because of a lack of system-level resources. The system administrator for the Flash Communication Server computer should appropriately configure the system's ulimit setting, which controls the number of available sockets, based on expected system loads.
  • If the Flash Communication Server ports are not free by the time a server restart command is issued, the restart command might fail and a "bind failed" error might be displayed. This error occurs whether the restart command is issued by the command line or through the Administration Console. If you get this error, issue a "server stop" command (in the Administration Console, click Shutdown) and wait for confirmation that the server has stopped. Then, issue a "server start" command (in the Administration Console, click Restart).
  • Permissions for FLV files are read and write for the owner and group by default. The Server.xml file contains a <Mask> node with a default value of 017 (15 in octal). Note: Do not deny read/write access to the owner, or the server will be unable to write or read from the file and application users will not be able to create FLV stream files.

Flash Player Client

  • The required Flash Player client for HTTP tunneling is version 6,0,65 or better on all platforms.
  • Flash Player clients running on Linux or Mac OS 9.x or earlier do not support HTTP tunneling. Explicit RTMPT connections made from these players will fail. If users will be running Flash Player on Linux or Mac OS 9.x or earlier, use the RTMP protocol in the NetConnection statements for those applications.


  • Help is not supported in Mozilla on Windows. To use the help in Mozilla on Windows, edit the help_data.txt file in <installation_directory>/flashcom_help/html and <FlashMX_authoring_directory>\Configuration\HelpSWF by putting "file:///" in front of the targetHelp and targetSamples paths.
  • In the entry in the Server-Side Communication ActionScript Dictionary, the example that shows how to create a playlist of three MP3 files is missing code:
application.myStream = Stream.get("foo");
if(application.myStream) {"mp3:beethoven", 0);"mp3:mozart", 0, false);"mp3:chopin.mp3", 0, false); }

The number/order of parameters passed to the last two play commands should read as follows (notice the added "-1"):"mp3:mozart", 0, -1, false);"mp3:chopin.mp3", 0, -1, false); }

Reporting a bug to the Macromedia Flash Communication Server MX team
Found a bug? Please send the detailed bug information via the online Macromedia Software Feature Request and Bug Report form.

Note: Due to the high volume of e-mail we receive, we are unable to respond to every request.

Thank you for using Macromedia Flash Communication Server MX, and for taking the time to send us your feedback!