Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Re: Exchange 2003 SP1 - Exchange 2003 not installed

2 views
Skip to first unread message

Evan Dodds [MSFT]

unread,
Jun 3, 2004, 11:37:07 AM6/3/04
to
Paul -

It pulls this information out of the registry. If it's wrong in the
registry, it makes me wonder if the initial Exchange 2003 upgrade succeeded
completely. What happens if you run through Exchange 2003 Setup and choose
the "reinstall" action. Does it then allow you to proceed with the Exchange
2003 SP1 upgrade?

--
Evan Dodds
Microsoft Exchange Support

****** Disclaimer ******
This posting is provided "AS IS" with no warranties, and confers no rights.

Note: Please do not reply to this e-mail address. It is used for newsgroup
purposes only.

"Paul Carr" <paul...@leics-his.nhs.uk> wrote in message
news:e$m60qXS...@TK2MSFTNGP11.phx.gbl...
> I apologise for cross-posting this message to several Exchange
> newsgroups. Like others I am not sure where it's true home should be!
>
> I have started the process of installing SP1 for EX2K3. First front-end
> server (W2K and EX2K3) went okay. However, the Exchange Installation
> Wizard on the second one reports the current (build version) as 6.0.
> Consequently, the install process won't proceed any further as it
> believes that EX2K is installed. However, ESM reports that the build
> installed on that server is 6.5 (6944.4) which is EX2K3.
>
> I have tried trawling the Web and Google Groups for any information
> indicating that others may be having the same problem. I have also
> tried to find out how EIW determines the version or build number by
> trawling inf files, the server registry, the Web and news groups, but
> all I have drawn so far is a blank.
>
> Has anyone else who is implementing SP1 come across this specific
> problem or has anyone at MS Support have any information on where EIW
> is picking up this information and whether they are aware of any such
> problem more universally.


Steve Schiemann[MSFT]

unread,
Jun 3, 2004, 1:28:33 PM6/3/04
to
Please post the part of the Exchange Server Setup Progress.log that contains
errors related to this problem- this file is found at the root of the drive
you installed Exchange 2003. SP1 setup will append to this log, look at the
end of the file for this info...

--


Steve Schiemann
Microsoft Exchange Support

Please do not send e-mail directly to this alias. This alias is for
newsgroup purposes only.


This posting is provided "AS IS" with no warranties, and confers no rights.

Paul Carr

unread,
Jun 3, 2004, 6:14:42 PM6/3/04
to
The whole section of the Install Progress Log file that covers the attempt
to install SP1 is 592 lines long, so I have attempted to extract the parts
of it that I think should be relevant (I hope!). To be honest I could not
see anything in any part of the whole section of the log file that screamed
"here's the obvious error!". Is there anything in particular that I should
be looking for?

[08:46:02] Looking for server object...
[08:46:02] Found server object; looking for serial number...
[08:46:02] Serial number is "Version 6.5 (Build 6944.4)"
[08:46:02] Previous build is 6944, so s_fUpgradingFromPT is FALSE


[08:46:02] Looking for domain proxy container
[08:46:02] Domain proxy container found -- checking DomainPrep version
[08:46:02] Installed DomainPrep version is 6936; current version is 6936
[08:46:02] This domain is DomainPrepped
[08:46:02] Leaving ScIsDomainPrepped
[08:46:02] Entering CFileManager::ScSetInstallDestDir(sz)
[08:46:02] Leaving CFileManager::ScSetInstallDestDir(sz)
[08:46:02] - You must have Exchange Server 2003 installed on this machine
before installing this Microsoft Exchange Server Service Pack. --
ID:62114 --
[08:46:02] Prerequisites for Microsoft Exchange failed: The component
"Microsoft Exchange" cannot be assigned the action "Update" because:
- You must have Exchange Server 2003 installed on this machine before
installing this Microsoft Exchange Server Service Pack.


Evan Dodds [MSFT]

unread,
Jun 3, 2004, 6:48:59 PM6/3/04
to
Paul -

Exchange setup looks at this reg value to determine what build is installed
for the upgrade process: HKLM\Software\Microsoft\Exchange\Setup\NewestBuild.
If this value is missing or wrong, it won't work properly.

That said, if the reg key is missing or wrong, there's a good chance other
stuff is also not properly in place. I still suggest you try to run through
the Exchange 2003 RTM setup with the "Reinstall" action to ensure all of the
settings are in place and then try the SP1 upgrade again...

--
Evan Dodds
Microsoft Exchange Support

****** Disclaimer ******


This posting is provided "AS IS" with no warranties, and confers no rights.

Note: Please do not reply to this e-mail address. It is used for newsgroup
purposes only.

"Paul Carr" <paul...@dsl.pipex.com> wrote in message
news:e4aotgbS...@tk2msftngp13.phx.gbl...

Paul Carr

unread,
Jun 4, 2004, 2:59:28 AM6/4/04
to
Hello Evan

Thank you for the prompt response. I have only picked it up now because of
time differences!

I have looked at the registry entry on the server. It is 4417. On one of our
back-end servers which is also EX2K3 it is 6944, so I guess we have some
sort of fundamental problem.

I agree with your logic about the probability that there are probably other
problems with the original RTM install. I am not aware of any problems from
that time, but as I was not directly involved in the upgrade install, that
is not relevant.

Once I get into the office, I will try to re-install the RTM as you suggest
and provide some feedback to the Group(s) in case it has any relevance for
other customers in a similar situation.


superdooperman

unread,
Jan 7, 2008, 6:04:29 PM1/7/08
to

Did you manage to sort this out? I've got exactly the same message.


--
superdooperman

superdooperman

unread,
Jan 24, 2008, 4:18:24 PM1/24/08
to
at having only one eye? Probably no man ever
ventured to mourn at not having three eyes. But any one is inconsolable at
having none.

410. Perseus, King of Macedon.--Paulus Aemilius reproached Perseus for not
killing himself.

411. Notwithstanding the sight of all our miseries, which press upon us and
take us by the throat, we have an instinct which we cannot repress and which
lifts us up.

412. There is internal war in man between reason and the passions.

If he had only reason without passions...

If he had only passions without reason...

But having both, he cannot be without strife, being unable to be at peace
with the one without being at war with the other. Thus he is always divided
against and opposed to himself.

413. This internal war of reason against the passions has made a division of
those who would have peace into two sects. The first would renounce their
passions and become gods; the others would renounce reason and become brute
beasts. (Des Barreaux.) But neither can do so, and reason still remains, to
condemn the vileness and injustice of the passions and to trouble the repose
of those who abandon themselves to them; and the passions keep always alive
in those who would renounce them.

414. Men are so necessarily mad that not to be mad would amount to another
form of madness.

415. The nature of man may be viewed in two ways: the one according to its
end, and then he is great and incomparable; the other according to the
multitude, just as we judge of the nature of the horse and the dog,
popularly, by seeing its fleetness, et animum arcendi; and then man is
abject and vile. These are the two ways which make us judge of him
differently and which occasion such disputes among philosophers. For one
denies the assumption of the other. One says, "He is not born for this end,
for all his actions are repugnant to it." The other says, "He forsakes his
end, when he does these base actions."

416. For Port-Roy


0 new messages