|
|
It sounds like on that particular customer's machine BITS 1.5 installer was
not able to stop the BITS service to replace the files. Could you send me
following files from this machine? Also what OS is on this machine? Could
you check the system event log and see if there is any error related to
BITS?
1. %windir%\bits*.log
2. %windir%\setup*.log
--
Narayana Mahankali
Microsoft, BITS
This posting is provided "As Is" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
<ljwhitmire@xxxxxxxxx> wrote in message
news:1111286732.455838.282910@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
> We've been installing BITS for a couple years now as a part of our
> service. We have our installshield installer set to not reboot.
> We've never had a problem before, but we've run into a customer
> environment
> where the BITS install does not work unless there is a reboot. Upon
> further
> inspection, it appears that the files qmgr.dll and qmgrprxy.dll
> are only getting updated after the reboot on these machines, where as
> on all other machines we've used, they get updated right away. What's
> weirder
> is that qmgrprxy.dll is getting updated, but qmgr.dll is not, until the
> reboot.
> Since our app uses BITS, this causes an error with using BITS since
> this
> particular customer has 1.2, we are installing 1.5 and we use the
> upstream components. When this happens we get the interface not
> supported
> error.
>
> I've racked my brain over what could cause this. It's worth mentioning
> that this customer has a very complicated and odd base image (we've had
> lot's
> of other weird problems in their environent that we've never seen
> anywhere else).
> I just don't know what else to look at or what to tell them to change.
> I need
> to get them to roll out BITS 1.5 or 2.0, but they aren't thrilled about
> the
> reboot. Any clues would be appreciated.
>
> -jaye
>
|
|