Outlook Connection Errors

When you try to send and receive e-mail using Microsoft Outlook, you may be familiar with some of the common error messages that indicate there is a problem with the connection or server. The server cannot be found or the server being interrupted are both common error messages that Outlook users may receive.

Listed below are just a few of the most common connection related error messages that are sent by Outlook:

• The server could not be found (0x800ccc0d)
• Sending and Receiving reported error (0x800ccc0f)
• Sending and Receiving reported error (0x80042109)
• The operation timed out waiting for a response from the POP server (0x8004210a)
• A time out occurred while communicating with the server (0x800ccc19)

Although these error messages appear to be different, they all basically indicate a problem with the connection, which is often due to:

• Your e-mail service is temporarily unavailable
• You are not connected to the Internet
• Outlook was accidentally removed from your computer or was damaged during installation

To troubleshoot through these common connection problems, try the following:

1. Try to connect two or three times. Sometimes if an e-mail server is unavailable, it is only for a few minutes before it works again. E-mail service problems can only be repaired from the service end. It may be as simple as waiting for your connection to be reinstated.
2. Verify that you are connected to the Internet by starting your browser and typing in an address. If you are able to load the page, then this is not the issue.
3. Send yourself a test e-mail using your Outlook. If this works, it would appear that connectivity and Outlook are both working as they should be.
4. You can start from scratch and re-install Outlook on your computer system by either installing a brand new version or doing an Internet search for the latest service pack for your operating system. If you choose to do this, you should visit the Windows website and identify the Windows program that you currently have, so you download the correct service pack for your system. This download will provide you with a fresh copy of Outlook without any problems.

USB Device Error Code 10 in Windows XP

Plugging a USB storage device into your computer can often result in either nothing or an error code; both being frustrating for the user. USB stands for Universal Serial Bus which is a way for a computer to establish a communication link between a device, such as a memory stick or flash drive, and the host computer.

Portable storage devices are small and can be purchased with different amounts of memory on them. Many people use portable storage devices to store information that they can easily transfer from one computer system quickly and easily. As with any computer equipment, you have to be prepared that systems, devices and connections don’t always work as they are intended. USB error codes do occur and usually in a few steps, problems with the device or the USB port can be easily remedied.

If you get any type of USB error code, you first want to ensure that the device itself is working. Plug the USB flash drive into the USB port on another system and see if you have any problems. If not, the device is not the problem; rather it is the configuration of the computer that would not accept the device. As with other errors, different codes mean different things. For instance, the code 10 error indicates that the device cannot start.

If you are using Windows XP and have encountered a USB error code, the best way to resolve it is to remove and re-install all of the USB controllers:

• Click on Start
• Right click on My computer
• Click on Properties
• Click the Hardware tab
• Expand the Universal Serial Bus Controllers Section
• Right click the devices under the USB controllers and click Uninstall to remove them one at a time
• Restart the computer, which will allow the computer to reinstall the USB controllers
• Plug in the removable USB storage device
• Test your USB device to see that this has resolved the issue and the error code 10

If you continue to have problems with USB error codes you should first contact Microsoft Support or your local computer repair shop for further assistance, as this could actually be a faulty connection in the computer hardware itself.

Mac Error Code 0

It may make you wonder why any error code would have a 0 rather than a number to identify it. This is a good question that remains without an answer, but error code 0 does mean something in the world of Mac computers. The error message often says that the file cannot be copied or an unexpected error has occurred, code 0. This usually signifies that the file is too big to copy.

The Mac error code 0 is considered an unidentified error that typically occurs when transferring files that are bigger than 4GB to a FAT32 hard drive. The File Allocation Table (FAT) system is used on many computer file systems and memory cards as a way to organize data in a relatively simplistic way. It is commonly criticized because it is said to make poor use of disk space, which causes overloading. It is supported by almost all of the current operating systems, which makes it very versatile. Placing many files on a system that has a FAT32 system can cause the system to slow down and even crash.

A Mac has a file size limit of 4GB by design. This means that it is likely that you will receive an error message if the file that you are trying to download or copy is too large for the file system. Typically, this will occur when you are attempting to copy a large file to a disk that is in the FAT32 or MS-DOS format. These systems are not equipped to accommodate files that are larger than 4GB, even if there is enough space on the drive to do so.

If you are trying to copy a file of 4GB or larger, you will need to reformat the hard drive to accommodate the size of the file. You can reformat your hard drive by:

• Backup all of your files before attempting reformatting.
• Open the Disk Utility from /Applications/Utilities/Disk Utility.
• Double click on the Disk Utility program to bring up a list of all of the drives available on the computer.
• Choose the name of your hard disk by highlighting it.
• Select the Erase tab. This will display the options for erasing the hard drive and reformatting it to work on the Mac.
• From the Volume Format menu you will choose Mac OS Extended. It is also recommended that you name your hard drive.
• Click the Erase button and then click Erase again to confirm this is what you want to do.
• Once the erase function has finished, quit out of Disk Utility and then you can reload any data you have backed up from your backup copy.

Reformatting your drive should both eliminate the Mac error 0 and allow you to have more space on your hard drive.

Firefox Unresponsive Script Warnings

Firefox is a web browser designed by Mozilla and is an alternative to Microsoft Internet Explorer. When using Firefox, you may receive an error message that states Warning: Unresponsive script or a script on this page may be busy or it may have stopped responding. A script is the set of instructions that provide a program with the directions to carry out a task. An unresponsive script is one that cannot move to action to carry out the command being asked of it.

Usually, Firefox generates these types of error messages because it thinks a script may be running out of control, or the web page you are trying to access is not working. Whatever the reason for the unresponsive script warning, there are a number of things that can be done to rectify the situation.

First, you can let the script run and see if it corrects itself. You can choose to click the Continue button, which will allow the script to keep running. Over time, it may finish running and the web page will begin working again. Unfortunately, this is not always the case and clicking the Continue button may just bring up the same error message again. If the Continue button does not work out the error, take the following steps to increase the length of time you allow the script to run:

• In the address bar, type about:config and press Enter.
• A warning message that states “This might void your warranty!” may pop up. If this comes up, click the “I’ll be careful, I promise!” button.
• You will be sent to the about:config page. Search the available options for the dom.max_script_run_time. You can type the preference name in the Filter: box to speed up the process.
• Double click on this preference.
• Change the 10 to a 20 and click the OK button. This will increase the amount of time the script is able to run in the hopes that it will have enough time to fix the error by itself.

If you have noticed that you only receive unresponsive script warnings when accessing certain websites, blocking these scripts from running on those sites will solve the problem.

• Do an Internet search for the Firefox YesScript extension and download it.
• Install YesScript as an add-on by following the prompts that will walk you through the download process.
• Restart Firefox.
• Open the Firefox window and click Tools.
• Select Add-ons from this menu.
• Click Options.
• In the YesScript Blacklist box, type the URL of the site where you are having script error problems.
• Click Add.

By completing the above steps, YesScript will block the site from running script errors when you are on it.

CPU Problems

The central processing unit (CPU) does most of the data processing in the computer, making it an integral system of the computer system. There are some common computer symptoms that are caused by CPU issues; however, CPU failure is much less common than other types of issues that come along with being a computer owner. It can be difficult to determine if a faulty CPU or motherboard is the culprit of your computer problem, but if you rule out other issues and are still left with a problem, it is likely that an issue with the CPU is probably the culprit.

Computer freezes, error messages, strange sounds and the inability to turn the computer on or off can all be indicators of CPU problems. Power failures or surges or electrical problems are the most common causes of CPU issues. Purchasing a surge protector is one of the main things that you can do to prevent CPU damage. CPU damage can be costly because it often requires complete replacement of your computer or minimally the CPU unit.

A power failure will most likely produce one of the following problems that could damage the CPU and will prevent your computer from working properly:

• Corruption of the operating system, motherboard, memory, power supply or CPU
• Only the fan runs when you turn on your computer
• The computer freezes up randomly
• The PC randomly shuts itself off

All of these scenarios are probably indicators of power supply issues or CPU problems. Start by checking the power supply and ensure that everything is connected properly, and then try restarting your PC. If this does not work, you may be looking at motherboard or CPU damage, which will usually require the expertise of a trained technician to rectify.

CPU issues are fatal to your system. Often the symptoms of errors or problems with your computer can be one of many things. Ruling out the small things can help to better determine if the CPU has been damaged. If you have had a power failure or do not have a power strip with a surge protector during a power loss, it is very possible that there is serious damage to your system. Ruling out corrupted memory, software installation problems and viruses before consulting with a computer repair technician may save you a few dollars in diagnostic costs.

The dlhost.exe Imposter

Problems with dll files, including corrupted or missing files, can cause an array of issues with your computer system. dll files are necessary to ensure that the operating system of the computer is functioning properly. These files are not only prone to errors, but to virus imposters that may pose as the files to get into the computer system and infect it.

The dllhost.exe is a crucial part of the Windows Operating System and manages the dll-based computer applications. The dllhost.exe program controls the processes in the IIS, or Internet Information Services, and many programs utilize this application to function properly. dllhost.exe comes preinstalled on your system when you purchase it, and it is always located on your hard drive in the following location: C:\Windows\System32\dllhost.exe.

Unfortunately, there is a spyware virus circulating that uses the same name as the dllhost.exe file. The virus disguises itself as an executable file in an attempt to fool the user. The best way to determine if the dllhost.exe file is valid is to take a look at your C drive. The correct dllhost.exe file is the one that is installed as listed above. If you find a dllhost.exe file located in areas of your computer other than as listed, it is because of a virus or spyware. Note that a dllhost file that is posing as a virus or spyware may be spelled slightly different than the original file. Remember that a virus and spyware is smart enough to be able to infect programs. This may be misspelled purposefully to keep you from locating and removing it.

By performing a search for dll files in each of your drives, you will be able to quickly produce a list of the dll files. Doing a quick search will make it easy for you to check to see if there is an imposter dll file in a drive other than the C drive. If the dll file is listed in any drive other than C you can assume that you have a virus. At this point, you should run a virus scan and remove any potentially threatening files that result from the scan.

If you can determine that the dllhost.exe file is in the correct location and with the exact spelling, a virus is probably not the cause for the issue. By ruling this out you can move on in your search for the dll error culprit, as viruses are not the only causes of dllhost.exe errors, but they are one of the more common ones.

Common Runtime Errors

A runtime error is a computer error message that occurs during the execution of a program. Runtime errors indicate problems with the program or design of the program. Typically, these errors are a nuisance, but usually, they are not critical or fatal. In most circumstances, there is an easy fix to this type of error that can be completed successfully by the user.

Runtime error messages may arise while trying to access a webpage or while opening a program or working in a document. There are several kinds of runtime errors that you may receive. Like other common computer errors, runtime errors are given with a number after the error, which explains what causes the error.

For example, you may receive an error message that states: runtime error 48. The fact that 48 is included with the error message is a way to clarify what exactly is causing the error with your machine. In order to best fix the error, users should use the numeric code to find the reason for the error, which should also identify the best approach for fixing it.

The following are a few fairly common runtime errors. Listed below each error is a possible cause, as well as an option for fixing the error.

Runtime Error 48 – Error Loading DLL

• Conflicts with other programs

Sometimes when too many programs are running at once this can prompt a runtime error. Close down all open programs and try again to open the program, document or webpage that you were working on when you originally received the error message. It may seem too easy that just closing out multiple programs will eliminate this error, but this simple solution is often the all that you need to do.

Runtime Error 58 – File Already Exists

• Software issues, add ons or plug ins

If you are receiving a runtime error while trying to use software, add ons or plug ins that have been installed on the computer, you can check your recently installed software to see if there are available updates for it. Often times, running out-of-date software can prompt a runtime error. When you receive a prompt that indicates that upgrades are available for your programs, you should accept these updates regularly as this will help eliminate these errors from occurring. If updating the software does not eliminate the runtime error, it may indicate that there is a problem with the software itself. In this case, you can uninstall and then reinstall the software. If this does not work, you should notify the support that is offered with the software package for assistance.

Runtime Error 7 – Out of Memory

• Memory issues

A runtime error 7 indicates that your computer is low on memory. You can start by deleting files and programs that you no longer use. This will help, but probably will not offer a long-term solution. The more programs you install and files that you save on your system, the more memory is taken up. If runtime errors are chronic, you may want to consider purchasing more memory. Memory can easily be purchased and installed by any computer repair shop.

The acrord32.exe Application Error

Most people are familiar with Adobe Acrobat Reader, which was developed by Adobe in the 1990’s to access and read PDF, or portable document format, files. PDF is a universal computer text file format that was designed by Adobe that preserves a document and allows it to be read by any computer that has the Adobe program installed. The acrord32.exe application error is usually a fault of Adobe Acrobat Reader and typically occurs because this is such a large program.

The acrord32.exe file is a file that automatically runs on your system whenever you are using Adobe Acrobat Reader to view a PDF file. In order for the file to be loaded and viewed properly, acrord32.exe needs to be intact and running properly. Sometimes, internal issues occur that cause the acrord32.exe to send an error message, such as acrord32.exe application error.

When you open Adobe Acrobat Reader, acrord32.exe automatically runs, and when you close Adobe Acrobat Reader, it should automatically shut down after the program closes. This process of running and stopping should start and end automatically, without any command from the user. The acrord32.exe file is very large and takes up a great deal of memory. In older computers or computers without sufficient memory, using Adobe can take up a great deal of computer memory space, causing computer freezes, slowing the computer down or generating an acrord32.exe application error. If you frequently use PDF files, increasing your memory is the best option to eliminating the frustration of this error.

If there appears to be problems running Adobe Acrobat Reader or the acrord32.exe file does not shut down when you close out Adobe, this is a sign of a potential problem such as virus. What sometimes happens is that a virus may pose as an acrord32.exe file and attempt to infect your computer system. If you are seeing repeated issues when using Adobe or with your computer in general, like slow running programs or frequent error messages, you may have a virus. At this stage it is important to run a virus scan on your system.

If you are confident that there is nothing critically wrong with your computer and want to eliminate this error from randomly popping up, this can be done in a few small steps. Open Adobe Acrobat Reader. Click Edit on the menu bar. Select Preferences and under the Categories heading, select Internet. Where the web browser option box is located, uncheck the box that says Display PDF in Browser. Close Adobe Reader and restart your computer. By doing this, the reader will not be displayed within your Internet browser automatically, which can then improve connection times greatly.

Windows Vista - BOOTMGR is Missing Error

Encountering the BOOTMGR is missing error while trying to boot a Windows Vista computer is not that uncommon. While this can be annoying, particularly if you are in the middle of something, on the positive side, this type of error is typically not related to an internal problem or hardware issue. Missing BOOTMGR errors are usually relatively quick and easy to fix.

Unfortunately, Windows Vista was released with a few bugs, but the good news is that they can be repaired quite easily. For many of these errors, including the BOOTMGR is missing error, you will need the Windows Vista CD. It is a good practice to keep all of your computer software available and in good working condition in the event that you ever need to reload a program in the future.

The reason that the BOOTMGR is missing error occurs is because the system may find a corrupted or missing file when trying to boot up. As we all know, problems with corrupted files often lead to many of the errors that we face when trying to use our computers.

When you receive the BOOTMGR is missing error, you correct the error by taking the following steps:

• Insert the Windows Vista CD.
• Press CTRL + ALT + DEL to restart your computer.
• When the computer starts up, you may be asked questions such as: what language you want to proceed in, the time and so on. Answer these questions appropriately.
• Click Next at the first prompt that you receive after booting up.
• A link will be provided with an option that reads: Startup Repair. Click this link.
• The installation process will search your computer for the Vista installation directory. If there is more than one directory, select Microsoft Windows Vista and click Next.

Your system will now be checked for the problems that are causing the BOOTMGR is missing error. Don’t be alarmed if the process takes a few minutes. Your computer may also restart itself randomly during the repair process; this is normal. Once the process is complete, you can reboot your system and remove the installation CD.

These simple steps should remedy the problems at boot up and the BOOTMGR missing error should disappear.

Understanding POST Error Codes

POST, or Power on Self Test, is a series of tests done by a computer, router or printer before booting up and is done every time a computer is turned on. POST is controlled by your computer’s BIOS, and similar to BIOS, POST also uses BEEPS to communicate boot up problems. For more information, on the BIOS beep errors, please see the BIOS Beep Error post.

When detected, the POST error will cause a beep and then may also display an error code on the screen. POST errors are generated from a problem with the tests that automatically happen during the boot up process. The BIOS generates the errors in the POST and a series of beeps that may include a number code will be generated. The beep codes in addition to the error message can be used to determine what the problem is, and hopefully offer a simple solution.

POST error codes are different from system error codes. Although the codes may share numbers with some common error messages such as the STOP code or system error code, POST codes have very different meanings and solutions than other error codes. A POST error code is a code generated using the hexadecimal number system, which is a number system that uses 16 symbols to represent values and is common in computer language.

There are hundreds of different beep codes. The specifics of the beeps and the meaning of them will depend largely on your system. Many operating systems are similar but not exact in the beep codes used to identify an error. If you are attempting to troubleshoot through a POST error, be sure you are using the information as it relates to your specific system.

Understanding how BIOS and POST works is the best first step to being an informed computer user. For example: in IBM computers, two short beeps indicate one of many general POST errors. When an error occurs the computer will generate the beeps along with the specific error code that is displayed on the computer screen. Also specific to IBM computers, a continuous beep indicates that a power supply or a keyboard problem exists. Errors such as these are very simple to fix. A power supply may be unplugged or the keyboard may be detached.

Often, POST errors provide specific information that can be easily understood, allowing the user to repair the problem quickly and easily. Other errors indicate much more serious problems, such as one long and one short beep, which indicates system board issues, and four beeps indicating a motherboard timing issue. The more serious errors will require the assistance of a trained technician.

Knowing your system information and what the beep codes mean can give you the knowledge you need to fix the simple things yourself and leave the more complex errors to the trained professionals.

Kernel Panic in Mac OS X

A kernel panic is a term specific to UNIX operating systems, such as Mac OS X, and it is the equivalent to the term bug check in the Windows world. It panic is the action taken when an internal fatal error is detected by the system. A kernel panic is designed by the operating system to react by sending out an error when something goes wrong.

If you receive a kernel panic error message that says you need to restart your computer, or that your Mac won’t start up in Mac OS X, the first thing you should do is restart your system to see if the same error remains when you boot back up. Basically, when a kernel panic occurs, there has been a system crash in Mac OS X. The computer system responds to the panic by doing one of two things: waiting for the system to be manually rebooted or initiating an automatic reboot.

There are several reasons why a kernel panic occurs. The information provided with a kernel panic is often very technical, and it has the goal of assisting a system administrator in diagnosing a computer problem. Some of the causes of kernel panics may require technical assistance beyond that of the average user. Listed below are a few of the causes and how to go about resolving them.

Defective or incompatible RAM or lack of hard disk space or RAM

This is the most frequent cause of a kernel panic error. You can first try to defragment your system and clean up your hard drive to get more available memory. In the Applications directory, open the Utilities folder and then open the Disc Utility Program. Select the drive you want to defragment by highlighting this drive from the list available. This process may take some time so plan to do this during a time when you will not need your computer, overnight for instance.

Defragmenting may work for the short term, but the best way to resolve a RAM issue over the long term is to purchase more RAM. Memory can easily be purchased through a computer store, and either you or a computer technician can install it. It is important to ensure that the RAM is compatible with Mac OS X.

Incompatible, or corrupted kernel extensions, or drivers

Third party hardware that is outdated or programs that are incompatible with the Mac OS X system being used can cause a kernel panic error. Ensure that the software and hardware that you are using is compatible with your Mac OS X system. This should be listed in the software documentation that you have. If you find you are using something that is not compatible, you should remove it and install something that is compatible. You can also check the website of the applications you are using and download or agree to updates as they are available. Most software prompts you periodically to search for updates. If you know that your software is compatible, keeping it up to date is the best way to avoid kernel panics.

Hard disk corruption

When there is a problem with your hard disk, it will often result in the freezing of your computer or your computer running slowly. If freezing occurs, it is a sure sign of trouble internally. In this case, you will want to obtain assistance from a professional to repair your corrupted hard disk.

DNS Lookup Failed Error

The Domain Name System (DNS) is a system of servers that translates domain names into IP addresses. The DNS system handles the workings of making Internet connections and DNS lookup failed simply means that you are unable to connect to a specific website. This can in fact happen for a variety of reasons.

Issues with the DNS do not always cause an actual error message to surface; rather they may take the form of other symptoms; such as:

• Inability to log on or very slow logon.
• Unable to join a domain or run a logon script.
• Inability to access an IP address.

Interestingly, when you visit websites, Windows automatically places DNS information about the site into a cache on your computer. A cache is a type of supply closet on your computer and the DNS stores negative and positive entries here. When the information on the website matches with what is stored by Windows, the connection is successful. If the Internet Service Provider does not update the DNS information, this may conflict with the information stored on your computer, creating a negative entry that causes a DNS lookup failed error.

DNS lookup failed errors may or may not be something that you can correct. These errors can be due to issues with the Internet Service Provider (ISP) or your cache may just be overloaded with negative or conflicting information. Cleaning out your cache is the first thing you can do, which will also let you know whether the error is due to your system or the ISP.

Flushing your cache will empty all the information stored on your computer and start you back at a clean slate. By cleaning out all of the information in the cache, there will be no conflicting information to cause DNS lookup failed errors. To do this, you will need to open the command screen.

For all Windows users except Vista and Windows 7, go to Start > Run. Click Run and in the pop-up box that opens, type: com or command and press Enter.

For Windows Vista and Windows 7 users, go to Start > All Programs > Accessories > Command Prompt. Right-click on Command Prompt and select Run as Administrator.

The remaining instructions are the same for all Windows users. Type ipconfig/flushdns and hit Enter. Once the DNS cache has been flushed, a confirmation window should open stating that the DNS resolver cache was successfully flushed. This should eliminate future DNS lookup failed errors. It is not a bad idea to do this when you begin to experience any of the symptoms listed above.

If you are still experiencing DNS failed lookup errors after you have flushed your cache, then it is likely an error at the ISP end of things. Unfortunately, there is not a lot you can do about this, which means you may not be able to access the site until the error is resolved.