|
|
Thanks, underrstood - I just failed to associate the error message I was
seeing with those rules about the accounts that BITS will work with.
We have a Service running under a named account so it can be authenticated
by other systems on the client LAN, but these accounts never actually log on
to the system. However the Service does want to upload files using BITS. It
looks like we need another Service just to upload files. It would be really
useful if this restriction to logged-on users could be removed for the case
when a Service is running with a named account (for security purposes or
access to resources on a client network) but that user account is not
intended for anyone to log on with, and in a Server environment where nobody
might log on at all.
--
Phil Wilson
[Microsoft MVP-Windows Installer]
"Scott White [MSFT]" <scottwhi@xxxxxxxxxxxxxxxxxxxx> wrote in message
news:uUJeWkPUFHA.3280@xxxxxxxxxxxxxxxxxxxxxxx
> BITS supports only the LocalSystem, LocalService, and NetworkService
> system
> accounts. If you're not using one of these accounts, the user account that
> you are using must be logged on to the computer. If you are using one of
> these accounts, consider this comment from the BITS documentation:
>
>
>
> If a service running under a system account impersonates the user before
> calling BITS, BITS responds as it would for any user account (for example,
> the user needs to be logged on to the computer for the transfer to occur).
>
>
>
> (from
> http://msdn.microsoft.com/library/en-us/bits/bits/service_accounts_and_bits.asp?frame=true)
>
>
>
> Is this the only call that is failing or are other calls that BITS would
> make on behalf of the user failing (for example, AddFile)?
>
>
> --
> 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
> www.microsoft.com/info/cpyright.htm">http://www.microsoft.com/info/cpyright.htm
>
> "Phil Wilson" <Phil.Wilson@xxxxxxxxxxxxxx> wrote in message
> news:OmkesOqSFHA.3300@xxxxxxxxxxxxxxxxxxxxxxx
>> IBackgroundCopyJob::SetNotifyInterface is failing with an error "The
>> operation being requested was not performed because the user has not
> logged
>> on to the network. The specified service does not exist", aka
>> ERROR_LOGON_REQUIRED. We're doing this from a Windows Service running
> with
>> a specified account. It's a requirement that this Service runs with this
>> particular account, so I'm looking for a detour. It's not clear to me
>> exactly why we're getting the error in this case, and I'm looking for a
>> detour that allows the Service to continue running under this account. I
>> assume a detour might be to NOT register a callback and instead poll for
> the
>> status of the upload job, but I'd rather not do that.
>> TIA
>> --
>> Phil Wilson [MVP Windows Installer]
>> ----
>>
>>
>
>
|
|