Wednesday, September 29, 2010

MSN Messenger Error 80048820

Error 80048820 can occur when trying to launch and log on to the Microsoft Messenger application. When this happens, you will often be greeted by a pop-up box that says “Sorry, we were unable to sign you in to the MSN Messenger at this time. Please try again later.” In the bottom left hand corner, a numeric code is shown that tells you which error you have encountered, in this case, 80048820.

In most cases, this error is triggered because the system time or date is incorrect and needs adjusting. Other possible causes of error 80048820 include: Internet Explorer has an incorrect proxy setting, the softpub.dll file has become de-registered, or firewall problems. In order to resolve this error and stop it from happening, you can do the following:
  1. Log on as an administrator and correct the computer’s clock and date so that it is showing the right time. This is the most common cause of this error, so once you have done this, try launching MSN Messenger. If this did not correct the error, move on to the following.
  2. In Internet Explorer, go to the Tools menu and click Internet options. Go to the Connections tab in the pop-up box that opens and then click LAN setting. In the LAN setting box, make sure that the check box beside “Use a proxy server for your LAN (These settings will not apply to dial-up or VPN connections)” is unchecked and then check the box beside “Automatically detect settings.” Click OK through the boxes to save the settings.
  3. Turn off your firewall temporarily and try to connect. If you can, then you need to adjust your settings in your firewall so that MSN Messenger is allowed access when the firewall is turned on.
  4. Finally, in some cases, correcting this issue can be as easy as unplugging your modem. Removing the power source for 15 – 30 seconds from your modem resets the connection and may be all you need to get yourself back on Messenger.

Wednesday, September 22, 2010

Internet Connection Error 619

When attempting to connect to the Internet from a computer that has Windows XP installed, a connection error may be generated. If connection error 619 occurs, it often causes the connection attempt to fail, which means that you will not be able to browse the Internet at all.

Internet connection error 619 can be caused by a number of different factors, including: a third party program, a problem with the access numbers provided by your Internet Service Provider (ISP) for those using dial-up, a modem problem, or a router problem. Depending on what is causing the error, there are different methods for resolving it.

If a third party program is causing a problem with your Internet connection, your best bet is to uninstall it. Once the program has been uninstalled, you should try connecting to the Internet to ensure that has resolved the problem. If you can once again connect to the Internet, you can try re-installing the program to see if it was just an issue with that installation. If it once again interrupts your connection, you should remove the third party program from your computer.

With a dial-up connection, there are often several numbers you can try to connect to the Internet. You should try all of them to see if any of them will connect. If you are still having issues, you may have to make some changes to your telephone line, like removing call waiting or adding a custom prefix when dialing your ISP.

To confirm if there is a problem with your modem, you should check its status in Device Manager. If there is an X or any issues, you can uninstall your modem. Once it has been uninstalled restart your computer and it will attempt to install the hardware. You may have to provide a disk for this. Once your modem has been installed, you can run a query on its set up from within the Properties window. If it appears to be set up correctly, try connecting again.

To resolve issues with your router, you will need the manual that was sent with it. Within that, you will find an IP address to enter so that you can check the configurations of your router. Follow the steps and ensure your router is set up as provided by your ISP.

If none of these remedies work, contact your ISP to determine if the problem is at their end.

Thursday, September 16, 2010

npswf32.dll Error

When browsing different sites on the Internet, it is not uncommon to come across sites that use Flash and Shockwave as part of their programming. Particularly those sites that are animated will have some kind of Flash programming embedded. The npswf32.dll file is associated with the plug-in that is needed to run the Shockwave animations on these websites.

When there is an issue with npswf32.dll, it will often cause a browser to crash, particularly with older versions. The fact that your browser crashes and you get an npswf32.dll error means that either your browser is out of date or the version of the npswf32.dll file on your computer is out of date.

To stop your browser from crashing when you visit pages that include Shockwave applications, you can do one of two things (in some cases, you may need to do both):
  1. Update your browser – Older versions of Internet browsers may not be able to connect properly with newer Flash plug-ins. Whichever browser you are using, you should download and install the latest version available. If you are still having problems after doing this, then it is likely that you will also have to update the npswf32.dll file version.
  2. Update the npswf32.dll file – If you don’t know what version of the npswf32.dll file you are using, it won’t hurt to try updating it. You can do this in a number of ways. The easiest and best way is to install the latest version of the Flash player. By doing this, you will be installing all the most up-to-date files associated with it. The npswf32.dll file is often found in a number of places on your computer, so you could copy it from another location, or download it from the Internet and replace the file you have.

Tuesday, September 14, 2010

Windows Media Player Error C00D11B1

If Windows Media Player cannot play a particular file, you may encounter the C00D11B1 error message. There are a number of different reasons that this error message is displayed, including:
  • The driver for the sound card in your computer needs to be updated.
  • The sound device you are trying to use to play the file has an out of date driver.
  • The sound device is not functioning properly.
  • A sound card or hardware to output sound has not been installed on your computer.
  • If trying to play an Internet file, the server hosting the file may be busy.
  • The file itself may be corrupt.
Because this is such a wide ranging and varied list, the first thing that needs to be done is to determine what is causing the error itself. Obviously, if you haven’t got a sound card or sound device installed, then you will need to do so. If you do have a sound card and sound device installed, then the best way to determine if one of them is the issue is to use Device Manager.

To run Device Manager, right click Computer (My Computer) in the Start menu and then click Manage. When the window opens, choose Device Manager from the left hand column. In the center column, expand Sound, video and game controllers. This should list your devices. If there is an X beside any of them, then it has been disabled. Right click and click enable.

To update the driver, right click your sound card or device in Device Manager and click Update Driver Software.

If the problem is with an Internet file, you can’t do a lot about it and will just have to try later. Finally, if the file is corrupt, you will not be able to play it and should try to find a new version of the file, one that is not damaged.

Wednesday, September 8, 2010

Runtime Error 339

One of the most common error types to come across when working with a Windows computer is runtime errors. Particularly as computers age and are used more and more, it is likely that runtime errors will occur more often.

Runtime error 339 commonly occurs due to a missing file when trying to install software on a computer. Specifically, this error occurs if the file that is missing is an .ocx file. OCX files are commonly referred to as ActiveX controls. These types of files can be used by many different software programs and usually control the interface between the user and the program.

Unfortunately, runtime error 339 doesn’t occur when you are installing the program, but is usually triggered when you try to launch it after installation or try to use some part of the program. The specific activity requires the missing .ocx file, which in turn causes the error message.

The most common reason for runtime error 339 messages is missing or corrupt Java files or ActiveX controls. Ensuring your versions of Java and ActiveX are up-to-date is one way of combating these types of errors. Also, the files may have been corrupted due to errors in the registry of your computer. In this case, it is worth running a scan of your hard drive and then using a registry cleaner to get rid of any corrupt or damaged files. Once you have done so, you should try re-installing the program.

Friday, September 3, 2010

Windows Installer Error 1722

While most software programs come with their own installation program, it is not uncommon for the installation to actually be run by the Microsoft Windows Installer. Microsoft included the Microsoft Windows Installer as a built in feature of Windows XP, 2000, 2003 and Vista.

If everything is running normally, upon starting the installation, you would just have to click through each window in the step-by-step process until the installation is complete. Unfortunately, this doesn’t always happen and, when there is a problem with a software installation, that is when the error 1722 message can appear.

Installer error 1722 occurs when the Windows Installer cannot run the necessary files required to install the program. As a result, the installation may fail and quit prematurely or you may get a message saying there is a fatal error during installation. The reason the installation fails is usually due to the files being damaged, corrupted or missing or due to a problem with the Windows Installer itself.

There are a number of ways to fix an installer error 1722, which include:
  • Try using a different software program. If you have downloaded it, delete the original and download again as there may have been a problem during the download. If you are installing from a disk, try using a different one to see if the problem persists.
  • Ensure the latest version of InstallShield is installed on your computer. If not, download and update your version.
  • If you are prompted that the files can’t be found, you can do a search to point the installer to the correct location. If the files are in fact missing, you will need a new program to install.
  • Finally, if none of the above work, you may need to run a registry cleaner to remove any corrupt files left from previous attempts at installation. Once your hard drive has been cleaned up, the installer should run fine.