Oops, My Installation Didn t Take

team lib

Oops, My Installation Didn't Take

REMEMBER 

In most cases, as long as your hardware is on the HCL, installation will be a breeze . (Well, how about a long, continuous gust?) For those other cases, here are some common problems and how you can resolve them:

  • CD-ROM problems: The entire Windows 2003 installation ships on a CD-ROM, so if you can't read the CD, you can't install Windows 2003 (unless you're installing over a network, but even then, the distribution files have to come from a CD at some point). CD-ROMs are similar to music records or CDs in that one little scratch or speck of dust on the surface can cause problems. On the other hand, the CD may be okay, but the drive may not be functioning correctly or Windows 2003 may not recognize the drive. We hope that your drive appears on the HCL. To determine whether the driver or the CD isn't functioning, take the CD to another CD-ROM drive and see whether you can read it there. After you determine which element is the culprit, you can replace it and retry your installation.

  • Hardware problems: If Windows 2003 Setup doesn't recognize a server's hardware, it's likely to stop. Make sure that the machine's hardware appears in the HCL and that you configured all devices correctly. If you have more than one SCSI device, for example, make sure that they are chained (connected) correctly.

  • Blue screen of death: Sometimes, Setup simply crashes and gives you a blue screen; other times, it gives you a display of error codes that only a propeller head can understand. By itself, the blue screen simply means that you must reboot. If you get a fancy stop screen, however, you can look at the first few lines to determine the error code and then use it to look up the error message in the error-message manual. Stops typically occur if a driver problem occurs; if you look beyond the first few lines of the error-message screen, it tells you which drivers were loaded at the time the crash occurred. A good idea is to write the first few lines of the stop screen down before attempting to reboot.

  • Connectivity problems: Installing a machine into an existing domain requires that the new system be capable of communicating with a domain controller to create a domain computer account. If communication is not possible for any reason (such as a wrong NIC, a wrong driver, a bad or missing cable, a domain controller offline, or too much network traffic), you won't be able to join the domain. In some cases, you can resolve the problem by quickly replacing a cable or allowing the system to try the connection a second or third time. In other cases, you can delay confronting the problem by joining a workgroup instead. Then you can resolve any problems (such as NIC, driver, and configuration problems) with a functioning system.

  • Dependency problems: Some services in Windows 2003 depend on other services loading correctly. If service A doesn't load, service B doesn't work, and you get error messages if service B is set to automatically start at bootup . For example, if a NIC isn't installed correctly, all services that use that NIC also fail to start. Your first order of business, therefore, is to get the NIC to function correctly. If you get this far in the installation process, you can view the error logs (Start Administrative Tools Event Viewer) to see which service did not start and then work your way from there.

  • Script file errors: The Windows 2003 automated installation program (see the next section) is not forgiving if you mistype a script. If a script stops midway and the Windows 2003 Setup program asks you for manual input, you entered something incorrectly. Check the input file to look for transposed letters or anything else that may be out of place. Scripts expect to feed the computer exactly what you put in the script file. If you don't enter the right information, Setup doesn't receive the information it expects.

  • SERVER1.TXT-SERVER4.TXT files: If you encounter driver problems or other problems missing from the preceding list, obtain and read these files to see whether some late-breaking news that Microsoft couldn't get into the manuals may have affected your installation. The file is in the \docs subdirectory.

team lib


Windows Server 2003 for Dummies
Windows Server 2003 for Dummies
ISBN: 0764516337
EAN: 2147483647
Year: 2003
Pages: 195

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net