Identifying Strategies for Resolving Special Problems
Applies To: Windows Server 2003, Windows Server 2003 R2, Windows Server 2003 with SP1, Windows Server 2003 with SP2
Some special problems cannot be resolved by applying application compatibility fixes or by debugging and modifying source code. If application compatibility fixes do not resolve an application problem, try one of the following solutions.
Reinstall the application by using an Administrator account
If the problematic application was written for Windows 95, Windows 98, or Windows Millennium Edition, use an Administrator account to install the application. These versions of Windows did not differentiate between Administrator and limited user accounts, so an application that runs on these versions might write to a location that is not allowed by Windows XP Professional.
Use the current Microsoft Virtual Machine
Use the most current version of the Microsoft Virtual Machine, which enables Java programs to run on Windows.
Remove and reinstall the application after upgrading to Windows XP Professional
If you upgraded the computer to Windows XP Professional, and the application is listed in the Windows Catalog as compatible with Windows XP Professional, try to remove and then reinstall the application after performing the upgrade. If removing and reinstalling the application on Windows XP Professional does not solve the problem, the application might not have been entirely removed. Contact the application vendor for specific instructions on how to remove the application manually. For example, it might be necessary to remove certain folders or registry entries in order to fully reinstall the application.
Verify MDAC and DirectX versions
If the application uses Microsoft Data Access Components (MDAC) or DirectX, ensure that you are using the correct versions. Windows XP Professional with Service Pack 1 and Windows Server 2003 support MDAC version 2.7 with Service Pack 1 and DirectX version 9.0. Some older applications attempt to install an earlier version of MDAC or DirectX, but Windows File Protection replaces the earlier version with the newer version. If the application requires the earlier version, errors can occur. In this case, you might need to create a redirection file, as described in the following section, to ensure that the required version is loaded when the application runs.
Load earlier versions of .dll files
Some older applications require earlier versions of .dll files than are supplied by Windows XP Professional or Windows Server 2003. If a newer version of a .dll file is loaded when an application runs, problems can occur. To ensure that the application uses the version of the .dll file that it requires, create a redirection file. The redirection file must be created in the same directory as the .dll files and the application.
A redirection file contains no data or information (the contents of the redirection file are ignored), but its name must have the format ApplicationExecutable.local. For example, if an application’s name is Editor.exe, the redirection file must be named Editor.exe.local.
Even if you do not use a redirection file, always install the .dll files for an application in the same directory as the application. Doing so ensures that the application does not overwrite copies of the .dll files, which might be used by other applications. Doing so also ensures that the application loads the .dll files that it requires.
Placing a redirection file in the directory with an application ensures that all the .dll files in that directory are loaded when the application runs, instead of the .dll files supplied by the operating system. Without a redirection file, the .dll files supplied by the operating system are loaded when the application runs.
Important
- You do not need to use a redirection file with Windows XP Professional with Service Pack 1 or higher, or with Windows Server 2003. You do need to use a redirection file with Windows XP Professional without Service Pack 1.
Create application manifest files
As you migrate applications to Windows XP Professional or Windows Server 2003, you should write an application manifest, a .man file, for each application. The manifest is a text file in XML format that lists the dynamic-link libraries that the application should be executed with, along with their version numbers. In the manifest, list the DLL versions with which the application was originally built and tested. When Windows XP Professional or Windows Server 2003 runs an .exe file for which a manifest exists, it loads only the DLL versions specified in the manifest. For more information about specific DLLs, see the DLL Help Database link on the Web Resources page at https://www.microsoft.com/windows/reskits/webresources.
Change the short date format
Some applications that were designed for Windows 95 do not handle short dates correctly when they run on Windows XP Professional. If an application does not accept short dates that are entered by a user, try changing the short date format in Regional and Language Options. For example, if the short date format is M/d/yyyy (the default), try changing the format to MM/dd/yyyy.
To change the short date format on Windows Server 2003
Open Regional and Language Options in Control Panel.
On the Regional Options tab, click Customize.
On the Date tab, next to Short date format, select a short date format.
To change the short date format on Windows XP Professional
Open Control Panel, and then click Date, Time, Language, and Regional Options.
Click Regional and Language Options.
On the Regional Options tab, click Customize.
On the Date tab, next to Short date format, select a short date format.
Verify that the Kodak Image Edit control is not required
Ensure that the application does not depend on the Kodak Image Edit control. This control has been removed from Windows XP Professional and Windows Server 2003.
Verify the length of network printer names
Some older applications fail when they attempt to print to a network printer with a name longer than 31 characters. To prevent this problem, create a local connection to the network printer for the application.
To create a local printer connection
Start the Add Printer Wizard.
On the Local or Network Printer page, select Local printer attached to this computer,and clear Automatically detect and install my Plug and Play printer.
On the Select a Printer Port page, select the port if it is listed. Otherwise, select Create a new port, and then for Type of Port, select Local Port.
Click Next to display the Port Name window, and enter the port name for the printer in the format \\PrintServer\PrinterName.
On the Install Printer Software page, select the printer manufacturer and the appropriate printer.
On the Use Existing Driver page, select Keep existing driver, if there is one.
On the Name Your Printer page, type a name using fewer than 31 characters and finish the wizard as appropriate for your environment.