Re: client installation error

From: Jeff Harbaugh [MSFT] (jeffharb_at_online.microsoft.com)
Date: 10/08/04


Date: Fri, 8 Oct 2004 14:11:02 -0700


The certificate is TRUST_E_TIME_STAMP however I do not think that will help.

Can you check here to see if this helps?
http://support.microsoft.com/default.aspx?scid=kb;en-us;842773

-- 
Thanks,
Jeff Harbaugh [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.
"Tony" <towong@siebel.com.NOSPAM> wrote in message 
news:OkMf9hXrEHA.3988@tk2msftngp13.phx.gbl...
> Unfortunately, BITS is not listed as one of the program that I can remove
> from ADD/REMOVE program (I do see it as running as a service).   Do you 
> have
> any alternative method?
> Also, the installation stop at this error "Error 0x80096005: The timestamp
> signature and/or certificate could not be
> verified or is malformed.".   Do you know certificate is it referring to?
>
>
> "Jeff Harbaugh [MSFT]" <jeffharb@online.microsoft.com> wrote in message
> news:#0PDmSXrEHA.2732@TK2MSFTNGP09.phx.gbl...
>> I would go into add/remove programs and remove BITS from that machine.
> Then
>> when you push SMS it will install BITS again.
>>
>> -- 
>> Thanks,
>> Jeff Harbaugh [MSFT]
>> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>>
>> "Tony" <towong@siebel.com.NOSPAM> wrote in message
>> news:%23KW2SBXrEHA.3868@TK2MSFTNGP15.phx.gbl...
>> > Here is the log, but I still don't find clue on how to fix it.   Also,
> in
>> > the SP1 release notes, there is a section about Crypto database and its
>> > log
>> > files are out of synchronization and the workaround is to rename the
>> > CatRoot2 folder.   However, that directory doesn't exist in this
>> > particular
>> > machine.
>> >
>> > 2004-10-08 13:34:31  19:34:31   Success   BITS CLNT
>> > ************************** Starting setup of BITS components
>> > ************************
>> > 2004-10-08 13:34:31  19:34:31   Success   BITS CLNT      Package 
>> > version
>> > is
>> > 6.5.3785.1260.
>> > 2004-10-08 13:34:31  19:34:31   Success   BITS CLNT      Loading 
>> > version
>> > functions dynamically
>> > 2004-10-08 13:34:31  19:34:31   Success   BITS CLNT      Setting the
>> > Uninstall Directory to C:\WINNT\system32\BITS\Uninstall 1.5 Client
>> > 2004-10-08 13:34:31  19:34:31   Success   BITS CLNT      Checking if
> user
>> > is
>> > an administrator
>> > 2004-10-08 13:34:31  19:34:31   Success   BITS CLNT      Checking the 
>> > OS
>> > version and SKU
>> > 2004-10-08 13:34:31  19:34:31   Success   BITS CLNT      Detected 
>> > client
>> > install type
>> > 2004-10-08 13:34:31  19:34:31   Success   BITS CLNT      Test for x86
>> > platform...
>> > 2004-10-08 13:34:31  19:34:31   Success   BITS CLNT      Processor
>> > architecture type is 0
>> > 2004-10-08 13:34:31  19:34:31   Success   BITS CLNT      Checking
> pending
>> > file operations...
>> > 2004-10-08 13:34:32  19:34:32   Success   BITS CLNT      Pending DELETE
>> > operation:  \??\c:\winnt\temp\CCM42.tmp
>> > 2004-10-08 13:34:32  19:34:32   Success   BITS CLNT      Installed
> version
>> > of BITS is BITS_v12
>> > 2004-10-08 13:34:32  19:34:32   Success   BITS CLNT      Detected that
>> > installation will be an upgrade of the current BITS version
>> > 2004-10-08 13:34:32  19:34:32   Success   BITS CLNT      Creating
>> > Uninstall
>> > directory
>> > 2004-10-08 13:34:32  19:34:32   Success   BITS CLNT      Directory
>> > C:\WINNT\system32\BITS\Uninstall 1.5 Client already exists;
>> > 2004-10-08 13:34:32  19:34:32   Success   BITS CLNT      Loading inf
> file
>> > c:\1acdb097521d5612b6b2e6\bitssetup_clnt.inf, entry point 
>> > Install_w2k...
>> > 2004-10-08 13:34:32  19:34:32   Success   BITS CLNT      Failed to
>> > retrieve
>> > SfcDllCacheDir policy. Error: 0x2
>> > 2004-10-08 13:34:32  19:34:32   Success   BITS CLNT      Failed to
>> > retrieve
>> > SfcDllCacheDir key. Defaulting to system32 subdirectory. Error: 0x2
>> > 2004-10-08 13:34:32  19:34:32   Success   BITS CLNT      Dllcache
>> > directory
>> > is C:\WINNT\system32\dllcache
>> > 2004-10-08 13:34:32  19:34:32   Success   BITS CLNT      >>> Processing
>> > section [StopBits]...
>> > 2004-10-08 13:34:32  19:34:32   Success   BITS CLNT      Service
> specified
>> > to be stopped: bits
>> > 2004-10-08 13:34:33  19:34:33   Success   BITS CLNT      Service bits 
>> > is
>> > not
>> > running.
>> > 2004-10-08 13:34:33  19:34:33   Success   BITS CLNT      Service bits 
>> > is
>> > not
>> > running, no need to stop.
>> > 2004-10-08 13:34:33  19:34:33   Success   BITS CLNT      +++ Starting
>> > execution of CopyFiles directive for section [StopBits]..
>> > 2004-10-08 13:34:33  19:34:33   Success   BITS CLNT      Execution of
>> > CopyFiles directive for section StopBits has completed successfully
>> > 2004-10-08 13:34:33  19:34:33   Success   BITS CLNT      Skiping
> execution
>> > of RegisterDLL directives for section StopBits because no new file was
>> > copied to the system
>> > 2004-10-08 13:34:33  19:34:33   Success   BITS CLNT      >>> Completed
>> > processing for section [StopBits].
>> > 2004-10-08 13:34:33  19:34:33   Success   BITS CLNT      >>> Processing
>> > section [Install_BITS_qmgrprxy]...
>> > 2004-10-08 13:34:33  19:34:33   Success   BITS CLNT      +++ Starting
>> > execution of CopyFiles directive for section [Install_BITS_qmgrprxy]..
>> > 2004-10-08 13:34:35  19:34:35   Error     BITS CLNT      Failed to
> install
>> > section Install_BITS_qmgrprxy. Aborting the entire setup. (Error
>> > 0x80096005:
>> > The timestamp signature and/or certificate could not be verified or is
>> > malformed.)
>> > 2004-10-08 13:34:35  19:34:35   Success   BITS CLNT      =========
>> > STARTING
>> > ROLLBACK ===========
>> > 2004-10-08 13:34:36  19:34:36   Success   BITS CLNT      ========= END
>> > ROLLBACK ===========
>> > 2004-10-08 13:34:36  19:34:36   Success   BITS CLNT      =========
>> > STARTING
>> > VERIFICATION ===========
>> > 2004-10-08 13:34:36  19:34:36   Success   BITS CLNT      ========= END
>> > VERIFICATION ===========
>> > 2004-10-08 13:34:36  19:34:36   Error     BITS CLNT      Setup has
> failed.
>> > (Error 0x80096005: The timestamp signature and/or certificate could not
> be
>> > verified or is malformed.)
>> > 2004-10-08 13:34:36  19:34:36   Success   BITS CLNT      Unloading
> version
>> > functions
>> > 2004-10-08 13:34:36  19:34:36   Success   BITS CLNT      bitssetup has
>> > finished. Exit code is 80096005
>> > 2004-10-08 13:34:36  19:34:36   Success   BITS CLNT
>> > ************************** BITS Setup has exited
> ************************
>> >
>> > "Jeff Harbaugh [MSFT]" <jeffharb@online.microsoft.com> wrote in message
>> > news:#Z1WEsWrEHA.1164@TK2MSFTNGP10.phx.gbl...
>> >> It looks like the clients are failing on the BITS installation. Can 
>> >> you
>> >> check the BITS installs on the machine.
>> >>
>> >> -- 
>> >> Thanks,
>> >> Jeff Harbaugh [MSFT]
>> >> This posting is provided "AS IS" with no warranties, and confers no
>> > rights.
>> >>
>> >> "Tony" <towong@siebel.com.NOSPAM> wrote in message
>> >> news:eyFluaMrEHA.324@TK2MSFTNGP11.phx.gbl...
>> >> > There are few machines that the adv. client installation terminate
>> >> > unexpected with this this error:
>> >> > <![LOG[Installation failed with error code
>> >> > 1603]LOG]!><time="17:25:49.397+360" date="10-07-2004"
>> > component="ccmsetup"
>> >> > context="" type="3" thread="3588" file="msiutil.cpp:679">
>> >> >
>> >> > Anybody has any idea where the problem is?
>> >> > ------------
>> >> > Here is the few lines from the end of ccmsetup.log
>> >> > <![LOG[MSI: Action 17:25:34: InstallFiles. Copying new
>> >> > files]LOG]!><time="17:25:34.382+360" date="10-07-2004"
>> >> > component="ccmsetup"
>> >> > context="" type="0" thread="3588" file="msiutil.cpp:353">
>> >> > <![LOG[MSI: Action 17:25:38: CcmInstallBITSClient. Updating 
>> >> > Operating
>> >> > System]LOG]!><time="17:25:38.350+360" date="10-07-2004"
>> >> > component="ccmsetup"
>> >> > context="" type="0" thread="3588" file="msiutil.cpp:353">
>> >> > <![LOG[MSI: Setup failed due to unexpected circumstances
>> >> > The error code is 80004005]LOG]!><time="17:25:47.397+360"
>> >> > date="10-07-2004"
>> >> > component="ccmsetup" context="" type="3" thread="3588"
>> >> > file="msiutil.cpp:339">
>> >> > <![LOG[MSI: Action 17:25:47: Rollback. Rolling back
>> >> > action:]LOG]!><time="17:25:47.429+360" date="10-07-2004"
>> >> > component="ccmsetup" context="" type="0" thread="3588"
>> >> > file="msiutil.cpp:353">
>> >> > <![LOG[Installation failed with error code
>> >> > 1603]LOG]!><time="17:25:49.397+360" date="10-07-2004"
>> > component="ccmsetup"
>> >> > context="" type="3" thread="3588" file="msiutil.cpp:679">
>> >> > <![LOG[No status servers specified. Status will not be
>> >> > sent.]LOG]!><time="17:25:49.397+360" date="10-07-2004"
>> >> > component="ccmsetup"
>> >> > context="" type="1" thread="3588" file="status.cpp:321">
>> >> > <![LOG[Next retry in 120 minute(s)...]LOG]!><time="17:25:49.476+360"
>> >> > date="10-07-2004" component="ccmsetup" context="" type="0"
>> >> > thread="3588"
>> >> > file="ccmsetup.cpp:3882">
>> >> >
>> >> > Few lines from client.msi.log
>> >> >
>> >> > Property(S): PrimaryVolumeSpaceAvailable = 51306744
>> >> > Property(S): PrimaryVolumeSpaceRequired = 32618
>> >> > Property(S): PrimaryVolumeSpaceRemaining = 51274126
>> >> > Property(S): INSTALLLEVEL = 1
>> >> > Property(S):
>> >> > SmsSoftwareDistributionCacheSize.8AE6A59B_5597_4D75_9BFD_7F566BF56500
> =
>> >> > 250
>> >> > Property(S): CcmAdministratorsGroupName = Administrators
>> >> > Property(S): CcmUsersGroupName = Users
>> >> > Property(S): CcmCreatorOwnerAccountName = CREATOR OWNER
>> >> > Property(S): PrimaryVolumePath = C:
>> >> > Property(S): SOURCEDIR =
>> >> > C:\WINNT\system32\ccmsetup\{9BE6F195-A36C-4584-919C-342B5A33E30D}\
>> >> > Property(S): SourcedirProduct =
> {D8EF2D11-47CF-45E5-B423-47B29706DE12}
>> >> > Property(S): ProductToBeRegistered = 1
>> >> > === Logging stopped: 10/7/2004  17:25:49 ===
>> >> > MSI (c) (A8:38): Decrementing counter to disable shutdown. If 
>> >> > counter
>> >> >  >=
>> >> > 0,
>> >> > shutdown will be denied.  Counter after decrement: -1
>> >> > MSI (c) (A8:38): MainEngineThread is returning 1603
>> >> > === Verbose logging stopped: 10/7/2004  17:25:49 ===
>> >> >
>> >> >
>> >> >
>> >> >
>> >> > -- 
>> >> > Remove ".NOSPAM" from email address to reply
>> >> >
>> >> >
>> >>
>> >>
>> >
>> >
>>
>>
>
> 


Relevant Pages

  • Signing drivers with signtool for XP 64-bit -- suppressing the war
    ... Ineed to suppress the unsigned driver installation dialog for an automation ... article "Driver signing policy is automatically elevated for unsigned ... I need to sign our drivers for unattended installation via ... Signing Certificate Chain: ...
    (microsoft.public.development.device.drivers)
  • Re: DIFx Framework - HOWTO
    ... The certificate was not installed on the machine, that's s why I did exactly ... The test certificate is obtained through the commands: ... I've successfully created the unsinged cat file using: ... >> installation through DIFx framework but have some troubles with it. ...
    (microsoft.public.development.device.drivers)
  • Re: recovering files encrypted using EFS
    ... > same name and password as the old WinXP installation, ... > intact backup of the old harddisk on COMP2, ... > didn't export the EFS certificate, ... I could of course restore ...
    (microsoft.public.windowsxp.security_admin)
  • Re: Dear "Well Known National Alarm Company":
    ... I believe it 's only until recent years that a dedicated circuit is required for the communicator. ... certificate was issued in 2006 and should be valid until 2011. ... The first "inspection" was signed off one month after installation. ... ULC requires that you monitor the supervisory output. ...
    (alt.security.alarms)
  • Re: error code 8007F0CB during installation of sp2 rc2
    ... Lucy [MSFT] ... This posting is provided "AS IS" with no warranties, ... > During installation of winxp service pack 2 release candidate 2 received ...
    (microsoft.public.windowsupdate)