Active10 months ago

I have server 2003 standard SP2 running in our enviroment. I am trying to upgrade to Enterprise edition with SP2 because we are hitting the 4GB limitation imposed by the standard edition.
Sure, Microsoft has its own table comparing the various Windows Server 2003 editions, but that version is incomplete, hard to read, and poorly organized. Ent - Windows Server 2003 Enterprise Edition DC - Windows Server 2003 Datacenter Edition Ent-64.

I'm trying to install IIS on Windows Server 2003 and in the Windows Components Wizard, it prompts me to 'Insert Service Pack 2 CD-ROM'. I'm assuming this is the Windows Server 2003 installation CD, CD 2. However when I try to put it in, it doesn't seem to recognize it. In the D: drive, it is called CR0SCD2X_EN. Do you folks have any ideas on how to fix this? Thanks.

This shows how to update to Windows Server 2003 Service Pack2 (SP2). Windows Server 2003 Service Pack 2 Installation and Deployment Guide. ・Microsoft(R) Windows Server(R) 2003 Enterprise Edition Service Pack 2 CD for Itanium(R)-based Systems SP2 Update procedure 1. Log on your system as a user with Administrator authority.

Edit: I entered in CD1 and seems like it gave it a kick start. However, now it is complaining about where a convlog.exe file is. Doesn't seem to be in CD1 or CD2. :(

O_OO_O

3352 gold badges9 silver badges25 bronze badges

4 Answers

No, it's asking for the installation files for Service Pack 2, not CD 2. It's asking for what it needs - the versions of the files already on the system are at SP2, but the installation source files aren't there for whatever reason.

Once you do what you're talking about - essentially, forcing SP1 files (2003 R2 shipped with SP1 included) in place of SP2 - you'll end up with a mostly-working-but-partially-broken IIS installation, which won't install at least some security updates correctly.

I'd suggest you download and extract the SP2 installation files to somewhere accessible from this computer, then uninstall and reinstall IIS on the box with that location specified when it prompts for the SP2 'CD'.

If not, after you've forced it through like this, a) reinstall SP2, and b) run Windows Update again.

Edit: One such breakage is this one: http://support.microsoft.com/kb/2009746

TristanKTristanK

8,3882 gold badges21 silver badges33 bronze badges

Kinda weird, but with the help of IIS forum, I was able to do this:Run this command from command prompt:

And installing IIS after that. It works!

O_OO_O

3352 gold badges9 silver badges25 bronze badges

If you have a slipstreamed CD, point the installer to it.

kinokijufkinokijuf

This problem might have an utterly stupid solution:

If the 'Files Needed' dialog is proposing the location 'C:WINDOWSINSTALLATIONI386i386', try deleting the last I386 (from the dialog's path):

With the current AWS EC2 Windows Server R2 image (ami-26e3e7cd) that's all is needed: it looks like some installer genius just typed the wrong location somewhere!

Windows Server 2008 Sp2

The prompt will come up for each missing file, so you'll have to do this several times.

Precisely these are the files for which I get a prompt when installing IIS (the Application Server role):

convlog.exe
iisback.vbs
iis6.cab

gbrgbr

protected by voretaq7Nov 8 '12 at 17:45

Thank you for your interest in this question. Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).
Would you like to answer one of these unanswered questions instead?

Not the answer you're looking for? Browse other questions tagged windows-server-2003iis or ask your own question.

Windows Server 2003
Support status
A version of the Windows NT operating system
Developer	Microsoft
OS family	Microsoft Windows
Working state	No longer supported
Source model	Source-available (through Shared Source Initiative)
General availability	April 24, 2003; 16 years ago^[1]
Final release	Service Pack 2 (5.2.3790) / March 13, 2007; 12 years ago^[2]
Marketing target	Business
Platforms	IA-32, x86-64, Itanium
Kernel type	Hybrid (Windows NT kernel)
Default user interface	Windows shell (Graphical)
License	Trialware^[3] and volume licensing,^[4] with client access licenses^[5]
Preceded by	Windows 2000 (2000)
Succeeded by	Windows Server 2003 R2 (2005)
Official website	www.microsoft.com/windowsserver2003/
Mainstream support ended on July 13, 2010 Extended support ended on July 14, 2015^[6]^[7]

Windows Server 2003 is a serveroperating system produced by Microsoft and released on April 24, 2003.^[8] It is the successor to Windows 2000 Server and the predecessor to Windows Server 2008. An updated version, Windows Server 2003 R2, was released to manufacturing on December 6, 2005. Windows Server 2003's kernel was later adopted in the development of Windows Vista.^[9]

How to execute 16-bit installer on 64-bit Win7? Ask Question 24. I am trying to install Sheridan controls (ActiveThreed 2.01) on Win7 64-bit, but evidently it is a 16-bit installer so it won't execute. What would be the best way to get round this problem? Activethreed 2 01 s. ActiveThreed Plus is a set of eleven 32-bit ActiveX controls that give your applications the look and feel of popular interfaces such as Office '97, Microsoft PowerPoint, Internet and more. Sheridan Active Threed 2.04 setup incompatibility on Windows 7 64-bits. Caroline posted over 6 years ago. Hi, I'm actually trying to run the installation setup for Active Threed 2.04 controls, as some of our legacy VB6 applications are still using them. Sep 17, 2016 UltraGrid 2.01.025.01 - January. Will occur if you are saving images to the pagePictureBackgroundURL properties to download. For ActiveThreed Plus. ActiveThreed 2.0 Oct-98 Expired Mar-03 Retired File Name Version Splitter.ocx 2.04.0003 Expired Mar-03 Retired.

4Editions
5Derivatives
- 5.2Windows Storage Server
6Updates

Overview[edit]

Windows Server 2003 is the follow-up to Windows 2000 Server, incorporating compatibility and other features from Windows XP. Unlike Windows 2000 Server, Windows Server 2003's default installation has none of the server components enabled, to reduce the attack surface of new machines. Windows Server 2003 includes compatibility modes to allow older applications to run with greater stability. It was made more compatible with Windows NT 4.0 domain-based networking. Windows Server 2003 brought in enhanced Active Directory compatibility and better deployment support to ease the transition from Windows NT 4.0 to Windows Server 2003 and Windows XP Professional.

The product went through several name changes during the course of development. When first announced in 2000, it was known by its codename 'Whistler Server'; it was named 'Windows 2002 Server' for a brief time in mid-2001, followed by 'Windows .NET Server' and 'Windows .NET Server 2003'. After Microsoft chose to focus the '.NET' branding on the .NET Framework, the OS was finally released as 'Windows

Windows Server 2003 Enterprise Edition Sp2