?
Solved

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

Posted on 2013-12-16
15
Medium Priority
?
1,235 Views
Last Modified: 2013-12-23
MS Exchange 2007 part of SBS 2008 - fully/current patched
Original problem is trying to add a Receive Connector .. fails .. see MS KB 2457729
As recommended by MS, ran:
  [PS] C:\Windows\system32>Setup.com /prepareschema
  Welcome to Microsoft Exchange Server 2007 Unattended Setup
  Preparing Exchange Setup
  Exchange Server setup encountered an error.
Can't find any solution/KB/workaround for this error from /prepareschema ..
Help!! Thanks!!
0
Comment
Question by:fmoultrie
  • 8
  • 4
13 Comments
 
LVL 60

Expert Comment

by:Cliff Galiher
ID: 39721739
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?
0
 
LVL 60

Expert Comment

by:Cliff Galiher
ID: 39721747
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
0
 

Author Comment

by:fmoultrie
ID: 39721770
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!
0
NFR key for Veeam Backup for Microsoft Office 365

Veeam is happy to provide a free NFR license (for 1 year, up to 10 users). This license allows for the non‑production use of Veeam Backup for Microsoft Office 365 in your home lab without any feature limitations.

 
LVL 60

Expert Comment

by:Cliff Galiher
ID: 39721804
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.
0
 
LVL 63

Expert Comment

by:Simon Butler (Sembee)
ID: 39721836
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.
0
 

Author Comment

by:fmoultrie
ID: 39722212
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
0
 

Author Comment

by:fmoultrie
ID: 39722704
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>
0
 
LVL 60

Expert Comment

by:Cliff Galiher
ID: 39722710
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)?
0
 

Author Comment

by:fmoultrie
ID: 39723064
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
0
 

Author Comment

by:fmoultrie
ID: 39725459
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!
0
 

Author Comment

by:fmoultrie
ID: 39725472
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 ...
0
 

Accepted Solution

by:
fmoultrie earned 0 total points
ID: 39725697
Ok -- maybe final post one this .. looks like in registry as:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\461C2B4266EDEF444B864AD6D9E5B613\InstallProperties\InstallSource with the value on my system of H:\EX2K7SP3\.

If the path doesn't exist, no problem, it runs. If the drive doesn't exist (e.g., h: not a valid drive any more), setup exits with cryptic error and no diagnostics. Boo hiss!
0
 

Author Comment

by:fmoultrie
ID: 39726678
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.
0

Featured Post

Concerto Cloud for Software Providers & ISVs

Can Concerto Cloud Services help you focus on evolving your application offerings, while delivering the best cloud experience to your customers? From DevOps to revenue models and customer support, the answer is yes!

Learn how Concerto can help you.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Want to know how to use Exchange Server Eseutil command? Go through this article as it gives you the know-how.
This article will help to fix the below errors for MS Exchange Server 2016 I. Certificate error "name on the security certificate is invalid or does not match the name of the site" II. Out of Office not working III. Make Internal URLs and Externa…
The basic steps you have just learned will be implemented in this video. The basic steps are shown to configure an Exchange DAG in a live working Exchange Server Environment and manage the same (Exchange Server 2010 Software is used in a Windows Ser…
With the advent of Windows 10, Microsoft is pushing a Get Windows 10 icon into the notification area (system tray) of qualifying computers. There are many reasons for wanting to remove this icon. This two-part Experts Exchange video Micro Tutorial s…
Suggested Courses
Course of the Month16 days, 16 hours left to enroll

864 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question