Article ID: 817093 - Last Review: September 12, 2011 - Revision: 3.0 How to troubleshoot Office XP Setup problems on Windows 2003 Server
IMPORTANT: This article contains information about modifying the registry.
Before you modify the registry, make sure to back it up and make sure that you
understand how to restore the registry if a problem occurs. For information
about how to back up, restore, and edit the registry, click the following
article number to view the article in the Microsoft Knowledge Base: 256986
(http://support.microsoft.com/kb/256986/EN-US/
)
Description of the Microsoft Windows Registry
On This PageSUMMARY This article describes how to troubleshoot when you are
installing Microsoft Office XP on a computer that is running Microsoft Windows
2003 Server, and Setup appears to stop responding, or "hang," without error
messages. MORE INFORMATIONMake Sure That Setup Actually Stopped RespondingSetup may appear to stop, but in fact it may be continuing slowly. Wait (about 20 minutes) before you end Setup. To test whether Setup has stopped, follow these steps:
Verify That the CD-ROM Is Clean and UnscratchedIf the problem occurs while you are installing from a CD-ROM, verify that the CD-ROM you are using is clean. You can wipe the CD-ROM with a soft, lint-free cloth. Also make sure that there are no large scratches on the CD-ROM. If the CD-ROM is damaged and unreadable, error messages may appear during installation. For additional information, click the article number below to view the article in the Microsoft Knowledge Base: 266700
(http://support.microsoft.com/kb/266700/EN-US/
)
OFFXP: Troubleshooting Installation from Compact Disc Media
Remove a Beta Version of Office XPIf a beta version of Office XP was installed earlier, you must remove the beta version before you install the final version of Office XP. Although Office XP Setup prompts you to remove such a prerelease version, the removal process may not be completed successfully. To remove a beta version of Office XP, follow these steps:
Verify the PermissionsMake sure that the correct permissions are set for your account. To determine whether you have the correct permissions to install, run, and use the Office program that you are having problems with, log on to the computer as an administrator. When you log on to Windows as an administrator, you have full read/write permission to all folders and files on the computer, and also to the registry. If the problem does not occur after you log on as an administrator, verify the permissions of your user account. Test the User ProfileSometimes, a user's specific information may be damaged, but other users on the same computer may have no problem. To determine whether this is the case, log on as a new user or create a new user, and then test. For additional information, click the article number below to view the article in the Microsoft Knowledge Base: 296834
(http://support.microsoft.com/kb/296834/EN-US/
)
User Profile May Become Corrupted After You Perform a Clean Windows 2000 Installation
Use the Setup Log FilesWhen you install Office XP, Setup automatically creates log files in your TEMP folder. The log files have names similar to the following: Collapse this table
In the table, edition is the edition of Office XP that you are installing. For example, these files may be:
Office XP Professional Setup(0001).txt Office XP Professional Setup(0001)_Task(0001).txt The #### characters in the log file names are numbers beginning with 0001. These numbers increment by 1 each time that you run Setup. Therefore, the log file with the highest number is the most recent log file. By default, verbose logging is enabled in Office XP. Therefore, the Windows Installer log files contain much information about events that occur during installation. This file may be requested if you contact Microsoft Product Support Services for more troubleshooting. For additional information about creating and reading Office Setup log files, click the following article number to view the article in the Microsoft Knowledge Base: 296603
(http://support.microsoft.com/kb/296603/
)
How To Use an Office XP Setup Log File to Troubleshoot Setup Problems in Office XP
For additional information about customizing Office
Setup log files, click the following article number to view the article in the
Microsoft Knowledge Base: 296604
(http://support.microsoft.com/kb/296604/
)
HOW TO: Customize Office Setup Logging Options
Close Unnecessary Memory-Resident ProgramsPrograms that run in the background in memory are known as terminate-and-stay-resident (TSR) programs. For example, these programs may be virus protection software, utility programs, print manager programs, or screen savers. To determine whether a terminate-and-stay-resident program is running, follow these steps:
WARNING: If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk. To see which programs are loaded through the registry, follow these steps:
Check the TEMP FolderAn invalid TEMP environment variable can cause errors with the Office Setup program. This section describes how to verify that your temporary folders are correctly set up. First, you must determine the location of your Windows TEMP folder and verify the validity of your TEMP environment variables. To do this, follow these steps:
Disk Cleanup UtilityIn Windows, you can delete many unused or temporary files with the Disk Cleanup Utility. Disk Cleanup searches your computer's hard disk and then shows you temporary files, Internet cache files, and nonessential program files that you can safely delete. You can direct Disk Cleanup to delete some or all those files. To open the utility, click Start, point to All Programs, point to Accessories, point to System Tools, and then click Disk Cleanup.Check the Hard Disk for Disk Errors and FragmentationUse the Disk Defragmenter program to check the hard disk volume for lost clusters and other master file tables (MFT) errors. You can also test the integrity of the hard disk's ability to read and write data and then repair most errors. To run the Disk Defragmenter program, follow these steps:
Scan the Computer for VirusesIf a virus is present on your computer and it has damaged any files, problems may occur when you run Setup. Scan the hard disk and floppy disks with virus detection software that is updated with a very recent virus signature file. If the antivirus software detects a virus on your computer, clean or remove the virus before you try to run Office Setup again.Clean Start Windows 2003 ServerTo disable common startup programs, drivers, and system settings that may conflict with the Office Setup program, you can clean start (clean boot) Windows. For additional information about how to clean start Windows XP by using the System Configuration Utility, click the following article number to view the article in the Microsoft Knowledge Base:310353
(http://support.microsoft.com/kb/310353/EN-US/
)
How to Perform a Clean Boot in Windows XP
Run Setup from a Flat FileIf sufficient space is available on the hard disk, make a copy of the contents of the Office XP CD-ROM. To do this, follow these steps:
For additional information about hard disk requirements, click the article number below to view the article in the Microsoft Knowledge Base: 285342
(http://support.microsoft.com/kb/285342/EN-US/
)
OFFXP: System Requirements for Office XP
Use this flat file to install Office while Windows
is in Safe mode (see the "Start Windows in Safe Mode" section later in this
article). If installing from a flat file fails, there may still be a problem
with the CD-ROM, because a damaged file can be copied without generating an
error message. When you install Office from this flat file in Safe mode, you
can determine whether startup items or services are conflicting with the Setup
program. Start Windows in Safe ModeWindows has a built-in troubleshooting mode named Safe mode. Safe mode bypasses startup files and uses only basic system drivers, including basic networking and system services. When you start Windows in Safe mode, Windows uses only the mouse, keyboard, and standard video graphics adapter (VGA) device drivers and those system services that are necessary to start. This makes Safe mode useful for isolating and resolving error conditions that are caused by startup programs, services, and Windows-based drivers. Windows also has troubleshooting features that may help you identify the problem. To start Windows in Safe mode and make the additional troubleshooting features available, follow these steps for your system configuration:
202485
(http://support.microsoft.com/kb/202485/EN-US/
)
Description of Safe Boot Mode in Windows 2000
Look for Software UpdatesOutdated and incompatible software also may cause Setup problems. Contact the manufacturer of your computer for various software updates, such as BIOS updates, original equipment manufacturer (OEM) Windows updates, and hardware driver updates (CD-ROM, video, and printer drivers). Reinstall Windows in a New FolderUse this method after you try all other troubleshooting methods listed earlier in this article. For testing purposes, you can install Windows in a different folder from your original Windows installation and then install Office to that environment. This is known as making a "parallel" copy, because your original installation of Windows is not completely removed. Instead, Windows is installed alongside your original copy. If installing Office this way is successful and you decide to keep the new installation of Windows, you must reinstall all Windows-based programs under the new Windows installation. For additional information about installing a parallel copy of Windows, click the following article number to view the article in the Microsoft Knowledge Base: 266465
(http://support.microsoft.com/kb/266465/
)
HOW TO: Perform a Parallel Installation of Windows 2000 or Windows 2003
Check HardwareIf you try all other troubleshooting steps and you still receive error messages, one or more devices in your computer hardware may be incompatible with Windows or may be damaged. To identify a problem with your computer hardware, contact your computer vendor. APPLIES TO
| Other Resources Other Support Sites
CommunityGet Help NowArticle Translations |






Windows Live
Facebook
Twitter
Linkedin
Digg it
Yahoo
Delicious
StumbleUpon
Yammer
Reddit
Technorati
FriendFeed
Email
Back to the top
