Information Resources & Technology

Troubleshooting Problems

Need to delete a file or files from the server

To have an indexed file removed from Google and other search engines, add a new Disallow command to the robots.txt file found at the domain root of your site. Typical syntax:

Disallow: /path/to/

Cannot display the remote folder: An HTTP WebDAV error occurred....

This error usually indicates a problem with the WebDAV URLs connection protocol, which must be secure. Check your WebDAV settings to make sure you have the correct WebDAV URL for the site in question, and that it begins "https://" and not "http://"

HTTP Error 401

This is a generic connection error that occurs in WebDAV connections.

If you are using Dreamweaver MX 2004 or older, you may just have a problem with the site definition settings for your password. You will need to re-enter your password each time you launch Dreamweaver MX 2004. See the training page on this. We also suggest you upgrade to the latest version, 8 or newer.

If you are using Dreamweaver 8 or newer, this type of error comes up most often when there's a problem with the LDAP cache used by WebDAV to retrieve the SUNet IDs that are allowed to edit the site. Contact Web Help to report your 401 Error and request that the WebDAV cache be cleared.

If you are getting a 401 error under other circumstances, please report it via Web Help along with as many details as you can provide about your situation.

HTTP Error 200

This is a newly reported error. We believe it is associated with permissions on the computer on which the site is downloaded by Dreamweaver. Interestingly, we were able to create new files and folders through the Desktop, but when getting the site with Dreamweaver, it was able to write the folders but not the files, in the local folder. We're investigating and will update this item when we have more information. But it appears to be a local computer problem, not a general connection problem.

Can't Upload a Page

WebDAV makes heavy use of the check-in/check-out function. When one user "checks out" a file, it can't be edited by any other user, to protect everyone from inadvertent overwrites. But more often than not, this comes up because one user checked out the file, but never checked it back in.

You may be able to overwrite the file anyway, in which case, do so. We recommend you get a fresh copy of the file from the server first, though, to be safer.

Dreamweaver may provide you with the email address of the user who checked the file out. You can contact that user and request that they check it back in. If this is impractical, or likely to take too long, contact Web Help to request assistance. Specify the file or files you need to edit.

Can't See My Changes in Browser

Did you refresh/reload your browser view? If yes, go back and check both Remote and Local file views. It must show under Remote to be live. Try a "put" using the Check In command instead of Put.

Can't Disconnect, Can't Do Anything

Under some circumstances, particularly on Macintosh computers, connecting with Contribute Compatibility turned on can lead to being trapped in connection mode; can't stop the connection, can't disconnect, can't quit or do anything. To escape this loop, Force Quit from Dreamweaver: Go to your Desktop and find "Force Quit" in the Apple menu. Find Dreamweaver in the list and click "Force Quit." Edit the site definition (Site menu > Manage Sites), find the Contribute category and uncheck "Enable Contribute compatibility." When you re-connect, be sure not to click Yes on the Contribute compatibilty prompt.

« Previous | Home | Next »

Footer Links: