GuidesLearn Windows XP Professional: Troubleshooting the Windows XP Professional Setup (Page 3)...

Learn Windows XP Professional: Troubleshooting the Windows XP Professional Setup (Page 3) Page 3

ServerWatch content and product recommendations are editorially independent. We may make money when you click on links to our partners. Learn More.






Additional Logs for Troubleshooting

Error Log (SETUPERR.LOG)The error log shows any errors
that occurred during setup and their severity level. If errors do occur, the log
viewer displays the error log at the end of setup.

(The SETUPERR.LOG can
be found in the Windows directory in a default Windows XP
Professional installation)

The log will be created even if no errors occur. (I
do not have anything available to show you from the error log as mine is empty.
Sorry.)

Setup also creates a number of additional logs during
setup.

Windowscomsetup.log –
Outlines installation for Optional Component Manager and COM+ components. A
subsection of mine is below.

COM+[11:31:52]:
********************************************************************************
COM+[11:31:52]:
Setup started – [DATE:01,07,2002 TIME: 11:31 pm]
COM+[11:31:52]:
********************************************************************************
COM+[11:31:52]:
Start OC_INIT_COMPONENT Component = com
COM+[11:31:52]: INF VERSION (com) =
2001,12,4414,42
COM+[11:31:52]: Instantiating
CMasterNT5Wks
COM+[11:31:52]: Memory usage for setup
process…
COM+[11:31:52]: PeakWorkingSetSize: 26336 Kb, WorkingSetSize:
23308 Kb
COM+[11:31:52]: QuotaPeakPagedPoolUsage: 53 Kb, QuotaPagedPoolUsage:
52 Kb
COM+[11:31:52]: PeakPagefileUsage: 18664 Kb, PagefileUsage: 17796
Kb
COM+[11:31:52]: MTSS: Answer File =
COM+[11:31:52]: Calling
SetupOpenInfFile.
COM+[11:31:52]: Unable to open Answer
File!!
COM+[11:31:52]: DRID-39104 -> Path:
H:WINDOWSJavaTrustlib
COM+[11:31:52]: Installed COM product version =
0.0.0.0
COM+[11:31:52]: SETUP VERSION = 3.0.0.4414
COM+[11:31:52]:
Installation Mode = FRESH
COM+[11:31:52]: Setup Mode =
CUSTOM
COM+[11:31:52]: DRID-39103 -> Path: H:Program FilesCommon
FilesODBCData Sources
COM+[11:31:52]: End OC_INIT_COMPONENT Return Value =
0
COM+[11:31:53]: Start OC_QUERY_STATEComponent = com Subcomponent =
com
COM+[11:31:53]: Subcomponent com state: O-,C-,R-
COM+[11:31:53]: End
OC_QUERY_STATE Return Value = 0
COM+[11:39:18]: Start OC_QUERY_STATEComponent
= com Subcomponent = com
COM+[11:39:18]: End OC_QUERY_STATE Return Value =
1
COM+[11:39:18]: Start OC_CALC_DISK_SPACE Component = com Subcomponent =
com
COM+[11:39:18]: End OC_CALC_DISK_SPACE Return Value = 0
COM+[1:0:25]:
Start OC_QUEUE_FILE_OPS Component = com Subcomponent =
COM+[1:0:25]: End
OC_QUEUE_FILE_OPS Return Value = 0
COM+[1:0:25]: Start OC_QUEUE_FILE_OPS
Component = com Subcomponent = com
COM+[1:0:25]: Subcomponent com state:
O-,C+,R-
COM+[1:0:25]: Reading persistent registry values
COM+[1:0:25]:
Finished reading persistent registry values, retval = 0x0
COM+[1:0:25]:
Queuing file ops for component com, Section Name: com_install
COM+[1:0:25]:
The following files will be copied:
COM+[1:0:25]:
H:WINDOWSSystem32clbcatq.dll
COM+[1:0:25]:
H:WINDOWSSystem32comsnap.dll
COM+[1:0:25]:
H:WINDOWSSystem32comuid.dll
COM+[1:0:25]:
H:WINDOWSSystem32comsvcs.dll
COM+[1:0:25]:
H:WINDOWSSystem32catsrv.dll
COM+[1:0:25]:
H:WINDOWSSystem32catsrvut.dll

COM+[1:0:25]: The following files will be
deleted:
COM+[1:0:25]: Nuke registry key:
HKEY_LOCAL_MACHINESOFTWAREMicrosoftCOM3Setup.
COM+[1:0:25]: DRID-39105
-> Path: H:Documents and SettingsAll UsersStart
MenuPrograms
COM+[1:0:25]: End OC_QUEUE_FILE_OPS Return Value =
0
COM+[1:0:26]: Start OC_QUERY_STEP_COUNT Component = com Subcomponent =

COM+[1:0:26]: End OC_QUERY_STEP_COUNT Return Value = 0
COM+[1:0:26]:
Start OC_QUERY_STEP_COUNT Component = com Subcomponent = com
COM+[1:0:26]:
End OC_QUERY_STEP_COUNT Return Value = 120
COM+[1:0:26]: Start
OC_ABOUT_TO_COMMIT_QUEUE Component = com Subcomponent =
COM+[1:0:26]: No
PendingFileRenameOperations
COM+[1:0:26]: End OC_ABOUT_TO_COMMIT_QUEUE Return
Value = 0
COM+[1:0:27]: Start OC_ABOUT_TO_COMMIT_QUEUE Component = com
Subcomponent = com
COM+[1:0:27]: Subcomponent com state:
O-,C+,R-
COM+[1:0:27]: Stopping service ComSysApp…
COM+[1:0:27]:
Stopping service ComLB…
COM+[1:0:27]: Stopping service
SENS…
COM+[1:0:27]: Stopping service EventSystem…
COM+[1:0:27]:
Stopping service SENS…
COM+[1:0:27]: Stopping service
fax…
COM+[1:0:27]: Stopping service w3svc…
COM+[1:0:27]: Stopping
service smtpsvc…
COM+[1:0:27]: Stopping service
iisadmin…
COM+[1:0:27]: End OC_ABOUT_TO_COMMIT_QUEUE Return Value =
0
COM+[1:1:4]: Start OC_COMPLETE_INSTALLATION Component = com Subcomponent =

COM+[1:1:4]: No PendingFileRenameOperations
COM+[1:1:4]: End
OC_COMPLETE_INSTALLATION Return Value = 0
COM+[1:1:16]: Start
OC_COMPLETE_INSTALLATION Component = com Subcomponent = com

Windowssetupapi.log –
Receives an entry each time a line from an .inf file is implemented. If an
error occurs, this log describes the failure. A subsection of mine is below.
(The full size was 245KB)

[SetupAPI Log]
OS Version = 5.1.2600
Platform
ID = 2 (NT)
Service Pack = 0.0
Suite = 0x0000
Product Type =
1
Architecture = x86
[2002/01/07 23:31:25 284.10]
#-199 Executing
“H:WINDOWSsystem32setup.exe” with command line: setup -newsetup
#I140
Installing device class: “1394” {6BDD1FC1-810F-11D0-BEC7-08002BE2092F}.
#I141
Class install completed with no errors.
[2002/01/07 23:31:26 284.12]
#-199
Executing “H:WINDOWSsystem32setup.exe” with command line: setup
-newsetup
#I140 Installing device class: “1394Debug”
{66f250d6-7801-4a64-b139-eea80a450b24}.
#I141 Class install completed with no
errors.
[2002/01/07 23:31:26 284.13]
#-199 Executing
“H:WINDOWSsystem32setup.exe” with command line: setup -newsetup
#I140
Installing device class: “61883”
{7EBEFBC0-3200-11d2-B4C2-00A0C9697D07}.
#I141 Class install completed with no
errors.
[2002/01/07 23:31:26 284.14]
#-199 Executing
“H:WINDOWSsystem32setup.exe” with command line: setup -newsetup
#I140
Installing device class: “Avc” {C06FF265-AE09-48f0-812C-16753D7CBA83}.
#I141
Class install completed with no errors.
[2002/01/07 23:31:26 284.15]
#-199
Executing “H:WINDOWSsystem32setup.exe” with command line: setup
-newsetup
#I140 Installing device class: “Battery”
{72631e54-78a4-11d0-bcf7-00aa00b7b32a}.
#I141 Class install completed with no
errors.
[2002/01/07 23:31:26 284.17]
#-199 Executing
“H:WINDOWSsystem32setup.exe” with command line: setup -newsetup
#I140
Installing device class: “CDROM”
{4D36E965-E325-11CE-BFC1-08002BE10318}.
#I141 Class install completed with no
errors.
[2002/01/07 23:31:26 284.19]
#-199 Executing
“H:WINDOWSsystem32setup.exe” with command line: setup -newsetup
#I140
Installing device class: “Processor”
{50127DC3-0F36-415e-A6CC-4CB3BE910B65}.
#I141 Class install completed with no
errors.
[2002/01/07 23:31:26 284.20]

#-199 Executing “H:WINDOWSsystem32setup.exe” with
command line: setup -newsetup
#I022 Found “PCIVEN_1274&DEV_5880” in
H:WINDOWSinfwdma_ens.inf; Device: “Creative AudioPCI (ES1371,ES1373) (WDM)”;
Driver: “Creative AudioPCI (ES1371,ES1373) (WDM)”; Provider: “Microsoft”; Mfg:
“Creative Technology Ltd.”; Section name: “ES1371”.
#I023 Actual install
section: [ES1371.NTx86]. Rank: 0x00002001. Effective driver date:
07/01/2001.
#-166 Device install function: DIF_SELECTBESTCOMPATDRV.
#I063
Selected driver installs from section [ES1371] in
“h:windowsinfwdma_ens.inf”.
#I320 Class GUID of device remains:
{4D36E96C-E325-11CE-BFC1-08002BE10318}.
#I060 Set selected driver.
#I058
Selected best compatible driver.
#-124 Doing copy-only install of
“PCIVEN_1274&DEV_5880&SUBSYS_A0001458&REV_024&21E63D15&0&28F0”.
#-166
Device install function: DIF_REGISTER_COINSTALLERS.
#I056 Coinstallers
registered.
#-166 Device install function: DIF_INSTALLINTERFACES.
#-011
Installing section [ES1371.NTx86.Interfaces] from
“h:windowsinfwdma_ens.inf”.
#I054 Interfaces installed.
#-166 Device
install function: DIF_INSTALLDEVICE.
#I123 Doing full install of
“PCIVEN_1274&DEV_5880&SUBSYS_A0001458&REV_024&21E63D15&0&28F0”.
#I121
Device install of
“PCIVEN_1274&DEV_5880&SUBSYS_A0001458&REV_024&21E63D15&0&28F0”
finished successfully.
[2002/01/07 23:33:19 284.1045 Driver Install]
#-019
Searching for hardware ID(s):
pciven_10b7&dev_9050&subsys_00000000&rev_00,pciven_10b7&dev_9050&subsys_00000000,
pciven_10b7&dev_9050&rev_00,pciven_10b7&dev_9050,pciven_10b7&dev_9050&cc_020000,pciven_10b7&dev_9050&cc_0200
#-018
Searching for compatible ID(s):
pciven_10b7&cc_020000,pciven_10b7&cc_0200,pciven_10b7,pcicc_020000,pcicc_0200
#-199
Executing “H:WINDOWSsystem32setup.exe” with command line: setup
-newsetup
#I022 Found “PCIVEN_10b7&DEV_9050” in
H:WINDOWSinfnetel90a.inf; Device: “3Com 3C905TX-based Ethernet Adapter
(Generic)”;
Driver: “3Com 3C905TX-based Ethernet Adapter (Generic)”; Provider:
“Microsoft”; Mfg: “3Com”; Section name: “EL90X.905TX.NDI”.
#I023 Actual
install section: [EL90X.905TX.NDI]. Rank: 0x00000003. Effective driver date:
07/01/2001.
#-166 Device install function: DIF_SELECTBESTCOMPATDRV.
#I063
Selected driver installs from section [EL90X.905TX.NDI] in
“h:windowsinfnetel90a.inf”.
#I320 Class GUID of device remains:
{4D36E972-E325-11CE-BFC1-08002BE10318}.
#I060 Set selected driver.
#I058
Selected best compatible driver.
#-124 Doing copy-only install of
“PCIVEN_10B7&DEV_9050&SUBSYS_00000000&REV_004&21E63D15&0&20F0”.

Get the Free Newsletter!

Subscribe to Daily Tech Insider for top news, trends & analysis

Latest Posts

Related Stories