Clearapps network inventory
software.

Troubleshooting Windows 2003 Issues

Can’t access Server 2003
Can't install SP1 for Windows 2003 server
Cannot view event log after changing administrator password
Some Services Do Not Start After You Upgrade to Win 2003
"STOP 0x0000008E" Error Message Occurs When You Upgrade to Server 2003
Windows 2000 Pro or 2003 Server Is Inaccessible from the Domain

Cannot view event log after changing administrator password

Symptoms: After you changed the administrator password on a 2003 server, you are unable to access some server information like the event logs.

Cause: When using Reset Password on Local Users and Groups, that may cause irreversible loss of information. You should use Ctrl+Alt+Del instead of Reset Password to change administrator password.

Some Services Do Not Start After You Upgrade to Win 2003

Symptoms: After you upgrade your w2k to 2003, when attempting to start the computer, some Windows services do not start. Additionally, you may receive a message that states that the page file is too small or that you do not have a page file.

Resolutions: This behavior occurs if you removed Read & Execute, List Folder Contents and Read permissions for the Authenticated Users group on the drive where Windows is installed before you upgrade to 2003. To resolve this issue, add the Authenticated Users group to the drive where Windows is installed, and then assign permissions.

"STOP 0x0000008E" Error Message Occurs When You Upgrade to Windows Server 2003

Symptoms: When attempting to upgrade a 2000 Server computer to Server 2003, you may receive a Stop error message similar to the following during the text-mode portion of Setup: STOP: 0x0000008E (0xC0000006, 0x808F1210, 0xFC99F5C0). Additionally, you can no longer access the partition that contains the operating system.

Resolutions: To avoid this problem, remove the disk that contains the Winnt.sif file from the computer's floppy disk drive before you upgrade to Server 2003. The Winnt.sif file is only used in unattended installations. Do not use it with the repartition=yes parameter when you upgrade a 2000 server to Server 2003.

Windows 2000 Pro or 2003 Server Is Inaccessible from the Domain

Symptoms: When attempting to connect to a Windows 2000 Pro or 2003 server from other computers on the network, you may receive one of the following error messages.

From a Microsoft Windows NT Server 4.0-based computer, you receive the following error message: Error = There are currently no logon servers available to service the logon request.
From a Microsoft Windows 98-based computer, you receive the following error message: Error 2215: serverrname is not accessible. The logon server cannot be found

The Windows 2000 Pro or 2003 server is logged on to the domain and can connect to everything else on the network, but Event Viewer shows that the computer cannot contact the domain controller. The Netdiag utility reports that the computer is logged on to the domain through cached credentials.

Resolutions: To resolve this behavior, join the Windows 2000 Pro or 2003 server to a workgroup named WORKGROUP, and then restart the computer. Rejoin the computer to the domain, and then restart the computer again. The computer no longer logs on through cached credentials.