End User License Agreement (EULA) failed to download
Alfred
I have a WSUS 3 server connected to the internet that manages updates for an
internet-connected network and it works fine.
Separately, I have an offline network in a lab environment with WSUS 3
server. I transferred updates and metadata to the lab with wsusutil.exe
(export, import, ...) procedure. The OS security patches, the office 2003 and
Office 2007 patches works but not the Office 2002 patches.
In the WSUS Console, for the Office 2002 patches, the status bar at the top
of the update (in the bottom frame) says, "This update cannot be approved
for installation because its End User License Agreement (EULA) failed to
download".
Any idea ?
Nothing better if I tried "wsusutil reset" command on the internet-connected
WSUS before export.
Regards
Lawrence Garvin [MVP]
news:27CA6BBA-21D8-4714...@microsoft.com...
>
> I have a WSUS 3 server connected to the internet that manages updates for
> an
> internet-connected network and it works fine.
>
> Separately, I have an offline network in a lab environment with WSUS 3
> server. I transferred updates and metadata to the lab with wsusutil.exe
> (export, import, ...) procedure. The OS security patches, the office 2003
> and
> Office 2007 patches works but not the Office 2002 patches.
>
> In the WSUS Console, for the Office 2002 patches, the status bar at the
> top
> of the update (in the bottom frame) says, "This update cannot be approved
> for installation because its End User License Agreement (EULA) failed to
> download".
>
> Any idea ?
Were the Office XP updates approved for installation successfully on the
internet-connected WSUS server?
--
Lawrence Garvin, M.S., MCITP, MCBMSP, MCTS(x4), MCP
Senior Data Architect, APQC, Houston, Texas
Microsoft MVP - Software Distribution (2005-2008)
MS WSUS Website: http://www.microsoft.com/wsus
My Websites: http://www.onsitechsolutions.com;
http://wsusinfo.onsitechsolutions.com
My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
Alfred
internet-connected WSUS server.
Lawrence Garvin [MVP]
>> > In the WSUS Console, for the Office 2002 patches, the status bar at the
>> > top
>> > of the update (in the bottom frame) says, "This update cannot be
>> > approved
>> > for installation because its End User License Agreement (EULA) failed
>> > to
>> > download".
>> >
>> > Any idea ?
>> Were the Office XP updates approved for installation successfully on the
>> internet-connected WSUS server?
> Yes, the Office XP updates are approved for installation successfully on
> the
> internet-connected WSUS server.
Okay, let's back up to basics, to make sure all of my assumptions are valid.
1. Is this the first time you've performed a restore/import on the lab
server?
2. When you did the restore on the lab server, did you restore to the *same*
logical volume and path as the connected server, or did you restore to an
"alternate" location? If an "alternate" location, was it the
~\WSUS\WSUSContent folder created by the installation of WSUS on the lab
server? Have you changed any filesystem permissions on the lab server?
3. Have you investigated to determine if the Office XP EULA file is
physically present on the lab server? Related to that, have you verified
that the Office XP EULA file is *still* present on the connected server.
(Consider the possibility that the EULA file was deleted from the connected
server after the update was approved for installation.)
Alfred
> 1. Is this the first time you've performed a restore/import on the lab server?
First time in WSUS 3.0 (but a lot of time in WSUS 2.0)
> 2. When you did the restore on the lab server, did you restore to the *same* logical volume and path as the connected server, or did you restore to an "alternate" location?
Alternate location
> If an "alternate" location, was it the ~\WSUS\WSUSContent folder created by the installation of WSUS on the lab server? Have you changed any filesystem permissions on the lab server?
No change
> 3. Have you investigated to determine if the Office XP EULA file is physically present on the lab server? Related to that, have you verified that the Office XP EULA file is *still* present on the connected server. (Consider the possibility that the EULA file was deleted from the connected server after the update was approved for installation.)
How can I determine if the Office XP EULA file is physically present on the
lab server ?
Where is this Office XP EULA file ?
Regards
Lawrence Garvin [MVP]
"Alfred" <Alf...@discussions.microsoft.com> wrote in message
news:B9F7F82D-CEBF-4FF4...@microsoft.com...
>
>> 1. Is this the first time you've performed a restore/import on the lab
>> server?
>
> First time in WSUS 3.0 (but a lot of time in WSUS 2.0)
>
>> 2. When you did the restore on the lab server, did you restore to the
>> *same* logical volume and path as the connected server, or did you
>> restore to an "alternate" location?
>
> Alternate location
>
>> If an "alternate" location, was it the ~\WSUS\WSUSContent folder created
>> by the installation of WSUS on the lab server? Have you changed any
>> filesystem permissions on the lab server?
>
> No change
Sadly, the one question you didn't answer is the *key* to giving you the
correct response.
>> If an "alternate" location, was it the ~\WSUS\WSUSContent folder created
>> by the installation of WSUS on the lab server?
If it was not the WSUS-created ~\WSUSContent folder, then you likely have
incorrect permissions on the folder you restored to, and the Update Services
service (which runs in the context of the NTAUTHORITY\Network Service
account has no read permissions on the folder).
Even if you did use the WSUS-created ~\WSUSContent folder, but there was no
preexisting content, it's possible that the subfolders ('00 through 'FF')
were created with incorrect permissions.
Ensure that the NTAUTHORITY\Network Service account has READ, READ &
EXECUTE, and LIST FOLDER CONTENTS permissions on the ~\WSUSContent folder
and they're inherited down the tree.
>> 3. Have you investigated to determine if the Office XP EULA file is
>> physically present on the lab server? Related to that, have you verified
>> that the Office XP EULA file is *still* present on the connected server.
>> (Consider the possibility that the EULA file was deleted from the
>> connected server after the update was approved for installation.)
>
> How can I determine if the Office XP EULA file is physically present on
> the
> lab server ?
>
> Where is this Office XP EULA file ?
Right click on the update. Select "File Information" from the list. Identify
the CAB file containing the update.
[1] Search inside the cab file for the EULA.TXT file (or something similar).
[2] Do a search on the ~\WSUSContent folder for all TXT files, sometimes
they're stored externally.
One of those two methods should find the EULA file if it exists.
It's also possible, though I've not researched this, that with the intro of
SQL2005, they might be storing the EULAs in the metadata inside the
database. If that's the case, I don't know how to get to it.
More significantly, and probably much easier, just do a Folder Properties on
both of the ~\WSUSContent folders, and compare the number of files, folders,
and bytes that exist. Do they match?
Alfred
In the MMC Console, on the disconnected WSUS server, right click on the
update with problem and choose "try to download again the update" (something
like this) and the EULA warning disappears.
I am on a disconnected network. I don't know what It do but It works !!!
Thanks
Alfred
Lawrence Garvin
> The Solution
>
> In the MMC Console, on the disconnected WSUS server, right click on the
> update with problem and choose "try to download again the update"
> (something
> like this) and the EULA warning disappears.
>
> I am on a disconnected network. I don't know what It do but It works !!!
If it worked on a disconnected server, that suggests something simply didn't
get 'updated' in the metadata once the file was available.
Most interesting!
Thank you for the reply and information, Alfred.