|
|
Ok, I know quite a few people have commented on it already. And it seems to
me that WSUS 3.0 is broken. I never had a problem with WSUS 2.0 w/ SP1, and
it automatically upgraded to WSUS 3.0 and my problems started. First off,
WSUS 3.0 would not download any of the newly approved files. So I followed
the troubleshooting and still does not work. My WSUS content drive has
NETWORK SERVICE and EVERYONE having at least read, while the NETWORK SERVICE
actually has read and write. I tried redoing my proxy settings to no avail
and have even removed and reinstalled WSUS 3.0. Now I have like 12 GB worth
of downloads to do and it will not download them one bit. Here is the setup
I am running WSUS 3.0 on a Windows Server 2003 box with SQL 2005. Disk space
is not the problem as I have 50 GB designated for WSUS alone. Now it goes
through my proxy server, as does everything else, which is a Windows 2003 box
running ISA Server 2006 Enterprise. From the WSUS box I can use the internet
and connect to the internet and even go to Microsoft Update and do updates
that way. So there is no way that my machine is broke. All that I can
figure is that the software is broken. That means it is in your court
Microsoft... WSUS 3.0 is definately broken, whether it is a install
configuration glitch or something, something don't work, I probably agree
with everyone that is having these problems that you need to figure out where
the glitch is and repair it. But if you can fix my problem in the mean time,
I'm all for it.
|
|
"Michael R. Mastro II" <MichaelRMastroII[ at ]discussions.microsoft.com> wrote in
message news:F2897DD8-9587-458C-AA38-DCDC95690994[ at ]microsoft.com...
[Quoted Text] > Ok, I know quite a few people have commented on it already. And it seems
> to
> me that WSUS 3.0 is broken. I never had a problem with WSUS 2.0 w/ SP1,
> and
> it automatically upgraded to WSUS 3.0 and my problems started.
First question: Did you review the Release Notes for WSUS 3.0 prior to
approving the product for upgrade?
> First off,
> WSUS 3.0 would not download any of the newly approved files. So I
> followed
> the troubleshooting and still does not work.
Before we dive off into the dozens of things you've "tried", what is the
*REAL* error? Review the Application Event Log and post the *actual* error
showing a download failure.
> Now I have like 12 GB worth
> of downloads to do and it will not download them one bit.
You got =12GB= of extra updates to download just from upgrading your system
from WSUS2.0 to WSUS 3.0<???>
> Now it goes
> through my proxy server, as does everything else, which is a Windows 2003
> box
> running ISA Server 2006 Enterprise. From the WSUS box I can use the
> internet
> and connect to the internet and even go to Microsoft Update and do updates
> that way. So there is no way that my machine is broke.
All of which is totally inconclusive, since WSUS uses =WinHTTP=, not
Internet Explorer. The only thing you've proven here is that your Internet
connection is not broken. You have *not* proven that there's nothing wrong
with the WSUS server.
> All that I can
> figure is that the software is broken. That means it is in your court
> Microsoft... WSUS 3.0 is definately broken, whether it is a install
> configuration glitch or something, something don't work, I probably agree
> with everyone that is having these problems that you need to figure out
> where
> the glitch is and repair it. But if you can fix my problem in the mean
> time,
> I'm all for it.
Well, that kinda depends on whether you've read the documentation (probably
not); whether we find out if your issue is caused by something documented
that you failed to do (most likely), or is actually being caused by
something never before seen (highly unlikely).
As for it being in "Microsoft's court"... I'm not Microsoft, so if you want
this to be in Microsoft's court, you'll need to pick up the phone and call
PSS, and pay them $$$ -- or you could lose the attitude, and I'll do my best
to help you here for FREE.
--
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://www.microsoft.com/wsus
And, almost everything else is at
http://wsusinfo.onsitechsolutions.com
.....
|
|
"Lawrence Garvin (MVP)" wrote:
[Quoted Text] > "Michael R. Mastro II" <MichaelRMastroII[ at ]discussions.microsoft.com> wrote in
> message news:F2897DD8-9587-458C-AA38-DCDC95690994[ at ]microsoft.com...
> > Ok, I know quite a few people have commented on it already. And it seems
> > to
> > me that WSUS 3.0 is broken. I never had a problem with WSUS 2.0 w/ SP1,
> > and
> > it automatically upgraded to WSUS 3.0 and my problems started.
>
> First question: Did you review the Release Notes for WSUS 3.0 prior to
> approving the product for upgrade?
Yes I reviewed the release notes. I also at that time, reset the proxy
server password in WSUS.
> > First off,
> > WSUS 3.0 would not download any of the newly approved files. So I
> > followed
> > the troubleshooting and still does not work.
>
> Before we dive off into the dozens of things you've "tried", what is the
> *REAL* error? Review the Application Event Log and post the *actual* error
> showing a download failure.
OK here is one of the latest failures I have gotten:
Event Type: Error
Event Source: Windows Server Update Services
Event Category: Synchronization
Event ID: 364
Date: 7/6/2007
Time: 8:58:24 PM
User: N/A
Computer: SERVER1
Description:
Content file download failed. Reason: Cannot complete this function.
Source File: /msdownload/update/v5/eula/xpsp2eula_fin.txt Destination File:
I:\WSUS\WsusContent\97\D1F77729939A8D41169630DA1BC0B1C3BF3A1797.txt.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Now I have done the following to try and fix this:
Open a command window.
Type sc config bits start= auto
Type net stop bits && net start bits
Type net stop wsusservice && net start wsusservice
Start WSUS 3.0: Click Start, click Administrative Tools, then click
Microsoft Windows Server Update Services v3.0.
Click Synchronization Results.
In the Action pane, click Synchronize Now.
Verify
Look for the corresponding error event.
Open a command window.
Type cd <WSUSInstallDir>\Tools
Type wsusutil checkhealth
Type eventvwr
Review the Application log for the most recent events from source Windows
Server Update Services and event id 10030.
Now I am also getting the following error:
Event Type: Error
Event Source: Windows Server Update Services
Event Category: Core
Event ID: 10032
Date: 7/2/2007
Time: 11:09:53 PM
User: N/A
Computer: SERVER1
Description:
The server is failing to download some updates.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Also have not a had a 10030 event id ever.
> > Now I have like 12 GB worth
> > of downloads to do and it will not download them one bit.
>
> You got =12GB= of extra updates to download just from upgrading your system
> from WSUS2.0 to WSUS 3.0<???>
No the 12 GB worth of downloaded files is from doing a clean reinstall of
WSUS. Which it is not downloading. Goes to say that I cannot even approve
half the files anyways because of the EULA's not downloading.
> > Now it goes
> > through my proxy server, as does everything else, which is a Windows 2003
> > box
> > running ISA Server 2006 Enterprise. From the WSUS box I can use the
> > internet
> > and connect to the internet and even go to Microsoft Update and do updates
> > that way. So there is no way that my machine is broke.
>
> All of which is totally inconclusive, since WSUS uses =WinHTTP=, not
> Internet Explorer. The only thing you've proven here is that your Internet
> connection is not broken. You have *not* proven that there's nothing wrong
> with the WSUS server.
Well if it worked with WSUS 2.0 and not WSUS 3.0 there must be something
wrong. Even restarting all internet services has done nothing.
> > All that I can
> > figure is that the software is broken. That means it is in your court
> > Microsoft... WSUS 3.0 is definately broken, whether it is a install
> > configuration glitch or something, something don't work, I probably agree
> > with everyone that is having these problems that you need to figure out
> > where
> > the glitch is and repair it. But if you can fix my problem in the mean
> > time,
> > I'm all for it.
>
>
> Well, that kinda depends on whether you've read the documentation (probably
> not); whether we find out if your issue is caused by something documented
> that you failed to do (most likely), or is actually being caused by
> something never before seen (highly unlikely).
>
> As for it being in "Microsoft's court"... I'm not Microsoft, so if you want
> this to be in Microsoft's court, you'll need to pick up the phone and call
> PSS, and pay them $$$ -- or you could lose the attitude, and I'll do my best
> to help you here for FREE.
I have read the documentation. Is it possible I missed something. Yeah, I
am human, I do make mistakes. But I also know that when you see people
having the same problem over and over again there is a trend. Believe me I
work Quality Assurance, I am always looking for trends, whether it is the
fault of the people that fix our aircraft or the fault of the people that fix
the parts. I notice trends. There have been so many posts on this same
problem with WSUS 3.0. To me that seems to be a trend, and yes I have also
followed most of those posts to try and fix this problem. I was just venting
a little frustration when I said that, which could be understandable. But
also maybe I was thinking out loud that why would Microsoft put out a product
that is causing such problems for a lot of people. I never said that any of
the people on the newsgroup worked for Microsoft. But maybe someone that
does work for Microsoft might have read it and do a little back searching.
> --
> 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://www.microsoft.com/wsus
>
> And, almost everything else is at
> http://wsusinfo.onsitechsolutions.com
> .....
|
|
"Michael R. Mastro II" <MichaelRMastroII[ at ]discussions.microsoft.com> wrote in
message news:AEB44301-E5FF-4B03-A3C3-D7BF568C4C56[ at ]microsoft.com...
[Quoted Text] >> > First off,
>> > WSUS 3.0 would not download any of the newly approved files. So I
>> > followed
>> > the troubleshooting and still does not work.
>> Before we dive off into the dozens of things you've "tried", what is the
>> *REAL* error? Review the Application Event Log and post the *actual*
>> error
>> showing a download failure.
> OK here is one of the latest failures I have gotten:
>
> Event Type: Error
> Event Source: Windows Server Update Services
> Event Category: Synchronization
> Event ID: 364
> Date: 7/6/2007
> Time: 8:58:24 PM
> User: N/A
> Computer: SERVER1
> Description:
> Content file download failed. Reason: Cannot complete this function.
Hmmmm. Interesting.. I must admit I've *never* seen a "Cannot complete this
function" error in a WSUS scenario before.
> Source File: /msdownload/update/v5/eula/xpsp2eula_fin.txt Destination
> File:
> I:\WSUS\WsusContent\97\D1F77729939A8D41169630DA1BC0B1C3BF3A1797.txt.
But one thing I do notice is that your ~\WSUS folder is on drive I:
Is drive I: a local drive, or a network drive?
If it's a local drive, does the NT AUTHORITY\Network Service have READ
permissions on drive I: ?
If it's a network drive, that's most likely the source of your error.
Was the WSUS 2.0 content store also on drive I:?
>> > Now I have like 12 GB worth
>> > of downloads to do and it will not download them one bit.
>> You got =12GB= of extra updates to download just from upgrading your
>> system
>> from WSUS2.0 to WSUS 3.0<???>
> No the 12 GB worth of downloaded files is from doing a clean reinstall of
> WSUS. Which it is not downloading.
Oh! Now that's also useful information, and radically different than from
what you implied in your original post which was that this was an upgraded
machine that was not working. In fact, we're talking about a *clean* install
of WSUS 3.0, so that opens up a whole new set of possibilities! The formerly
working WSUS 2.0 server is now, for all purposes, irrelevant to this issue.
>> All of which is totally inconclusive, since WSUS uses =WinHTTP=, not
>> Internet Explorer. The only thing you've proven here is that your
>> Internet
>> connection is not broken. You have *not* proven that there's nothing
>> wrong
>> with the WSUS server.
>
> Well if it worked with WSUS 2.0 and not WSUS 3.0 there must be something
> wrong.
Obviously!.. there is something wrong. I never challenged that assertion. My
only point was that certain pieces of information are irrelevant to the
diagnostic situation. Whether or not you can access the Internet with
Internet Explorer is generally irrelevant, unless you'd determined from that
test that your entire Internet link were down. But if that was the case,
your WSUS server would be failing to synchronize, not failing to download.
>> Well, that kinda depends on whether you've read the documentation
>> (probably
>> not); whether we find out if your issue is caused by something documented
>> that you failed to do (most likely), or is actually being caused by
>> something never before seen (highly unlikely).
>>
>> As for it being in "Microsoft's court"... I'm not Microsoft, so if you
>> want
>> this to be in Microsoft's court, you'll need to pick up the phone and
>> call
>> PSS, and pay them $$$ -- or you could lose the attitude, and I'll do my
>> best
>> to help you here for FREE.
>
> I have read the documentation. Is it possible I missed something. Yeah,
> I
> am human, I do make mistakes. But I also know that when you see people
> having the same problem over and over again there is a trend.
Yes. You're right. Almost always there is a trend. And without intending to
step on anybody's toes, the facts are that in the past 2 years of WSUS, 95%
of those "trends" have been directly attributable to configuration errors
(human caused) and/or failing to read the documentation.
Probably the only "trend" that I've observed that is not one of those two
cases are the BITS/HTTP v1.1 issues with Sonicwall firewalls.
>There have been so many posts on this same
> problem with WSUS 3.0. To me that seems to be a trend,
To be absolutely accurate, your problem, as reported, is the FIRST of its
kind. The error messages you cited here have *never* been previously
reported. Now, general issues with downloading content have occurred quite
often, and we've identified a short list of causes over the past two years
that accounts for 85% of the cases. The remaining 14% were Sonicwall issues
(maybe even a higher percentage), and every once in a while something comes
along that doesn't fall into these known buckets of cause. Once we identify
your specific issue and resolution, we'll know whether your just another one
of those 'bucket' cases (albeit with a unique error message), or if your
scenario was never-before-seen.
> and yes I have also
> followed most of those posts to try and fix this problem. I was just
> venting
> a little frustration when I said that, which could be understandable. But
> also maybe I was thinking out loud that why would Microsoft put out a
> product
> that is causing such problems for a lot of people.
If you'd followed most of the posts in the past couple of years, you'd also
recognize that the majority of issues are of the two types I noted above,
either misconfigurations in WSUS, or some other system in the network, or
simple failure to review the supplied documentation. Microsoft did *not*
"put out a product that is causing such problems for a lot of people", but
the "people" are causing a lot of their own problems by not being properly
prepared to install the product.
So.. continuing on... and back to your ISA Server 2006... which seems to be
the most likely culprit at this moment...
Since you installed WSUS 3.0 from scratch, we should look at:
[a] The WinHTTP configuration on your WSUS Server. (Please post the
output from the proxycfg.exe command.)
[b] The Proxy Configuration in your WSUS Server Options | Proxy Server
setup screen. (Do you have the proxy options configured?)
[c] A statement as to whether you've enabled the proxy server in ISA
2006, and if so, whether it *requires* authentication, and if so, what form
of authentication does it require. (And, do these match the configuration
set in the WSUS proxy options?)
[d] Confirmation that you have an access rule configured for the =WSUS
Server= allowing access on both HTTP (80) and HTTPS (443) protocols. (This
would seem to be the case, but if you're using proxy authentication, your
successful access via IE may also be because you were logged on with an
admin account which has unrestricted access<??>)
[e] Confirmation that nothing in the ISA Server has been enabled to
restrict downloading of files from the Internet by/to the WSUS Server.
[f] Confirmation that nothing on the WSUS Server has been enabled to
prevent writing of files to the designated destination drive/folder. (i.e.
I:\WSUS)
--
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://www.microsoft.com/wsus
And, almost everything else is at
http://wsusinfo.onsitechsolutions.com
.....
|
|
|