RE: Fatal Error Installing XPsv2 Deployment for SBS sv1 Upgrade
- From: v-yanniw@xxxxxxxxxxxxxxxxxxxx ("Jenny wu [MSFT]")
- Date: Fri, 11 Nov 2005 12:14:55 GMT
Hi,
Thanks for your update! I am glad to know that things are getting fine
now. I appreciate your time and effort to try my suggestions and get the
resolved.
Have you Rerun CEICW wizard to refresh network connection? If not, please
perform it to test if the add computer wizard works.
I suggest you refer to KB 825763 to configure the network connection:
825763 How to configure Internet access in Windows Small Business Server
2003
http://support.microsoft.com/?id=825763
1. If the issue persists, could you tell me the accurate error message? And
also please help me collect a screen shot when reproduce the issue.
To make a screen shot:
A. Press Alt + Pr Scrn to capture a screen shot.
B. From Start, go to Run, enter pbrush in the Open box, and then click OK.
C. Use Ctrl + V to paste the screen shot to the canvas.
D. From the File menu, go to Save and save as a JPG file.
2. Could you find related error event in Event Viewer (Start ->
Administrative Tools -> Event Viewer) in the SBS server box? If yes, please
paste the detail error information in the newsgroup or mail to me.
Please mail me the screen shot at v-yanniw@xxxxxxxxxxxxx
I am happy to be assistance of you!
Have a nice day!
Sincerely,
Jenny Wu
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: Fatal Error Installing XPsv2 Deployment for SBS sv1 Upgrade
>thread-index: AcXmBzIYFOqmcsmOQ3CgYBA5eF+vdg==
>X-WBNR-Posting-Host: 66.95.162.225
>From: "=?Utf-8?B?dHJhdmVsYWRtaW4=?="
<traveladmin@xxxxxxxxxxxxxxxxxxxxxxxxx>
>References: <F2E42E33-1D28-436A-BB31-FEEE9A423CF3@xxxxxxxxxxxxx>
<H25D#I43FHA.2984@xxxxxxxxxxxxxxxxxxxxx>
<73FD2321-BE49-46D4-AD8F-11E9C2B5C8A6@xxxxxxxxxxxxx>
<MQKnIgG5FHA.1144@xxxxxxxxxxxxxxxxxxxxx>
>Subject: RE: Fatal Error Installing XPsv2 Deployment for SBS sv1 Upgrade
>Date: Thu, 10 Nov 2005 06:58:22 -0800
>Lines: 312
>Message-ID: <E100D172-04D2-4418-A23A-8344C3C4ECA9@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.0
>Newsgroups: microsoft.public.windows.server.sbs
>NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
>Path: TK2MSFTNGXA02.phx.gbl!TK2MSFTNGXA01.phx.gbl!TK2MSFTNGXA03.phx.gbl
>Xref: TK2MSFTNGXA02.phx.gbl microsoft.public.windows.server.sbs:220894
>X-Tomcat-NG: microsoft.public.windows.server.sbs
>
>Jenny:
>
>Tried things and had no luck but then realized that there was another
issue
>as I tried to stop services that weren't Microsoft and get a weird need to
be
>an admin error. I wasn't using the orginal admin account so I logged in as
>that and was able to run 4092 and then SBS svp1. Now it looks fine except
the
>add computer wizard in the console no longer works. Haven't noticed any
other
>errors elsewise (although I know I need to reinstall the fax but no one is
>using that currently) Ideas?
>
>""Jenny wu [MSFT]"" wrote:
>
>> Hi,
>>
>> Thanks for your update!
>>
>> Based on the installation log and my research, all errors except the
>> following ones are able to be safely ignored.
>>
>> 324.891: DoInstallation: CustomizeCall failed : 0x643
>> 325.547: Fatal error during installation.
>> 343.063: Message displayed to the user: Fatal error during installation.
>> 343.063: User Input: OK
>> 343.063: KB891193 installation did not complete.
>>
>> Small Business Server 2003 has been partially updated and may not work
>> properly.
>> 347.953: Message displayed to the user: KB891193 installation did not
>> complete.
>>
>> Small Business Server 2003 has been partially updated and may not work
>> properly.
>> 347.953: User Input: OK
>> 347.953: Update.exe extended error code = 0x643
>> 347.953: Update.exe return code was masked to 0x643 for MSI custom
action
>> compliance.
>>
>> However, 0x643 error means "Installation Failure". In this scenario, the
>> error log shows nothing to us. At this point, please understand that we
may
>> have to take some time to troubleshoot this issue.
>>
>> For your xp2 deployment log, I find you have moved the folder ClientApps
to
>> another location. I suggest you carefully refer to the following KB to
>> check if permissions and others are configured properly:
>>
>> How to move the client programs folder to another location in Windows
Small
>> Business Server 2003
>> http://support.microsoft.com/default.aspx?scid=kb;en-us;830254
>>
>> And then try to test to see if the issue be fixed. If the issue
persists, I
>> suggest you try follow suggestions to try to trouble shoot the issue:
>>
>> Info 1.
>>
>> Please perform a Clean Boot and check whether the problem persists.
>>
>> 1. Click Start->Run...->type msconfig and press Enter
>> 2. Click Services tab and select Hide All Microsoft Services and Disable
>> All third party Services.
>> 3. Click Startup tab and Disable All startup items
>> 4. Click OK and choose Restart
>> 5. After reboot, check whether the problem still occurs
>>
>> Info 2.
>>
>> Please use SUBINACL tool to make sure that there's no permission
limitation.
>>
>> 1. Download and install subinacl from:
>>
>>
http://www.microsoft.com/downloads/details.aspx?FamilyID=e8ba3e56-d8fe-4a91-
>> 93cf-ed6985e3927b&displaylang=en
>>
>> 2. Create a file named reset.cmd in C:\Program Files\Windows Resource
>> Kits\Tools folder.
>>
>> 3. Edit the reset.cmd file with the following content.
>>
>> subinacl /subkeyreg HKEY_LOCAL_MACHINE /grant=administrators=f
>> subinacl /subkeyreg HKEY_CURRENT_USER /grant=administrators=f
>> subinacl /subkeyreg HKEY_CLASSES_ROOT /grant=administrators=f
>> subinacl /subdirectories %SystemDrive% /grant=administrators=f
>>
>> subinacl /subkeyreg HKEY_LOCAL_MACHINE /grant=system=f
>> subinacl /subkeyreg HKEY_CURRENT_USER /grant=system=f
>> subinacl /subkeyreg HKEY_CLASSES_ROOT /grant=system=f
>> subinacl /subdirectories %SystemDrive% /grant=system=f
>>
>> 4. Enter into CMD prompt.
>>
>> 5. Enter the following commands one at a time and click Enter.
>>
>> cd\
>> cd "C:\Program Files\Windows Resource Kits\Tools"
>> reset.cmd
>>
>> 6. After a few minutes by processing subinacl, please test the problem
>> again.
>>
>> [Note] As a quick work around, I'd like to provide the following info
for
>> your reference:
>>
>> If you've already installed XP SP2 on all client computers, you can
follow
>> the steps below to avoid installing 891193. If some of the client
computers
>> have not installed XP SP2, please dismiss the following info.
>>
>> 1. Download and install 872769 on the SBS machine.
>>
>> Update for Windows Small Business Server 2003: KB 872769
>>
http://www.microsoft.com/downloads/details.aspx?familyid=d70097c2-4317-40e0-
>> b7da-feb52c6b6386&displaylang=en
>>
>> 2. Follow the instruction in the following KB's "Update installation
>> instructions" section to prepare XP SP2.
>>
>> Update is available for the Windows Small Business Server 2003 Client
Setup
>> feature to deploy Windows XP Service Pack 2 to Windows XP
>> Professional-based clients
>> http://support.microsoft.com/kb/884032#XSLTH3142121122120121120120
>>
>> 3. Download and install 884032 on the SBS machine.
>>
>> Update for Windows Small Business Server 2003: KB 884032
>>
http://www.microsoft.com/downloads/details.aspx?familyid=A8F72FDD-6D82-4C2B-
>> 8078-114460826A40&displaylang=en
>>
>> 4. Skip 891193 and install SBS SP1 885918.
>>
>> Windows Small Business Server 2003 Service Pack 1
>>
http://download.microsoft.com/download/e/0/f/e0fee8ce-768d-41c0-8871-9bc48e0
>> b3fc3/SBS2003-KB885918-SP1-X86-ENU.EXE
>>
>> I hope the above info helps. I am happy to be assistance of you and look
>> forward to your reply!
>>
>> Have a nice day!
>>
>> Sincerely,
>>
>> Jenny Wu
>> 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: Fatal Error Installing XPsv2 Deployment for SBS sv1
Upgrade
>> >thread-index: AcXkFJFJoHewnyN7R/KB6A1a2ZRhmA==
>> >X-WBNR-Posting-Host: 66.95.162.225
>> >From: "=?Utf-8?B?dHJhdmVsYWRtaW4=?="
>> <traveladmin@xxxxxxxxxxxxxxxxxxxxxxxxx>
>> >References: <F2E42E33-1D28-436A-BB31-FEEE9A423CF3@xxxxxxxxxxxxx>
>> <H25D#I43FHA.2984@xxxxxxxxxxxxxxxxxxxxx>
>> >Subject: RE: Fatal Error Installing XPsv2 Deployment for SBS sv1 Upgrade
>> >Date: Mon, 7 Nov 2005 19:29:03 -0800
>> >Lines: 223
>> >Message-ID: <73FD2321-BE49-46D4-AD8F-11E9C2B5C8A6@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.0
>> >Newsgroups: microsoft.public.windows.server.sbs
>> >NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
>> >Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGXA03.phx.gbl
>> >Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.windows.server.sbs:168493
>> >X-Tomcat-NG: microsoft.public.windows.server.sbs
>> >
>> >No luck. enclosing xp2 deployment log portion:
>> >
>> >[KB891193.log]
>> >1.078:
>>
>===========================================================================
>> =====
>> >1.078: 2005/10/31 23:02:25.125 (local)
>> >1.078: f:\ac74d7ef9af432dfe85627522e\update\update.exe (version
6.1.22.4)
>> >1.281: DoInstallation: GetProcAddress(InitializeCustomizationDLL)
>> Returned:
>> >0x7f
>> >1.281: Hotfix started with following command line:
>> >1.484: CreateUserInterface: GetProcAddress for DefineInstallCustomUI
>> >failed: 0x7f
>> >1.625: Return Value From IsSbs2003 = 1
>> >1.625: IsSbs2003 returned value( 0x1 ) which is Equal To 0x1
>> >1.625: Condition succeeded for section ChkSBS.Section in Line 1 of
>> >PreRequisite
>> >12.953: In Function TestVolatileFlag, line 11660, RegOpenKeyEx failed
with
>> >error 0x2
>> >12.953: In Function TestVolatileFlag, line 11692, RegOpenKeyEx failed
with
>> >error 0x2
>> >12.953: DoInstallation: CleanPFR failed: 0x2
>> >12.984: SetProductTypes: InfProductBuildType=BuildType.IL
>> >13.000: SetAltOsLoaderPath: No section uses DirId 65701; done.
>> >13.234: DoInstallation: FetchSourceURL for
>> >f:\ac74d7ef9af432dfe85627522e\update\update.inf failed
>> >13.234: LoadFileQueues: UpdSpGetSourceFileLocation for halmacpi.dll
>> failed:
>> >0xe0000102
>> >13.234: BuildCabinetManifest: update.url absent
>> >13.234: Starting AnalyzeComponents
>> >13.234: AnalyzePhaseZero used 0 ticks
>> >13.250: OEM file scan used 0 ticks
>> >13.344: AnalyzePhaseOne: used 110 ticks
>> >13.344: AnalyzeComponents: Hotpatch analysis disabled; skipping.
>> >13.344: AnalyzeComponents: Hotpatching is disabled.
>> >14.109: AnalyzePhaseTwo used 765 ticks
>> >14.109: AnalyzePhaseThree used 0 ticks
>> >14.109: AnalyzePhaseFive used 0 ticks
>> >14.109: AnalyzePhaseSix used 0 ticks
>> >925.328: AnalyzeComponents used 912094 ticks
>> >925.328: Downloading 0 files
>> >925.328: bPatchMode = FALSE
>> >925.328: Inventory complete: ReturnStatus=0, 912094 ticks
>> >926.125: CreateUninstall = 0,Directory =
C:\WINDOWS\$NtUninstallKB891193$
>> >926.125: Num Ticks for invent : 912891
>> >926.125: Allocation size of drive C: is 4096 bytes, free space =
>> 4206944256
>> >bytes
>> >926.141: Drive C: free 4012MB req: 8MB w/uninstall 0MB
>> >926.141: CabinetBuild complete
>> >926.141: Num Ticks for Cabinet build : 16
>> >926.141: DynamicStrings section not defined or empty.
>> >926.141: FileInUse:: need to restart already, turn off
>> >927.281: Registering Uninstall Program for -> KB891193, KB891193 , 0x0
>> >927.297: LoadFileQueues: UpdSpGetSourceFileLocation for halmacpi.dll
>> failed:
>> >0xe0000102
>> >927.406: Copied file: C:\WINDOWS\system32\spmsg.dll
>> >927.438: PFE2: Not avoiding Per File Exceptions.
>> >928.328: GetCatVersion: Failed to retrieve version information from
>>
>C:\WINDOWS\system32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\KB891193
>> .cat with error 0x57
>> >938.641: KB891193 Setup encountered an error: KB891193 Setup
>> >938.766: Copied file: C:\Program Files\Microsoft Windows Small
Business
>> >Server\ClientSetup\Clients\Setup\AppLnch.exe
>> >939.203: KB891193 Setup encountered an error: KB891193 Setup
>> >939.297: Copied file: C:\Program Files\Microsoft Integration\Windows
>> Small
>> >Business Server 2003\SBSComp.dll
>> >940.156: DoInstallation: Installing assemblies with source root path:
>> >f:\ac74d7ef9af432dfe85627522e\
>> >1888.547: DoInstallation: CustomizeCall failed : 0x643
>> >1895.109: Fatal error during installation.
>> >2214.047: Message displayed to the user: Fatal error during
installation.
>> >2214.047: User Input: OK
>> >2214.078: KB891193 installation did not complete.
>> >
>> >Small Business Server 2003 has been partially updated and may not work
>> >properly.
>> >2219.453: Message displayed to the user: KB891193 installation did not
>> >complete.
>> >
>> >Small Business Server 2003 has been partially updated and may not work
>> >properly.
>> >2219.453: User Input: OK
>> >2219.453: Update.exe extended error code = 0x643
>> >2219.453: Update.exe return code was masked to 0x643 for MSI custom
action
>> >compliance.
>> >
>> >""Jenny wu [MSFT]"" wrote:
>> >
>> >> Hi
>> >>
>> >> Thanks for posting here!
>> >>
>> >> Based on my research, the issue may occur if the information
regarding
>> >> location of the Clientapps folder is incorrect in the registry.
Please
>> >> perform the following steps to see if the problem can be resolved:
>> >>
>> >> 1. Open Registry Editor.
>> >> 2. Point to the following location:
>> >>
>> >> HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SmallBusinessServer\clientsetup
>> >>
>> >> 3. By default, "ClientAppsRoot"="C:\ClientApps". If you moved the
>> >> Clientapps to other folders or partition, please modify it and then
>> reboot
>> >> the machine.
>> >>
>> >> And also please follow steps to uninstall fax services to prepare SBS
>> >> deploy Windows XP SP2 to client computers that are running Windows XP
>> >> Professional:
>> >>
>> >> 1. Schedule a down time.
>> >> 2. Open Control Panel | Add or Remove Programs, and then launch SBS
>> >> Integrate Setup program.
>> >> 3. Uninstall Fax Service via SBS Setup using component Selection
screen,
>
.
- References:
- RE: Fatal Error Installing XPsv2 Deployment for SBS sv1 Upgrade
- From: traveladmin
- RE: Fatal Error Installing XPsv2 Deployment for SBS sv1 Upgrade
- From: "Jenny wu [MSFT]"
- RE: Fatal Error Installing XPsv2 Deployment for SBS sv1 Upgrade
- Prev by Date: Re: Files system log files
- Next by Date: Re: Script error when running server management "applets" - SOLVED
- Previous by thread: RE: Fatal Error Installing XPsv2 Deployment for SBS sv1 Upgrade
- Next by thread: RE: Fatal Error Installing XPsv2 Deployment for SBS sv1 Upgrade
- Index(es):
Relevant Pages
|
