Accessibility

TechNote (Archived)

Dreamweaver MX 2004 emerging issues

Last updated: June 7, 2005
(There is one new issue to report)

Some users have reported that the following issues are affecting their usage of Dreamweaver MX 2004. Issues described in this document may prove to be platform or system specific, and may not affect all users. Technical support will update this document as we learn more about any of the issues, so check back frequently.

Updater for Macromedia Dreamweaver MX 2004

This product updater (version 7.0.1, released March 11, 2004) resolves issues identified in Dreamweaver MX 2004 including performance and stability improvements, and the restoration of the Timelines feature. All users should apply this updater, regardless of location or operating system. Download the installer and read the release notes for more information.

Note:Known issues (no longer emerging) can be found in the bottom section of this document.

Note: If you would like to see support for unsupported issues on this TechNote, or have other feature or change requests please use the online form "Macromedia Software Feature Request and Bug Report" to submit your request. This e-mail list is reviewed daily by members of our engineering and marketing departments, and the information is used to determine customer demand for a given issue.

Emerging Issues
Known Issues
Dreamweaver and Macintosh OS X v10.4 "Tiger"
topic update: June 7, 2005
Issue

Macromedia and Apple have worked together to ensure compatibility between Dreamweaver and Mac OS X v10.4 "Tiger." There are no known significant issues regarding compatibility for Dreamweaver. There are some minor issues though, described in Dreamweaver compatibility with Macintosh OS X v10.4 (Tiger) (TechNote d9e959b3).

Dreamweaver and Windows XP Service Pack 2
topic update: August 30, 2004
Issue

Some Dreamweaver users may experience various problems after installing Windows XP Service Pack 2 (XP SP2).

Solution

Please refer to Dreamweaver and Windows XP Service Pack 2 (TechNote 19515) for a summary of the XP SP2 issues affecting Dreamweaver users. That TechNote also references other more in-depth documents on the Macromedia support site. Macromedia also has a general XP Service Pack 2 support center.

'Build' button in ASP.NET OLE DB dialog box breaks with MDAC 2.8
topic update: August 30, 2004
Issue

After installing MDAC 2.8, the 'Build' button in the ASP.NET OLE DB Connection dialog box stops working. Installing XP SP2 will install MDAC 2.8 by default. MDAC 2.8 can also be installed separately on XP SP1.

Solution

Please refer to Dreamweaver and Windows XP Service Pack 2 (TechNote 19515) for more information. Users that come across this problem, will most likely first see it when updating to XP SP2. (Ref. 178520, 164036)

Product activation issue after installing the Flash MX 2004 7.2 Updater (Windows only)
topic update: July 30, 2004
Issue

Some Windows users may experience problems with product activation after installing the Flash 7.2 updater.

Solution

After installing the Flash 7.2 updater, users may find other Macromedia products require reactivation. Further reactivations are required each time the application is launched. Ultimately, activation will fail after the product has been reactivated several times. This issue is addressed in the ServiceNote Reactivation failure after upgrading to Flash 7.2 (ServiceNote 19468).

ColdFusion Reference help has been updated
topic update: June 14, 2004
Issue

As communicated in the 7.0.1 Release Notes, the reference chapters for ColdFusion help (Help > Using ColdFusion) have been updated. The update fixes a problem with section introductions that contained only a heading and no links to the section topics. It also fixes a problem where the standard reference subheadings (Description, Category, Syntax, and so on) were not displayed.

Solution

Download the applicable extension to install the updated help files. These extensions are MXP file format and must be installed using the Macromedia Extension Manager. Note: The extension updates the Help system, not the Reference panel

Access Denied error when connecting to an IBM AIX FTP server
topic update: June 14, 2004
Issue

When attempting to access files or folders older than the current calendar year via FTP on an IBM AIX server, the following error occurs:

An FTP error occurred - cannot get remote folder information.
Access Denied. The file may not exist, or there could be a permission problem.

Reason

Dreamweaver misinterprets the file listing because files and folders older than the current calendar year include values for month, day and year values. Files and folders from the current calendar year include values for month, date and time. This difference causes errors when Dreamweaver tries to access older files and folders.

Solution

Download and install the Dreamweaver extension that resolves this issue. This extension works for both Windows and Macintosh versions and will update the following file:

  • Windows: C:\Program Files\Macromedia\Dreamweaver MX 2004\NetIO.dll
  • Macintosh: Applications/Macromedia Dreamweaver MX 2004 (the NetIO file in the package)

Note: You should only install this extension if you are connecting to an IBM AIX server. (Ref. 169317)

Clean Up Word HTML drop down list does not include Word 2003 or Word X
topic update: June 14, 2004
Issue

In Dreamweaver, when you select Commands > Clean Up Word HTML, the drop down menu does not list Word 2003 (Win) or Word X (Mac). When running Clean Up Word HTML on a Word 2003 document, the following warning message appears after Dreamweaver tries to detect which version of Word the document was created with:

Dreamweaver was unable to determine the version of Word used to generate this document. You may manually select a version from the dropdown menu. However, if the incorrect version is selected, the import filter may not work correctly.

No warning message appears with Word X when running Clean Up Word HTML, but Dreamweaver automatically selects Word 2000/2002.

Reason

Microsoft Word 2003 for Windows was released on October 21, 2003, which was after Dreamweaver MX 2004 was released (September 10, 2003). Word X for Macintosh was released on November 19, 2001. Dreamweaver currently recognizes Word X documents as Word 2000/2002 documents.

Solution

Here are some workarounds for this issue:

  • Clean Up Word HTML should work fine with Word X files. Even though you receive the version warning with Word 2003 files, you can still run Clean Up Word HTML and it will still remove most of the invalid markup.
  • Highlight the text in Word, copy it, and paste it into Dreamweaver using one of the three methods below. Each of the Paste methods results in different HTML code, so experiment with each of them and see which works best for your particular task:
    • Edit > Paste
    • Edit > Paste Formatted
    • Edit > Paste Text
  • On Windows, another option is to import the DOC file via File> Import > Word Document. The import features are native to the Windows operating system, so this menu option is not in the Macintosh version. Mac users should use the workarounds above, which will achieve similar results. This discrepancy is addressed in the Using Dreamweaver MX 2004 Errata. (Ref. 157214, 148326)
XHMTL validator is not catching invalid markup
topic update: June 14, 2004
Issue

In Dreamweaver, when running File > Check Page > Validate Markup, the validator does not catch invalid XHTML. For example, the validator will not report a missing DTD or missing alt, height or width attributes for an <image> tag, all of which are required for a document to be considered XHTML compliant.

Reason

This problem appears to affect Dreamweaver MX 2004 7.0 and 7.0.1. The engineering team is aware of this issue and is researching the problem. (Ref. 168472)

Unidentified error when testing PHP/MySQL connection
topic update: June 14, 2004
Issue

This is a common error often resulting from an incorrect environment configuration. However, some users are reporting that connections to a MySQL database work correctly in Dreamweaver MX, but generate the unidentified error in Dreamweaver MX 2004.

Reason

Make sure your version of PHP is compatible with Dreamweaver MX 2004. Dreamweaver MX 2004 supports PHP 4.1.1 and higher, 4.2.x and 4.3.x. Dreamweaver MX 2004 does not support PHP 4.1.0 and below.

Dreamweaver MX 2004 users running Mac OS X 10.3.x cannot use localhost in the Testing Server category's URL Prefix field. Apple changed how localhost works in Mac OS X 10.3.x, so using localhost as the prefix breaks the PHP/MySQL database connectivity features in Dreamweaver MX 2004. Instead of using localhost in the Site Definition URL Prefix, use one of the following:

  • the loopback IP address (127.0.0.1)
  • the static IP address
  • the machine name

The following TechNotes can help identify other configuration problems:

Dreamweaver won't run after using Macintosh Archive and Install
topic update: June 14, 2004
Issue

Some users are reporting that Dreamweaver MX 2004 will not launch after upgrading to Macintosh OS X version 10.2.8 or to version 10.3 (also known as Panther). These issues are specific to users who upgraded using either the "Archive and Install" or the "Erase and Install" features. This issue has frequently been described as the application icon bounces on the dock, but the application doesn't launch. This issue has also been described as the application continually prompts the user for a Macintosh administrator password and never accepts the valid password.

Solution

This issue and the solution are described in Some applications won't run after upgrading to Macintosh OS X version 10.2.8 or to Panther (version 10.3) (ServiceNote 18933).

Extensions are misplaced or are missing from menus after installing the 7.0.1 updater
topic update: April 2, 2004
Issue

Some customers are reporting problems with certain extensions after installing the 7.0.1 updater. With extensions that create menu entries, either the menu entry appears in the wrong place, or not at all.

Reason

The menus.xml file has become corrupted, resulting from not following the updater installation prompt instructions correctly:

  • If you have installed any Dreamweaver MX 2004 extensions, please disable them using the Macromedia Extension Manager before installing the Dreamweaver MX 2004 Updater.
  • If you install the updater while extensions are enabled, your extensions will disappear from the Dreamweaver menus.
  • After you have reinstalled the updater and started Dreamweaver for the first time, you can re-enable your extensions using the Extension Manager.
Solution

If the updater has already been installed, take the following steps to resolve the issue.

Note: Because Dreamweaver is designed to allow multiple users the ability to customize it (except Windows 98), these steps must be performed by each individual user that uses Dreamweaver on a particular machine.

  • Open the Macromedia Extension Manager and uninstall all Dreamweaver MX 2004 extensions.
    • Do not simply disable the extensions, uninstall them completely.
  • Close Dreamweaver.
  • Find and delete the menus.xml file in your user configuration folder.
    • Windows (all but Windows 98): C:\Documents and Settings\<username>\Application Data\Macromedia\Dreamweaver MX 2004\Configuration\Menus\
    • Windows 98: C:\Program Files\Macromedia\Dreamweaver MX 2004\Configuration\Menus\
    • Macintosh: Users/<username>/Library/Application Support/Macromedia/Dreamweaver MX 2004/Configuration/Menus/
  • Open Dreamweaver and immediately shut it down.
  • Open Extension Manager.
  • Install your extensions one by one.
    • Open Dreamweaver after each installation to check.
    • Close Dreamweaver before installing the next extension.
Macintosh installation error: Error creating folder. 1008:9,-5000 Access denied
topic update: March 26, 2004
Issue

When installing full Macromedia programs or updaters, some Mac OS X users may encounter the above error. The program or updater cannot be installed.

Reason

This is a known permissions issue on Macintosh systems. Please refer to Mac installation: Error creating folder. 1008:9,-5000 Access denied error (TechNote 19225) for instructions to resolve the problem.

Known Issues

The following issues have been removed from theemerging issues list because the issue is resolved or has been moved to its own TechNote. When appropriate, the TechNote link will be included with the issue.

Dreamweaver is not supported on Mac OS Extended (Case-Sensitive) and UNIX File Systems (UFS)
topic update: April 28, 2005
Issue

While Dreamweaver may appear to install correctly on a Macintosh system with a Mac OS Extended (Case-Sensitive) File System or a UNIX File System (UFS), it will not run properly.

Reason

Dreamweaver MX 2004 was not designed for or tested on Macintosh systems formatted with Case-Sensitive File Systems or UFS. Dreamweaver also does not support using local or remote folders (via Local/Network) located on a Case-Sensitive File System or UFS partition. You can see if your Macintosh has a Case-Sensitive File System or UFS format by choosing Macintosh HD > Get Info, then check the value for the Format property.

"This folder does not contain Dreamweaver MX 2004" error when trying to install the 7.0.1 updater
topic update: April 28, 2005
Issue

When attempting to install the Dreamweaver MX 2004 7.0.1 updater, the above error message is displayed and the updater cannot be installed.

Reason

The updater will only install if it finds Dreamweaver MX 2004 version 7.0 on your machine. If you have already installed the updater, or do not have the official 7.0 build installed, the updater will not install. For more details, please refer to Dreamweaver MX 2004 7.0.1 Updater installation issues (TechNote a6d80248).

Known issues with the Dreamweaver MX 2004 7.0.1 Updater
topic update: June 11, 2004

The following issues are reported in the Dreamweaver MX 2004 Update 7.0.1 Release Notes. Please refer to that document for more information.

  • Image Viewer Flash element does not support GIFs
  • Saving an HTML file as an ASP file
  • Renaming form objects after inserting them
  • Installing ColdFusion MX 6.1 on Windows 98 or 2000
  • Mac OS 10.3 user authentication dialog fails
  • Using a non-roman keyboard on a Macintosh
  • Documentation Errata
  • Dead links in Apple Help Viewer
Dreamweaver issues with Macintosh OS X version 10.3 (Panther)
topic update: March 11, 2004
Issue 1

Users are unable to use the eyedropper to select a color from anywhere but the color picker.

Solution

This issue has been corrected with the Dreamweaver MX 2004 updater.

Issue 2

In dialog boxes that display an item's URL, the URL is not displayed on Macintosh OS X Version 10.3 (Panther).

Solution

This issue has been corrected with the Dreamweaver MX 2004 updater.

For a list of issues with Panther that affect a number of applications including Dreamweaver, see Macromedia compatibility with Apple Macintosh OS X v 10.3 (Panther) (TechNote 18972).

Slow performance on Macintosh
topic update: March 11, 2004
Issue

Some users are reporting that Dreamweaver MX 2004 performs typical operations slowly on Mac OS X.

Solution

This issue has been addressed in the Dreamweaver MX 2004 updater. Dreamweaver users can expect improved performance with the updater installed.

The following information for improving application performance was provided prior to the updater release, and remains available for reference.

  1. Verify that your computer meets the System Requirements
  2. Check for any available updates from Apple. Go to System Preferences > System Software Update.
  3. Close any other programs that may be running and check the performance.

Note: This is not the full list of troubleshooting options available for Macintosh users. For more troubleshooting information, see General Macintosh troubleshooting (TechNote 3500).

We have identified the following steps to help improve performance.

  • By turning off the Document toolbar in Dreamweaver (View > Toolbars > Document), switching between Dreamweaver and other applications speeds up.
  • By turning off the Start page (Edit > Preferences, General category, uncheck the Show start page option), launching Dreamweaver speeds up.
  • By closing the Application panel (choose Close panel group from the Application panel group's Options menu), launching Dreamweaver speeds up. The Applications panel can be re-opened by selecting Databases, Bindings, Server Behaviors, or Components from the Window menu.
FTP 550 Access Denied errors
topic update: March 11, 2004
Issue

Some users are reporting that the FTP client in Dreamweaver MX 2004 returns 550 Access Denied errors although the connection continues to work in Dreamweaver MX.

Please keep in mind there are many factors besides Dreamweaver's FTP client that could cause connectivity problems. Be sure to review Troubleshooting FTP (TechNote 14834) for more information.

Solution

Many FTP issues, including the 550 error, have been corrected with the Dreamweaver MX 2004 updater.

Floating panel icons appear in Windows taskbar
topic update: March 11, 2004
Issue

When panels are undocked, icons for the panel appear in the Windows taskbar.

Solution

This issue has been corrected with the Dreamweaver MX 2004 updater.

Screen flicker in Dreamweaver MX 2004
topic update: October 24, 2003
Issue

Some users are reporting their screen flickers while using Dreamweaver MX 2004, particularly when working on dynamic pages.

Solution

This situation occurs in two situations, each with their own solution.

General screen flicker when performing routine operations.
We recommend reducing hardware acceleration to resolve the problem. See General Windows Troubleshooting (TechNote 15481) for instructions on reducing hardware acceleration.
Working with dynamic pages, particularly large recordsets.
This issue has been corrected with the Dreamweaver MX 2004 updater.
Dreamweaver continually asks for a serial number when launched
topic update: November 7, 2003
Issue

This issue is most evident in volume licensing environments. Each end user is prompted to enter a serial number when launching Dreamweaver, even though a user with administrator privileges has already entered a serial number for the application.

Solution

This issue and the solution are described in Each user is prompted for serial number even though the product has been serialized (ServiceNote 19004).

AlertThis content requires Flash

To view this content, JavaScript must be enabled, and you need the latest version of the Adobe Flash Player.

Download the free Flash Player now!

Get Adobe Flash Player

Creative Commons License

Search Support


Document Details

ID:tn_18895
Browser:Chrome
Internet Explorer
Netscape
Opera
Safari
Firefox
Database:DB2
Informix
MySQL
Oracle
SQL Server
Sybase
MS Access

Products Affected:

dreamweaver