Server Unleashed

Order of Group Policy Processing

Admin — Thu, 18 Dec 2008 04:10:04 GMT

The Group Policy objects (GPOs) that apply to a user (or computer) do not all have the same precedence. Settings that are applied later can override settings that are applied earlier. Order of processing settings Group Policy settings are processed in the following order: 1. Local Group Policy object—Each computer has exactly one Group Policy object that is stored locally. This processes for both computer and user Group Policy processing. 2. Site—Any GPOs that have been linked ...

Authentication Methods in IIS

Admin — Tue, 30 Dec 2008 17:06:46 GMT

AUTHENTICATION METHODS IN IIS 6.0 Anonymous Authentication: Anonymous authentication gives users access to the public areas of your Web or File Transfer Protocol (FTP) site without prompting the users for a user name or password. When a user attempts to connect to your public Web or FTP site, your Web server assigns the connection to the Windows user account that is specified for anonymous connections. By default, this account is named IUSR_ComputerName, where ComputerName is the name ...

Event id 4004 DNS errors and external name resolution problems

Admin — Mon, 29 Dec 2008 20:19:38 GMT

Internal names resolve but external DNS names won’t resolve. The following error will also appear in the event log. Event Type: Error Source: DNS Event ID: 4004 Description: The DNS server was unable to complete directory service enumeration of zone . This DNS server is configured to use information obtained from Active Directory for this zone and is unable to load the zone without it. Check that the Active Directory is functioning properly and repeat enumeration ...

Stop 0x7F or UNEXPECTED_KERNEL_MODE_TRAP

Admin — Mon, 29 Dec 2008 17:43:42 GMT

The Stop 0x7F message indicates that one of two types of problems occurred in kernel-mode: • A condition that the kernel is not allowed to have or intercept (also known as a bound trap). • A fault occurred while processing an earlier fault (also known as a double fault). Interpreting the Stop 0x7F Message This Stop message has four parameters, as listed below. Parameters for the Stop 0x7F Message Parameter Description Parameter 1 Processor exception code. Parameter ...

Stop 0x7B or INACCESSIBLE_BOOT_DEVICE

Admin — Sat, 27 Dec 2008 01:47:19 GMT

The Stop 0x7B message indicates that Windows Server 2003 has lost access to the system partition or boot volume during the startup process. There are several circumstances that can cause this: • A hard disk or disk controller has failed. • A Boot.ini file is configured incorrectly. This often occurs when disks or controllers are added and change the ARC mapping of existing disks. • Incorrect disk controller device drivers are installed. This might happen because incorrect drivers ...

Stop 0x7A or KERNEL_DATA_INPAGE_ERROR

Admin — Sat, 27 Dec 2008 01:42:17 GMT

The Stop 0x7A message indicates that a page of kernel data was not found in the paging (virtual memory) file and could not be read into memory. The causes of this might be incompatible disk or controller drivers, outdated firmware, or a hardware problem. Interpreting the Stop 0x7A Message The parameters for this Stop message have two sets of meanings. The value of parameter 1 determines the meaning of parameters 2, 3, and 4. If parameter 1 is 0x1, 0x2, or 0x3, the parameters should ...

Stop 0x79 or MISMATCHED_HAL

Admin — Sat, 27 Dec 2008 01:36:13 GMT

The Stop 0x79 message indicates that the HAL and the kernel type for the computer do not match. This error generally results from one of the following circumstances: • Either Ntoskrnl.exe or Hal.dll has been manually updated. • ACPI firmware settings were changed after Windows Server 2003 was installed. For example, an administrator might have installed Windows Server 2003 on an x86-based computer with the firmware ACPI enable option enabled, and later decided to disable it. • ...

Stop 0x77 or KERNEL_STACK_INPAGE_ERROR

Admin — Thu, 25 Dec 2008 20:19:14 GMT

The Stop 0x77 message indicates that a page of kernel data requested from the paging (virtual memory) file could not be found or read into memory. This Stop message can also indicate disk hardware failure or possible virus infection. Interpreting the Stop 0x77 Message The parameters for this Stop message have one of two different meanings. The value of the first parameter determines the meaning of parameters 2, 3, and 4. If parameter 1 is anything other than 0x0, 0x1, or 0x2, the parameters ...

Stop 0x6B or PROCESS1_INITIALIZATION_FAILED

Admin — Thu, 25 Dec 2008 20:09:25 GMT

The Stop 0x6B message indicates that system startup failed during Phase 1 of the Executive initialization. During Phase 1, interrupts are enabled, device drivers are initialized, components initialized in Phase 0 continue the initialization process, and those Executive components that were not initialized during Phase 0 are initialized. Executive components initialized in Phase 1 include the power manager and the I/O manager. The progress bar on the startup screen advances during this phase to ...

Stop 0x50 or PAGE_FAULT_IN_NONPAGED_AREA

Admin — Thu, 25 Dec 2008 20:05:45 GMT

The Stop 0x50 message indicates that requested data was not in memory. The system generates an exception error when using a reference to an invalid system memory address. Defective memory (including main memory, L2 cache memory, and video RAM) or incompatible software (including remote control and antivirus software) might cause Stop 0x50 messages. Interpreting the Stop 0x50 Message Parameter Description Parameter 1 Memory address referenced. Parameter 2 • Type of access: ...

Stop 0x3F or NO_MORE_SYSTEM_PTES

Admin — Wed, 24 Dec 2008 17:45:15 GMT

The Stop 0x3F message indicates one or more of the following problems: • The system Page Table Entries (PTEs) are fragmented because the system performed a large number of input/output (I/O) actions and a driver has requested a block of memory that is too large to fit in any of the available contiguous blocks of memory. PTEs map virtual memory to physical locations. • A faulty device driver is not managing memory properly. • An application, such as a backup program, is improperly ...

Stop 0x32 or PHASE1_INITIALIZATION_FAILED

Admin — Wed, 24 Dec 2008 17:36:34 GMT

The Stop 0x32 message indicates that system startup failed during Phase 1 of the Executive initialization. During Phase 1, interrupts are enabled, device drivers are initialized, and those Executive components that were not initialized during Phase 0 are initialized. Executive components initialized in Phase 1 include the power manager and the I/O manager. The progress bar on the startup screen advances during this phase to provide a visual representation of this part of the boot process. This ...

Stop 0x31 or PHASE0_INITIALIZATION_FAILED

Admin — Wed, 24 Dec 2008 17:33:05 GMT

The Stop 0x31 message indicates that system startup failed during Phase 0 of the Executive initialization. During Phase 0, interrupts are disabled and the HAL is initialized. Several Executive components are started: the memory manager, object manager, security reference monitor, process manager, and the Plug and Play manager. This error indicates a failure of one of those components. Note This Stop message includes no parameters. Troubleshooting the Stop 0x31 Error A Stop error ...

Stop 0x2E or DATA_BUS_ERROR

Admin — Wed, 24 Dec 2008 17:29:56 GMT

The Stop 0x2E message indicates a system memory parity error. The cause is typically failed or defective RAM (including memory on the motherboard, Level 2 cache, or video adapter), incompatible or mismatched memory hardware, or a device driver attempting to access an address in the 0x8xxxxxxx range that does not exist (that is, it does not map to a physical address). A Stop 0x2E message can also indicate hard disk damage caused by a virus or other problems. Interpreting the Stop 0x2E Message This ...

Stop 0x24 or NTFS_FILE_SYSTEM

Admin — Wed, 24 Dec 2008 17:23:25 GMT

The Stop 0x24 message indicates that a problem occurred within Ntfs.sys, the driver file that allows the system to read and write to NTFS file system drives. A similar Stop message, 0x23, exists for the file allocation table (FAT32) file systems. Interpreting the Stop 0x24 Message This Stop message has four parameters, as listed below: Parameter Description Parameter 1 Source file and line number. Parameter 2 A nonzero value that contains the address of the exception record ...

Memory Dump Files

Admin — Sun, 21 Dec 2008 19:10:42 GMT

When a Stop error occurs, Windows Server 2003 displays information that can help you analyze the root cause of the problem. Windows Server 2003 writes the information to the paging file (Pagefile.sys) on the systemdrive root by default. When you restart the computer in Start Windows Normally mode (commonly called “normal mode”) or Safe Mode after a Stop error occurs, Windows Server 2003 uses the paging file information to create a memory dump file in the systemroot or systemroot\Minidump ...

Stop 0x1E or KMODE_EXCEPTION_NOT_HANDLED

Admin — Tue, 23 Dec 2008 16:34:25 GMT

The Stop 0x1E message indicates that the Windows Server 2003 kernel detected an illegal or unknown processor instruction. The problems that cause Stop 0x1E messages share similarities with those that generate Stop 0xA errors, in that they can be caused by invalid memory and access violations. The default Windows Server 2003 error handler typically intercepts these problems if error-handling routines are not present in the code itself. Interpreting the Stop 0x1E Message This Stop message ...

Stop 0xA or IRQL_NOT_LESS_OR_EQUAL

Admin — Tue, 23 Dec 2008 16:23:59 GMT

The Stop 0xA message indicates that a driver or the kernel attempted to access a memory location to which it did not have permission, or at a kernel interrupt request level (IRQL) that was too high. The kernel represents an IRQL as a number from 0 to 31, with higher numbers representing higher-priority interrupts. Normal thread execution is at the lowest priority: IRQL 0. This Stop error is typically caused by faulty or incompatible hardware or software. Interpreting the Stop 0xA Message This ...

Common Stop Messages

Admin — Tue, 23 Dec 2008 16:09:58 GMT

The following Stop message descriptions contain details that help you troubleshoot or learn more about specific Stop errors. For information about the format of Stop messages as displayed on the screen, see “Stop Messages” earlier in this forum. The list of Stop messages in this chapter is not comprehensive. For information about additional Stop messages, see Help in the Microsoft Debugging Tools for Windows, which contains a more extensive list of Stop messages, is updated regularly, ...

Being Prepared for Stop Errors

Admin — Tue, 23 Dec 2008 16:03:36 GMT

Some useful software and hardware-related techniques can help you prepare for Stop errors when they occur. Stop messages do not always pinpoint the root of the problem, but they do provide important clues that you or a trained support technician can use to identify and troubleshoot the cause. Prevent System Restarts After a Stop Error When a Stop error occurs, Windows Server 2003 displays a Stop message related to the problem, followed by one of these events: • Windows Server ...

No internet connection after connecting via VPN

Admin — Mon, 22 Dec 2008 21:11:51 GMT

VPN connects but you lose internet connection as soon as the machine connects to the server via vpn

Resolution
=======

-Create a new vpn connection.
-Go to the propeties of the connection-.networking->tcpip properties-.advanced->uncheck the box for the default gateway from the remote server
-Connect again and you would not loose internet aftre connecting via vpn

Using Memory Dump Files to analyze STOP Errors

Admin — Sun, 21 Dec 2008 19:40:24 GMT

Memory dump files record detailed information about the state of your operating system when the Stop error occurred. You can analyze memory dump files manually by using debugging tools or by using automated processes provided by Microsoft. The information you obtain can help you understand more about the root cause of the problem. You can use the Error Reporting Service to upload your memory dump file information to Microsoft. You can also use the following debugging tools to manually analyze ...

STOP Erros Overview

Admin — Sun, 21 Dec 2008 18:25:11 GMT

Stop Errors Overview Stop errors only occur when a problem cannot be handled by using the higher-level error-handling mechanisms in the Microsoft® Windows Server™ 2003 operating system. Normally, when an error occurs in an application, the application interprets the error message and provides detailed information to the system administrator. However, Stop errors are handled by the kernel, and Windows Server 2003 is only able to display basic information about the error, write the contents ...

Metadata Cleanup After Unsucuseeful demotion of server during Migration

Admin — Sun, 21 Dec 2008 16:43:11 GMT

We see a lot of problems in the domain if there is unsuccessful demotion of any Domain Controller in the domain. Unsuccessful Demotions will include: 1. Either the DC was directly disconnected form the network without running the DCPROMO on the box. 2. We ran a DCPROMO /FORCEREMOVAL command on the domain controller. 3. The DC went down due to some reason and did not boot again. If this DC does not exists in the domain and we still see it listed in the Active Directory Sites and ...

Exchange services and DNS not starting

Admin — Fri, 19 Dec 2008 18:43:14 GMT

When you try to start the Microsoft SA we get the error: --------------------------- Services --------------------------- The Microsoft Exchange System Attendant service on Local Computer started and then stopped. Some services stop automatically if they have no work to do, for example, the Performance Logs and Alerts service. --------------------------- OK --------------------------- Although RPC service is started. Also DNS server had a RED X on it. Check the ...

Remote Desktop Fails after installing SP2 for windows 2003 server

Admin — Fri, 19 Dec 2008 16:50:00 GMT

After installing Windows Service Pack 2 for Windows 2003 we are unable to RDP into the Windows 2003 SP2 machine. Error message “This computer can't connect to the remote computer. The connection was lost due to a network error. Try connecting again. If the problem continues, contact your network administrator or technical support.” Event ID Event Type: Error Event Source: TermDD Event ID: 50 Description: The RDP protocol component "DATA ENCRYPTION" ...

Uninstalling Service Packs from the recovery console

Admin — Fri, 19 Dec 2008 03:13:39 GMT

Sometimes when we install service packs (1 or2) for windows servers, the servers do not boot up. This happens due to some incompatibilty of the servcie pack with the drivers of some applications or hardware. In such cases we have to go to the recovery console to uninstall them. 1. From recovery console browse to the following director:windows\$NtServicePackUninstall$\spuninst 2. Run Batch spuninst.txt 3. Browse to c;\windows\system32\config 4. ren system system.old 5. ren software ...

Unable to install SP2 for Windows 2003

Admin — Thu, 18 Dec 2008 19:45:00 GMT

While installing SP2 foe 2003 server, you may get the error: --------------------------- Service Pack 2 Setup Error --------------------------- Failed to install catalog files. Select 'OK' to undo the changes that have been made. --------------------------- OK --------------------------- or --------------------------- Service Pack 2 Setup Error --------------------------- Setup could not verify the integrity of the file Update.inf. Make sure the Cryptographic ...

Error returned while creating the volume shadow copy: 0xfffffff

Admin — Thu, 18 Dec 2008 19:12:34 GMT

Error Message for the backup log states the following: =================================== Volume shadow copy creation: Attempt 1. Timeout before function completed Error returned while creating the volume shadow copy: 0xffffffff. Error returned while creating the volume shadow copy: ffffffff Aborting Backup. Event Logs Show: Event Type: Error Event Source: NTBackup Event Category: None Event ID: 8019 Date: 12/16/2006 Time: 11:05:07 PM User: N/A Computer: ...

Unable to run forestprep due to MSDTC service errors

Admin — Thu, 18 Dec 2008 17:19:44 GMT

Symptoms: ======================= You may be unable to run setup /Forestprep and the errors below may be seen. This may happen even with the correct permissions to modify the schema and to the TEMP location. If you review the setup log like the one below, it tells you to consult the LDIF.ERR file but it is never created. Error Messages: ======================= "[The component "Microsoft Exchange Forest Preparation" cannot be assigned the action "ForestPrep" ...

Troubleshooting Unshared sysvol and netlogon.

Admin — Thu, 18 Dec 2008 04:52:57 GMT

When we do a “net share” from the command prompt we do not see the SYSVOL and NETLOGON folder shared. Following is the troubleshooting to be done…. SCENARIO I - Single DC. Check for the "SysvolReady" key under "HKLM\SYSTEM\CurrentControlSet\Services\Netlogon\Parameters" and make sure it set to 1. If it s set to 0 change it to 1 (HEX). Restart netlogon service. SYSVOL and NETLOGON shares gets created successfully. SCENARIO II - Two domain controller ...

Steps to Migrate a Server (from 2000 to 2003 or 2003 to 2003)

Admin — Wed, 17 Dec 2008 01:35:27 GMT

The FIRST step before migrating is to take a complete backup of your server including the system state. The best way to migrate is mentioned in Microsoft's KB884453, the link to which is mentioned below: http://support.microsoft.com/kb/884453 Though this article talks about migrating a Small Business Server 2003 to an existing AD domain, however, it is the same procedure if you are migrating from a 2000 to 2003 server or from 2003 to another 2003 server.