1

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

Labels: , , ,

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.

Haja is currently working in a multi-disciplinary role that combines programming including, SAP Administration, Network Management, and System Administration. He is passionate about Technology and this blog is his platform for sharing his ideas. If you like this post, Please leave a comment. And if you have any queries, mail to help @ bench3 . com


Share |
0

Downlevel Client Support Service Is Being Removed From Windows 7

Labels: , , , ,

And The Downlevel Client Support Service that is a part of Microsoft Message Queuing (MSMQ) is being removed from Windows 7.

The MSMQ Service is the core service that makes it possible for you to perform basic Message Queuing functions, such as creating and managing queues, sending and receiving messages, and so on.

What are the major changes?
As a result of this change, Windows NT 4.0 and Windows 2000 MSMQ clients running against Windows Server 2008 R2 domain controllers that have no Windows Server 2003 or Windows Server 2008 domain controllers in the same environment will not support MSMQ in domain mode. This change affects customers who have Windows NT 4.0 or Windows 2000 clients that are joined to domain controllers, which have been upgraded toWindows 7. If any domain controller in these environments is running Windows Server 2008 or earlier, full functionality remains available.

Dependencies:
MSMQ has several dependencies on a directory service infrastructure; in version 1.0 the MSMQ product implements its own directory through a SQL-based database named MQIS and subsequent versions of MSMQ use Active Directory as its directory. MSMQ 1 and MSMQ 2 (Windows 2000) clients use a proprietary RPC-based interface to communicate with the underlying MSMQ Directory.

The MSMQ directory service server implements the server-end of this RPC interface and is required to be installed on the  domain controller. This proprietary RPC interface is deprecated in MSMQ 3 (Windows XP / Windows Server 2003) in that, newer MSMQ clients use LDAP to directly communicate with the Active Directory. The deprecated RPC Server is still available in Windows Server 2003 and Windows Server 2008 domain controllers as a separate Down-level Client Support service to enable inter-operability with Windows®°2000 and Windows NT 4.0 clients.

Solutions:
There are two solutions for this:
  1. Upgrade the client from Windows NT 4.0 or Windows 2000 to Windows XP, Windows Vista, or Windows 7.
  2. Add a Windows Server 2003 or Windows Server 2008 domain controller to the environment.

Haja is currently working in a multi-disciplinary role that combines programming including, SAP Administration, Network Management, and System Administration. He is passionate about Technology and this blog is his platform for sharing his ideas. If you like this post, Please leave a comment. And if you have any queries, mail to help @ bench3 . com


Share |
2

Windows No Longer Supports Tape Backup | Removable Storage Manager No Longer Available As Of Windows 7 And Server 2008 R2

Labels: , ,

After being reduced to an optional component in previous releases of the Windows and Windows Server operating systems, Removable Storage Manager (RSM) has been removed. Windows Backup no longer supports writing directly to sequential (tape) backup devices so RSM is no longer required. Third-party backup software does not use RSM, but manages backup device objects directly.

Removable Storage Manager (RSM) facilitates communication among applications, robotic changers, and media libraries. It enables multiple applications to share local robotic media libraries and tape or disk drives, and manage removable media within a single-server system. A group of libraries, drives, and media that are managed by RSM is called an RSM system. RSM can help you create an application that makes effective use of the media resources in an RSM system.
The Microsoft Windows Software Development Kit (SDK) contains information about RSM that is tailored for developers creating RSM client applications. There is additional information in the Windows Resource Kit about administrative aspects of RSM. To understand how to utilize RSM within your application and design a good user experience, please refer to the Resource Kit.
Backup made on windows 2000 machine using ntbackup.exe. will no longer supported by Windows 7 machine and any one trying to restore older files using  ntbackup.exe can not succeed as this feature not available for Windows 7.

Upgrading to Windows 7 can simply not require one to abandon years of backups made by Microsoft's NtBackup! Microsoft should have to pay for people having to purchase a 3rd party backup software to accomidate this.

Haja is currently working in a multi-disciplinary role that combines programming including, SAP Administration, Network Management, and System Administration. He is passionate about Technology and this blog is his platform for sharing his ideas. If you like this post, Please leave a comment. And if you have any queries, mail to help @ bench3 . com


Share |
0

Windows Server 2008 R2 Available Only In 64-bit | Solution For 16bit And 32bit Applications On 64bit Platform

Labels: , , ,

Microsoft Deprecated Features for Windows 7 and Windows Server 2008 R2. What this  mean is Windows Server® 2008 R2 ships with a 64-bit SKU only; no 32-bit SKU is available for the server version of the operating system. However, a 32-bit SKU continues to be available for Windows® 7. 

64-Bit Only will impact three areas:
32-bit drivers

32-bit plug-ins

16-bit executables

Now, how to install a 32bit driver or a 32 bit plug-ins or a 16 bit executables in a 64bit system?

The solution for 32-bit Drivers:
Recompile 32-bit drivers as signed 64-bit drivers.

Solution for 32-bit Plug-ins
WoW64, an x86 emulator, allows 32-bit Windows-based applications to run seamlessly on 64-bit Windows. WoW64 is now an optional feature that you must install if it is necessary to run 32-bit code.

The system isolates 32-bit applications from 64-bit applications, which includes preventing file and registry collisions. Console, GUI, and service applications are supported. The system provides interoperability across the 32/64 boundary for scenarios such as cut and paste and COM. However, 32-bit processes cannot load 64-bit DLLs, and 64-bit processes cannot load 32-bit DLLs. We commonly see this in shell plug-ins written for Windows Explorer.

A 32-bit application can detect whether it is running under WOW64 by calling the IsWow64Process function. The application can obtain additional information about the processor by using the GetNativeSystemInfo function

Note that 64-bit Windows does not support running 16-bit Windows-based applications. The primary reason is that handles have 32 significant bits on 64-bit Windows. Therefore, handles cannot be truncated and passed to 16-bit applications without loss of data. Attempts to launch 16-bit applications fail with the following error: ERROR_BAD_EXE_FORMAT.

Solution for 16-bit Executables
64-bit Windows recognizes a limited number of specific 16-bit installer programs and substitutes a ported 32-bit version. The list of substitutions is stored in the registry under the following key: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\NtVdm64 There is built-in support for several installer engines, including InstallShield 5.x installers. Note that the 64-bit Windows Installer can seamlessly install 32-bit MSI-based applications on 64-bit Windows.

Haja is currently working in a multi-disciplinary role that combines programming including, SAP Administration, Network Management, and System Administration. He is passionate about Technology and this blog is his platform for sharing his ideas. If you like this post, Please leave a comment. And if you have any queries, mail to help @ bench3 . com


Share |
0

What Are The Ways To Define Metatag

Labels: , , ,

A meta tag is a tag (that is, a coding statement) in the Hypertext Markup Language (HTML) that describes some aspect of the contents of a Web page. The information that you provide in a meta tag is used by search engines to index a page so that someone searching for the kind of information the page contains will be able to find it. The meta tag is placed near the top of the HTML in a Web page as part of the heading.

There are several kinds of meta tags, but the most important for search engine indexing are the keywords meta tag and the description meta tag. The keywords meta tag lists the words or phrases that best describe the contents of the page. The description meta tag includes a brief one- or two-sentence description of the page. Both the keywords and the description are used by search engines in adding a page to their index. Some search engines also use the description to show the searcher a summary of the page's contents.

Although most search engines also use the contents of a page as a way to determine how to index it, the creator of a Web page should be sure to include meta tags with appropriate keywords and description. Well-written meta tags can help make the page rank higher in search results. 

Metatags are for us to define our website to outside users.We can declare title, keywords etc. There are two types of meta tags
  1. HTTP-EQUIV
  2. NAME
HTTP-EQUIV
These tags are equivalent to http,Say for example if u click hyperlink which begins with http:// you are actually asking to transfer using http protocol.In additional what HTTP-EQUIV Metatags does is, it define additional information to be sent to the browser in the http header.This gives the web site creator additional; control over his data.

NAME
The NAME is acvtually used to define information which is to be referenced outside the document.Here is the actuall data is passed to search engines. Metatags must be placed between tags before the body. 
Note: On framed pages, be sure and include the metatags on the frameset page and the framed pages. An important note some people copy someones else’s Metatags and they have punished in the court (like trademarks etc.).
Some of them.
Attributes:
http-equiv=”name” content=”value”
Value      Description and example
content   - language - Specifies the language.
content   - script-type - Defines scripting language used.
content   - style-type  - Defines type of style sheets used.
content   - type - Specifies type of data within document.
expires    - Expiration date of the document.
ext          - cache - Define Netscape external cache.
page      - enter - Specifies the transition effect that is to be performed when the page is loaded.
page     - exit - Specifies the transition effect that is to be performed when the page is unloaded.

name=”value”

The following is the Name and description of the element that is being set.
Value             Description and example
abstract         - Define a secondary description.
author           - Records the name of the author of the document.
classification  - Classify the site into the appropriate category.
copyright       - Used to include copyright information in the document.
description   - Some search engines pick up this description to show with the results of searches.

Haja is currently working in a multi-disciplinary role that combines programming including, SAP Administration, Network Management, and System Administration. He is passionate about Technology and this blog is his platform for sharing his ideas. If you like this post, Please leave a comment. And if you have any queries, mail to help @ bench3 . com


Share |
30

Difference Between Various Scripting Languages | PHP | PERL | ASP | JSP | ColdFusion

Labels: , , , ,

Here is the main difference between the different scripting languages which most of them get confuse.

PHP
PHP uses a blend of interpretation and compilation in order to provide the best mix of performance and flexibility to programmers.
Hypertext Preprocessor (the name is a recursive acronym) is a widely used, general-purpose scripting language that was originally designed for web development to produce dynamic web pages. For this purpose, PHP code is embedded into the HTML source document and interpreted by a web server with a PHP processor module, which generates the web page document. As a general-purpose programming language, PHP code is processed by an interpreter application in command-line mode performing desired operating system operations and producing program output on its standard output channel. It may also function as a graphical application. PHP is available as a processor for most modern web servers and as standalone interpreter on most operating systems and computing platforms.
Behind the scenes, PHP compiles your script down to a series of instructions (called opcodes) whenever it is accessed. These instructions are then executed one by one until the script terminates. This is different from conventional compiled languages such as C++ where the code is compiled down to native executable code then that executable is run from then on. Instead, PHP re-compiles your script each time it is requested.

This constant recompilation may seem a waste of processor time, but it is actually not all that bad because you no longer need to worry about hand recompiling your scripts when you make any changes. On the flip side, many scripts take longer to compile than they do to execute!

Furthermore, it provides very quick feedback during development. If you have an error somewhere in your file, PHP will refuse to compile the page until you have fixed the problem, and you are able to step through execution of your code line by line until you find the problem.

The speed hit of regular compilation is nullified entirely by the use of PHP accelerators.

One major advantage to having interpreted code is that all memory used by the script is managed by PHP, and the language automatically cleans up after every script has finished. This means that you do not need to worry about closing database links, freeing memory assigned to images, and so on, because PHP will do it for you. That is not to say you should be lazy and make PHP do all the work – good programmers clean up themselves, and let PHP work as backup in case something is missed.

Perl
Perl is the most popular of the PHP alternatives out there, arguably because it is also the oldest. There is a large installed base of Perl out there; many open-source projects require Perl to be installed to work properly. 
Perl is a high-level, general-purpose, interpreted, dynamic programming language. Perl was originally developed by Larry Wall in 1987 as a general-purpose Unix scripting language to make report processing easier. Since then, it has undergone many changes and revisions and become widely popular amongst programmers. Larry Wall continues to oversee development of the core language.
It has the advantages of being very (very!) flexible, and also having a large collection of modules already written for it. However, it is let down by the fact that it is very easy to write obfuscated and confusing Perl without really realising you are doing so, and this has resulted in such marvels as the annual Obfuscated Perl Contest.

Well-written Perl scripts often look fairly like their PHP equivalent. The major cause for Perl’s messy appearance is that many Perl programmers rely on “one-liners” – packing large amounts of functionality into just one line of code. Perl was once described very accurately by its creator, Larry Wall, when he argued that the front cover for his O’Reilly book on Perl should be a camel, saying that Perl was ugly but serviceable, and able to go long distances without much nourishment.

Perl is often a better choice when you want to take advantage of some of the pre-written libraries. CPAN, Perl’s library repository, is very big, and there is a huge range of code for you to take, customise, and re-use. Perl also has a very active – and very cool – hacker community around it that’s a whole lot of fun to be part of and is really a bedrock of support when you need it. Larry Wall and Damian Conway (both core Perl developers) are both rightfully revered as “alpha geeks” – people who really push the envelope of programming by doing cool new things. They are both very friendly, and and attend many conferences year round – go ahead and introduce yourself if you meet them, because they really are fascinating to talk to.

ASP
Active Server Pages (ASP) and ASP.NET is Microsoft’s attempt to succeed in the web development market, and comes as standard with their web server, IIS. ASP has been mauled by the open source community ever since it came out, and they gave a variety of reasons: it is proprietary, single platform (Windows), and slow.
Active Server Pages (ASP), also known as Classic ASP or ASP Classic, was Microsoft's first server-side script engine for dynamically-generated web pages. Initially released as an add-on to Internet Information Services (IIS) via the Windows NT 4.0 Option Pack, it was subsequently included as a free component of Windows Server (since the initial release of Windows 2000 Server). It has now been superseded by ASP.NET.
I would like to say, “Yes, yes, and yes”, but I’m not going to try to pull the wool over your eyes. The reality is that ASP has been implemented on other platforms, and, when running on Windows and Microsoft Internet Information Services (IIS), is actually lightning-fast.

That coupled with the fact that you can write add-on modules for ASP using Visual Basic and COM would make the whole solution very attractive indeed if it were not for the fact that ASP only really works well on IIS. On other platforms there are many fewer features, and it generally runs a great deal slower. When running on Windows, the security issues and licensing costs tends to be the most important thing, particularly when an all-Microsoft solution stack is being used.

And ASP/ASP.NET is generally favoured when an all-Microsoft stack is in place. When used on Windows, it is very easy to deploy .NET code to ASP.NET pages or even write your ASP pages using C#.

ColdFusion
Most of the content about cold fusion was taken from the comment by - Jason Dean, You can also read that below to know what i wrote before and how i changed now.
ColdFusion became quite popular back in the hey-days of the dot.com boom. ColdFusion can be developed with any text editor, just like any other scripting language. It has an IDE, but you don't need to use it if you don't want to.

ColdFusion performs fairly well. Its development speed is good.  ColdFusion was bought out by Macromedia but now it is owned by Adobe.

With ColdFusion you have COMPLETE control over the source code. Additionally, you can access the underlying Java if ColdFusion is missing something that you need. You can also develop your own Java to add even MORE functionality to ColdFusion.


If something goes wrong in your code, it’s normally very easy to track it down and solve the problem, or change your plans and implement a different solution to the same problem. 
ColdFusion has design patterns that you can use or you can develop your own. Just like ANY OTHER LANGUAGE. There are many ways to skin the cat. There are no limitations to how you solve the problem. 

ColdFusion used to be quite popular back in the hey-days of the dot.com boom because it is developed using a proprietary IDE designed for novice programmers who have no wish to see source code of any complexity.

One of the nicer features of ColdFusion is that it comes with a whole application to help you write it the language. While it can be used with Apache or IIS once you're finished, this application effectively acts as your test server while you're writing your scripts, saving you quite a lot of trouble.

The biggest advantage to ColdFusion "EASY TO LEARN" is its IDE and the language it uses, “CFML” (ColdFusion Markup Language) – even junior programmers can learn the system and start making pages quickly. As a result, you will often find ColdFusion in use at very large companies where they use Visual Basic (another easy, but not very powerful or fast language) for offline work.
One of the things that make ColdFusion easy to learn is that it isn't all that different from normal HTML: it acts more like a set of extension tags for HTML than like trying to get a programming language to do things and output HTML afterwards. This is because it was designed from scratch for the web – it's not just a normal language trying to be web-compatible.
ColdFusion on the web can sometimes be unreliable and slow, mainly because it runs on a Java framework. Its Java support does, however, make it capable of running on many more operating systems than it otherwise would be – for most purposes, having written a page in ColdFusion is as good as having used Java for it, but much less difficult. Since ColdFusion also uses the ODBC (Open Database Connectivity) standard instead of tying itself down to one database, this gives you a lot of choices.
Integration with Other Macromedia Products: If you already design your pages in Dreamweaver, it can be good to do the scripting in ColdFusion, as you get the advantages that integration between the two gives you. You can insert ColdFusion code into Dreamweaver files quickly and easily, and you can even use its built-in editor to edit the code however you want without messing up Dreamweaver's WYSIWYG view. ColdFusion also integrates surprisingly well with Macromedia's flagship product, Flash – but don't let that lead you into developing nothing but ColdFusion-scripted websites with fancy Flash interfaces, whatever you do.
JSP
Java Servlet Pages has often been considered the “dark horse” in web scripting because at first many thought it would be overkill for the job and yet has managed to get quite a substantial community about it nonetheless. JSP has three key advantages over some of its competitors, which may be why it has done so well:
  1. It uses Java, a language that already has a large skill set of developers and a massive amount of functionality available. Java is also conducive to scalability as it distributes across multiple computers well. Sun, as well as other members of the community, has worked hard to promote the language and tools that support it, which means that JSP has a lot of backing inside larger enterprises.
  2. It strongly encourages templating of pages for maximum code re-use. Templates for PHP are widely available, but they are a great deal more popular in JSP.
  3. It is a common argument that because JSP is based on Java it scales better than PHP. This is not correct per se in the same way that most other over-generalisations are not correct (yes, I realise that is an over-generalisation too, and hence you are free to enjoy the irony!) – PHP scales perfectly well as long as you write your PHP scripts usi andng the same design patterns you would have used writing your JSPs.
JSP is a popular choice when existing back-end business logic is written in Java also, as this keeps the development team language-homogeneous.

And Finally, Thanks to all comments for making me write an article with absolutely no knowledge about any of the above codes! Thanks Every One! And i will update as and when people give more comments! And I have published every comment except one comment saying "You Coward, Turning on comment moderation, just admint you are wrong.-  Jason Dean" I turned moderation for some other reason Jason. Thankyou for your help I just made one quality post with your help. Really thank you.

Haja is currently working in a multi-disciplinary role that combines programming including, SAP Administration, Network Management, and System Administration. He is passionate about Technology and this blog is his platform for sharing his ideas. If you like this post, Please leave a comment. And if you have any queries, mail to help @ bench3 . com


Share |
0

Make Windows To Shutdown Faster

Labels: , ,

This method is tested and worked with Windows XP but never tried with windows vista or windows 7. If anyone can do it, please write a comment in this post.

When a user shut down his windows XP the operating system waits till all the services is killed ,some time the service does not shut down and windows gives a chance to shut down before killing.

The amount of time the windows waits to kill the service is stores in registry ,my modifying this setting the time time taken for windows to wait the service to shut down will reduce and kills instantly.
  • Go To Registry Editor. [Click Start - Run - And Type REGEDIT]

  • Navigate To HKEY_LOCAL_MACHINE/SYSTEM/CurrentControlSet/Control.
  • Click on the “Control” Folder.
  • Select “WaitToKillServiceTimeout”
  • Right click on it and select Modify.
  • Set it a value lower than 2000.

Haja is currently working in a multi-disciplinary role that combines programming including, SAP Administration, Network Management, and System Administration. He is passionate about Technology and this blog is his platform for sharing his ideas. If you like this post, Please leave a comment. And if you have any queries, mail to help @ bench3 . com


Share |
0

How To Bring Back The Missing My Documents Folder In Windows XP

Labels: , ,

When you open the My Computer screen and your Documents folder is missing but all the other users folders are there try this tweak.
  • Go To START - RUN And Type REGEDIT
  • Navigate To HKEY_LOCAL_MACHINE / Software / Microsoft / Windows / Current Version / Explorer / DocFolderPaths

[Once you click the DocFolderPaths folder you should see all the user’s folders.]
  •  Add a new string value
  • Value Name: your user name
  • Value Data: the path to your docs folder ( ex. C:\Documents and Settings\your docs folder )

Exit Registry editor and open my computer, now you will see My Documents Folder.

Haja is currently working in a multi-disciplinary role that combines programming including, SAP Administration, Network Management, and System Administration. He is passionate about Technology and this blog is his platform for sharing his ideas. If you like this post, Please leave a comment. And if you have any queries, mail to help @ bench3 . com


Share |
0

Configuring A Broadcast Site In Office Web Apps To Broadcast Slide Show

Labels: , , , ,

The information provided in this article about configuring a Broadcast Slide Show site is aimed at IT pros who maintain Microsoft Office Web Apps installed on Microsoft SharePoint 2010 Products on a stand-alone server or on a server farm. SharePoint 2010 Products in this article refers to Microsoft SharePoint Server 2010 and Microsoft SharePoint Foundation 2010 unless otherwise noted.

Configure a PowerPoint Broadcast site

Broadcast Slide Show requires that Office Web Apps be installed on SharePoint 2010 Products on a stand-alone server or server farm, the PowerPoint service application be created, and a broadcast site collection be created. If the PowerPoint service application has been created during post-setup configuration of a stand-alone installation or by running the Farm Configuration Wizard, a default broadcast site is also created. In most cases, the default site’s URL is “http:///sites/broadcast”. Setup also installs a broadcast site template. Multiple site collections that use the broadcast site template can be created.


If the PowerPoint service application has not been created during post-setup configuration of a stand-alone installation or by running the Farm Configuration Wizard, you can create the PowerPoint service application manually. To learn about creating Office Web Apps service applications manually, see Activate the Office Web Apps services and feature by using PowerShell in Deploy Office Web Apps (Installed on SharePoint 2010 Products). If the PowerPoint service application is created manually, to use PowerPoint Broadcast Slide Show, a PowerPoint Broadcast site must also be created manually.

For Broadcast Slide Show sites that were created manually, administrators must give users appropriate permissions through SharePoint 2010 Products to broadcast a slide show and to attend broadcast slide shows. For Broadcast Slide Show sites that were created by default, authenticated users are added to both the Broadcast Presenters and Broadcast Attendees groups; however, it is recommended that administrators verify that appropriate permissions are given for their organization. 
Important: Users should not be granted Full Control or Full Read policy permissions to a Web Application that contains a broadcast site collection. This circumvents the permissions on the broadcast site and might allow users to access broadcast documents.
Procedures in this task:
  • To create a PowerPoint broadcast site by using Central Administration
  • To create a PowerPoint broadcast site by using Windows PowerShell
  • To configure permissions on the broadcast site by using a Web browser
  • To configure permissions on the broadcast site by using Windows PowerShell
Some procedures in this task require using Windows PowerShell or SharePoint 2010 Management Shell to run cmdlets. To run SharePoint 2010 cmdlets in Windows PowerShell, you must add the Microsoft.SharePoint.PowerShell snapin by using the Add-PSSnapin cmdlet, or you can run the SharePoint 2010 cmdlets by using SharePoint 2010 Management Shell. By default, the Microsoft.SharePoint.PowerShell snapin is already registered, and the snapin is added to the SharePoint 2010 Management Shell.

To run SharePoint 2010 cmdlets, you must be a member of the SharePoint_Shell_Access role on the configuration database and a member of the WSS_ADMIN_WPG local group on the computer where SharePoint 2010 Products is installed. To run scripts in Windows PowerShell or SharePoint 2010 Management Shell, you must set the execution policy by using the set-executionpolicy cmdlet, using the unrestricted parameter. For more information about the Add-PSSnapin cmdlet, see Add-PSSnapin. For more information about using Windows PowerShell with SharePoint 2010 Products, see SharePoint 2010 Products administration by using Windows PowerShell.

To create a PowerPoint broadcast site by using Central Administration
Verify that you have the following administrative credentials:
  1. To create a PowerPoint broadcast site, you must be a member of the Farm Administrators SharePoint group on the computer that is running the SharePoint Central Administration Web site.
  2. On the Central Administration Web site, in Application Management, click Create site collections.
  3. On the Create Site Collection page, specify the following settings.
  • Web Application Specify the Web application that will contain the site or use the default selection (recommended).
  • Title Enter the user-friendly title of the site.
  • Description Enter an optional description of the broadcast service
  • URL This is the URL where users will access this broadcast service.
  • Template Selection Click Enterprise and then select PowerPoint Broadcast Site.
  • Primary Site Collection Administrator Enter or browse for a user to be the primary site collection administrator.
  • Secondary Site Collection Administrator Enter or browse for a user to be the secondary site collection administrator (optional).
  • Quota Template Add a quota template to this site (optional).
   4. Verify settings and then click OK.

To create a PowerPoint broadcast site by using Windows PowerShell
  • Using Notepad, create a text file and then copy and paste the following script into the file.
$rootSites = Get-SPWebApplication | Get-SPSite -Limit ALL | where { $_.ServerRelativeUrl -eq "/" }
$bcastTmpl = Get-SPWebTemplate | where { $_.Name -eq "PowerPointBroadcast#0" foreach ($rootSite in $rootSites) { $url = $rootSite.Url + "/sites/broadcast" New-SPSite -Url $url -OwnerAlias "contoso\admin" -Template $bcastTmpl}
  • Specify the following parameters and its value:
                URL            =  Broadcast Site URL
               –OwnerAlias =  Domain\alias
  • Save the file with a .ps1 file name extension to a folder where you run scripts (typically C:\scripts).
  • In the Windows PowerShell console, at the command prompt (that is, PS C:\), type the following command and press ENTER:

C:\(path)\(filename).ps1
To configure permissions on the broadcast site by using a Web browser

  1. In a Web browser, browse to the broadcast site.
  2. In the broadcast site, click Site Actions, and then click Site Permissions.
  3. On the Permissions menu bar, click Grant Permissions, and then select one of the following.

  • To allow users or groups to broadcast, add them to the Broadcast Presenters group.
  • To allow users or groups to attend a slide show presented through Broadcast Slide Show, add them to the Broadcast Attendees group.
  • To allow users or groups to administer the site and change group membership, add them to the Broadcast Administrators group.
To configure permissions on the broadcast site by using Windows PowerShell
Using Notepad, create a text file and then copy and paste the following script into the file.
New-SPUser -web $url -UserAlias "NT AUTHORITY\Authenticated Users" -Group "Broadcast Attendees"
New-SPUser -web $url -UserAlias "NT AUTHORITY\Authenticated Users" -Group "Broadcast Presenters" 
Specify the following parameter and its Value 
-UserAlias        =  Domain\Name
Domain\Group  = -Group
Broadcast Attendees  = Broadcast Presenters

Save the file with a .ps1 file name extension to a folder where you run scripts (typically C:\scripts).

In the Windows PowerShell console, at the command prompt (that is, PS C:\), type the following command and press ENTER:

C:\(path)\(filename).ps1

Haja is currently working in a multi-disciplinary role that combines programming including, SAP Administration, Network Management, and System Administration. He is passionate about Technology and this blog is his platform for sharing his ideas. If you like this post, Please leave a comment. And if you have any queries, mail to help @ bench3 . com


Share |
Subscribe to: Posts (Atom)