Re: Setup failed due to unexpected circumstances

Tech-Archive recommends: Fix windows errors by optimizing your registry

Have you downloaded the client toolkit from microsoft.com/sms? If so I would
run the BITS log and BITS test from the tool kit.
I am thinking this machine has a problem with BITS when SMS is trying to
install it.
Atleast we can get a BITS log to see what is happening.

--
Thanks,
Jeff Harbaugh [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.

"Kevin" <Kevin@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:0B8A03CD-E9B9-4164-A30F-D8016D15F725@xxxxxxxxxxxxxxxx
> Jeff,
>
> Here is part of the client.msi.log file:
>
> InstallFiles: File: SMSRC.chm, Directory:
> D:\WINNT\system32\CCM\clicomp\RemCtrl\help\1033\, Size: 50698
> InstallFiles: File: wusermsg.dll, Directory:
> D:\WINNT\system32\CCM\clicomp\RemCtrl\1033\, Size: 45056
> Action 4:11:24: CcmInstallBITSClient. Updating Operating System
> [4:11:31] @@ERR:25001
> Error 25001. Setup failed due to unexpected circumstances
> The error code is 80004005
> Action ended 4:11:31: InstallFinalize. Return value 3.
> Action 4:11:31: Rollback. Rolling back action:
>
> There was no BITSsetup.log file.
>
> Looks like the same error message "Setup failed due to unexpected
> circumstances" and then the error code 80004005.
>
> BITS service is installed.
>
> -Kevin
>
>
> "Jeff Harbaugh [MSFT]" wrote:
>
>> Can you look at the client.msi.log file on the clients? Searhc for return
>> value 3 to see where the installation is failing.
>> Also check the BITSsetup.log on the clients if there is one. (Should be
>> in
>> %windir%\system32)
>> Looks like the client is having trouble getting BITS installed.
>>
>> --
>> Thanks,
>> Jeff Harbaugh [MSFT]
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>>
>> "Kevin" <Kevin@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
>> news:10DE0085-44B7-4984-9038-20FBC8B603DB@xxxxxxxxxxxxxxxx
>> >I have installed SMS 2003 on a Windows 2003 server in an AD environment.
>> > I have just over 1000 workstations that have the Advanced client
>> > installed
>> > and working fine. But I have a couple of workstations that will not
>> > install
>> > the client.
>> > They are discovered (via AD system discovery) and assigned. In the
>> > ccmsetup.log file I am getting the following:
>> > File download 99% complete (7065600 of 7078400 bytes). ccmsetup
>> > 4/1/2005
>> > 12:01:40 AM 460 (0x01CC)
>> > File download 100% complete (7078400 of 7078400 bytes). ccmsetup
>> > 4/1/2005
>> > 12:01:40 AM 460 (0x01CC)
>> > Download complete. ccmsetup 4/1/2005 12:01:43 AM 460 (0x01CC)
>> > Searching for available transform ccmsetup 4/1/2005 12:01:43 AM 460
>> > (0x01CC)
>> > Failed to find resource file 'client.mst' ccmsetup 4/1/2005 12:01:44 AM
>> > 460
>> > (0x01CC)
>> > No transform available for this locale. Installation will proceed with
>> > no
>> > transformation. ccmsetup 4/1/2005 12:01:44 AM 460 (0x01CC)
>> > Updated security on object D:\WINNT\system32\ccmsetup\. ccmsetup
>> > 4/1/2005
>> > 12:01:44 AM 460 (0x01CC)
>> > No client is currently installed. ccmsetup 4/1/2005 12:01:44 AM 460
>> > (0x01CC)
>> > Installing version 2.50.3174.1018 of the client with product code
>> > {FCDC3CDD-F53E-4239-8CA5-BC492942931B} ccmsetup 4/1/2005 12:01:44 AM
>> > 460
>> > (0x01CC)
>> > Running installation package
>> > Package:
>> > D:\WINNT\system32\ccmsetup\{EA6AF9AB-72EA-4E9F-934E-941E408C023F}\client.msi
>> > Log: D:\WINNT\system32\ccmsetup\client.msi.log
>> > Properties: INSTALL="ALL" SMSSITECODE="AUTO" CCMHTTPPORT=80
>> > INSTALL=ALL ccmsetup 4/1/2005 12:01:44 AM 460 (0x01CC)
>> > MSI: Action 0:01:49: AppSearch. Searching for installed
>> > applications ccmsetup 4/1/2005 12:01:49 AM 460 (0x01CC)
>> > MSI: Action 0:01:59: GenerateScript. Generating script operations for
>> > action: ccmsetup 4/1/2005 12:01:59 AM 460 (0x01CC)
>> > MSI: Action 0:06:28: CcmStopServiceRollback. ccmsetup 4/1/2005 12:06:28
>> > AM 460 (0x01CC)
>> > MSI: Action 0:06:29: ProcessComponents. Updating component
>> > registration ccmsetup 4/1/2005 12:06:29 AM 460 (0x01CC)
>> > MSI: Action 0:06:36: CcmStopService. ccmsetup 4/1/2005 12:06:36 AM 460
>> > (0x01CC)
>> > MSI: Action 0:06:38: StopServices. Stopping services ccmsetup 4/1/2005
>> > 12:06:38 AM 460 (0x01CC)
>> > MSI: Action 0:06:38: SmsStopUIComponents. Stopping UI
>> > Components ccmsetup 4/1/2005 12:06:38 AM 460 (0x01CC)
>> > MSI: Action 0:06:39: DeleteServices. Deleting services ccmsetup
>> > 4/1/2005
>> > 12:06:39 AM 460 (0x01CC)
>> > MSI: Action 0:06:39: SmsRemoveUIEvents. Removing UI Events ccmsetup
>> > 4/1/2005
>> > 12:06:39 AM 460 (0x01CC)
>> > MSI: Action 0:06:40: CcmUnregisterPerfCounters. Unregistering
>> > performance
>> > counters ccmsetup 4/1/2005 12:06:40 AM 460 (0x01CC)
>> > MSI: Action 0:06:41: RemoveRegistryValues. Removing system registry
>> > values ccmsetup 4/1/2005 12:06:41 AM 460 (0x01CC)
>> > MSI: Action 0:06:54: RemoveFiles. Removing files ccmsetup 4/1/2005
>> > 12:06:54
>> > AM 460 (0x01CC)
>> > MSI: Action 0:06:55: SmsDeinstallDesktopClientRollback. Deinstalling
>> > the
>> > SMS
>> > Legacy Client or SMS 2.0 Client ccmsetup 4/1/2005 12:06:55 AM 460
>> > (0x01CC)
>> > MSI: Action 0:06:55: SmsMigrateSwDistExecutionHistory. Migrating
>> > Software
>> > Distribution History ccmsetup 4/1/2005 12:06:55 AM 460 (0x01CC)
>> > MSI: Action 0:06:56: SmsDeinstallDesktopClient. Deinstalling the SMS
>> > Legacy
>> > Client or SMS 2.0 Client ccmsetup 4/1/2005 12:06:56 AM 460 (0x01CC)
>> > MSI: Action 0:06:59: CreateFolders. Creating folders ccmsetup 4/1/2005
>> > 12:06:59 AM 460 (0x01CC)
>> > MSI: Action 0:07:00: CcmStopAndDisableWmiRollback. ccmsetup 4/1/2005
>> > 12:07:00 AM 460 (0x01CC)
>> > MSI: Action 0:07:01: CcmStopAndDisableWmi. ccmsetup 4/1/2005 12:07:01
>> > AM 460 (0x01CC)
>> > MSI: Action 0:07:03: CcmDetectFilesInUseRollback. ccmsetup 4/1/2005
>> > 12:07:03 AM 460 (0x01CC)
>> > MSI: Action 0:07:03: CcmDetectFilesInUse. ccmsetup 4/1/2005 12:07:03 AM
>> > 460
>> > (0x01CC)
>> > MSI: Action 0:07:05: CcmDetectFilesInUseCommit. ccmsetup 4/1/2005
>> > 12:07:05
>> > AM 460 (0x01CC)
>> > MSI: Action 0:07:05: InstallFiles. Copying new files ccmsetup 4/1/2005
>> > 12:07:05 AM 460 (0x01CC)
>> > MSI: Action 0:07:32: CcmInstallBITSClient. Updating Operating
>> > System ccmsetup 4/1/2005 12:07:32 AM 460 (0x01CC)
>> > MSI: Setup failed due to unexpected circumstances
>> > The error code is 80004005 ccmsetup 4/1/2005 12:07:54 AM 460 (0x01CC)
>> > MSI: Action 0:07:56: Rollback. Rolling back action: ccmsetup 4/1/2005
>> > 12:07:56 AM 460 (0x01CC)
>> > Installation failed with error code 1603 ccmsetup 4/1/2005 12:08:27 AM
>> > 460
>> > (0x01CC)
>> >
>> > Anyone else experiencing this problem or have some suggestions?
>> > All the workstations are running Windows 2000 SP-4.
>> >
>> > Thanks.
>> >
>> >
>>
>>
>>


.

Relevant Pages

  • Re: Non AD client push problems
    ... Is there a way you can run system discovery or network discovery? ... If this is blank then SMS ... >> cannot determine the OS and will not install the client. ... Under the client push installation we are using are ...
    (microsoft.public.sms.setup)
  • Re: Problem with Legacy client discovery
    ... Smsman is the only installation method for W98 machines. ... them and even logon installation simply runs smsman. ... >I have tried to manually install the client on 98 machines using smsman.exe ... > download the enhanced system discovery tool at myitforum.com...I have ...
    (microsoft.public.sms.setup)
  • Re: Client push question - the plot thickens
    ... for clients within the site boundaries of a secondary site are disseminated ... If Client Push is enabled at that site then the ... SMS 2003 and Advanced Client push installation behavior. ... secondary site unless the secondary site has both initiated discovery of the ...
    (microsoft.public.sms.admin)
  • Re: Office Installation Not Syncing to AIP
    ... We want to replace all files since we are reaching to a brand new AIP. ... To answer your question about whether or not you can tell how the client ... patches got installed. ... If the installation is in a "mixed state" the symptom that you usually see ...
    (microsoft.public.officeupdate)
  • Re: Advanced Client install nightmare
    ... I have previously successfully installed a client over the network, ... I can succesfully connect to the remote registry using the account. ... MVP Windows Server System - SMS ... account specified in the Client push installation properties. ...
    (microsoft.public.sms.admin)