RE: Failed to install Windows Server 2003 SP1

Dear Terence,
Thanks a bunch for the advise. I really appreciate your input. I will let
you know the result promptly.

Best regards,
Alim

"Terence Liu [MSFT]" wrote:

Hello Customer,

Thanks for posting here.

According to your description, I understand that you encountered the SBS
2003 SP1 installation error. If I have misunderstood the problem, please
don't hesitate to let me know.

Let us perform the following steps and then try to apply the SBS 2003 SP1
to see if it can be applied successfully.

1. Make sure a good backup is at hand. If not, please fully back up the
server. You can refer to the following Microsoft white paper to get detail
steps to backup and restore server:

Backing Up and Restoring Windows Small Business Server 2003
http://www.microsoft.com/technet/prodtechnol/sbs/2003/maintain/bkuprstr.mspx

2. Move all the tmp*.cat files out of the
%systemroot%\system32\CatRoot\{127D0A1D-4EF2-11D1-8608-00C04FC295EE} folder
and the
%systemroot%\system32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE} folder.

3. Move all oem*.* files out the %systemroot%\inf folder.

4. Run the following from a CMD prompt:

net stop cryptsvc
rename the %systemroot%\system32\CatRoot2
%systemroot%\system32\oldcatRoot2
net start cryptsvc

5. Make sure that "Windows" folder and "Windows\System32\CATROOT" is not
hidden.

6. Open Internet Explorer, click "Tools", and then click "Internet
Options". On the "Content" tab, click "Certificates", on the "Trusted Root
Certification Authorities" tab, Make sure that the "Microsoft Root
Authority" certificate is listed. Double click it to make sure that it is
fine.

7. If you have any anti-virus programs and backup programs, please stop
them.

8. Please check the registry setting for driver signing:

a. Click "Start", click "Run", type "regedit" (without the quotation
marks), and then click "OK".
b. Locate, and then click the following key in the registry:
HKEY_LOCAL_MACHINE\Software\Microsoft\Non-Driver Signing
c. Right-click the "Policy" binary value, and then click "Modify".
d. The Value data will appear in the following format: 0000 02

Press DELETE to remove the current value (02 in this example), and then
type "0" (without the quotation marks) (the current value will now appear
as 00).

e. Click "OK", and then quit Registry Editor.

9. Please ensure you have enough free space in the system drive to apply
the SBS 2003 SP1. If you have no sufficient free space in the system drive,
you can refer to the following articles to move exchange database,
transaction logs, client programs folder, sharepoint database, monitor
database, and so on to another drive to free up more space.

821915 How to move Exchange databases and logs in Exchange Server 2003
http://support.microsoft.com/?id=821915

Moving Data Folders for Windows Small Business Server 2003
http://www.microsoft.com/technet/prodtechnol/sbs/2003/maintain/movedata.mspx

830254 How to move the client programs folder to another location in Windows
http://support.microsoft.com/?id=830254

10. Start the SP1 installation.

*More suggestions are addressed in the following article, you can check
into see if it can work.

You cannot install some updates or programs
http://support.microsoft.com/?id=822798

Some 3rd-paryt software reading or scanning temp folder will relate to this
issue. If the issue persists after above steps, please try to do clean boot
on SBS and then install SBS 2003 sp1 again.

To clean boot the problematic computer, please use the steps below:
a. Click Start, click Run, and then in the Open box, type "MSCONFIG"
(without the quotation marks). Click OK.

b. In the System Configuration Utility (MSConfig) window, click to select
the Selective Startup button.

c. Click to clear the check mark from the "Load startup items" below
Selective Startup.

d. Click the Services tab, click to check the "Hide All Microsoft Services"
box, and remove all the check marks from the remained Non-Microsoft
Services. Please note that the Exchange services could be marked as
non-Microsoft. Please do not disable those services.

e. Click OK to close the MSConfig window. Click Yes when you are asked to
restart your computer in order to enable the changes.

f. After restarting, please try to install SBS 2003 sp1 agagin.

g. If there are no more problems, please use the above steps to enable
services and startup items one by one in order to figure out the root cause
of this issue.

If we can not resolve the issue after we perform the above steps, please
help me collect the following log files to analyze the issue:

1. C:\Windows\svcpack.log.

2. C:\Windows\KB885918.log

3. All files under the folder: C:\Program Files\Microsoft
Integration\Windows Small Business Server 2003\Logs

4. Please collect the MPS Report for analyze:

a. Please download the MPSRPT_SETUPPerf.EXE from the following link and
then run this tool to gather some information from the problematic computer:
http://download.microsoft.com/download/b/b/1/bb139fcb-4aac-4fe5-a579-30b0bd9
15706/MPSRPT_SETUPPerf.EXE

b. Double-click on the MPSRPT_SETUPPerf.EXE file.

[Note] This process may take some time; however, it will not have a
negative effect on the performance.

c. A CAB file will be generated in the
%systemroot%\MPSReports\Setup\Reports\Cab directory called
%COMPUTERNAME%_MPSReports.CAB. The CAB file will contain the reports
generated by the MPS Reporting Tool.

Please compress all files and send to my working mailbox:
v-terliu@xxxxxxxxxxxxx

I appreciate your time to collect information. I am happy to be of
assistance to you and look forward to your reply.

Best regards,

Terence Liu(MSFT)

Microsoft CSS Online Newsgroup Support

Get Secure! - www.microsoft.com/security

=====================================================
This newsgroup only focuses on SBS technical issues. If you have issues
regarding other Microsoft products, you'd better post in the corresponding
newsgroups so that they can be resolved in an efficient and timely manner.
You can locate the newsgroup here:
http://www.microsoft.com/communities/newsgroups/en-us/default.aspx

When opening a new thread via the web interface, we recommend you check the
"Notify me of replies" box to receive e-mail notifications when there are
any updates in your thread. When responding to posts via your newsreader,
please "Reply to Group" so that others may learn and benefit from your
issue.

Microsoft engineers can only focus on one issue per thread. Although we
provide other information for your reference, we recommend you post
different incidents in different threads to keep the thread clean. In doing
so, it will ensure your issues are resolved in a timely manner.

For urgent issues, you may want to contact Microsoft CSS directly. Please
check http://support.microsoft.com for regional support phone numbers.

Any input or comments in this thread are highly appreciated.
=====================================================

This posting is provided "AS IS" with no warranties, and confers no rights.

--------------------
| Thread-Topic: Failed to install Windows Server 2003 SP1
| thread-index: Aceciq2DUyUd6UJqRvGQbE46mCv4Kg==
| X-WBNR-Posting-Host: 207.46.193.207
| From: =?Utf-8?B?QWxpbQ==?= <Alim@xxxxxxxxxxxxxxxxxxxxxxxxx>
| Subject: Failed to install Windows Server 2003 SP1
| Date: Tue, 22 May 2007 09:03:03 -0700
| Lines: 385
| Message-ID: <69D62A9A-E95B-4EB0-9274-4DDC28311FE4@xxxxxxxxxxxxx>
| MIME-Version: 1.0
| Content-Type: text/plain;
| charset="Utf-8"
| Content-Transfer-Encoding: 7bit
| X-Newsreader: Microsoft CDO for Windows 2000
| Content-Class: urn:content-classes:message
| Importance: normal
| Priority: normal
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.2826
| Newsgroups: microsoft.public.windows.server.sbs
| Path: TK2MSFTNGHUB02.phx.gbl
| Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.windows.server.sbs:38621
| NNTP-Posting-Host: tk2msftibfm01.phx.gbl 10.40.244.149
| X-Tomcat-NG: microsoft.public.windows.server.sbs
|
| Hi...
| Please help.
| I've had several attempts to install Windows Server 2003 Service Pack 1
(1st
| step on SBS 2003 SP1 installation process) on SBS 2003 standard edition
and
| it got failed.
| - First error message is: Service Pack 1 Setup Error - "Setup could not
| verify the integrity of the file Update.inf. Make sure the Cryptographic
| service is running on this computer"
| I fixed this problem by applying method 1 in article ID 822798: Rename
the
| Edb.log file.
| - Then I ran the installation process again and I got different error
| message (this one is happened during stopping WINS services)
| Service Pack 1 Set Up Error: "Failed to install catalog files" After I
| pressed OK button then I got another message said: "Service Pack 1
| installation did not complete" "Windows Server 2003 has been partially
| updated and may not work properly" then the server started autmatically.
| I tried again with WINS service turned off and I got the same message
again.
|
| Note:
| - Cyrptographic Services is started and set to automatic start up druing
| these processes
| - Symantec Anti Virus and 3rd party software (APC UPC service and
| Pervasive.SQL 2000) are active (started) during all this process.
|
| Here is the last svcpack log on 05/22/07
|
| 6.188:
|
============================================================================
====
| 6.203: 2007/05/22 08:22:12.390 (local)
| 6.203: c:\4374601a78db8901f34b4292\i386\update\update.exe (version
5.6.1013.0)
| 6.203: Service Pack started with following command line:
| 6.344: Return Value From OnACPower = 1
| 6.344: OnACPower returned value( 0x1 ) which is Equal To 0x1
| 6.344: Condition succeeded for section OnACPower.Section in Line 1 of
| PreRequisite
| 6.391: InternalFileName of C:\WINNT\system32\HAL.DLL is Not Equal To
| halcmpx.dll
| 6.391: Condition succeeded for section CustomHalUnisysBlock.Section in
Line
| 2 of PreRequisite
| 6.391: InternalFileName of C:\WINNT\system32\HAL.DLL is Not Equal To
Unisys
| CMP Server ACPI HAL
| 6.391: First Condition in CustomHalUniSysBlock.Section2 Succeeded
| 6.391: Condition succeeded for section CustomHalUniSysBlock.Section2 in
Line
| 3 of PreRequisite
| 6.391: InternalFileName of C:\WINNT\system32\HAL.DLL is Not Equal To
| HALSRAAC.DLL
| 6.391: Condition succeeded for section CustomHalStratusBlock.Section in
Line
| 4 of PreRequisite
| 6.391: InternalFileName of C:\WINNT\system32\HAL.DLL is Not Equal To
| halce52.dll
| 6.391: Condition succeeded for section CustomHalMarathonBlock.Section in
| Line 5 of PreRequisite
| 6.391: Service SpUpdSvc Not Registered in SCM 0x424
| 6.391: Condition succeeded for section SpUpdSvcBlock.Section in Line 6 of
| PreRequisite
| 6.391: Start is Present
| 6.406: SYSTEM\CurrentControlSet\Services\MSDTC\Start is Not Equal To
| Specified Value
| 6.406: Second Condition in MSDTC.Not.Disabled Succeeded
| 6.406: Condition succeeded for section MDSTC.Check.Disabled in Line 7 of
| PreRequisite
| 46.953: DoInstallation: CleanPFR failed: 0x2
| 46.969: SetProductTypes: InfProductBuildType=BuildType.IL
| 47.000: SetAltOsLoaderPath: No section uses DirId 65701; done.
| 47.188: DoInstallation: FetchSourceURL for
| c:\4374601a78db8901f34b4292\i386\update\update.inf failed
| 47.453: CreateUninstall = 1,Directory = C:\WINNT\$NtServicePackUninstall$
| 66.438: BuildCabinetManifest: update.url absent
| 66.453: Starting AnalyzeComponents
| 66.453: AnalyzePhaseZero used 0 ticks
| 66.453: SetupFindFirstLine in LoadExclusionList Failed with error:
0xe0000102
| 71.219:
|
C:\WINNT\system32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\oem10.CAT
| trusts inf c:\winnt\inf\oem10.inf of device
| HID\VID_051D&PID_0002\6&3871FDEA&0&0000
| 82.453:
| C:\WINNT\system32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\oem1.CAT
| trusts inf c:\winnt\inf\oem1.inf of device
| SCSI\OTHER&VEN___RAID&PROD__DUMMYDEVICE&REV_0000\6&3B6F8772&0&2390
| 89.219: OEM file scan used 22766 ticks
| 146.234: c:\winnt\system32\drivers\mraid35x.sys is in the list of oem
| drivers...skipping copy!
| 184.328: AnalyzePhaseOne: used 117875 ticks
| 184.328: AnalyzeComponents: Hotpatch analysis disabled; skipping.
| 184.328: AnalyzeComponents: Hotpatching is disabled.
| 184.328: FindFirstFile c:\winnt\$hf_mig$\*.*
.

Loading