Error from "setup.com /prepareschema " following MS KB Article ID: 2457729 instructions

Pretty tough to find a KB or solution when you don't know what the error is. Did you open the setup log and see if there are more details? Or are there more details you haven't posted?

Hah, and while I'm thinking of it, why are you running setup from windows\system32? That isn't a normal location.

I'd download SP3 again, unpack it in a folder, and run the setup from that folder so you know you have a clean version of the setup.

-Cliff

Cliff -
Good point about the CWD - but - it is running the application from:
C:/program files/microsoft/exchange server/bin/setup.exe

Running from that directory (or the higher level "exchange server" directory) still fails.
Also, running from C:\Temp gives same error.

Where would the "setup log" be? There's nothing in the Event Viewer / Application log.

I'll happily post more details if I could find any error/background. What else would be useful?
Thanks!

The setup actually writes a log file when it runs. Plain text. Nothing fancy. Can open it in notepad. Depending on how you installed SP3, it could be a few places. Honestly, use windows search, and look for files modified around the time you ran the setup. Should pop easily enough.

You are running the "wrong" setup.exe.
You need to follow the previous instructions - run setup.com from the location of the service pack download.

The log file by default goes in to a directory called ExchangeSetupLogs on the root of the C drive.

Simon.

Simon - there is nothing new in ExchangeSetupLogs. Any other ideas for log location?
I'll get the SP download, unpack, and re-run setup from there later today.
Regards,
   Ferrell

Simon & Cliff -
  Extracting the SP3 XPU and using the setup.exe there, same result - below.
Again, no log files I have found.
Any ideas/suggestions appreciated!
Ferrell
------------------------
[PS] C:\temp>setup /prepareschema

Welcome to Microsoft Exchange Server 2007 Unattended Setup

Preparing Exchange Setup


Exchange Server setup encountered an error.
[PS] C:\temp>

I guarantee you there is a log file (or you are not running as administrator so it can't write a log file...or anything else!)

It isn't like I can log into your machine and find the log file for you, but I did give you a suggestion to find it.

You are opening the command prompt as administrator (if you have UAC on)?

Cliff - I understand your certainty that there should be a log file - however, I cannot find anything. See attached. The setup command ran/failed a few seconds before 21:16:30. The attached list has all files and directories last updated from 21:14 through about 21:19. I searched all the hard drives attached to the system. If you can identify anything that *might* be the log file, let me know and I'll examine it.

Yes, I'm running under the administrator account, launched, just for good measure, using the "run as administrator" option.

I very much appreciate your help - this is the second or third time I've tilted at this problem - have never been able to figure it out and the need has become more urgent.
Ferrell
newlist.txt

Ok - found/solved problem. Not completely clear but - figured it out. Entering here to help others since I've seen this query repeatedly in Google but never with a solution.

Key "guess" - recalled there used to be, many moons ago, a large scratch volume (H:) used for backups, staging media for installations, etc. That went away 3-4 years ago with migration from physical to virtual server and better disk management (so, system now has C: .. G: .. but no H:). "Guessed" that maybe Ex2007 SP3 had been installed from media sitting on that long defunct H:. Couldn't find anything interesting in the registry other than lots of references to paths on H: still in history - but nothing active looking.

Still - used "subst h:\ d:\scratch" to create an H:. Ran "setup /ps" - IT WORKED!!

Nothing was created on, or written to the fake H: during the PS upgrade - but apparently something in Exchange was looking there.

So:
1) immediate problem is solved .. may be what others have been searching for ..
2) anyone have any bright idea where Exchange may be hiding some archaic setup drive used for a patch/upgrade long ago that it wants to find again whenever using setup?

Thanks everyone for playing - would love to award some points now for helping me figure out what knows/wants H: still around!

In fact, looking in the logs in c:\ExhangeSetupLogs, I see lots of references to H:\ as install source going back to Feb 2010 - including for SP3 ..

ExchangeSetup.log: [10/6/2012 9:50:27 PM] [0] Setup will use the path 'H:\EX2K7SP3' for installing Exchange.

So - clearly - that's in the history and was the issue. Without having an H:, setup bails without a clue and with no logs. Would love to know where it's hiding this H: history ...

Ok .. after massive search & replace in regedit for h:\ex2k7sp3, setup /ps now works properly without a fake H: drive available. Problem solved. Someone can close this thread - but suggest retaining comments/solution for others.