Bobby
Guest
|
 Posted:
Wed Nov 09, 2005 1:50 am Post subject:
Services.exe crashes after SP1 Installation (Win Server 2003 |
|
|
Last friday 11/08/05 i updated the domain controller running windows server
2003 to SP1. Everything seemed to go fine, the event viewer states:
Installation Successful: Windows successfully installed the following
update: Windows Server 2003 Service Pack 1
I then restarted the server and while booting up services.exe crashed with
the following event viewer entry:
Event Type: Information
Event Source: Application Popup
Event Category: None
Event ID: 26
Computer: PRIMARY
Description:
Application popup: services.exe - Application Error : The instruction at
"0x00910000" referenced memory at "0x00910000". The memory could not be
"written".
Click on OK to terminate the program
Click on CANCEL to debug the program
Obviously i couldn't even log in to roll back the Service Pack (i backed up
settings so that i would be able to uninstall SP1). Safe mode would crash as
well, as would any other boot up option. So i had no option but to do install
windows server 2003 with the repair option. This worked well enough. I'm
currently doing some updates but i don't know if i should retry to install
SP1 (this is a production server).
I checked svcpack.log and it contains the following at the time of
installation of SP1:
2.375: 2005/11/04 17:14:04.953 (local)
2.375:
C:\WINDOWS\SoftwareDistribution\Download\f1915c127b68f23f5487746099ecbec0\update\update.exe (version 5.6.1013.0)
2.375: Failed To Enable SE_SHUTDOWN_PRIVILEGE
2.375: Service Pack started with following command line: -z -er
/ParentInfo:98669aeaf3b7304992a292c929241486
2.562: Return Value From OnACPower = 1
2.562: OnACPower returned value( 0x1 ) which is Equal To 0x1
2.562: Condition succeeded for section OnACPower.Section in Line 1 of
PreRequisite
2.593: InternalFileName of C:\WINDOWS\system32\HAL.DLL is Not Equal To
halcmpx.dll
2.593: Condition succeeded for section CustomHalUnisysBlock.Section in Line
2 of PreRequisite
2.593: InternalFileName of C:\WINDOWS\system32\HAL.DLL is Not Equal To
Unisys CMP Server ACPI HAL
2.609: First Condition in CustomHalUniSysBlock.Section2 Succeeded
2.609: Condition succeeded for section CustomHalUniSysBlock.Section2 in Line
3 of PreRequisite
2.609: InternalFileName of C:\WINDOWS\system32\HAL.DLL is Not Equal To
HALSRAAC.DLL
2.609: Condition succeeded for section CustomHalStratusBlock.Section in Line
4 of PreRequisite
2.609: InternalFileName of C:\WINDOWS\system32\HAL.DLL is Not Equal To
halce52.dll
2.609: Condition succeeded for section CustomHalMarathonBlock.Section in
Line 5 of PreRequisite
2.609: Service SpUpdSvc Not Registered in SCM 0x424
2.609: Condition succeeded for section SpUpdSvcBlock.Section in Line 6 of
PreRequisite
2.609: Start is Present
2.609: SYSTEM\CurrentControlSet\Services\MSDTC\Start is Not Equal To
Specified Value
2.609: Second Condition in MSDTC.Not.Disabled Succeeded
2.609: Condition succeeded for section MDSTC.Check.Disabled in Line 7 of
PreRequisite
22.140: DoInstallation: CleanPFR failed: 0x2
22.156: SetProductTypes: InfProductBuildType=BuildType.IS
22.172: SetAltOsLoaderPath: No section uses DirId 65701; done.
22.297: DoInstallation:SetupOpenInfFile for OldUninstallInf file
C:\WINDOWS\$NtServicePackUninstall$\spuninst\spuninst.inf not found: 0x3
22.297: CreateUninstall = 1,Directory = C:\WINDOWS\$NtServicePackUninstall$
82.890: ref tag c:\windows\driver cache\i386\sp1.cab does not exist
82.890: ref tag c:\windows\servicepackfiles\i386\sp1.cab does not exist
82.968: Starting AnalyzeComponents
82.984: AnalyzePhaseZero used 0 ticks
82.984: SetupFindFirstLine in LoadExclusionList Failed with error: 0xe0000102
85.281:
C:\WINDOWS\system32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\oem0.CAT
trusts inf c:\windows\inf\oem0.inf of device ACPI\PNP0103\0
86.828:
C:\WINDOWS\system32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\oem9.CAT
trusts inf c:\windows\inf\oem9.inf of device
HID\VID_051D&PID_0002\6&16DD9CAC&0&0000
90.218:
C:\WINDOWS\system32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\oem1.CAT
trusts inf c:\windows\inf\oem1.inf of device
PCI\VEN_8086&DEV_0326&SUBSYS_00000000&REV_09\4&3007CA40&0&0110
90.343:
C:\WINDOWS\system32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\oem1.CAT
trusts inf c:\windows\inf\oem1.inf of device
PCI\VEN_8086&DEV_0327&SUBSYS_00000000&REV_09\4&3007CA40&0&0310
90.531:
C:\WINDOWS\system32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\oem1.CAT
trusts inf c:\windows\inf\oem1.inf of device
PCI\VEN_8086&DEV_0329&SUBSYS_00000000&REV_09\4&3007CA40&0&0010
90.687:
C:\WINDOWS\system32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\oem1.CAT
trusts inf c:\windows\inf\oem1.inf of device
PCI\VEN_8086&DEV_032A&SUBSYS_00000000&REV_09\4&3007CA40&0&0210
91.453:
C:\WINDOWS\system32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\oem0.CAT
trusts inf c:\windows\inf\oem0.inf of device
PCI\VEN_8086&DEV_244E&SUBSYS_00000000&REV_C2\3&13C0B0C5&0&F0
91.718:
C:\WINDOWS\system32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\oem4.CAT
trusts inf c:\windows\inf\oem4.inf of device
PCI\VEN_8086&DEV_24D0&SUBSYS_00000000&REV_02\3&13C0B0C5&0&F8
92.203:
C:\WINDOWS\system32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\oem3.CAT
trusts inf c:\windows\inf\oem3.inf of device
PCI\VEN_8086&DEV_24D1&SUBSYS_01831028&REV_02\3&13C0B0C5&0&FA
92.609:
C:\WINDOWS\system32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\oem2.CAT
trusts inf c:\windows\inf\oem2.inf of device
PCI\VEN_8086&DEV_24D2&SUBSYS_01831028&REV_02\3&13C0B0C5&0&E8
92.750:
C:\WINDOWS\system32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\oem2.CAT
trusts inf c:\windows\inf\oem2.inf of device
PCI\VEN_8086&DEV_24D4&SUBSYS_01831028&REV_02\3&13C0B0C5&0&E9
92.890:
C:\WINDOWS\system32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\oem2.CAT
trusts inf c:\windows\inf\oem2.inf of device
PCI\VEN_8086&DEV_24D7&SUBSYS_01831028&REV_02\3&13C0B0C5&0&EA
93.156:
C:\WINDOWS\system32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\oem3.CAT
trusts inf c:\windows\inf\oem3.inf of device
PCI\VEN_8086&DEV_24DB&SUBSYS_01831028&REV_02\3&13C0B0C5&0&F9
93.484:
C:\WINDOWS\system32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\oem2.CAT
trusts inf c:\windows\inf\oem2.inf of device
PCI\VEN_8086&DEV_24DD&SUBSYS_01831028&REV_02\3&13C0B0C5&0&EF
93.703:
C:\WINDOWS\system32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\oem1.CAT
trusts inf c:\windows\inf\oem1.inf of device
PCI\VEN_8086&DEV_3590&SUBSYS_00000000&REV_09\3&13C0B0C5&0&00
93.843:
C:\WINDOWS\system32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\oem1.CAT
trusts inf c:\windows\inf\oem1.inf of device
PCI\VEN_8086&DEV_3595&SUBSYS_00000000&REV_09\3&13C0B0C5&0&10
94.000:
C:\WINDOWS\system32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\oem1.CAT
trusts inf c:\windows\inf\oem1.inf of device
PCI\VEN_8086&DEV_3597&SUBSYS_00000000&REV_09\3&13C0B0C5&0&20
94.140:
C:\WINDOWS\system32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\oem1.CAT
trusts inf c:\windows\inf\oem1.inf of device
PCI\VEN_8086&DEV_3599&SUBSYS_00000000&REV_09\3&13C0B0C5&0&30
96.547: OEM file scan used 13563 ticks
109.922: c:\windows\system32\drivers\symmpi.sys is in the list of oem
drivers...skipping copy!
157.187: AnalyzePhaseOne: used 74203 ticks
157.187: AnalyzeComponents: Hotpatch analysis disabled; skipping.
157.187: AnalyzeComponents: Hotpatching is disabled.
157.187: FindFirstFile c:\windows\$hf_mig$\*.*
157.937: Service Pack 1 Setup encountered an error: The update.ver file is
not correct.
158.109: Service Pack 1 Setup encountered an error: The update.ver file is
not correct.
158.109: Service Pack 1 Setup encountered an error: The update.ver file is
not correct.
158.109: Service Pack 1 Setup encountered an error: The update.ver file is
not correct.
158.109: Service Pack 1 Setup encountered an error: The update.ver file is
not correct.
158.109: Service Pack 1 Setup encountered an error: The update.ver file is
not correct.
158.109: Service Pack 1 Setup encountered an error: The update.ver file is
not correct.
158.109: Service Pack 1 Setup encountered an error: The update.ver file is
not correct.
158.109: Service Pack 1 Setup encountered an error: The update.ver file is
not correct.
158.109: Service Pack 1 Setup encountered an error: The update.ver file is
not correct.
158.109: Service Pack 1 Setup encountered an error: The update.ver file is
not correct.
158.125: Service Pack 1 Setup encountered an error: The update.ver file is
not correct.
158.125: Service Pack 1 Setup encountered an error: The update.ver file is
not correct.
158.125: Service Pack 1 Setup encountered an error: The update.ver file is
not correct.
158.125: Service Pack 1 Setup encountered an error: The update.ver file is
not correct.
158.125: Service Pack 1 Setup encountered an error: The update.ver file is
not correct.
158.125: Service Pack 1 Setup encountered an error: The update.ver file is
not correct.
158.125: Service Pack 1 Setup encountered an error: The update.ver file is
not correct.
158.125: Service Pack 1 Setup encountered an error: The update.ver file is
not correct.
158.172: Failed to open c:\windows\$hf_mig$\KB890046\update\updatebr.inf
158.187: Failed to open c:\windows\$hf_mig$\KB893756\update\updatebr.inf
158.187: Failed to open c:\windows\$hf_mig$\KB896358\update\updatebr.inf
158.187: Failed to open c:\windows\$hf_mig$\KB896422\update\updatebr.inf
158.187: Failed to open c:\windows\$hf_mig$\KB896423\update\updatebr.inf
158.187: Failed to open c:\windows\$hf_mig$\KB896428\update\updatebr.inf
158.187: Failed to open c:\windows\$hf_mig$\KB896688\update\updatebr.inf
158.187: Failed to open c:\windows\$hf_mig$\KB897715\update\updatebr.inf
158.187: Failed to open c:\windows\$hf_mig$\KB899587\update\updatebr.inf
158.187: Failed to open c:\windows\$hf_mig$\KB899588\update\updatebr.inf
158.187: Failed to open c:\windows\$hf_mig$\KB899589\update\updatebr.inf
158.187: Failed to open c:\windows\$hf_mig$\KB899591\update\updatebr.inf
158.187: Failed to open c:\windows\$hf_mig$\KB900725\update\updatebr.inf
158.187: Failed to open c:\windows\$hf_mig$\KB901017\update\updatebr.inf
158.187: Failed to open c:\windows\$hf_mig$\KB901214\update\updatebr.inf
158.187: Failed to open c:\windows\$hf_mig$\KB902400\update\updatebr.inf
158.187: Failed to open c:\windows\$hf_mig$\KB904706\update\updatebr.inf
158.187: Failed to open c:\windows\$hf_mig$\KB905414\update\updatebr.inf
158.187: Failed to open c:\windows\$hf_mig$\KB905495\update\updatebr.inf
158.187: Analyzing Devices...
I have APC Personal installed, and the server is running Exchange Server,
ISA and is a Domain Controller. For antivirus it runs Panda AdminSecure.
Any thoughts on this, i couldn't find a similar problem online.
Thanks for your help
Bobby |
|
Bobby
Guest
|
| Posted:
Sat Nov 12, 2005 9:50 am Post subject:
RE: Services.exe crashes after SP1 Installation (Win Server |
|
|
For those of you searching around who may have a similar error, it turned out
that a service from the Antivirus Package (from Panda), more specifically
"ExchangeSecure", was actually causing the exception on services.exe (the
exception is thrown when starting this service). By disabling it the OS
booted as it should. If you don't have Panda installed i recommend disabling
any non-microsoft services (these are the ones most likely to not work with a
microsoft product) and seeing if it helps. By doing this successively you can
determine the faulty service. Good luck.
Bobby
"Bobby" wrote:
| Quote: | Last friday 11/08/05 i updated the domain controller running windows server
2003 to SP1. Everything seemed to go fine, the event viewer states:
Installation Successful: Windows successfully installed the following
update: Windows Server 2003 Service Pack 1
I then restarted the server and while booting up services.exe crashed with
the following event viewer entry:
Event Type: Information
Event Source: Application Popup
Event Category: None
Event ID: 26
Computer: PRIMARY
Description:
Application popup: services.exe - Application Error : The instruction at
"0x00910000" referenced memory at "0x00910000". The memory could not be
"written".
Click on OK to terminate the program
Click on CANCEL to debug the program
Obviously i couldn't even log in to roll back the Service Pack (i backed up
settings so that i would be able to uninstall SP1). Safe mode would crash as
well, as would any other boot up option. So i had no option but to do install
windows server 2003 with the repair option. This worked well enough. I'm
currently doing some updates but i don't know if i should retry to install
SP1 (this is a production server).
I checked svcpack.log and it contains the following at the time of
installation of SP1:
2.375: 2005/11/04 17:14:04.953 (local)
2.375:
C:\WINDOWS\SoftwareDistribution\Download\f1915c127b68f23f5487746099ecbec0\update\update.exe (version 5.6.1013.0)
2.375: Failed To Enable SE_SHUTDOWN_PRIVILEGE
2.375: Service Pack started with following command line: -z -er
/ParentInfo:98669aeaf3b7304992a292c929241486
2.562: Return Value From OnACPower = 1
2.562: OnACPower returned value( 0x1 ) which is Equal To 0x1
2.562: Condition succeeded for section OnACPower.Section in Line 1 of
PreRequisite
2.593: InternalFileName of C:\WINDOWS\system32\HAL.DLL is Not Equal To
halcmpx.dll
2.593: Condition succeeded for section CustomHalUnisysBlock.Section in Line
2 of PreRequisite
2.593: InternalFileName of C:\WINDOWS\system32\HAL.DLL is Not Equal To
Unisys CMP Server ACPI HAL
2.609: First Condition in CustomHalUniSysBlock.Section2 Succeeded
2.609: Condition succeeded for section CustomHalUniSysBlock.Section2 in Line
3 of PreRequisite
2.609: InternalFileName of C:\WINDOWS\system32\HAL.DLL is Not Equal To
HALSRAAC.DLL
2.609: Condition succeeded for section CustomHalStratusBlock.Section in Line
4 of PreRequisite
2.609: InternalFileName of C:\WINDOWS\system32\HAL.DLL is Not Equal To
halce52.dll
2.609: Condition succeeded for section CustomHalMarathonBlock.Section in
Line 5 of PreRequisite
2.609: Service SpUpdSvc Not Registered in SCM 0x424
2.609: Condition succeeded for section SpUpdSvcBlock.Section in Line 6 of
PreRequisite
2.609: Start is Present
2.609: SYSTEM\CurrentControlSet\Services\MSDTC\Start is Not Equal To
Specified Value
2.609: Second Condition in MSDTC.Not.Disabled Succeeded
2.609: Condition succeeded for section MDSTC.Check.Disabled in Line 7 of
PreRequisite
22.140: DoInstallation: CleanPFR failed: 0x2
22.156: SetProductTypes: InfProductBuildType=BuildType.IS
22.172: SetAltOsLoaderPath: No section uses DirId 65701; done.
22.297: DoInstallation:SetupOpenInfFile for OldUninstallInf file
C:\WINDOWS\$NtServicePackUninstall$\spuninst\spuninst.inf not found: 0x3
22.297: CreateUninstall = 1,Directory = C:\WINDOWS\$NtServicePackUninstall$
82.890: ref tag c:\windows\driver cache\i386\sp1.cab does not exist
82.890: ref tag c:\windows\servicepackfiles\i386\sp1.cab does not exist
82.968: Starting AnalyzeComponents
82.984: AnalyzePhaseZero used 0 ticks
82.984: SetupFindFirstLine in LoadExclusionList Failed with error: 0xe0000102
85.281:
C:\WINDOWS\system32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\oem0.CAT
trusts inf c:\windows\inf\oem0.inf of device ACPI\PNP0103\0
86.828:
C:\WINDOWS\system32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\oem9.CAT
trusts inf c:\windows\inf\oem9.inf of device
HID\VID_051D&PID_0002\6&16DD9CAC&0&0000
90.218:
C:\WINDOWS\system32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\oem1.CAT
trusts inf c:\windows\inf\oem1.inf of device
PCI\VEN_8086&DEV_0326&SUBSYS_00000000&REV_09\4&3007CA40&0&0110
90.343:
C:\WINDOWS\system32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\oem1.CAT
trusts inf c:\windows\inf\oem1.inf of device
PCI\VEN_8086&DEV_0327&SUBSYS_00000000&REV_09\4&3007CA40&0&0310
90.531:
C:\WINDOWS\system32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\oem1.CAT
trusts inf c:\windows\inf\oem1.inf of device
PCI\VEN_8086&DEV_0329&SUBSYS_00000000&REV_09\4&3007CA40&0&0010
90.687:
C:\WINDOWS\system32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\oem1.CAT
trusts inf c:\windows\inf\oem1.inf of device
PCI\VEN_8086&DEV_032A&SUBSYS_00000000&REV_09\4&3007CA40&0&0210
91.453:
C:\WINDOWS\system32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\oem0.CAT
trusts inf c:\windows\inf\oem0.inf of device
PCI\VEN_8086&DEV_244E&SUBSYS_00000000&REV_C2\3&13C0B0C5&0&F0
91.718:
C:\WINDOWS\system32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\oem4.CAT
trusts inf c:\windows\inf\oem4.inf of device
PCI\VEN_8086&DEV_24D0&SUBSYS_00000000&REV_02\3&13C0B0C5&0&F8
92.203:
C:\WINDOWS\system32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\oem3.CAT
trusts inf c:\windows\inf\oem3.inf of device
PCI\VEN_8086&DEV_24D1&SUBSYS_01831028&REV_02\3&13C0B0C5&0&FA
92.609:
C:\WINDOWS\system32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\oem2.CAT
trusts inf c:\windows\inf\oem2.inf of device
PCI\VEN_8086&DEV_24D2&SUBSYS_01831028&REV_02\3&13C0B0C5&0&E8
92.750:
C:\WINDOWS\system32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\oem2.CAT
trusts inf c:\windows\inf\oem2.inf of device
PCI\VEN_8086&DEV_24D4&SUBSYS_01831028&REV_02\3&13C0B0C5&0&E9
92.890:
C:\WINDOWS\system32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\oem2.CAT
trusts inf c:\windows\inf\oem2.inf of device
PCI\VEN_8086&DEV_24D7&SUBSYS_01831028&REV_02\3&13C0B0C5&0&EA
93.156:
C:\WINDOWS\system32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\oem3.CAT
trusts inf c:\windows\inf\oem3.inf of device
PCI\VEN_8086&DEV_24DB&SUBSYS_01831028&REV_02\3&13C0B0C5&0&F9
93.484:
C:\WINDOWS\system32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\oem2.CAT
trusts inf c:\windows\inf\oem2.inf of device
PCI\VEN_8086&DEV_24DD&SUBSYS_01831028&REV_02\3&13C0B0C5&0&EF
93.703:
C:\WINDOWS\system32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\oem1.CAT
trusts inf c:\windows\inf\oem1.inf of device
PCI\VEN_8086&DEV_3590&SUBSYS_00000000&REV_09\3&13C0B0C5&0&00
93.843:
C:\WINDOWS\system32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\oem1.CAT
trusts inf c:\windows\inf\oem1.inf of device
PCI\VEN_8086&DEV_3595&SUBSYS_00000000&REV_09\3&13C0B0C5&0&10
94.000:
C:\WINDOWS\system32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\oem1.CAT
trusts inf c:\windows\inf\oem1.inf of device
PCI\VEN_8086&DEV_3597&SUBSYS_00000000&REV_09\3&13C0B0C5&0&20
94.140:
C:\WINDOWS\system32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\oem1.CAT
trusts inf c:\windows\inf\oem1.inf of device
PCI\VEN_8086&DEV_3599&SUBSYS_00000000&REV_09\3&13C0B0C5&0&30
96.547: OEM file scan used 13563 ticks
109.922: c:\windows\system32\drivers\symmpi.sys is in the list of oem
drivers...skipping copy!
157.187: AnalyzePhaseOne: used 74203 ticks
157.187: AnalyzeComponents: Hotpatch analysis disabled; skipping.
157.187: AnalyzeComponents: Hotpatching is disabled.
157.187: FindFirstFile c:\windows\$hf_mig$\*.*
157.937: Service Pack 1 Setup encountered an error: The update.ver file is
not correct.
158.109: Service Pack 1 Setup encountered an error: The update.ver file is
not correct.
158.109: Service Pack 1 Setup encountered an error: The update.ver file is
not correct.
158.109: Service Pack 1 Setup encountered an error: The update.ver file is
not correct.
158.109: Service Pack 1 Setup encountered an error: The update.ver file is
not correct.
158.109: Service Pack 1 Setup encountered an error: The update.ver file is
not correct.
158.109: Service Pack 1 Setup encountered an error: The update.ver file is
not correct.
158.109: Service Pack 1 Setup encountered an error: The update.ver file is
not correct.
158.109: Service Pack 1 Setup encountered an error: The update.ver file is
not correct.
158.109: Service Pack 1 Setup encountered an error: The update.ver file is
not correct.
158.109: Service Pack 1 Setup encountered an error: The update.ver file is
not correct.
158.125: Service Pack 1 Setup encountered an error: The update.ver file is
not correct.
158.125: Service Pack 1 Setup encountered an error: The update.ver file is
not correct.
158.125: Service Pack 1 Setup encountered an error: The update.ver file is
not correct.
158.125: Service Pack 1 Setup encountered an error: The update.ver file is
not correct.
158.125: Service Pack 1 Setup encountered an error: The update.ver file is
not correct.
158.125: Service Pack 1 Setup encountered an error: The update.ver file is
not correct.
158.125: Service Pack 1 Setup encountered an error: The update.ver file is
not correct.
158.125: Service Pack 1 Setup encountered an error: The update.ver file is
not correct.
158.172: Failed to open c:\windows\$hf_mig$\KB890046\update\updatebr.inf
158.187: Failed to open c:\windows\$hf_mig$\KB893756\update\updatebr.inf
158.187: Failed to open c:\windows\$hf_mig$\KB896358\update\updatebr.inf
158.187: Failed to open c:\windows\$hf_mig$\KB896422\update\updatebr.inf
158.187: Failed to open c:\windows\$hf_mig$\KB896423\update\updatebr.inf
158.187: Failed to open c:\windows\$hf_mig$\KB896428\update\updatebr.inf
158.187: Failed to open c:\windows\$hf_mig$\KB896688\update\updatebr.inf
158.187: Failed to open c:\windows\$hf_mig$\KB897715\update\updatebr.inf
158.187: Failed to open c:\windows\$hf_mig$\KB899587\update\updatebr.inf
158.187: Failed to open c:\windows\$hf_mig$\KB899588\update\updatebr.inf
158.187: Failed to open c:\windows\$hf_mig$\KB899589\update\updatebr.inf
158.187: Failed to open c:\windows\$hf_mig$\KB899591\update\updatebr.inf
158.187: Failed to open c:\windows\$hf_mig$\KB900725\update\updatebr.inf
158.187: Failed to open c:\windows\$hf_mig$\KB901017\update\updatebr.inf
158.187: Failed to open c:\windows\$hf_mig$\KB901214\update\updatebr.inf
158.187: Failed to open c:\windows\$hf_mig$\KB902400\update\updatebr.inf
158.187: Failed to open c:\windows\$hf_mig$\KB904706\update\updatebr.inf
158.187: Failed to open c:\windows\$hf_mig$\KB905414\update\updatebr.inf
158.187: Failed to open c:\windows\$hf_mig$\KB905495\update\updatebr.inf
158.187: Analyzing Devices...
I have APC Personal installed, and the server is running Exchange Server,
ISA and is a Domain Controller. For antivirus it runs Panda AdminSecure.
Any thoughts on this, i couldn't find a similar problem online.
Thanks for your help
Bobby |
|
|
FAQ
Memberlist
Register
Profile
Log in to check your private messages
Log in