Microsoft Software License Terms failed to download
nqetech
I'm just setting up WSUS 3.0 from scratch and I've noticed that there are
some downloads that can't be approved because:
"This update cannot be approved for installation because its Microsoft
Software License Terms failed to download. Click Retry Download to start the
download again."
I've tried re-starting the download but without success. This affects quite
a few downloads, including WinXP SP2. Am I doing something wrong, or is this
normal behaviour?
If anybody can help, I'd appreciate it!
Lawrence Garvin (MVP)
news:84A4F16A-236F-46DD...@microsoft.com...
This is not normal behavior, but it does sometimes happen.... reasons not
quite known.
Try running 'wsusutil reset' to let the WSUS server scan the database for
content files that are supposed to exist, but do not. That will regen a BITS
download request for the missing files. Monitor the server status and when
files to download is zero, try approving the update(s) again.
--
Lawrence Garvin, M.S., MCTS, MCP
Independent WSUS Evangelist
MVP-Software Distribution (2005-2007)
https://mvp.support.microsoft.com/profile=30E00990-8F1D-4774-BD62-D095EB07B36E
Everything you need for WSUS is at
http://technet2.microsoft.com/windowsserver/en/technologies/featured/wsus/default.mspx
And, almost everything else is at
http://wsusinfo.onsitechsolutions.com
....
nqetech
time.
"Lawrence Garvin (MVP)" wrote:
> .....
>
>
>
>
nqetech
Further to my previous post, I can't get any further with the following
updates:
Update for Windows XP (KB920342)
Windows Malicious Software Removal Tool - June 2007 (KB890830)
Windows XP Service Pack 2
I've now run 'wsusutil reset' several times. Is there a means of removing
these updates completely and then re-syncing them from Microsoft?
Obviously, XP SP2 is quite an important update, so being unable to approve
it is a bit of an issue!
"Lawrence Garvin (MVP)" wrote:
> .....
>
>
>
>
Lawrence Garvin (MVP)
> Further to my previous post, I can't get any further with the following
> updates:
>
> Update for Windows XP (KB920342)
> Windows Malicious Software Removal Tool - June 2007 (KB890830)
> Windows XP Service Pack 2
>
> I've now run 'wsusutil reset' several times.
It could be the files are physically present, but corrupted, although all
files are digitally signed, and if they fail the digisig test, they're not
supposed to be 'imported' into the content store.
> Is there a means of removing these updates completely and then re-syncing
> them from Microsoft?
Yes. Mark the updates as Declined. Run the Server Cleanup Utility to remove
content for all declined updates. Reapprove the updates.
nqetech
I've tried decling the updates, running the server cleanup wizard and
re-approving them - then running wsusutil reset, all to no avail.
At least 5 WSUS required updates that are set to install by default are
showing that their files need to be downloaded before they will install and
won't download, other updates (like WinXP SP2) that have license terms won't
download their license terms.
I don't think that I have a firewall-related problem as the majority of
other updates appear to have downloaded their files successfully.
As the WSUS updates (that include the Windows Installer 3.1 and BITS
updates) are critical to the functioning of WSUS, I don't see how WSUS is
going to work.
I really am struggling with this.
"Lawrence Garvin (MVP)" wrote:
> .....
>
>
>
nqetech
Please shoot me!
I've discovered (by checking the event logs) that the cause of the problem
was incorrect permissions on the drive where the WSUS content folder is
located.
After adding the 'NT Authority\Network Service' account in the root with
read permissions and checking that the other folder dependencies also had
full control permissions for the same account, the downloads functioned
correctly.
Thanks for all of your help. You were at least able to point me in the right
direction.
David Hicks
Senior Systems Engineer
Newsquest (Essex) Limited
"Lawrence Garvin (MVP)" wrote:
> .....
>
>
>
Lawrence Garvin (MVP)
> I've discovered (by checking the event logs) that the cause of the problem
> was incorrect permissions on the drive where the WSUS content folder is
> located.
>
Well.. *SHUCKS*... I skipped over that possible reason because you told me
that *most* files were downloading, which made me think filesystem
permissions were a non-issue.
> After adding the 'NT Authority\Network Service' account in the root with
> read permissions and checking that the other folder dependencies also had
> full control permissions for the same account, the downloads functioned
> correctly.
Yep.. this is a *known* issue. It's a 'bug' in the .NET Framework v1.1
installer, that doesn't properly set that permission.
It only manifests when the content store is on a non-system drive.
> Thanks for all of your help. You were at least able to point me in the
> right
> direction.
Well, I'm glad I helped somehow, but golly gee, I've known about that
'Network Service' account on the drive permission since the dawn of time,
and didn't think it applied in this case.
I apologize for the complications in getting you the right 'fix' in the
first place.
Luc Van der Veken
One of the updates I can't approve is the September 2010 malicious software removal tool x64 (the x86 version came through OK).
In my case, my WSUS is downstream of another server, as full server, not as a replica.
After searching and trying everything I could imagine on the downstream server, I though it might be a good idea to take a look at the upstream one.
And there, I found a number of messages like this in the event log (I just picked the one at the top, it happens to be about another kind of file, but I suppose the license files will have the same failure reason):
Content file download failed. Reason: The requested URL does not exist on the server.
Source File: /msdownload/v7/driver/drvs/2007/12/driver_c98a5e24caeee8c5f1d1501e494ba30cd94d4046.cab Destination File: E:\WSUS\WsusContent\46\C98A5E24CAEEE8C5F1D1501E494BA30CD94D4046.cab.
That's on the upstream server, i.e. the files don't exist at the windows update website.
>> On Sunday, June 24, 2007 11:02 PM Lawrence Garvin \(MVP\) wrote:
>> "nqetech" <nqe...@discussions.microsoft.com> wrote in message
>> news:84A4F16A-236F-46DD...@microsoft.com...
>>
>>
>> This is not normal behavior, but it does sometimes happen.... reasons not
>> quite known.
>>
>> Try running 'wsusutil reset' to let the WSUS server scan the database for
>> content files that are supposed to exist, but do not. That will regen a BITS
>> download request for the missing files. Monitor the server status and when
>> files to download is zero, try approving the update(s) again.
>>
>>
>> --
>> Lawrence Garvin, M.S., MCTS, MCP
>> Independent WSUS Evangelist
>> MVP-Software Distribution (2005-2007)
>> https://mvp.support.microsoft.com/profile=30E00990-8F1D-4774-BD62-D095EB07B36E
>>
>> Everything you need for WSUS is at
>> http://technet2.microsoft.com/windowsserver/en/technologies/featured/wsus/default.mspx
>>
>> And, almost everything else is at
>> http://wsusinfo.onsitechsolutions.com
>> ....
>>> On Monday, June 25, 2007 6:56 AM nqetec wrote:
>>> Thanks, looks like that might solve the problem. It appears to fix a few at a
>>> time.
>>>
>>> "Lawrence Garvin (MVP)" wrote:
>>>> On Monday, June 25, 2007 9:58 AM nqetec wrote:
>>>> Lawrence,
>>>>
>>>> Further to my previous post, I can't get any further with the following
>>>> updates:
>>>>
>>>> Update for Windows XP (KB920342)
>>>> Windows Malicious Software Removal Tool - June 2007 (KB890830)
>>>> Windows XP Service Pack 2
>>>>
>>>> I've now run 'wsusutil reset' several times. Is there a means of removing
>>>> these updates completely and then re-syncing them from Microsoft?
>>>>
>>>> Obviously, XP SP2 is quite an important update, so being unable to approve
>>>> it is a bit of an issue!
>>>>
>>>> "Lawrence Garvin (MVP)" wrote:
>>>>> On Monday, June 25, 2007 9:44 PM Lawrence Garvin \(MVP\) wrote:
>>>>> "nqetech" <nqe...@discussions.microsoft.com> wrote in message
>>>>> news:79857A92-C08D-44C9...@microsoft.com...
>>>>>
>>>>>
>>>>> It could be the files are physically present, but corrupted, although all
>>>>> files are digitally signed, and if they fail the digisig test, they're not
>>>>> supposed to be 'imported' into the content store.
>>>>>
>>>>>
>>>>> Yes. Mark the updates as Declined. Run the Server Cleanup Utility to remove
>>>>> content for all declined updates. Reapprove the updates.
>>>>>
>>>>>
>>>>> --
>>>>> Lawrence Garvin, M.S., MCTS, MCP
>>>>> Independent WSUS Evangelist
>>>>> MVP-Software Distribution (2005-2007)
>>>>> https://mvp.support.microsoft.com/profile=30E00990-8F1D-4774-BD62-D095EB07B36E
>>>>>
>>>>> Everything you need for WSUS is at
>>>>> http://technet2.microsoft.com/windowsserver/en/technologies/featured/wsus/default.mspx
>>>>>
>>>>> And, almost everything else is at
>>>>> http://wsusinfo.onsitechsolutions.com
>>>>> ....
>>>>>> On Tuesday, June 26, 2007 3:54 AM nqetec wrote:
>>>>>> Sorry Lawrence,
>>>>>>
>>>>>> I've tried decling the updates, running the server cleanup wizard and
>>>>>> re-approving them - then running wsusutil reset, all to no avail.
>>>>>>
>>>>>> At least 5 WSUS required updates that are set to install by default are
>>>>>> showing that their files need to be downloaded before they will install and
>>>>>> won't download, other updates (like WinXP SP2) that have license terms won't
>>>>>> download their license terms.
>>>>>>
>>>>>> I don't think that I have a firewall-related problem as the majority of
>>>>>> other updates appear to have downloaded their files successfully.
>>>>>>
>>>>>> As the WSUS updates (that include the Windows Installer 3.1 and BITS
>>>>>> updates) are critical to the functioning of WSUS, I don't see how WSUS is
>>>>>> going to work.
>>>>>>
>>>>>> I really am struggling with this.
>>>>>>
>>>>>>
>>>>>> "Lawrence Garvin (MVP)" wrote:
>>>>>>> On Tuesday, June 26, 2007 4:25 AM nqetec wrote:
>>>>>>> Hi Lawrence,
>>>>>>>
>>>>>>> Please shoot me!
>>>>>>>
>>>>>>> I've discovered (by checking the event logs) that the cause of the problem
>>>>>>> was incorrect permissions on the drive where the WSUS content folder is
>>>>>>> located.
>>>>>>>
>>>>>>> After adding the 'NT Authority\Network Service' account in the root with
>>>>>>> read permissions and checking that the other folder dependencies also had
>>>>>>> full control permissions for the same account, the downloads functioned
>>>>>>> correctly.
>>>>>>>
>>>>>>> Thanks for all of your help. You were at least able to point me in the right
>>>>>>> direction.
>>>>>>>
>>>>>>> David Hicks
>>>>>>>
>>>>>>> Senior Systems Engineer
>>>>>>> Newsquest (Essex) Limited
>>>>>>>
>>>>>>>
>>>>>>> "Lawrence Garvin (MVP)" wrote:
>>>>>>>> On Tuesday, June 26, 2007 9:19 PM Lawrence Garvin \(MVP\) wrote:
>>>>>>>> "nqetech" <nqe...@discussions.microsoft.com> wrote in message
>>>>>>>> news:A5EC31A5-CE63-4719...@microsoft.com...
>>>>>>>>
>>>>>>>>
>>>>>>>> Well.. *SHUCKS*... I skipped over that possible reason because you told me
>>>>>>>> that *most* files were downloading, which made me think filesystem
>>>>>>>> permissions were a non-issue.
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> Yep.. this is a *known* issue. It's a 'bug' in the .NET Framework v1.1
>>>>>>>> installer, that doesn't properly set that permission.
>>>>>>>>
>>>>>>>> It only manifests when the content store is on a non-system drive.
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> Well, I'm glad I helped somehow, but golly gee, I've known about that
>>>>>>>> 'Network Service' account on the drive permission since the dawn of time,
>>>>>>>> and didn't think it applied in this case.
>>>>>>>>
>>>>>>>> I apologize for the complications in getting you the right 'fix' in the
>>>>>>>> first place.
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> Lawrence Garvin, M.S., MCTS, MCP
>>>>>>>> Independent WSUS Evangelist
>>>>>>>> MVP-Software Distribution (2005-2007)
>>>>>>>> https://mvp.support.microsoft.com/profile=30E00990-8F1D-4774-BD62-D095EB07B36E
>>>>>>>>
>>>>>>>> Everything you need for WSUS is at
>>>>>>>> http://technet2.microsoft.com/windowsserver/en/technologies/featured/wsus/default.mspx
>>>>>>>>
>>>>>>>> And, almost everything else is at
>>>>>>>> http://wsusinfo.onsitechsolutions.com
>>>>>>>> ....
>>>>>>>> Submitted via EggHeadCafe - Software Developer Portal of Choice
>>>>>>>> ObjectDumper LINQ To Export Collection Via .NET Reflection
>>>>>>>> http://www.eggheadcafe.com/tutorials/aspnet/21737599-5a63-4672-a32c-a36cca282a3f/objectdumper-linq-to-export-collection-via-net-reflection.aspx
Luc Van der Veken
One of the updates I can't approve is the September 2010 malicious software removal tool x64 (the x86 version came through OK).
In my case, my WSUS is downstream of another server, as full server, not as a replica.
After searching and trying everything I could imagine on the downstream server, I though it might be a good idea to take a look at the upstream one.
And there, I found a number of messages like this in the event log (I just picked the one at the top, it happens to be about another kind of file, but I suppose the license files will have the same failure reason):
Content file download failed. Reason: The requested URL does not exist on the server.
Source File: /msdownload/v7/driver/drvs/2007/12/driver_c98a5e24caeee8c5f1d1501e494ba30cd94d4046.cab Destination File: E:\WSUS\WsusContent\46\C98A5E24CAEEE8C5F1D1501E494BA30CD94D4046.cab.
That's on the upstream server, i.e. the files don't exist at the windows update website.
> On Sunday, June 24, 2007 5:27 PM nqetec wrote:
>>>>>>>>> On Thursday, September 23, 2010 8:57 AM Luc Van der Veken wrote:
>>>>>>>>> I'm getting the same error on a new WSUS 3.2, 104 security and 10 critical updates I can't approve because the license terms faiuled to download.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> One of the updates I can't approve is the September 2010 malicious software removal tool x64 (the x86 version came through OK).
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> In my case, my WSUS is downstream of another server, as full server, not as a replica.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> After searching and trying everything I could imagine on the downstream server, I though it might be a good idea to take a look at the upstream one.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> And there, I found a number of messages like this in the event log (I just picked the one at the top, it happens to be about another kind of file, but I suppose the license files will have the same failure reason):
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Content file download failed. Reason: The requested URL does not exist on the server.
>>>>>>>>>
>>>>>>>>> Source File: /msdownload/v7/driver/drvs/2007/12/driver_c98a5e24caeee8c5f1d1501e494ba30cd94d4046.cab Destination File: E:\WSUS\WsusContent\46\C98A5E24CAEEE8C5F1D1501E494BA30CD94D4046.cab.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> That's on the upstream server, i.e. the files don't exist at the windows update website.
>>>>>>>>> Submitted via EggHeadCafe - Software Developer Portal of Choice
>>>>>>>>> Silverlight Binary Serialization and Compression with WCF Services
>>>>>>>>> http://www.eggheadcafe.com/tutorials/aspnet/96487d4c-d92f-4ca5-85b7-0fef6f42d6c3/silverlight-binary-serialization-and-compression-with-wcf-services.aspx
Harry Johnston
> I'm getting the same error on a new WSUS 3.2, 104 security and 10 critical
> updates I can't approve because the license terms faiuled to download. [...]
>
> Content file download failed. Reason: The requested URL does not exist on the
> server. Source File:
> /msdownload/v7/driver/drvs/2007/12/driver_c98a5e24caeee8c5f1d1501e494ba30cd94d4046.cab
> Destination File:
> E:\WSUS\WsusContent\46\C98A5E24CAEEE8C5F1D1501E494BA30CD94D4046.cab.
>
> That's on the upstream server, i.e. the files don't exist at the windows
> update website.
This sort of error is often due to a proxy server or hardware firewall
interfering with the download, typically because it has been programmed to block
.cab files.
Otherwise, I suggest you try the web forum, details below.
Harry.
--
PS: if it seems quiet in here, that's because Microsoft have closed this newsgroup.
You might want to consider visiting the appropriate web forum instead.
WSUS: http://go.microsoft.com/fwlink/?LinkID=161025
Windows Update: http://social.answers.microsoft.com/Forums/en-US/vistawu/threads