For those of you who edit parts of the WOU website, here are a few steps to try if you run into errors like “Can’t connect to site” or “Local root folder is missing” or just “File not found” when you try to open up Contribute or Dreamweaver. If this happens, it generally comes when you’re first starting Dreamweaver, or first connecting to a site in Contribute.
Of course, the first thing to check is that the page or site actually works on the web. It’s pretty rare, but sometimes there may be a problem with the webserver itself or with the page file or folder. Most of the time, though, this happens because the X: drive on your computer (or the terminal server) isn’t connected properly.
Here’s what to try…
First, a bit of explanation.
You can skip to “Troubleshooting instructions” below if you just want to know what to do, not why.
Still here? Great! Web pages on our site are just files stored on our network, and in order to work with them, your computer needs a connection to the right network location. For historical reasons, Windows uses single letters (followed by colons) to refer to network connections, just like it does for hard disks, DVD drives, USB sticks, and so forth that are physically connected to your machine. To Windows, these are all just different locations that contain files. Mostly, the particular letters don’t matter; they’re just labels for convenient access. Here at WOU, we use X: for the website. Every time you log in, if you have web editing permissions, your computer should automatically connect (or “map”) the X: label to the network location where the web files are kept.
If that connection isn’t made properly, or is lost for any reason, your computer can’t find the files. As far as it can tell, they just don’t exist. Of course, they almost certainly still do exist, and the network location might even be available; it’s just that if that X: label isn’t mapped, Windows is helpless and can’t even take the first step towards finding the files you need. (By the way, even though X: and the others are nothing more than labels, they’re usually still referred to as “drives” whether they are mapped to an actual hardware drive, or a network location, or anything else. I’ll be using that terminology for the rest of this post.)
The first thing to check is that the X: drive is correctly mapped. Make sure you do this on the computer where you were getting the error, whether that’s your office machine, a terminal server, or whatever. Open “My Computer” from the Start menu and look for a drive labeled “WOU Website (X:)”. If it is there, double-click it; that should open up a folder window with a lot of subfolders inside.
go into it and look for the “las” folder and make sure you can go into it as well. If that works, then the error has probably already corrected itself; if Dreamweaver still won’t work, even after quitting and restarting it, please let me know.
If the X: drive isn’t there, go to the Run command in the start menu and enter “\\firefly.wou.edu\wou_website$” (note that those are backlashes, not normal slashes, and the dollar sign at the end is necessary.) This should open up a folder window in the same network location to which the X: drive should be connected. If it does, please make sure you can go into the “las” folderas well. If that works even if there is no X: drive, it means that the login process did not correctly connect the X: drive. If a logout and login doesn’t bring the X: drive back, or if the X: drive comes back but Dreamweaver still gives you an error, please contact me and include any error messages you saw during the process.
If entering the network location in the Run box doesn’t make a folder window show up, please email me the error message, and if there was no error, please describe the behavior instead. Currently, a few people have reported seeing a login box pop up when they try to connect, but that it won’t accept their login; that is a symptom of a specific network issue we have seen once last week and once this week. Normally this fixes itself in 10-15 minutes, but if you don’t want to wait, or if it is still demanding a login after that time, please call the UCS Service Request Desk at 88925 and explain what is happening. You should be routed to either Brian Berkley or Dave Diemer; one of them should be able to fix the problem. If you aren’t seeing this specific behavior, contact me instead, and only go to the service desk if I’m not available.
Hopefully this will help; if you have any questions, or see any problems not mentioned here, please let me know.