Become a Columnist Microsoft Exchange Site Microsoft Support SiteMSDN Exchange Site

   

Subscribe to OutlookExchange
Anderson Patricio
Ann Mc Donough
Bob Spurzem
Brian Veal
Catherine Creary
Cherry Beado
Colin Janssen
Collins Timothy Mutesaria
Drew Nicholson
Fred Volking
Glen Scales
Goran Husman
Guy Thomas
Henrik Walther
Jason Sherry
Jayme Bowers
John Young
Joyce Tang
Justin Braun
Konstantin Zheludev
Kristina Waters
Kuang Zhang
Mahmoud Magdy
Martin Tuip
Michael Dong
Michele Deo
Mitch Tulloch
Nicolas Blank
Pavel Nagaev
Ragnar Harper
Ricardo Silva
Richard Wakeman
Russ Iuliano
Santhosh Hanumanthappa
Steve Bryant
Steve Craig
Todd Walker
Tracey J. Rosenblath
 
  Exchange Server Setup.log

Exchange Server Setup.log

This article applies to : Exchange 2000

Originally Published : 9th February 2003

Last Updated :


Exchange 2000 installations are by no means easier to troubleshoot in Exchange 2000 than they were in Exchange 5.5. We have many more dependencies to take into account, such as Active Directory (AD) and Internet Information Services (IIS).

A good source of information, is the 'Exchange Server Setup Progress.log'. If error messages give you no clue as to the problem, this should be your next port of call. As with most error logging, there is a lot of meaningless messages in the logs, however in a lot of cases the Exchange Server Setup Progress.log can give you the information you require to troubleshoot a failed installation.

The log file is created in your root partition (C Drive), and is concatenated. This basically means, all new information is appended to the end of the file. If you do a re-install, and/or add a component, it is logged in here. Therefore when troubleshooting, you should start at the end of the file.

On an new installation, you should see the following type of information :-

[14:32:34] Setup configuration information:

[14:32:34] This is a(n) Enterprise version of Microsoft Exchange 2000

[14:32:34] This is an evaluation copy of Microsoft Exchange 2000; it expires in 120 days

[14:32:34]    InstallSourceDir = Uninitialized

[14:32:34]      InstallDestDir = C:\Program Files\Exchsrvr

[14:32:34]          InetSrvDir = C:\WINNT\System32\inetsrv

[14:32:34]         System32Dir = C:\WINNT\System32

[14:32:34]         LocalServer = ADDC02

[14:32:34]      SchemaMasterDC = ADDC01

[14:32:34]                  DC = ADDC02

[14:32:34]              Domain = testlab.adminfaq.com

[14:32:34]            DomainDN = /dc=com/dc=adminfaq/dc=testlab

[14:32:34]       NetBIOSDomain = ADMINFAQ

[14:32:34]             NT5Site = Default-First-Site-Name

[14:32:34]                 Org = AdminFAQ

[14:32:34]           LegacyOrg = AdminFAQ

[14:32:34]          AdminGroup = Perth

[14:32:34]    LegacyAdminGroup = Perth

[14:32:34] AdminGroupContainingRoutingGroup = Perth

[14:32:34]        RoutingGroup = Perth

[14:32:35] 55ServiceAccountLogin = Uninitialized

[14:32:35] PTAdministratorAccount = ADMINFAQ\Administrator

[14:32:35] This is not a clustered machine

Most administrators will be able to understand this information. We can tell from this the domain controller from which the server reads Active Directory, which is usually where a lot of installation problems originate from.

Some of the messages are pretty weird. Have a search through your logs, and you will find an entry which states "We always ask to show this page for this component in this mode - but Cartman should ignore it". I know what your wondering here....."Who the heck is Cartman?".

As with most logging, short names are used for some items. With Exchange 2000 logging, so of the short names you will see are :-

  • 55 = Exchange Server 5.5

  • Osmium = Exchange Server 5.5

  • Oz = Exchange Server 5.5

  • Pt = Exchange 2000

  • Platinum = Exchange 2000

  • PtOz = Mixed Exchange 5.5 and Exchange 2000 site or organization

  • Udog = Exchange 2000 Setup

  • Underdog = Exchange 2000 Setup

  • Cartman = BackOffice Setup

Why Exchange 2000 is referred to as the "Underdog", and BackOffice is referred to as "Cartman" remains a mystery to me, but at least you know your not going crazy! :-)

If you have ever been asked to recover an undocumented server, the Exchange Server Setup.log can be your lifesaver. It's surprising how many companies are unaware of these basic details and don't have them documented. You can use a utility like "NTFS Reader for DOS" from NTFS.com ( www.ntfs.com ) to boot the system using a floppy disk, read the file for the configuration, then proceed to rebuild the system. Obviously a good backup is more preferable.


Back to Home

 

 


Disclaimer: Your use of the information contained in these pages is at your sole risk. All information on these pages is provided "as is", without any warranty, whether express or implied, of its accuracy, completeness, fitness for a particular purpose, title or non-infringement, and none of the third-party products or information mentioned in the work are authored, recommended, supported or guaranteed by Stephen Bryant or Pro Exchange. OutlookExchange.Com, Stephen Bryant and Pro Exchange shall not be liable for any damages you may sustain by using this information, whether direct, indirect, special, incidental or consequential, even if it has been advised of the possibility of such damages.

Copyright Stephen Bryant 2008