Archive for the ‘Server’ Category

Symptoms:

–          The Server service fails to start and the below events are recorded

Event ID: 7023

Source: Service Control manager

Type: Error

Description: The Server service terminated with the following error: More data is available.

–          Not Enough storage is available to process this command.

Event ID: 7001

Source: Service Control manager

Type: Error

Description: The Netlogon service depends on the server service which failed to start because of the following error: More data is available.

–          System Error 8 has occurred. Not enough storage is available to process this command.

–          If you try to start the Server Service manually, the following errors may occur: A System error has occurred: System Error 234 has occurred.

–          You will not be able to execute any command in the Server.

–          You get error message when you open the Network connections (ncpa.cpl)

Observations:

–          Other services may fail to start because these services are dependent on the Server Service.

–          The Server service queries the registry value above for its entries. The buffer for the amount of information that the Server service can accept when it queries is approximately 32 KB. If there are more than 32 KB in that entry, the Server service will fail to start and return the error “More data is available,” or “Not enough storage is available.”

–          It looks like certain software’s can also cause for this error, those maybe the Norton Antivirus, Acronis trueImage, Seagate DiscWizard, IBM antivirus, Microsoft Bitdefender, Symantec Endpoint Protection or AVG, Try Disabling them or uninstalling and check if the problem persists.

–          You can instantly rectify this error if you restart the server, but the error re-occurs in 2 to 3 days.

Resolution:

PLEASE BACKUP YOUR REGISTRY FIRST BEFORE YOU MAKE ANY CHANGES

This issue may be cause of two reasons, one is the NullSessionPipes and the other is IRPStackSize.

  1. NullSessionPipes

The Cause of these errors is due to too much data stored in the following registry key:

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\LanmanServer\Parameters\NullSessionPipes

The Server service queries the registry value above for its entries. The buffer for the amount of information that the Server service can accept when it queries is approximately 32 KB. If there are more than 32 KB in that entry, the Server service will fail to start and return the error “More data is available,” or “Not enough storage is available.”

The Solution is to remove any unnecessary entries from this value in the registry.

The Default information stored in this key is:

COMNAP

COMNODE

SQL\QUERY

SPOOLSS

LLSRPC

EPMAPPER

LOCATOR

  1. IRPStackSize

Go to the below Registry entry to edit the IRPStackSize

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters

If you do not have the Registry entry then create one manually, but make sure the name should be correct as it is case sensitive.

To create the Registry entry follow the below steps:

–          Open REGEDIT

–          Proceed to the following location: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters

–          Click Edit, and point to New and then click DWORD Value

–          Type IRPStackSize , Click Edit and then modify the Value

–          The Value should be 0x00000050 in Hexadecimal or 80 in Decimal. This should resolve your issue, normally values are provided to 1 to 15 in decimal notation. Better if you provide higher value so that the problem doesn’t come back.

–          Restart the Server after the changes are done.

You may get the error message as below:

Symptoms:

–          Not able to login to Domain Controllers due to low disk space in the systems drive.

–          You get the above error message and the server reboots every time.

–          Users not able to login in the particular network.

–          Users not able to access the shared resources from the Domain Controller.

 

Resolution:

–          Reboot the server and login using Windows directory restore mode.

–          Go To Start > Run and type ‘Cleanmgr’ and clean up the drive space of C

–          If you have lost the Restore Mode password then follow the below steps to reset the DSRM Password:

Go to Command Prompt from the nearest Domain Controller and type the below command:

ntdsutil

set dsrm password

reset password on server ServerName

–          Once you have cleared the Space in the Systems drive, reboot the Server.

–          After Reboot login normally to the Domain Controller and everything should be back to normal.

–         Everyone should be able to access the Shared Resources from the Server.

Procedure to Restore the System State Backup:

  1. Click Start, point to All Programs, point to Accessories, point to System Tools, and then click Backup. The Backup or Restore Wizard starts.
  2. Click Advanced Mode.
  3. Click the Restore and Manage Media tab.
  4. In the Items to restore box, expand the media that you want to restore, and then click to select the System State check box.
  5. In the Restore file tobox, specify the location where you want to restore the files by doing one of the following:
    • If you want to restore the files or folders to the same location in which they were when you backed up the data, click Original location, and then go to step 7.
    • If you want to restore the files or folders to a new location, click Alternate location.
      This option preserves the folder structure of the backed up data.
    • If you want to restore the files and folders to a single location, click Single folder.NOTE: If you do not designate an alternate location for the restored data, the restore operation erases the current system state data and replaces it with the information that you are restoring.
  6. If you selected Alternate location or Single folder, type the location in which you want the data to be restored, or click Browse and select the location.
  7. Click Start Restore.
  8. On the Confirm Restore page that appears, click Advanced if you want to set advanced restore options, and then click OK.
  9. Click OK to start the restore operation.

Procedure to Configure System State Backup:

Note: The Account must be a Domain Admin Account to perform the System State Backup.

To Back Up the System State:

To back up the system state (including the registry hives system, software, security, the Security Accounts Manager (SAM), and the default user (but not HKEY_CURRENT_USER)), follow these steps:

  1. Click Start, point to All Programs, point to Accessories, point to System Tools, and then click Backup. The Backup or Restore Wizard starts.
  2. Click Advanced Mode.
  3. Click the Backup tab.
  4. On the Job menu, click New.
  5. Click to select the System State check box.
  6. In the Backup destination box, specify the destination for the new job.
  7. In the Backup media or file namebox, do the following:
    • If you are backing up to a file, specify a path and file name for the backup (.bkf) file. Or, click Browse, specify a file name and location where you want to save the file, and then click Save.
    • If the NAS is available save it to \\NASName\Backup location
    • If NAS is not available, save it to some Local Machine and make note of this local machine. Make sure that the destination location or drive has enough free space.
  8. Click Start Backup.
  9. If you want to set advanced backup options, such as data verification or hardware compressions, click Advanced. Specify the options that you want, and then click OK.
  10. Review the settings on the Backup Job Information page. Specify whether you want this backup to replace the information that is already present on the destination media, or add this backup to the existing information.
  11. Click Start Backup.

 

For Restore Procedure click here

By Default a Global Catalog is created automatically on the initial Domain Controller in the forest. It stores a full replica of all the objects in the directory for its host domain and a partial replica of all objects contained in the directory of every other domain in the forest. The replica is partial because it stores some, but not all, of the property values for every object in the forest.

The Global Catalog performs two key directory roles:

–  It enables network logon by providing universal group membership information to a domain controller when a logon process is initiated.

–  It enables finding directory information in the entire forest regardless of which domain in the forest actually contains the data.

When a user logs in to the network, the global catalog provides universal group membership information for the account sending the logon request to the domain controller. If there is only one domain controller in the Domain, the domain controller and the global catalog are the same server. If there are multiple domain controllers in the network, the global catalog is hosted on the domain controller configured as such. If a Global Catalog is not available when a user initiates a network logon process, the user is only able to log on to the local computer.

Note: If a user is a member of the Domain Admins group, then they will be able to log on to the network even when the Global Catalog is not available.

The Global Catalog is designed to respond to queries about objects anywhere in the forest with maximum speed and minimum network traffic, because a single Global Catalog contains information about objects in all domain in the forest, a query about an object can be resolved by a global catalog in the domain in which the query is initiated. Thus finding the information in the directory does not produce unnecessary query traffic across domain boundaries.

You can optionally configure any domain controller to host a global catalog, based on your Company’s requirements for servicing logon requests and search queries.

After Additional domain controllers are installed in the domain, you can change the default location of the global catalog to another domain controller using the Active Directory Sites and Services.

 

 

By using replication monitor 

Go to start > run > type repadmin

Go to start > run > type replmon

The Replmon graphical user interface (GUI) tool is included when you install Windows Server 2003 Support Tools from the product CD or from the Microsoft Download Center

Replmon.exe: Active Directory Replication Monitor

This GUI tool enables administrators to view the low-level status of Active Directory replication, force synchronization between domain controllers, view the topology in a graphical format, and monitor the status and performance of domain controller replication.

The Replmon graphical user interface tool was removed from Windows Server 2008 and later. Repadmin is still available for troubleshooting replication.

Repadmin.exe: Replication Diagnostics Tool

This command-line tool assists administrators in diagnosing replication problems between Windows domain controllers.

Administrators can use Repadmin to view the replication topology as seen from the perspective of each domain controller. In addition, Repadmin can be used to manually create the replication topology, to force replication events between domain controllers, and to view both the replication metadata and up-to-date vectors.

Repadmin.exe can also be used for monitoring the relative health of an Active Directory forest. The operations replsummaryshowreplshowrepl /csv, and showvector /latency can be used to check for replication problems.

 

Introduction

Replication ensures that all information in Active Directory is current on all domain controllers and client computers across your entire network. Many networks consist of a number of smaller networks, and the network links between these networks may operate at varying speeds. Sites in Active Directory enable you to control replication traffic and other types of traffic related to Active Directory across these various network links. You can use subnet objects, site links, and site link bridges to help control the replication topology when configuring replication between sites. An efficient, reliable replication topology depends on the configuration of site links and site link bridges.

 

What Are Sites and Subnet Objects?

 

Introduction

You use sites to control replication traffic, logon traffic, and requests to the Global Catalog server.

 

Sites

In Active Directory, sites help define the physical structure of a network. A site is defined by a set of Transmission Control Protocol/Internet Protocol (TCP/IP) subnet address ranges. Sites are used to define a group of domain controllers that are well-connected in terms of speed and cost. Sites consist of server objects, which contain connection objects that enable replication.

 

Subnet Objects

The TCP/IP subnet address ranges are represented by subnet objects that group computers. For example, a subnet object might represent all the computers on a floor in a building, or on a campus. Subnet objects are associated with sites and, because the subnet objects map to the physical network, so do the sites. For example, if you have three subnets that represent three campuses in a city, and these campuses are connected by high-speed, highly available connections, you could associate each of those subnets with the same site. A site can consist of one or more subnets. For example, on a network with three subnets in London and two in Boston, the administrator can create a site in London, a site in Boston, and then add the subnets to the respective sites.

 

Default Site

A default site is set up automatically when you install Windows Server on the first domain controller in a forest. This site is called Default-First-Site- Name. This site can be renamed. When you create your first domain in a forest it is automatically placed in the default site.

Introduction

A global catalog server is a domain controller that stores two forest-wide partitions, schema and configuration, a read/write copy of the partition from its own domain, and also a partial replica of all other domain partitions in the forest. These partial replicas contain a read-only subset of the information in each domain partition.

 

How does replication affect the global catalog server?

When a new domain is added to a forest, the information about the new domain is stored in the configuration partition, which is replicated to all domain controllers, including global catalog servers, through normal forest-wide replication. Then each global catalog server becomes a partial replica of the new domain by contacting a domain controller for that domain and obtaining the partial replica information. The configuration partition also contains a list of all global catalog servers in the forest and provides this information to the domain controllers. Global catalog servers register special DNS records in the DNS zone that correspond to the Forest Root domain. These records, which are registered only in the Forest Root DNS zone, help clients and servers locate global catalog servers throughout the forest.