List Of Error Codes And Its Description Related To Dial-Up Connection Or VPN In Windows 7

List Of Error Codes And Its Description Related To Dial-Up Connection Or VPN In Windows 7

By   19:14   1 comment:

This article lists the Error Codes that you may receive when you try to make a dial-up connection or a VPN connection on a computer that is running Windows 7.

The following is the list of errors and its description that you may receive when you try to make a dial-up connection or a VPN connection:

• 600  An operation is pending.
• 601 An invalid port handle was detected.
• 602 The specified port is already open.
• 603 The caller's buffer is too small.
• 604 Incorrect information was specified.
• 606 The specified port is not connected.
• 608 A device was specified that does not exist.
• 609 A device type was specified that does not exist.
• 610 An invalid buffer was specified.
• 612 A route was specified that is not allocated.
• 615 The specified port was not found.
• 616 An asynchronous request is pending.
• 617 The modem (or other connecting device) is already disconnecting.
• 618 The specified port is not open.
• 619 A connection to the remote computer could not be established, so the port used for this connection was closed.
• 621 The system could not open the phone book file.
• 622 The system could not load the phone book file.
• 623 The system could not find the phone book entry for this connection.
• 624 The system could not update the phone book file.
• 625 The system found invalid information in the phone book file.
• 627 A key could not be found.
• 628 The connection was terminated by the remote computer before it could be completed.
• 629 The connection was closed by the remote computer.
• 630 The modem (or other connecting device) was disconnected due to hardware failure.
• 631 The user disconnected the modem (or other connecting device).
• 632 An incorrect structure size was detected.
• 633 The modem (or other connecting device) is already in use or is not configured properly.
• 635 There was an unknown error.
• 636 The device attached to the port is not the one expected.
• 638 The remote server is not responding in a timely fashion.
• 645 There was an internal authentication error.
• 646 The account is not permitted to log on at this time of day.
• 647 The account is disabled.
• 648 The password for this account has expired.
• 649 The account does not have permission to dial in.
• 651 The modem (or other connecting device) has reported an error.
• 652 There was an unrecognized response from the modem (or other connecting device).
• 653 A macro required by the modem (or other connecting device) was not found in the device.INF file.
• 654 A command or response in the device.INF file section refers to an undefined macro.
• 655 The macro was not found in the device.INF file section.
• 656 The macro in the device.INF file section contains an undefined macro.
• 657 The device.INF file could not be opened.
• 658 The device name in the device.INF or media.INI file is too long.
• 659 The media.INI file refers to an unknown device name.
• 660 The device.INF file contains no responses for the command.
• 661 The device.INF file is missing a command.
• 662 There was an attempt to set a macro not listed in device.INF file section.
• 663 The media.INI file refers to an unknown device type.
• 664 The system has run out of memory.
• 665 The modem (or other connecting device) is not properly configured.
• 666 The modem (or other connecting device) is not functioning.
• 667 The system was unable to read the media.INI file.
• 668 The connection was terminated.
• 669 The usage parameter in the media.INI file is invalid.
• 670 The system was unable to read the section name from the media.INI file.
• 671 The system was unable to read the device type from the media.INI file.
• 672 The system was unable to read the device name from the media.INI file.
• 673 The system was unable to read the usage from the media.INI file.
• 676 The phone line is busy.
• 677 A person answered instead of a modem (or other connecting device).
• 678 The remote computer did not respond. To make sure that the server can be reached, ping the remote computer.
• 679 The system could not detect the carrier.
• 680 There was no dial tone.
• 691 The connection was denied because the username or password you specified is not valid or because the selected authentication protocol is not permitted on the remote server. Credentials are not valid for any of the following reasons: your username or password was not typed correctly; the username does not exist on the server; your password has expired; or the administrator has not given you access to connect remotely.
• 692 There was a hardware failure in the modem (or other connecting device).
• 693 ERROR_NOT_BINARY_MACRO
• 694 ERROR_DCB_NOT_FOUND
• 695 The state machines are not started.
• 696 The state machines are already started.
• 697 The response looping did not complete.
• 698 A response keyname in the device.INF file is not in the expected format.
• 699 The modem (or other connecting device) response caused a buffer overflow.
• 700 The expanded command in the device.INF file is too long.
• 701 The modem moved to a connection speed not supported by the COM driver.
• 702 Device response received when none expected.
• 703 The connection needs information from you, but the application does not allow user interaction.
• 704 The callback number is invalid.
• 705 The authorization state is invalid.
• 707 There was an error related to the X.25 protocol.
• 708 The account has expired.
• 709 There was an error changing the password on the domain. The password might have been too short or might have matched a previously used password.
• 710 Serial overrun errors were detected while communicating with the modem.
• 711 The operation could not finish because it could not start the Remote Access Service Manager service in time. Please try the operation again.
• 713 No active ISDN lines are available.
• 716 The Remote Access Service IP configuration is unusable.
• 717 No IP addresses are available in the static pool of Remote Access Service IP addresses.
• 718 The connection was terminated because the remote computer did not respond in a timely manner.
• 720 A connection to the remote computer could not be established. You might need to change the network settings for this connection.
• 721 The remote computer did not respond.
• 722 Invalid data was received from the remote computer. This data was ignored.
• 723 The phone number, including prefix and suffix, is too long.
• 726 The IPX protocol cannot be used for dialing out on more than one modem (or other connecting device) at a time.
• 728 The system cannot find an IP adapter.
• 729 SLIP cannot be used unless the IP protocol is installed.
• 731 The protocol is not configured.
• 732 Your computer and the remote computer could not agree on PPP control protocols.
• 733 A connection to the remote computer could not be completed. You might need to adjust the protocols on this computer.
• 734 The PPP link control protocol was terminated.
• 735 The requested address was rejected by the server.
• 736 The remote computer terminated the control protocol.
• 737 Loopback was detected.
• 738 The server did not assign an address.
• 739 The authentication protocol required by the remote server cannot use the stored password. Redial, entering the password explicitly.
• 740 An invalid dialing rule was detected.
• 741 The local computer does not support the required data encryption type.
• 742 The remote computer does not support the required data encryption type.
• 749 The destination address or phone number is either invalid or not present.
• 752 A syntax error was encountered while processing a script.
• 753 The connection could not be disconnected because the user does not have the required permission to disconnect.
• 754 The system could not find the multi-link bundle.
• 755 The system cannot perform automated dial because this connection has a custom dialer specified.
• 756 This connection is already being dialed.
• 757 Remote Access Services could not be started automatically. Additional information is provided in the event log.
• 764 No smart card reader is installed.
• 765 Internet Connection Sharing cannot be enabled. A LAN connection is already configured with the IP address that is required for automatic IP addressing.
• 766 A certificate could not be found. Connections that use the L2TP protocol over IPSec require the installation of a machine certificate, also known as a computer certificate.
• 767 Internet Connection Sharing cannot be enabled. The LAN connection selected as the private network has more than one IP address configured. Please reconfigure the LAN connection with a single IP address before enabling Internet Connection Sharing.
• 768 The connection attempt failed because of failure to encrypt data.
• 769 The specified destination is not reachable.
• 770 The remote computer rejected the connection attempt.
• 771 The connection attempt failed because the network is busy.
• 772 The remote computer's network hardware is incompatible with the type of call requested.
• 773 The connection attempt failed because the destination number has changed.
• 774 The connection attempt failed because of a temporary failure. Try connecting again.
• 775 The call was blocked by the remote computer.
• 776 The call could not be connected because the remote computer has invoked the Do Not Disturb feature.
• 777 The connection attempt failed because the modem (or other connecting device) on the remote computer is out of order.
• 778 It was not possible to verify the identity of the server.
• 780 An attempted function is not valid for this connection.
• 782 Internet Connection Sharing (ICS) and Internet Connection Firewall (ICF) cannot be enabled because Routing and Remote Access has been enabled on this computer. To enable ICS or ICF, first disable Routing and Remote Access. For more information about Routing and Remote Access, ICS, or ICF, see Help and Support.
• 783 Internet Connection Sharing cannot be enabled. The LAN connection selected as the private network is either not present, or is disconnected from the network. Please ensure that the LAN adapter is connected before enabling Internet Connection Sharing.
• 784 You cannot dial using this connection at logon time, because it is configured to use a user name different than the one on the smart card. If you want to use it at logon time, you must configure it to use the user name on the smart card.
• 785 You cannot dial using this connection at logon time, because it is not configured to use a smart card. If you want to use it at logon time, you must edit the properties of this connection so that it uses a smart card.
• 786 The connection attempt failed because there is no valid machine certificate on your computer for security authentication.
• 787 The L2TP connection attempt failed because the security layer could not authenticate the remote computer.
• 788 The L2TP connection attempt failed because the security layer could not negotiate compatible parameters with the remote computer.
• 789 The L2TP connection attempt failed because the security layer encountered a processing error during initial negotiations with the remote computer.
• 790 The L2TP connection attempt failed because certificate validation on the remote computer failed.
• 791 The L2TP connection attempt failed because security policy for the connection was not found.
• 792 The L2TP connection attempt failed because security negotiation timed out.
• 793 The L2TP connection attempt failed because an error occurred while negotiating security.
• 794 The Framed Protocol RADIUS attribute for this user is not PPP.
• 795 The Tunnel Type RADIUS attribute for this user is not correct.
• 796 The Service Type RADIUS attribute for this user is neither Framed nor Callback Framed.
• 797 A connection to the remote computer could not be established because the modem was not found or was busy.
• 798 A certificate could not be found that can be used with this Extensible Authentication Protocol.
• 799 Internet Connection Sharing (ICS) cannot be enabled due to an IP address conflict on the network. ICS requires the host be configured to use 192.168.0.1. Please ensure that no other client on the network is configured to use 192.168.0.1.
• 800 Unable to establish the VPN connection because a tunnel could not be setup. This might be because the VPN server cannot be reached or because security parameters for this connection are not configured correctly.
• 801 This connection is configured to validate the identity of the access server, but Windows cannot verify the digital certificate sent by the server.
• 802 The card supplied was not recognized. Please check that the card is inserted correctly, and fits tightly.
• 803 The PEAP configuration stored in the session cookie does not match the current session configuration.
• 804 The PEAP identity stored in the session cookie does not match the current identity.
• 805 You cannot dial using this connection at logon time, because it is configured to use logged on user's credentials.
• 806 The VPN connection between your computer and the VPN server could not be completed. The most common cause for this failure is that at least one Internet device (for example, a firewall or a router) between your computer and the VPN server is not configured to allow Generic Routing Encapsulation (GRE) protocol packets. If the problem persists, contact your network administrator or Internet Service Provider.
• 807 The network connection between your computer and the VPN server was interrupted. This can be caused by a problem in the VPN transmission and is commonly the result of internet latency or simply that your VPN server has reached capacity. Please try to reconnect to the VPN server. If this problem persists, contact the VPN administrator and analyze quality of network connectivity.
• 808 The network connection between your computer and the VPN server could not be established because the remote server refused the connection. This is typically caused by a mismatch between the server's configuration and your connection settings. Please contact the remote server's Administrator to verify the server configuration and your connection settings.
• 809 The network connection between your computer and the VPN server could not be established because the remote server is not responding. This could be because one of the network devices (e.g, firewalls, NAT, routers, etc) between your computer and the remote server is not configured to allow VPN connections. Please contact your Administrator or your service provider to determine which device may be causing the problem.
• 810 A network connection between your computer and the VPN server was started, but the VPN connection was not completed. This is typically caused by the use of an incorrect or expired certificate for authentication between the client and the server. Please contact your Administrator to ensure that the certificate being used for authentication is valid.
• 811 The network connection between your computer and the VPN server could not be established because the remote server is not responding. This is typically caused by a pre-shared key problem between the client and server. A pre-shared key is used to guarantee you are who you say you are in an IP Security (IPSec) communication cycle. Please get the assistance of your administrator to determine where the pre-shared key problem is originating.
• 812 The connection was prevented because of a policy configured on your RAS/VPN server. Specifically, the authentication method used by the server to verify your username and password may not match the authentication method configured in your connection profile. Please contact the Administrator of the RAS server and notify them of this error.
• 813 You have attempted to establish a second broadband connection while a previous broadband connection is already established using the same device or port. Please disconnect the earlier connection and then reestablish the connection.
• 814 The underlying Ethernet connectivity required for the broadband connection was not found. Please install and enable the Ethernet adapter on your computer via the Network Connections folder before attempting this connection.
• 815 The broadband network connection could not be established on your computer because the remote server is not responding. This could be caused by an invalid value for the 'Service Name' field for this connection. Please contact your Internet Service Provider and inquire about the correct value for this field and update it in the Connection Properties.
• 816 A feature or setting you have tried to enable is no longer supported by the remote access service.
• 817 Cannot delete a connection while it is connected.
• 818 The Network Access Protection (NAP) enforcement client could not create system resources for remote access connections. Some network services or resources might not be available. If the problem persists, disconnect and retry the remote access connection or contact the administrator for the remote access server.
• 819 The Network Access Protection Agent (NAPAgent) service has been disabled or is not installed on this computer. Some network services or resources might not be available. If the problem persists, disconnect and retry the remote access connection or contact the administrator for the remote access server.
• 820 The Network Access Protection (NAP) enforcement client failed to register with the Network Access Protection Agent (NAPAgent) service. Some network services or resources might not be available. If the problem persists, disconnect and retry the remote access connection or contact the administrator for the remote access server.
• 821 The Network Access Protection (NAP) enforcement client was unable to process the request because the remote access connection does not exist. Retry the remote access connection. If the problem persists, make sure that you can connect to the Internet, and then contact the administrator for the remote access server.
• 822 The Network Access Protection (NAP) enforcement client did not respond. Some network services or resources might not be available. If the problem persists, disconnect and retry the remote access connection or contact the administrator for the remote access server.
• 823 Received Crypto-Binding TLV is invalid.
• 824 Crypto-Binding TLV is not received.
• 825 Point-to-Point Tunneling Protocol (PPTP) is incompatible with IPv6. Change the type of virtual private network to Layer Two Tunneling Protocol (L2TP)
• 826 EAPTLS validation of the cached credentials failed. Please discard cached credentials.
• 827 The VPN connection cannot be completed because the 'IKE and AuthIP IPSec Keying Modules' service and/or the 'Base Filtering Engine' service is not running. These services are required to establish the connection. Please ensure that these services have been started before dialing the connection.
• 828 The connection was terminated because of idle timeout.
• 829 The modem (or other connecting device) was disconnected due to link failure.
• 830 The connection was terminated because user logged off.
• 831 The connection was terminated because user switch happened.
• 832 The connection was terminated because of hibernation.
• 833 The connection was terminated because the system got suspended.
• 834 The connection was terminated because Remote Access Connection manager stopped.
• 835 The L2TP connection attempt failed because the security layer could not authenticate the remote computer. This could be because one or more fields of the certificate presented by the remote server could not be validated as belonging to the target destination.
• 836 The Network Access Protection (NAP) health state of the computer cannot be determined. Contact your administrator to verify that the NAP enforcement client is enabled, the NAP Agent service is running, and NAP is enforced in the Protected Extensible Authentication Protocol (PEAP) properties of the remote access connection. 
• 837 Invalid Tunnel ID.
• 838 Another Update connection request is in progress. RAS allows only one Update Connection request at a time.
• 839 Negotiating using configured protocol is disable. Edit connection properties and select different protocol for negotiation and try again.
• 840 Internal address negotiation failed.
• 841 Client has to request a Internal IPv4 or IPv6 address.
• 842 Traffic Selectors negotiation failed.
• 843 Mobility is disabled for this connection.
• 844 The VPN Connection is still connecting or reauthenticating because of Quarantine state change. Initiate mobile update only when connection state is 'Connected'.
• 845 Server rejected client authentication, due unexpected TLV or value mismatch for a TLV.
• 846 Either VPN Destination preference is not selected by the user or it is no longer valid.
• 847 Cached smart card credential is invalid.
• 848 VPN connection attempt failed due to internal error occurred while adding cookies to the Secure Socket Tunneling Protocol (SSTP). Please see the System Event Log for the detailed information.
• 849 The PEAP inner method attributes stored in the cookie is invalid
• 850 The Extensible Authentication Protocol type required for authentication of the remote access connection is not installed on your computer.
• 851 The Extensible Authentication Protocol type configured on the remote access connection does not support single sign- on.
• 852 The Extensible Authentication Protocol type configured on the remote access connection does not support the requested operation.
• 853 The remote access connection completed, but authentication failed because the certificate that authenticates the client to the server is not valid. Ensure that the certificate used for authentication is valid.
• 854 The remote access connection completed, but authentication failed because the certificate that authenticates the client to the server is expired. Renew the certificate.
• 855 The remote access connection completed, but authentication failed because the certificate that authenticates the client to the server is revoked.
• 856 The remote access connection completed, but authentication failed because of an error in the certificate that authenticates the client to the server.
• 857 The remote access connection completed, but authentication failed because the certificate that the client uses to authenticate the server is not valid.
• 858 The remote access connection completed, but authentication failed because the certificate that the client uses to authenticate the server is expired.
• 859 The remote access connection completed, but authentication failed because the certificate that the client uses to authenticate the server is revoked.
• 860 The remote access connection completed, but authentication failed because of an error in the certificate that the client uses to authenticate the server.
• 861 The remote access connection completed, but authentication failed because a trusted root certificate that validates the user certificate was not found in the Trusted Root Certification Authorities certificate store.
• 862 The remote access connection completed, but authentication failed because the trusted root certificate that is used to validate the user certificate is not valid.
• 863 The remote access connection completed, but authentication failed because the certificate in the Trusted Root Certification Authorities certificate store that authenticates the user certificate is expired. Renew the certificate.
• 864 The remote access connection completed, but authentication failed because a certificate that validates the server certificate was not found in the Trusted Root Certification Authorities certificate store.
• 865 The remote access connection completed, but authentication failed because the certificate in the Trusted Root Certification Authorities certificate store that validates the server certificate is not valid.
• 866 The remote access connection completed, but authentication failed because the certificate on the server computer does not have a server name specified.
• 867 The PEAP outer identity is not same as the inner identity when identity privacy is turned OFF.
• 868 The Dns name is not resolvable. Make sure the DNS Name is resolvable and reachable.

Read More

Error 0x80131700 Loading Troubleshooting Wizard | Fix Crashing Troubleshooting Wizard

Error 0x80131700 Loading Troubleshooting Wizard | Fix Crashing Troubleshooting Wizard

By   11:01   No comments:

The following article will explain how to fix if your Windows 7 Troubleshooting Wizard does not start.

If you experience this kind of problem that none of your Troubleshooting wizard starts to work. And even if you manually attempt to use the wizard you will see the following error message.

"An unexpected error has occurred.  The trouble shooting wizard can't continue."  Some times you will see (0x80131700) error code in advanced dialog box. So, what is the cause and what is the solution for this problem or error 0x80131700.

Solution:

Error code 0x80131700 is usually relevant to the old version of .NET Framework installed on your system. By default, the built-in version of Micorosoft .NET Framework is 3.5.1. You can reinstall Microsoft .NET Framework 3.5 Service Pack 1 through the following steps:

1) Click  the Start and type: features in the Search box.

2) Select "Turn Windows Features on or off " and click Enter.

3) Find Microsoft .NET Framework 3.5.1 and uncheck the box.

4) Restart the computer.

5) Repeat the step 1) to step 2.

6) Check the box before Microsoft .NET Framework 3.5.1.

7) Restart the computer.

If you still face problem, you can either download the Microsoft .NET Framework 3.5.1 package and install it or you can download the latest Microsoft .NET Framework package from this location.

Read More

Specified Network Provider Name Is Invalid | How To Fix

Specified Network Provider Name Is Invalid | How To Fix

By   19:25   No comments:

The specified network provider name is invalid and with that you can not connect to printer or other computers from your PC or laptop on the same home group.

The following Article will let you know how to troubleshoot the error message “The specified network provider name is invalid.”

But before you continue troubleshooting this error make sure that this worked for you earlier and you are facing the problem most recently. if  it was not working fine for you from the beginning, then you need to know how to setup a HomeGroup. Watch the video below to know how to setup HomeGroup In Windows 7.

Steps To Setup HomeGroup In Windows 7

If you are sure that HomeGroup worked for you in the past and it is not working right now, then another reason is that you might have installed any Security Software on your computer. If yes, disable the Security Software for the time being and check if you are able to login. Also turn off the Firewall for the time being and check.

Make sure to turn on or enable the Security Software once you are done with the test. And also make sure to turn on the Firewall once you are done with the test.

Troubleshooting HomeGroup In Windows: Follow this step to fix the issue:

• Click Start->Click Control Panel.
• Click System and Maintenance-> Click Administrative Tools.
• Double-Click Local Security Policy.
• In the left pane, click the triangle next to Local Policy.
• In the left pane, click Security Options.
• In the right pane near the bottom, double-click "Network security: LAN manager authentication level".
• Click the drop-down box, and click "Send LM & NTLM responses". Click OK.

If you still face problem in connecting to your HomeGroup Machines, then you need to Run the HomeGroup Troubleshooter and check if it fixes the issue.

If your computer is having problems viewing computers or shared files in your HomeGroup, try using the HomeGroup troubleshooter to fix the problem. It makes sure that your computer's different network services are running correctly, and that your computer is a member of a HomeGroup.

Refer this link to open the HomeGroup Troubleshooter: Open the HomeGroup troubleshooter
http://windows.microsoft.com/en-US/windows7/Open-the-HomeGroup-troubleshooter

Read More

How To Perform A Clean Boot In Windows Vista Or In Windows 7

How To Perform A Clean Boot In Windows Vista Or In Windows 7

By   14:36   No comments:

Support for Windows Vista without any service packs installed ended on April 13, 2010. To continue receiving security updates for Windows, make sure you're running Windows Vista with Service Pack 2 (SP2). For more information, refer to this Microsoft web page: Support is ending for some versions of Windows

 

To help troubleshoot error messages and other issues, you can start Windows Vista or Windows 7 by using a minimal set of drivers and startup programs. This kind of startup is known as a "clean boot." A clean boot helps eliminate software conflicts. This article describes how to troubleshoot problems in Windows Vista or in Windows 7 by performing a clean boot. This article also describes how to start the Windows Installer service and how to reset the computer so that it starts as usual.
Note When you perform a clean boot, you may temporarily lose some functionality. When you start the computer as usual, the functionality returns. However, you may receive the original error message, or you may experience the original behavior.

 

This information is not intended to troubleshoot specific problems. Therefore, before you follow these steps, search the Microsoft Knowledge Base for information about your problem. Use the text of the error message or a description of the problem when you search. To search the Knowledge Base, visit the following Microsoft Web site:

Step 1: Perform a clean boot

Note If the computer is connected to a network, network policy settings may prevent you from following these steps. We strongly recommend that you do not use the System Configuration utility to modify the advanced boot options on the computer unless a Microsoft support engineer directs you to do this. Doing this may make the computer unusable.

• 1. Log on to the computer by using an account that has administrator rights.
• 2. Click Start   , type msconfig.exe in the Start Search box, and then press ENTER to start the System Configuration utility.

    If you are prompted for an administrator password or for confirmation, type your password, or click Continue.

   
• 3. On the General tab, click to select the option Selective startup, and then click to clear the option Load startup items check box. (The Use Original Boot.ini check box is unavailable.)

  

• 4. On the Services tab, click to select the Hide all Microsoft services check box, and then click Disable all.

  Following this step lets Microsoft services continue to run. These services include Networking, Plug and Play, Event Logging, Error Reporting, and other services. If you disable these services, you may permanently delete all restore points. Do not do this if you want to use the System Restore utility together with existing restore points.

• 5. Click OK, and then click Restart.

Step 2: Enable half of the services

• 1. Follow steps 1a and 1b to start the System Configuration utility.
• 2. Click the Services tab, and then click to select the Hide all Microsoft services check box.
• 3. Click to select half of the check boxes in the Service list.
• 4. Click OK, and then click Restart.

Step 3: Determine whether the problem returns

If the problem still occurs, repeat step 1 and step 2. In step 2, click to clear half of the check boxes that you originally selected in the Service list.
If the problem does not occur, repeat step 1 and step 2. In step 2, select only half of the remaining check boxes that are cleared in the Service list. Repeat these steps until you have selected all the check boxes.
If only one service is selected in the Service list, and you still experience the problem, the selected service causes the problem. Go to step 6. If no service causes this problem, go to step 4.

Step 4: Enable half of the Startup items

• 1. Perform a clean boot by repeating step 1.
• 2. Click the Startup tab, and then click to select half of the check boxes in the Startup Item list.
• 3. Click OK, and then click Restart.

Step 5: Determine whether the problem returns

If the problem still occurs, repeat step 1 and step 4. In step 4, click to clear half of the check boxes that you originally selected in the Startup Item list.
If the problem does not occur, repeat step 1 and step 4. In step 4, select only half of the remaining check boxes that are cleared in the Startup Item list. Repeat these steps until you have selected all the check boxes.
If only one startup item is selected in the Startup Item list, and you still experience the problem, the startup item that is selected in the list is the service that is causing the problem. Go to step 6.
If no startup item causes this problem, a Microsoft service most likely causes the problem. To determine which Microsoft service may be causing the problem, repeat step 1 and step 2 without selecting the Hide all Microsoft services check box in either step.

Step 6: Resolve the problem

After you determine the startup item or the service that causes the problem, contact the program manufacturer to determine whether the problem can be resolved. Or, run the System Configuration utility, and then click to clear the check box for the problem item. 

Step 7: Reset the computer to start as usual

After you have finished troubleshooting, follow these steps to reset the computer to start as usual:

• 1. Click Start   , type msconfig.exe in the Start Search box, and then press ENTER to start the System Configuration utility.

    If you are prompted for an administrator password or for confirmation, type your password, or click Continue.

• 2. In the General tab, click the Normal Startup option, and then click OK.
• 3. When you are prompted to restart the computer, click Restart.

Was this information helpful? Please send us your feedback

How to start the Windows Installer service when system services are not loaded

If you run a Setup program without starting the Windows Installer service, you may receive the following error message:

The Windows Installer service could not be accessed. Contact your support personnel to verify that the windows Installer service is properly registered.

The Windows Installer service does not start if you clear the Load system services check box in the System Configuration utility. To use the Windows Installer service when system services are not loaded, you must start the service manually. To do this, follow these steps: 

• 1. Click Start, right-click Computer, and then click Manage. If you are prompted for an administrator password or for confirmation, type your password, or click Continue.
• 2. In the console tree, click Services and Applications, and then click Services.
• 3. In the details pane, right-click Windows Installer, and then click Start.

Read More

Steps For Troubleshooting Softwares

Steps For Troubleshooting Softwares

By   13:54   No comments:

Tips & Techniques For Stress-Free Troubleshooting: Sooner or later, you’re going to have computer problems. That’s not a warning; it’s a guarantee. Read more: http://www.bench3.com/2011/01/simple-tips-for-easy-troubleshooting.html

Troubleshooting Software.

Software glitches occur far more frequently than hardware glitches. That’s because software (which includes the operating system, OS utilities, and other applications) is responsible for carrying out every single task the computer performs. And when you consider that multiple programs may be running at any given moment—either behind the scenes or in your computer’s foreground—it’s no surprise that applications occasionally conflict with one another.

Viruses and bugs, however, cause most software problems. Viruses are better prevented than fixed (with antivirus software and firewalls), but users have less control over bugs (which are actually coding errors or defects within the software program). A good software company will offer updates, or patches, to fix bugs in its products, but often minor bugs can be eliminated by the user.

If you experience problems immediately after you’ve installed a new program, try simply uninstalling or reinstalling the software.

If your computer freezes, try pressing the ESC key. If the ESC key doesn’t work, try closing the application with the Windows Task manager. Press CTRL-ALT-DELETE and select Task Manager. Now choose the Applications tab. Here you’ll see a list of all the programs open on your computer. If a program is not working properly, or is “Not Responding,” use the End Task button to terminate the program.

Also in the Task Manager, under the Processes tab, you’ll find a list of all the applications your computer is running, including those applications running in the background, along with a reading of how much memory each task is using. If too many programs run at once, or your system gets low on memory resources, you’re likely to notice a slowdown in your computer, perhaps even a BSOD (Blue Screen of Death).

Items listed under the Processes tab as LOCAL SERVICE, NETWORK SERVICE, and SYSTEM typically can’t be closed, but other items can be (select the program and click the End Process button). You might be able to end slowdowns by closing some of these items. Just don’t close any applications if you aren’t sure what they are.

The best way, however, to end freezes, crashes, slowdowns, and even some glitches is

to simply reboot your computer. If you think you’ve caused a problem by accidentally deleting a necessary file, try recovering if from the Recycle Bin or a backup disk. Windows Me/XP users have the option of using System Restore. (Click Start, point to All Programs, Accessories, System Tools, and select System Restore.) System Restore, although not a backup utility, monitors system and program files and creates restore points at selected intervals.

If a user with either of these OSes experiences a problem, she can revert the system to a state when it worked properly.

WinXP users also have access to The Last Known Good Configuration feature. This feature will revert your OS to the same settings in effect the last time your computer started successfully. To use The Last Known Good Configuration feature, start your computer, tap the F8 key to enter the Windows Advanced Options menu, select Last Known Good Configuration (your most recent settings that worked), and press ENTER.

During major crises you may have no choice but to refer to technical support. Try to make this your final option. Tech support can be expensive and time consuming, especially if you seek help through email, which can take days to receive a response. With patience and a little effort you can solve most computer problems on your own . . . without the panicking.

Also Read: Steps For Troubleshooting Hardware

Read More

Steps For Troubleshooting Hardware

Steps For Troubleshooting Hardware

By   13:48   No comments:

Tips & Techniques For Stress-Free Troubleshooting: Sooner or later, you’re going to have computer problems. That’s not a warning; it’s a guarantee. Read more:

Troubleshooting Hardware.

Let’s be honest, you don’t want to open your computer unless you have to. So before you go reaching for a screwdriver, listen for irregular noises coming from inside your PC. A ratchety “zzzzz” sound may mean a stray wire is touching the fan blades or that the fan motor is low on lubricant. A grinding noise may indicate a problem with the hard drive. 

If that’s the case, save the drive’s data immediately: The motor or head system, which contains read/write heads that record and retrieve information from within the drive’s case, could be preparing to fail. You have a right to panic. 

Try solving hardware problems outside your PC by first making sure the hardware is plugged in and turned on. This may sound obvious, but more than a few people have spent valuable time troubleshooting a PC when all they had to do was just reattach a loose cable or flip a switch.

If the power and cable sources check out OK, refer to the Device Manager. 

In Windows XP:

• Right-click My Computer, select Properties, choose the Hardware tab, 
• And click Device Manager. Navigate to the hardware device that is giving you problems. 
• A small yellow circle and an exclamation point or question mark to the left of the device’s name indicates that Windows has detected a problem. 
• Click the exclamation point, and you might be directed through a series of problem-solving steps.
• If not, right-click the device, uninstall it, and remove it from Device Manager. 
• Then reboot your computer. 

Windows will redetect the hardware, hopefully without the problem.

If your computer won’t reboot, try starting it in Windows’ diagnostics mode, called Safe Mode. In Safe Mode, Windows uses only the most vital drivers and components, which limits the numbers of tasks you can perform but makes it easier for you to spot problems caused by newly installed drivers. 

To enter Safe Mode:

Start your computer and begin tapping the F8 key until an Advanced Options menu appears. Select Safe Mode and press ENTER. 

• WinXP users can add Safe Mode to their Boot Menu. 
• Right-click My Computer and select Properties. 
• Choose the Advanced Tab. 
• Under Startup And Recovery, click Settings. 
• Then, in the resulting Startup And Recovery dialog box, click the Edit button under System Startup. 
• After Notepad opens, copy the last line of text and paste it in the next line. 
• Delete the description inside the quotes (most likely “Microsoft Windows XP Home Edition”) and replace it with Safe Mode. 
• In the same line, change “/fastdetect” to “/safeboot:minimal/sos/bootlog”. 
• Now click File, Save, and then exit Notepad. 
• Click OK twice (once to close the Startup And Recovery dialog box and again to close the System Properties dialog box).
• The Safe Mode option will appear the next time you boot your computer.

During major crises you may have no choice but to refer to technical support. Try to make this your final option. Tech support can be expensive and time consuming, especially if you seek help through email, which can take days to receive a response. With patience and a little effort you can solve most computer problems on your own . . . without the panicking.

Also Read: Steps For Troubleshooting Software's

Read More