What Should I do When...

What Should I do When...

Common Error Messages

Anyone who regularly uses a computer knows all about error messages. Those of you who are also Windows users probably see more than your fair share of them.

Listed below are troubleshooting guides for some of the more common error messages that my readers and clients see on their computers.

• 404 Not Found  

404 Not Found error messages are frequently customized by individual websites. You can see some of the more creatively designed 404 errors. 

So, keep in mind that the 404 error may show up in just about any way imaginable depending on what website it's shown from.

Here are some common ways in which you might see the HTTP 404 error displayed:

• "404 Error"
   
• "404 Not Found"
   
• "Error 404"
   
• "The requested URL [URL] was not found on this server."
   
• "HTTP 404"
   
• "Error 404 Not Found"
   
• "404 File or Directory Not Found"
   
• "HTTP 404 Not Found"
   
• "404 Page Not Found"

Cause of HTTP 404 Errors

A 404 error is an HTTP status code that means that the page you were trying to reach on a website couldn't be found on their server.

Technically, an Error 404 is a client-side error, implying that the error is your mistake, either because you typed the URL in wrong or the page has been moved or removed from the website and you should have known.

Another possibility is if a website has moved a page or resource but did so without redirecting the old URL to the new one. When that happens, you'll receive a 404 error instead of being automatically routed to the new page.

Note: Microsoft IIS web servers sometimes give more specific information about the cause of 404 Not Found errors by suffixing a number after the 404 as in HTTP Error 404.3 - Not Found which means MIME type restriction.

How To Fix the 404 Not Found Error

1. Retry the web page by pressing F5, clicking the refresh/reload button, or trying the URL from the address bar again.
   The 404 Not Found error might appear for several reasons even though no real issue exists, so sometimes a simple refresh will often load the page you were looking for.
    
2. Check for errors in the URL. Often times the 404 Not Found error appears because the URL was typed wrong or the link that was clicked on points to the wrong URL.
    
3. Move up one directory level at a time in the URL until you find something.
   For example, if www.web.com/a/b/c.htm gave you the 404 Not Found error, move up to www.web.com/a/b/. If you get nothing here (or an error), move up to www.web.com/a/. This should lead you toward what you're looking for or at least confirm that it's no longer available.  
                                                                                                                                                        Tip: If you have moved all the way up to the website's homepage, try to run a search for the information you're looking for. If the site doesn't have a search function, try navigating to the page you want using category links to dig deeper into the site.
    
4. Search for the page at a popular search engine. It's possible that you simply have the entirely wrong URL in which case a quick Google or Bing search should get you where you want to go.
   If you do find the page you were after, update your bookmark or favorite to avoid the HTTP 404 error in the future.
    
5. Clear your browser's cache if you have any indication that the 404 Not Found message might just be yours. For example, if you can reach the URL from your phone but not from your tablet, clearing the cache on your tablet's browser might help.
   You might also consider clearing your browser's cookies, or at least the one(s) involved with the website in question, if clearing the cache didn't work.
    
6. Change the DNS servers used by your computer but usually only if an entire website is giving you a 404 error, especially if the website is available to those on other networks (e.g. your mobile phone network or a friend in another city).
   404's on an entire website isn't particularly common unless your ISP or government filters/censors websites. No matter the reason, if it does happen, giving another set of DNS servers a try is a good step to take. See my Public DNS Servers List for some alternatives and instructions on doing this.
    
7. Finally, if all else fails, contact the website directly. If they've removed the page you're after then the 404 error is completely legitimate and they should be able to tell you that. If they've moved the page, and are generating 404's instead of redirecting visitors to the new page, they'll be happy to hear from you so they can go fix it.

• The 500 Internal Server Error

  











The 500 Internal Server Error message might be seen in any number of ways because each website is allowed to customize the message. Here are several common ways that you might see the HTTP 500 error:

•   "500 Internal Server Error"
   
•   "HTTP 500 - Internal Server Error"
   
•   "Temporary Error (500)"
   
•   "Internal Server Error"
   
•   "HTTP 500 Internal Error"
   
•   "500 Error"
   
•   "HTTP Error 500"
   
•   "500. That's an error."

Cause of HTTP 500 Errors

The 500 Internal Server Error is a very general HTTP status code that means something has gone wrong on the web site's server but the server could not be more specific on what the exact problem is.

Most of the time, "gone wrong" means an issue with the page or site's programming, nothing you have anything to do with.

Note: More specific information about the cause of a particular HTTP 500 error is often provided when it occurs on a server using Microsoft IIS software. Look for numbers after 500 as in HTTP Error 500.19 - Internal Server Error which means Configuration data is invalid. 

 

How To Fix the 500 Internal Server Error

Like I alluded to above, the 500 Internal Server Error is a server-side error, meaning the problem probably isn't with your computer or Internet connection but instead is a problem with the web site's server.

While not probable, it is possible that there's something wrong on your end and we'll look at some things you can try.

1. Reload the web page. You can do that by clicking the refresh/reload button, pressing F5, or trying the URL again from the address bar.
   
   Even if the 500 Internal Server Error is a problem on the web server, the issue may only be temporary. Trying the page again will often be successful.
   
   Note: If the 500 Internal Server Error message appears during the checkout process at an online merchant, be aware that duplicate attempts to checkout may end up creating multiple orders - and multiple charges! Most merchants have automatic protections from these kinds of actions but it's still something to keep in mind.
    
2. Clear your browser's cache. If there's a problem with the cached version of the page you're viewing, it could be causing HTTP 500 issues.
   
   Note: Internal Server Errors are not often caused by caching issues but I have, on occasion, seen the error go away after clearing the cache. It's such an easy and harmless thing to try so don't skip it.
    
3. Delete your browser's cookies. Some 500 Internal Server Error issues can be corrected by deleting the cookies associated with the site you're getting the error on.
   
   After removing the cookie(s), restart the browser and try again.
    
4. Troubleshoot as a 504 Gateway Timeout error instead.
   
   It's not very common, but some servers produce a 500 Internal Server Error when in reality the more appropriate message based on the cause of the problem is 504 Gateway Timeout.
    
5. Contacting the website directly is another option. Chances are good that the site's administrators already know about the 500 error but if you suspect they don't, letting them know helps both you and them (and everyone else).

• BOOTMGR Error Message

  

   

  There are few ways that the "BOOTMGR is missing" error may show up on your computer, but the most common is :
  
  
• "BOOTMGR is missing
  Press Ctrl Alt Del to restart"
   
• "BOOTMGR is missing
  Press any key to restart"
   
• "Couldn't find BOOTMGR

The "BOOTMGR is missing" error displays shortly after the computer is turned on, immediately after the Power On Self Test (POST) is complete. Windows has only initially started to load when the BOOTMGR error message appears.

Causes of BOOTMGR Errors

There are a number of possible causes for BOOTMGR errors, including the most common "BOOTMGR is missing" error message.

The most common reasons for BOOTMGR errors include corrupt and misconfigured files, hard drive and operating system upgrade issues, corrupt hard drive sectors, an outdated BIOS, and damaged or loose hard drive interface cables.

Another reason you might see BOOTMGR errors is if your PC is trying to boot from a hard drive or flash drive that is not properly configured to be booted from. In other words, it's trying to boot from a non-bootable source. This also would apply to media on an optical drive or floppy drive that you're trying to boot from.

How To Fix BOOTMGR is Missing Errors

1. Restart the computer. The BOOTMGR error could be a fluke.
    
2. Check your optical drives, USB ports, and floppy drives for media. Often times, the "BOOTMGR is Missing" error will appear if your PC is trying to boot to a non-bootable disc, external drive, or floppy disk.
   
   Note: If you find that this is the cause of your issue and it's happening regularly, you might want to consider changing the boot order in BIOS so the hard drive is listed as the first boot device.
    
3. Check the boot sequence in BIOS and make sure the correct hard drive or other bootable device is listed first, assuming you have more than one drive. If the wrong drive is listed first, you could see BOOTMGR errors.
   
   I know I sort of hit on this in the troubleshooting step above, but I wanted to call out specifically that you might have the wrong hard drive listed, as many BIOS/UEFI systems allow you to specify specific a particular hard drive to be booted from first.
    
4. Reseat all internal data and power cables. BOOTMGR error messages could be caused by unplugged, loose, or malfunctioning power or controller cables.
   
   Try replacing the PATA or SATA cable if you suspect it might be faulty.
    
5. Perform a Startup Repair of Windows. This type of installation should replace any missing or corrupt files, including BOOTMGR.
   
   Even though a Startup Repair is a common solution for BOOTMGR problems, don't worry if it doesn't fix your problem. Just continue troubleshooting - something will work.
    
6. Write a new partition boot sector to the Windows system partition to correct any possible corruption, configuration problem, or other damage.
   
   The partition boot sector is an important piece in the boot process so if there's any issue with it, you'll see problems like "BOOTMGR is Missing" errors.
    
7. Rebuild the Boot Configuration Data (BCD). Similar to the partition boot sector, a corrupted or incorrectly configured BCD could cause BOOTMGR error messages.
   
   Important: The following troubleshooting steps are much less likely to help fix your BOOTMGR problem. If you've skipped any of the above ideas then you may have overlooked a very likely solution to this problem!
    
8. Check the hard drive and other drive settings in BIOS and ensure they are correct. The BIOS configuration tells the computer how to use a drive so incorrect settings can cause problems, including BOOTMGR errors.
   
   Note: There's usually an Auto setting in BIOS for hard disk and optical drive configurations which is usually a safe bet if you're not sure what to do.
    
9. Update your motherboard's BIOS. An outdated BIOS version can sometimes cause the "BOOTMGR is Missing" error.
    
10. Perform a clean installation of Windows. This type of installation will completely remove Windows from your PC and install it again from scratch. While this will almost certainly resolve any BOOTMGR errors, it's a time consuming process due to the fact that all of your data must be backed up and then later restored.
    
    If you can't gain access to your files to back them up, please understand that you will lose them all if you continue with a clean installation of Windows!
     
11. Replace the hard drive and then install a new copy of Windows. If all else has failed, including the clean installation from the last step, you're most likely facing a hardware issue with your hard drive.

 

BOOTMGR Errors Apply To

BOOTMGR issues apply to Windows 8, Windows 7, and Windows Vista operating systems only.

Windows XP does not utilize BOOTMGR. The equivalent function in Windows XP is NTLDR which produces the NTLDR is Missing error when there's a similar problem.

• 403 Forbidden

403 Forbidden error messages are sometimes customized by the websites they appear on but for the most part, you'll see them in one of the following ways:

• "403 Forbidden"
   
• "HTTP 403"
   
• "Forbidden: You don't have permission to access [directory] on this server."
   
• "Forbidden"
   
• "Error 403"
   
• "HTTP Error 403.14 - Forbidden"
   
• "Error 403 - Forbidden"
   
• "HTTP Error 403 - Forbidden"

The 403 Forbidden error displays inside the browser window, just as web pages do. 403 errors, like all errors of this type, might be seen in any browser on any operating system.
In Internet Explorer, a The website declined to show this webpage message indicates a 403 Forbidden error. The IE title bar should say 403 Forbidden or something similar.
 403 errors received when opening links via Microsoft Office programs generate a Unable to open [url]. Cannot download the information  you requested. message inside the MS Office program. Windows Update may also report an HTTP 403 error but it will display as error code 0x80244018 or with the following message: WU_E_PT_HTTP_STATUS_FORBIDDEN.

Cause of 403 Forbidden Errors

The 403 Forbidden error is an HTTP status code that means that accessing the page or resource you were trying to reach is absolutely forbidden for some reason. In other words: "Go away and don't come back here."
Note: Microsoft IIS web servers provide more specific information about the cause of 403 Forbidden errors by suffixing a number after the 403 as in HTTP Error 403 .14 - Forbidden which means Directory listing denied.

How To Fix the 403 Forbidden Error

1. Check for URL errors and make sure you're specifying an actual web page file name and extension, not just a directory. Most websites are configured to disallow directory browsing so a 403 Forbidden message when trying to display a folder instead of a specific page is normal and expected.
   
   Important: This is, by far, the most common reason for a web site to return the 403 Forbidden error. Be sure you fully explore this possibility before investing time in the troubleshooting below.
   
   Tip: If you operate the website in question, and you want to prevent 403 errors in these cases, enable directory browsing in your web server software.
    
2. Clear your browser's cache. Issues with a cached version of the page you're viewing could be causing 403 Forbidden issues.
    
3. Log in to the website, assuming it's possible and appropriate to do so. A 403 Forbidden message could mean that you need additional access before you can view the page.
   
   Typically, a website produces a 401 Unauthorized error when special permission is required but sometimes a 403 Forbidden is used instead.
    
4. Clear your browser's cookies, especially if you typically log in to this website and logging in again (the last step) didn't work.
   
   Note: While we're talking about cookies, be sure you have them enabled in your browser, or at least for this website, if you do actually log in to access this page. The 403 Forbidden error in particular indicates that cookies may be involved in obtaining proper access.
    
5. Contact the website directly. It's possible that the 403 Forbidden error is a mistake, everyone else is seeing it too, and the website isn't yet aware of the problem.
    
6. Contact your ISP if your still getting the 403 error, especially if you're pretty sure that the website in question is working for others right now.
   
   It's possible that your public IP address, or your entire Internet Service Provider, has been blacklisted, a situation that could produce a 403 Forbidden error, usually on all pages on one or more sites.
7. Come back later. Once you've verified that the page you're accessing is the correct one and that the HTTP 403 error is being seen by more than just you, just revisit the page on a regular basis until the problem is fixed.

* By: Hams Saad AlHarthi.



 
[source]