Re: SP2(KB914961) installation fails 2003(64 bit) endpoint with 0x800705B3

[[Forwarded to Win64bit General via crosspost]]

Pushku wrote:
> Hello Everyone,
>
> We are installing - windows patches - using WUA API. Till now we are
> okey with installing many windows updates and SPs too. but 64-bit SP2
> (KB914961) it failing with following error:
>
> Error Code: 0x800705B3
> Error Desc: This operation requires an interactive window station.
>
> It occurs ONLY when script is executed remotely on endpoint. When we
> run it manually using logged in using RDC, it works fine. Please let
> us know if anyone has got similar problem.
>
>
> Following way we are using API in the vbscript:
>
> *************CODE START***************
> Dim UpdateSession, UpdatesToInstall, UpdateInstaller
>
> Set UpdateSession = CreateObject("Microsoft.Update.Session")
> Set UpdatesToInstall = CreateObject("Microsoft.Update.UpdateColl")
> Set UpdateInstaller = UpdateSession.CreateUpdateInstaller
> ...
> 'Here we initialize 'UpdatesToInstall ' with - UpdatesToInstall.Add()
> ...
> UpdateInstaller.Updates = UpdatesToInstall
> UpdateInstaller.ForceQuiet = True
> UpdateInstaller.IsForced = True
>
> Dim intCount
> For intCount=0 To UpdateInstaller.Updates.Count-1
> UpdateInstaller.Updates.Item(intCount).AcceptEula
> Next
> Set InstallationResult =
> UpdateInstaller.Install 'Install
> updates *fails here*
> *************CODE END***************
>
> Thanks,
> Pushkaraj
>
> PS: I will add svcpack log file in a hour or so.

(interleaved response)
"Pushku" <> wrote in message
news:ff5bbbc0-fc49-435c-9f4e-...


Inserting comment for OP...


"Pushku" <> wrote in message
news:60d66605-73f5-419e-a15f-...
> Hello Everyone,
>
> We are installing - windows patches - using WUA API. Till now we are
> okey with installing many windows updates and SPs too. but 64-bit SP2
> (KB914961) it failing with following error:
>
> Error Code: 0x800705B3
> Error Desc: This operation requires an interactive window station.
>
> It occurs ONLY when script is executed remotely on endpoint.

> When we run it manually using logged in using RDC, it works fine.


Have you tried comparing the logs from those two cases?
(FWIW I don't run that OS so I don't have an example
I could compare for you.)

Also, it may help if you made clear which "upgrade scenario"
your case fits in. (I tried to follow one of the links in the Release Notes
and found this after refining the search it provided


http://technet.microsoft.com/en-us/w...b294403.aspx#1

(BING search for
technet content windowsserver sp2
)



> Please let us know if anyone has got similar problem.
>
>
> Following way we are using API in the vbscript:
>
> *************CODE START***************
> Dim UpdateSession, UpdatesToInstall, UpdateInstaller
>
> Set UpdateSession = CreateObject("Microsoft.Update.Session")
> Set UpdatesToInstall = CreateObject("Microsoft.Update.UpdateColl")
> Set UpdateInstaller = UpdateSession.CreateUpdateInstaller
> ...
> 'Here we initialize 'UpdatesToInstall ' with - UpdatesToInstall.Add()
> ...
> UpdateInstaller.Updates = UpdatesToInstall
> UpdateInstaller.ForceQuiet = True
> UpdateInstaller.IsForced = True
>
> Dim intCount
> For intCount=0 To UpdateInstaller.Updates.Count-1
> UpdateInstaller.Updates.Item(intCount).AcceptEula
> Next
> Set InstallationResult =
> UpdateInstaller.Install 'Install
> updates *fails here*
> *************CODE END***************
>
> Thanks,
> Pushkaraj
>
> PS: I will add svcpack log file in a hour or so.


> Here is the log file:


This is the only thing that really sticks out in it for me.
(E.g. the shell variable should have a trailing % as well as an opening one.)


> 163.453: Starting process: C:\WINDOWS\ADFS\adfsreg.exe backupassembly
> System.Web.Security.SingleSignon %windir \ADFS
> \System.Web.Security.SingleSignon.dll
> 163.453: RunInfProcesses: SpawnProcessAndWaitForItToComplete on "C:
> \WINDOWS\ADFS\adfsreg.exe backupassembly
> System.Web.Security.SingleSignon %windir \ADFS
> \System.Web.Security.SingleSignon.dll" in
> [ADFS.SingleSignOn.RunProcess.ProcessesToRun] failed: 0x3
> 163.453: Return Code = 3


This would be an interesting point of comparison in the two cases,
I suspect. ; )


Good luck

Robert Aldwinckle
---

"Pushku" <> wrote in message
news:a65fb82d-9376-4b9a-a037-...
> Hello Robert,
>
> This are the logs:
....


There is no instance of the line which caught my attention in these.

>> > System.Web.Security.SingleSignon %windir \ADFS


It may be that when the update is run successfully such logging is suppressed.
In that case you might have to invoke verbose logging or even supplement
that with a ProcMon trace.


Good luck

Robert
---