Service Unavailable

I have WUS installed on port 8530 on a WIN2k3 server... I get the following
error message when trying to view the WUS Admin Page through IE: Service
Unavailable. I have also installed it on port 80 with the same results. The
installation completed successfully and there were no error messages logged.
Anyone have this same problem or know what is going on? The only thing is
that I did it through Terminal Services logged on as the Administrator... I
plan on trying from the console this week but can't see where that would make
a difference. Thanks in advance :)

Posting the complete message would help.. but I suspect it has to do with
"Selfupdate", given that this is a new installation.

Assuming that... check this article for resolutions to that condition:
http://wsusinfo.onsitechsolutions.com/articles/020.htm
"What does WSUS mean by "Selfupdate service not running"?"

"DFJosey" <DFJosey@discussions.microsoft.com> wrote in message
news:B393D0DD-94E8-47CD-AC8D-A9801E92D702@microsoft.com...
>I have WUS installed on port 8530 on a WIN2k3 server... I get the following
> error message when trying to view the WUS Admin Page through IE: Service
> Unavailable. I have also installed it on port 80 with the same results.
> The
> installation completed successfully and there were no error messages
> logged.
> Anyone have this same problem or know what is going on? The only thing is
> that I did it through Terminal Services logged on as the Administrator...
> I
> plan on trying from the console this week but can't see where that would
> make
> a difference. Thanks in advance :)

Lawrence,

Thanks for the reply... The error message I mentioned is the complete
message "Service Unavailable". I get this when I try to access the WUS Admin
Page. I get nothing else. I don't think it has to do with any self updates
as it appears I can't even access the Admin Page. Any other ideas?

Thanks,

Dave

"Lawrence Garvin (MVP)" wrote:

> Posting the complete message would help.. but I suspect it has to do with
> "Selfupdate", given that this is a new installation.
>
> Assuming that... check this article for resolutions to that condition:
> http://wsusinfo.onsitechsolutions.com/articles/020.htm
> "What does WSUS mean by "Selfupdate service not running"?"
>
> "DFJosey" <DFJosey@discussions.microsoft.com> wrote in message
> news:B393D0DD-94E8-47CD-AC8D-A9801E92D702@microsoft.com...
> >I have WUS installed on port 8530 on a WIN2k3 server... I get the following
> > error message when trying to view the WUS Admin Page through IE: Service
> > Unavailable. I have also installed it on port 80 with the same results.
> > The
> > installation completed successfully and there were no error messages
> > logged.
> > Anyone have this same problem or know what is going on? The only thing is
> > that I did it through Terminal Services logged on as the Administrator...
> > I
> > plan on trying from the console this week but can't see where that would
> > make
> > a difference. Thanks in advance :)
>
>
>

Frankly, I've never heard of a message that terse.... but the only thing
that could possibly cause a message that terse would be the "Update
Services" service not being started.

Even that, though, generates a longer message.

Can you confirm that the build number is 2.0.0.2472?

"DFJosey" <DFJosey@discussions.microsoft.com> wrote in message
news:71D32569-C18B-464E-8B19-B07CF8C13E6C@microsoft.com...
> Lawrence,
>
> Thanks for the reply... The error message I mentioned is the complete
> message "Service Unavailable". I get this when I try to access the WUS
> Admin
> Page. I get nothing else. I don't think it has to do with any self
> updates
> as it appears I can't even access the Admin Page. Any other ideas?
>
> Thanks,
>
> Dave
>
> "Lawrence Garvin (MVP)" wrote:
>
>> Posting the complete message would help.. but I suspect it has to do with
>> "Selfupdate", given that this is a new installation.
>>
>> Assuming that... check this article for resolutions to that condition:
>> http://wsusinfo.onsitechsolutions.com/articles/020.htm
>> "What does WSUS mean by "Selfupdate service not running"?"
>>
>> "DFJosey" <DFJosey@discussions.microsoft.com> wrote in message
>> news:B393D0DD-94E8-47CD-AC8D-A9801E92D702@microsoft.com...
>> >I have WUS installed on port 8530 on a WIN2k3 server... I get the
>> >following
>> > error message when trying to view the WUS Admin Page through IE:
>> > Service
>> > Unavailable. I have also installed it on port 80 with the same
>> > results.
>> > The
>> > installation completed successfully and there were no error messages
>> > logged.
>> > Anyone have this same problem or know what is going on? The only thing
>> > is
>> > that I did it through Terminal Services logged on as the
>> > Administrator...
>> > I
>> > plan on trying from the console this week but can't see where that
>> > would
>> > make
>> > a difference. Thanks in advance :)
>>
>>
>>

Lawrence,

I can't find the build number but the version number of the setup file is
5.4.3790.2472 and was just downloaded. I show all services as started, I
have verified all the settings of IIS are set correctly according to
Microsoft as well. Is there any known problems running WUS with Backup Exec?
My thought is that Backup Exec runs using a SQL desktop version as well.

Thanks again,

Dave

"Lawrence Garvin (MVP)" wrote:

> Frankly, I've never heard of a message that terse.... but the only thing
> that could possibly cause a message that terse would be the "Update
> Services" service not being started.
>
> Even that, though, generates a longer message.
>
> Can you confirm that the build number is 2.0.0.2472?
>
> "DFJosey" <DFJosey@discussions.microsoft.com> wrote in message
> news:71D32569-C18B-464E-8B19-B07CF8C13E6C@microsoft.com...
> > Lawrence,
> >
> > Thanks for the reply... The error message I mentioned is the complete
> > message "Service Unavailable". I get this when I try to access the WUS
> > Admin
> > Page. I get nothing else. I don't think it has to do with any self
> > updates
> > as it appears I can't even access the Admin Page. Any other ideas?
> >
> > Thanks,
> >
> > Dave
> >
> > "Lawrence Garvin (MVP)" wrote:
> >
> >> Posting the complete message would help.. but I suspect it has to do with
> >> "Selfupdate", given that this is a new installation.
> >>
> >> Assuming that... check this article for resolutions to that condition:
> >> http://wsusinfo.onsitechsolutions.com/articles/020.htm
> >> "What does WSUS mean by "Selfupdate service not running"?"
> >>
> >> "DFJosey" <DFJosey@discussions.microsoft.com> wrote in message
> >> news:B393D0DD-94E8-47CD-AC8D-A9801E92D702@microsoft.com...
> >> >I have WUS installed on port 8530 on a WIN2k3 server... I get the
> >> >following
> >> > error message when trying to view the WUS Admin Page through IE:
> >> > Service
> >> > Unavailable. I have also installed it on port 80 with the same
> >> > results.
> >> > The
> >> > installation completed successfully and there were no error messages
> >> > logged.
> >> > Anyone have this same problem or know what is going on? The only thing
> >> > is
> >> > that I did it through Terminal Services logged on as the
> >> > Administrator...
> >> > I
> >> > plan on trying from the console this week but can't see where that
> >> > would
> >> > make
> >> > a difference. Thanks in advance :)
> >>
> >>
> >>
>
>
>

"DFJosey" <DFJosey@discussions.microsoft.com> wrote in message
news:D0074AB3-56E9-43EF-AB32-4955CB655E23@microsoft.com...
> Lawrence,
>
> I can't find the build number but the version number of the setup file is
> 5.4.3790.2472 and was just downloaded.

The build number is displayed in the lower left corner of the WSUS
Administration Console Home Page, right under where you would be observing
this "Service Unavailable" error message.

The version number of the setup file is correct for the "gold" code package.

> I show all services as started, I
> have verified all the settings of IIS are set correctly according to
> Microsoft as well. Is there any known problems running WUS with Backup
> Exec?
> My thought is that Backup Exec runs using a SQL desktop version as well.

There are no known issues, and several installations are operating in
production. Backup Exec does use MSDE, however, it uses a different instance
name. WSUS uses it's own instance name of (W)MSDE, which is "WSUS" and will
not conflict with any other MSDE-based application that we know of.

If you would like to send me a screen shot of that message to: l r g a r v i
n @ s w b e l l . n e t

I'll see if I can glean any additional clues as to the problem.

Also, a screen shot of services.mmc in full screen mode with all four
columns expanded for readability showing the following services would also
be useful:
Automatic Updates
Background Intelligent Transfer Service
IIS Admin
MSSQL$WSUS
Update Services
World Wide Web Publishing Service


> Thanks again,
>
> Dave
>
> "Lawrence Garvin (MVP)" wrote:
>
>> Frankly, I've never heard of a message that terse.... but the only thing
>> that could possibly cause a message that terse would be the "Update
>> Services" service not being started.
>>
>> Even that, though, generates a longer message.
>>
>> Can you confirm that the build number is 2.0.0.2472?
>>
>> "DFJosey" <DFJosey@discussions.microsoft.com> wrote in message
>> news:71D32569-C18B-464E-8B19-B07CF8C13E6C@microsoft.com...
>> > Lawrence,
>> >
>> > Thanks for the reply... The error message I mentioned is the complete
>> > message "Service Unavailable". I get this when I try to access the WUS
>> > Admin
>> > Page. I get nothing else. I don't think it has to do with any self
>> > updates
>> > as it appears I can't even access the Admin Page. Any other ideas?
>> >
>> > Thanks,
>> >
>> > Dave
>> >
>> > "Lawrence Garvin (MVP)" wrote:
>> >
>> >> Posting the complete message would help.. but I suspect it has to do
>> >> with
>> >> "Selfupdate", given that this is a new installation.
>> >>
>> >> Assuming that... check this article for resolutions to that condition:
>> >> http://wsusinfo.onsitechsolutions.com/articles/020.htm
>> >> "What does WSUS mean by "Selfupdate service not running"?"
>> >>
>> >> "DFJosey" <DFJosey@discussions.microsoft.com> wrote in message
>> >> news:B393D0DD-94E8-47CD-AC8D-A9801E92D702@microsoft.com...
>> >> >I have WUS installed on port 8530 on a WIN2k3 server... I get the
>> >> >following
>> >> > error message when trying to view the WUS Admin Page through IE:
>> >> > Service
>> >> > Unavailable. I have also installed it on port 80 with the same
>> >> > results.
>> >> > The
>> >> > installation completed successfully and there were no error messages
>> >> > logged.
>> >> > Anyone have this same problem or know what is going on? The only
>> >> > thing
>> >> > is
>> >> > that I did it through Terminal Services logged on as the
>> >> > Administrator...
>> >> > I
>> >> > plan on trying from the console this week but can't see where that
>> >> > would
>> >> > make
>> >> > a difference. Thanks in advance :)
>> >>
>> >>
>> >>
>>
>>
>>

Lawrence,

I would be able to get the build number if I could actually get to the admin
page but... that is the problem. I can't get to the admin page. I will send
you a screen shot to your email.

Thanks,

Dave

"Lawrence Garvin (MVP)" wrote:

>
> "DFJosey" <DFJosey@discussions.microsoft.com> wrote in message
> news:D0074AB3-56E9-43EF-AB32-4955CB655E23@microsoft.com...
> > Lawrence,
> >
> > I can't find the build number but the version number of the setup file is
> > 5.4.3790.2472 and was just downloaded.
>
> The build number is displayed in the lower left corner of the WSUS
> Administration Console Home Page, right under where you would be observing
> this "Service Unavailable" error message.
>
> The version number of the setup file is correct for the "gold" code package.
>
> > I show all services as started, I
> > have verified all the settings of IIS are set correctly according to
> > Microsoft as well. Is there any known problems running WUS with Backup
> > Exec?
> > My thought is that Backup Exec runs using a SQL desktop version as well.
>
> There are no known issues, and several installations are operating in
> production. Backup Exec does use MSDE, however, it uses a different instance
> name. WSUS uses it's own instance name of (W)MSDE, which is "WSUS" and will
> not conflict with any other MSDE-based application that we know of.
>
> If you would like to send me a screen shot of that message to: l r g a r v i
> n @ s w b e l l . n e t
>
> I'll see if I can glean any additional clues as to the problem.
>
> Also, a screen shot of services.mmc in full screen mode with all four
> columns expanded for readability showing the following services would also
> be useful:
> Automatic Updates
> Background Intelligent Transfer Service
> IIS Admin
> MSSQL$WSUS
> Update Services
> World Wide Web Publishing Service
>
>
> > Thanks again,
> >
> > Dave
> >
> > "Lawrence Garvin (MVP)" wrote:
> >
> >> Frankly, I've never heard of a message that terse.... but the only thing
> >> that could possibly cause a message that terse would be the "Update
> >> Services" service not being started.
> >>
> >> Even that, though, generates a longer message.
> >>
> >> Can you confirm that the build number is 2.0.0.2472?
> >>
> >> "DFJosey" <DFJosey@discussions.microsoft.com> wrote in message
> >> news:71D32569-C18B-464E-8B19-B07CF8C13E6C@microsoft.com...
> >> > Lawrence,
> >> >
> >> > Thanks for the reply... The error message I mentioned is the complete
> >> > message "Service Unavailable". I get this when I try to access the WUS
> >> > Admin
> >> > Page. I get nothing else. I don't think it has to do with any self
> >> > updates
> >> > as it appears I can't even access the Admin Page. Any other ideas?
> >> >
> >> > Thanks,
> >> >
> >> > Dave
> >> >
> >> > "Lawrence Garvin (MVP)" wrote:
> >> >
> >> >> Posting the complete message would help.. but I suspect it has to do
> >> >> with
> >> >> "Selfupdate", given that this is a new installation.
> >> >>
> >> >> Assuming that... check this article for resolutions to that condition:
> >> >> http://wsusinfo.onsitechsolutions.com/articles/020.htm
> >> >> "What does WSUS mean by "Selfupdate service not running"?"
> >> >>
> >> >> "DFJosey" <DFJosey@discussions.microsoft.com> wrote in message
> >> >> news:B393D0DD-94E8-47CD-AC8D-A9801E92D702@microsoft.com...
> >> >> >I have WUS installed on port 8530 on a WIN2k3 server... I get the
> >> >> >following
> >> >> > error message when trying to view the WUS Admin Page through IE:
> >> >> > Service
> >> >> > Unavailable. I have also installed it on port 80 with the same
> >> >> > results.
> >> >> > The
> >> >> > installation completed successfully and there were no error messages
> >> >> > logged.
> >> >> > Anyone have this same problem or know what is going on? The only
> >> >> > thing
> >> >> > is
> >> >> > that I did it through Terminal Services logged on as the
> >> >> > Administrator...
> >> >> > I
> >> >> > plan on trying from the console this week but can't see where that
> >> >> > would
> >> >> > make
> >> >> > a difference. Thanks in advance :)
> >> >>
> >> >>
> >> >>
> >>
> >>
> >>
>
>
>

So I now understand... having seen the actual screen dump. Thank you for
sending that over, it helped me tremendously.

For the benefit of the group, Dave isn't even getting the default.aspx page
to load, but is getting an error message, either from IIS or from ASP.NET (I
haven't determined which yet) -- my working theory is that it's from IIS and
caused by some inability to engage the ASP.NET services.

I'll followup with additional information as it becomes available.

"DFJosey" <DFJosey@discussions.microsoft.com> wrote in message
news:E6883C3B-26E3-4D1F-9FCD-CA7AD28A29A3@microsoft.com...
> Lawrence,
>
> I would be able to get the build number if I could actually get to the
> admin
> page but... that is the problem. I can't get to the admin page. I will
> send
> you a screen shot to your email.
>
> Thanks,
>
> Dave
>
> "Lawrence Garvin (MVP)" wrote:
>
>>
>> "DFJosey" <DFJosey@discussions.microsoft.com> wrote in message
>> news:D0074AB3-56E9-43EF-AB32-4955CB655E23@microsoft.com...
>> > Lawrence,
>> >
>> > I can't find the build number but the version number of the setup file
>> > is
>> > 5.4.3790.2472 and was just downloaded.
>>
>> The build number is displayed in the lower left corner of the WSUS
>> Administration Console Home Page, right under where you would be
>> observing
>> this "Service Unavailable" error message.
>>
>> The version number of the setup file is correct for the "gold" code
>> package.
>>
>> > I show all services as started, I
>> > have verified all the settings of IIS are set correctly according to
>> > Microsoft as well. Is there any known problems running WUS with Backup
>> > Exec?
>> > My thought is that Backup Exec runs using a SQL desktop version as
>> > well.
>>
>> There are no known issues, and several installations are operating in
>> production. Backup Exec does use MSDE, however, it uses a different
>> instance
>> name. WSUS uses it's own instance name of (W)MSDE, which is "WSUS" and
>> will
>> not conflict with any other MSDE-based application that we know of.
>>
>> If you would like to send me a screen shot of that message to: l r g a r
>> v i
>> n @ s w b e l l . n e t
>>
>> I'll see if I can glean any additional clues as to the problem.
>>
>> Also, a screen shot of services.mmc in full screen mode with all four
>> columns expanded for readability showing the following services would
>> also
>> be useful:
>> Automatic Updates
>> Background Intelligent Transfer Service
>> IIS Admin
>> MSSQL$WSUS
>> Update Services
>> World Wide Web Publishing Service
>>
>>
>> > Thanks again,
>> >
>> > Dave
>> >
>> > "Lawrence Garvin (MVP)" wrote:
>> >
>> >> Frankly, I've never heard of a message that terse.... but the only
>> >> thing
>> >> that could possibly cause a message that terse would be the "Update
>> >> Services" service not being started.
>> >>
>> >> Even that, though, generates a longer message.
>> >>
>> >> Can you confirm that the build number is 2.0.0.2472?
>> >>
>> >> "DFJosey" <DFJosey@discussions.microsoft.com> wrote in message
>> >> news:71D32569-C18B-464E-8B19-B07CF8C13E6C@microsoft.com...
>> >> > Lawrence,
>> >> >
>> >> > Thanks for the reply... The error message I mentioned is the
>> >> > complete
>> >> > message "Service Unavailable". I get this when I try to access the
>> >> > WUS
>> >> > Admin
>> >> > Page. I get nothing else. I don't think it has to do with any self
>> >> > updates
>> >> > as it appears I can't even access the Admin Page. Any other ideas?
>> >> >
>> >> > Thanks,
>> >> >
>> >> > Dave
>> >> >
>> >> > "Lawrence Garvin (MVP)" wrote:
>> >> >
>> >> >> Posting the complete message would help.. but I suspect it has to
>> >> >> do
>> >> >> with
>> >> >> "Selfupdate", given that this is a new installation.
>> >> >>
>> >> >> Assuming that... check this article for resolutions to that
>> >> >> condition:
>> >> >> http://wsusinfo.onsitechsolutions.com/articles/020.htm
>> >> >> "What does WSUS mean by "Selfupdate service not running"?"
>> >> >>
>> >> >> "DFJosey" <DFJosey@discussions.microsoft.com> wrote in message
>> >> >> news:B393D0DD-94E8-47CD-AC8D-A9801E92D702@microsoft.com...
>> >> >> >I have WUS installed on port 8530 on a WIN2k3 server... I get the
>> >> >> >following
>> >> >> > error message when trying to view the WUS Admin Page through IE:
>> >> >> > Service
>> >> >> > Unavailable. I have also installed it on port 80 with the same
>> >> >> > results.
>> >> >> > The
>> >> >> > installation completed successfully and there were no error
>> >> >> > messages
>> >> >> > logged.
>> >> >> > Anyone have this same problem or know what is going on? The only
>> >> >> > thing
>> >> >> > is
>> >> >> > that I did it through Terminal Services logged on as the
>> >> >> > Administrator...
>> >> >> > I
>> >> >> > plan on trying from the console this week but can't see where
>> >> >> > that
>> >> >> > would
>> >> >> > make
>> >> >> > a difference. Thanks in advance :)
>> >> >>
>> >> >>
>> >> >>
>> >>
>> >>
>> >>
>>
>>
>>

Any news or progress on this? I am having the same problems & have
un-installed & reinstalled many times. Tried on the default port 80 & the
special 8530.

"Lawrence Garvin (MVP)" wrote:

> So I now understand... having seen the actual screen dump. Thank you for
> sending that over, it helped me tremendously.
>
> For the benefit of the group, Dave isn't even getting the default.aspx page
> to load, but is getting an error message, either from IIS or from ASP.NET (I
> haven't determined which yet) -- my working theory is that it's from IIS and
> caused by some inability to engage the ASP.NET services.
>
> I'll followup with additional information as it becomes available.
>
> "DFJosey" <DFJosey@discussions.microsoft.com> wrote in message
> news:E6883C3B-26E3-4D1F-9FCD-CA7AD28A29A3@microsoft.com...
> > Lawrence,
> >
> > I would be able to get the build number if I could actually get to the
> > admin
> > page but... that is the problem. I can't get to the admin page. I will
> > send
> > you a screen shot to your email.
> >
> > Thanks,
> >
> > Dave
> >
> > "Lawrence Garvin (MVP)" wrote:
> >
> >>
> >> "DFJosey" <DFJosey@discussions.microsoft.com> wrote in message
> >> news:D0074AB3-56E9-43EF-AB32-4955CB655E23@microsoft.com...
> >> > Lawrence,
> >> >
> >> > I can't find the build number but the version number of the setup file
> >> > is
> >> > 5.4.3790.2472 and was just downloaded.
> >>
> >> The build number is displayed in the lower left corner of the WSUS
> >> Administration Console Home Page, right under where you would be
> >> observing
> >> this "Service Unavailable" error message.
> >>
> >> The version number of the setup file is correct for the "gold" code
> >> package.
> >>
> >> > I show all services as started, I
> >> > have verified all the settings of IIS are set correctly according to
> >> > Microsoft as well. Is there any known problems running WUS with Backup
> >> > Exec?
> >> > My thought is that Backup Exec runs using a SQL desktop version as
> >> > well.
> >>
> >> There are no known issues, and several installations are operating in
> >> production. Backup Exec does use MSDE, however, it uses a different
> >> instance
> >> name. WSUS uses it's own instance name of (W)MSDE, which is "WSUS" and
> >> will
> >> not conflict with any other MSDE-based application that we know of.
> >>
> >> If you would like to send me a screen shot of that message to: l r g a r
> >> v i
> >> n @ s w b e l l . n e t
> >>
> >> I'll see if I can glean any additional clues as to the problem.
> >>
> >> Also, a screen shot of services.mmc in full screen mode with all four
> >> columns expanded for readability showing the following services would
> >> also
> >> be useful:
> >> Automatic Updates
> >> Background Intelligent Transfer Service
> >> IIS Admin
> >> MSSQL$WSUS
> >> Update Services
> >> World Wide Web Publishing Service
> >>
> >>
> >> > Thanks again,
> >> >
> >> > Dave
> >> >
> >> > "Lawrence Garvin (MVP)" wrote:
> >> >
> >> >> Frankly, I've never heard of a message that terse.... but the only
> >> >> thing
> >> >> that could possibly cause a message that terse would be the "Update
> >> >> Services" service not being started.
> >> >>
> >> >> Even that, though, generates a longer message.
> >> >>
> >> >> Can you confirm that the build number is 2.0.0.2472?
> >> >>
> >> >> "DFJosey" <DFJosey@discussions.microsoft.com> wrote in message
> >> >> news:71D32569-C18B-464E-8B19-B07CF8C13E6C@microsoft.com...
> >> >> > Lawrence,
> >> >> >
> >> >> > Thanks for the reply... The error message I mentioned is the
> >> >> > complete
> >> >> > message "Service Unavailable". I get this when I try to access the
> >> >> > WUS
> >> >> > Admin
> >> >> > Page. I get nothing else. I don't think it has to do with any self
> >> >> > updates
> >> >> > as it appears I can't even access the Admin Page. Any other ideas?
> >> >> >
> >> >> > Thanks,
> >> >> >
> >> >> > Dave
> >> >> >
> >> >> > "Lawrence Garvin (MVP)" wrote:
> >> >> >
> >> >> >> Posting the complete message would help.. but I suspect it has to
> >> >> >> do
> >> >> >> with
> >> >> >> "Selfupdate", given that this is a new installation.
> >> >> >>
> >> >> >> Assuming that... check this article for resolutions to that
> >> >> >> condition:
> >> >> >> http://wsusinfo.onsitechsolutions.com/articles/020.htm
> >> >> >> "What does WSUS mean by "Selfupdate service not running"?"
> >> >> >>
> >> >> >> "DFJosey" <DFJosey@discussions.microsoft.com> wrote in message
> >> >> >> news:B393D0DD-94E8-47CD-AC8D-A9801E92D702@microsoft.com...
> >> >> >> >I have WUS installed on port 8530 on a WIN2k3 server... I get the
> >> >> >> >following
> >> >> >> > error message when trying to view the WUS Admin Page through IE:
> >> >> >> > Service
> >> >> >> > Unavailable. I have also installed it on port 80 with the same
> >> >> >> > results.
> >> >> >> > The
> >> >> >> > installation completed successfully and there were no error
> >> >> >> > messages
> >> >> >> > logged.
> >> >> >> > Anyone have this same problem or know what is going on? The only
> >> >> >> > thing
> >> >> >> > is
> >> >> >> > that I did it through Terminal Services logged on as the
> >> >> >> > Administrator...
> >> >> >> > I
> >> >> >> > plan on trying from the console this week but can't see where
> >> >> >> > that
> >> >> >> > would
> >> >> >> > make
> >> >> >> > a difference. Thanks in advance :)
> >> >> >>
> >> >> >>
> >> >> >>
> >> >>
> >> >>
> >> >>
> >>
> >>
> >>
>
>
>

Yes, Dave was installing WSUS on a Terminal Services service and attempting
to have coexistence between tsweb and WSUS.

WSUS is not supported for installation on Terminal Services, and even if it
were, I would strongly advise against doing so for performance related
reasons.

Are you attempting to install WSUS on a Terminal Services server, Rick?

If not... let's take a closer look at what you've got.

"Rick Smith" <Rick Smith@discussions.microsoft.com> wrote in message
news:76FF4E4E-8AC2-446A-BB2D-BF01EA6B023C@microsoft.com...
> Any news or progress on this? I am having the same problems & have
> un-installed & reinstalled many times. Tried on the default port 80 & the
> special 8530.
>
> "Lawrence Garvin (MVP)" wrote:
>
>> So I now understand... having seen the actual screen dump. Thank you for
>> sending that over, it helped me tremendously.
>>
>> For the benefit of the group, Dave isn't even getting the default.aspx
>> page
>> to load, but is getting an error message, either from IIS or from ASP.NET
>> (I
>> haven't determined which yet) -- my working theory is that it's from IIS
>> and
>> caused by some inability to engage the ASP.NET services.
>>
>> I'll followup with additional information as it becomes available.
>>
>> "DFJosey" <DFJosey@discussions.microsoft.com> wrote in message
>> news:E6883C3B-26E3-4D1F-9FCD-CA7AD28A29A3@microsoft.com...
>> > Lawrence,
>> >
>> > I would be able to get the build number if I could actually get to the
>> > admin
>> > page but... that is the problem. I can't get to the admin page. I
>> > will
>> > send
>> > you a screen shot to your email.
>> >
>> > Thanks,
>> >
>> > Dave
>> >
>> > "Lawrence Garvin (MVP)" wrote:
>> >
>> >>
>> >> "DFJosey" <DFJosey@discussions.microsoft.com> wrote in message
>> >> news:D0074AB3-56E9-43EF-AB32-4955CB655E23@microsoft.com...
>> >> > Lawrence,
>> >> >
>> >> > I can't find the build number but the version number of the setup
>> >> > file
>> >> > is
>> >> > 5.4.3790.2472 and was just downloaded.
>> >>
>> >> The build number is displayed in the lower left corner of the WSUS
>> >> Administration Console Home Page, right under where you would be
>> >> observing
>> >> this "Service Unavailable" error message.
>> >>
>> >> The version number of the setup file is correct for the "gold" code
>> >> package.
>> >>
>> >> > I show all services as started, I
>> >> > have verified all the settings of IIS are set correctly according to
>> >> > Microsoft as well. Is there any known problems running WUS with
>> >> > Backup
>> >> > Exec?
>> >> > My thought is that Backup Exec runs using a SQL desktop version as
>> >> > well.
>> >>
>> >> There are no known issues, and several installations are operating in
>> >> production. Backup Exec does use MSDE, however, it uses a different
>> >> instance
>> >> name. WSUS uses it's own instance name of (W)MSDE, which is "WSUS" and
>> >> will
>> >> not conflict with any other MSDE-based application that we know of.
>> >>
>> >> If you would like to send me a screen shot of that message to: l r g a
>> >> r
>> >> v i
>> >> n @ s w b e l l . n e t
>> >>
>> >> I'll see if I can glean any additional clues as to the problem.
>> >>
>> >> Also, a screen shot of services.mmc in full screen mode with all four
>> >> columns expanded for readability showing the following services would
>> >> also
>> >> be useful:
>> >> Automatic Updates
>> >> Background Intelligent Transfer Service
>> >> IIS Admin
>> >> MSSQL$WSUS
>> >> Update Services
>> >> World Wide Web Publishing Service
>> >>
>> >>
>> >> > Thanks again,
>> >> >
>> >> > Dave
>> >> >
>> >> > "Lawrence Garvin (MVP)" wrote:
>> >> >
>> >> >> Frankly, I've never heard of a message that terse.... but the only
>> >> >> thing
>> >> >> that could possibly cause a message that terse would be the "Update
>> >> >> Services" service not being started.
>> >> >>
>> >> >> Even that, though, generates a longer message.
>> >> >>
>> >> >> Can you confirm that the build number is 2.0.0.2472?
>> >> >>
>> >> >> "DFJosey" <DFJosey@discussions.microsoft.com> wrote in message
>> >> >> news:71D32569-C18B-464E-8B19-B07CF8C13E6C@microsoft.com...
>> >> >> > Lawrence,
>> >> >> >
>> >> >> > Thanks for the reply... The error message I mentioned is the
>> >> >> > complete
>> >> >> > message "Service Unavailable". I get this when I try to access
>> >> >> > the
>> >> >> > WUS
>> >> >> > Admin
>> >> >> > Page. I get nothing else. I don't think it has to do with any
>> >> >> > self
>> >> >> > updates
>> >> >> > as it appears I can't even access the Admin Page. Any other
>> >> >> > ideas?
>> >> >> >
>> >> >> > Thanks,
>> >> >> >
>> >> >> > Dave
>> >> >> >
>> >> >> > "Lawrence Garvin (MVP)" wrote:
>> >> >> >
>> >> >> >> Posting the complete message would help.. but I suspect it has
>> >> >> >> to
>> >> >> >> do
>> >> >> >> with
>> >> >> >> "Selfupdate", given that this is a new installation.
>> >> >> >>
>> >> >> >> Assuming that... check this article for resolutions to that
>> >> >> >> condition:
>> >> >> >> http://wsusinfo.onsitechsolutions.com/articles/020.htm
>> >> >> >> "What does WSUS mean by "Selfupdate service not running"?"
>> >> >> >>
>> >> >> >> "DFJosey" <DFJosey@discussions.microsoft.com> wrote in message
>> >> >> >> news:B393D0DD-94E8-47CD-AC8D-A9801E92D702@microsoft.com...
>> >> >> >> >I have WUS installed on port 8530 on a WIN2k3 server... I get
>> >> >> >> >the
>> >> >> >> >following
>> >> >> >> > error message when trying to view the WUS Admin Page through
>> >> >> >> > IE:
>> >> >> >> > Service
>> >> >> >> > Unavailable. I have also installed it on port 80 with the
>> >> >> >> > same
>> >> >> >> > results.
>> >> >> >> > The
>> >> >> >> > installation completed successfully and there were no error
>> >> >> >> > messages
>> >> >> >> > logged.
>> >> >> >> > Anyone have this same problem or know what is going on? The
>> >> >> >> > only
>> >> >> >> > thing
>> >> >> >> > is
>> >> >> >> > that I did it through Terminal Services logged on as the
>> >> >> >> > Administrator...
>> >> >> >> > I
>> >> >> >> > plan on trying from the console this week but can't see where
>> >> >> >> > that
>> >> >> >> > would
>> >> >> >> > make
>> >> >> >> > a difference. Thanks in advance :)
>> >> >> >>
>> >> >> >>
>> >> >> >>
>> >> >>
>> >> >>
>> >> >>
>> >>
>> >>
>> >>
>>
>>
>>

No, I am not. It is just a new Win2003 Standard SP1. I have added the IIS
components and all seems to be correct.

Another note, when I browse to "http://servername" I get the "Server
Unavailable" message, so I think there is an underlying issue with IIS or
..Net. I have tried all that I can but cannot get this darn thing to work
right.

Do you have any other questions that I can answer?

"Lawrence Garvin (MVP)" wrote:

> Yes, Dave was installing WSUS on a Terminal Services service and attempting
> to have coexistence between tsweb and WSUS.
>
> WSUS is not supported for installation on Terminal Services, and even if it
> were, I would strongly advise against doing so for performance related
> reasons.
>
> Are you attempting to install WSUS on a Terminal Services server, Rick?
>
> If not... let's take a closer look at what you've got.
>
> "Rick Smith" <Rick Smith@discussions.microsoft.com> wrote in message
> news:76FF4E4E-8AC2-446A-BB2D-BF01EA6B023C@microsoft.com...
> > Any news or progress on this? I am having the same problems & have
> > un-installed & reinstalled many times. Tried on the default port 80 & the
> > special 8530.

"Rick Smith" <Rick Smith@discussions.microsoft.com> wrote in message
news:889C0B1A-1AB8-4C4D-B428-6A4956C48F05@microsoft.com...
> No, I am not. It is just a new Win2003 Standard SP1. I have added the
> IIS
> components and all seems to be correct.
>
> Another note, when I browse to "http://servername" I get the "Server
> Unavailable" message,

So, it seems you do not have the same issue as Dave. This is a case of
trying to access browser-based content that does not exist. The only
browser-based content in as WSUS deployment is the WSUS Admin Console, which
would be accessed at http://servername/WSUSAdmin.

> so I think there is an underlying issue with IIS or
> .Net. I have tried all that I can but cannot get this darn thing to work
> right.
>
> Do you have any other questions that I can answer?

There is also a list of URLs you can test and the expected responses in the
article at
http://wsusinfo.onsitechsolutions.com/articles/020.htm


>
> "Lawrence Garvin (MVP)" wrote:
>
>> Yes, Dave was installing WSUS on a Terminal Services service and
>> attempting
>> to have coexistence between tsweb and WSUS.
>>
>> WSUS is not supported for installation on Terminal Services, and even if
>> it
>> were, I would strongly advise against doing so for performance related
>> reasons.
>>
>> Are you attempting to install WSUS on a Terminal Services server, Rick?
>>
>> If not... let's take a closer look at what you've got.
>>
>> "Rick Smith" <Rick Smith@discussions.microsoft.com> wrote in message
>> news:76FF4E4E-8AC2-446A-BB2D-BF01EA6B023C@microsoft.com...
>> > Any news or progress on this? I am having the same problems & have
>> > un-installed & reinstalled many times. Tried on the default port 80 &
>> > the
>> > special 8530.
>

All of those links give me the same message:

"Service Unavailable"

"Lawrence Garvin (MVP)" wrote:

>
> "Rick Smith" <Rick Smith@discussions.microsoft.com> wrote in message
> news:889C0B1A-1AB8-4C4D-B428-6A4956C48F05@microsoft.com...
> > No, I am not. It is just a new Win2003 Standard SP1. I have added the
> > IIS
> > components and all seems to be correct.
> >
> > Another note, when I browse to "http://servername" I get the "Server
> > Unavailable" message,
>
> So, it seems you do not have the same issue as Dave. This is a case of
> trying to access browser-based content that does not exist. The only
> browser-based content in as WSUS deployment is the WSUS Admin Console, which
> would be accessed at http://servername/WSUSAdmin.
>
> > so I think there is an underlying issue with IIS or
> > .Net. I have tried all that I can but cannot get this darn thing to work
> > right.
> >
> > Do you have any other questions that I can answer?
>
> There is also a list of URLs you can test and the expected responses in the
> article at
> http://wsusinfo.onsitechsolutions.com/articles/020.htm
>
>
> >
> > "Lawrence Garvin (MVP)" wrote:
> >
> >> Yes, Dave was installing WSUS on a Terminal Services service and
> >> attempting
> >> to have coexistence between tsweb and WSUS.
> >>
> >> WSUS is not supported for installation on Terminal Services, and even if
> >> it
> >> were, I would strongly advise against doing so for performance related
> >> reasons.
> >>
> >> Are you attempting to install WSUS on a Terminal Services server, Rick?
> >>
> >> If not... let's take a closer look at what you've got.
> >>
> >> "Rick Smith" <Rick Smith@discussions.microsoft.com> wrote in message
> >> news:76FF4E4E-8AC2-446A-BB2D-BF01EA6B023C@microsoft.com...
> >> > Any news or progress on this? I am having the same problems & have
> >> > un-installed & reinstalled many times. Tried on the default port 80 &
> >> > the
> >> > special 8530.
> >
>
>
>

It sounds like either the ASP.NET service is corrupted, not installed, or
perhaps 'disabled' in IIS Admin.

First check IIS Admin, under Web Service Extensions, and make sure that
ASP.NET is marked as "Allowed".

Also, have you installed IISLockdown on this machine? If so, try
uninstalling it.

If neither of those provide resolution, my best suggestion would be to
completely uninstall WSUS, making sure that all filesystem traces of the
application are removed. Then reboot the server, make sure necessary
prerequisites are installed, and reinstall WSUS, following the directions in
the appropriate "WSUS Step-by-Step to Getting Started..." guide.

"Rick Smith" <RickSmith@discussions.microsoft.com> wrote in message
news:B1190D2C-92B3-4F80-9A04-173D5504D650@microsoft.com...
> All of those links give me the same message:
>
> "Service Unavailable"
>
> "Lawrence Garvin (MVP)" wrote:
>
>>
>> "Rick Smith" <Rick Smith@discussions.microsoft.com> wrote in message
>> news:889C0B1A-1AB8-4C4D-B428-6A4956C48F05@microsoft.com...
>> > No, I am not. It is just a new Win2003 Standard SP1. I have added the
>> > IIS
>> > components and all seems to be correct.
>> >
>> > Another note, when I browse to "http://servername" I get the "Server
>> > Unavailable" message,
>>
>> So, it seems you do not have the same issue as Dave. This is a case of
>> trying to access browser-based content that does not exist. The only
>> browser-based content in as WSUS deployment is the WSUS Admin Console,
>> which
>> would be accessed at http://servername/WSUSAdmin.
>>
>> > so I think there is an underlying issue with IIS or
>> > .Net. I have tried all that I can but cannot get this darn thing to
>> > work
>> > right.
>> >
>> > Do you have any other questions that I can answer?
>>
>> There is also a list of URLs you can test and the expected responses in
>> the
>> article at
>> http://wsusinfo.onsitechsolutions.com/articles/020.htm
>>
>>
>> >
>> > "Lawrence Garvin (MVP)" wrote:
>> >
>> >> Yes, Dave was installing WSUS on a Terminal Services service and
>> >> attempting
>> >> to have coexistence between tsweb and WSUS.
>> >>
>> >> WSUS is not supported for installation on Terminal Services, and even
>> >> if
>> >> it
>> >> were, I would strongly advise against doing so for performance related
>> >> reasons.
>> >>
>> >> Are you attempting to install WSUS on a Terminal Services server,
>> >> Rick?
>> >>
>> >> If not... let's take a closer look at what you've got.
>> >>
>> >> "Rick Smith" <Rick Smith@discussions.microsoft.com> wrote in message
>> >> news:76FF4E4E-8AC2-446A-BB2D-BF01EA6B023C@microsoft.com...
>> >> > Any news or progress on this? I am having the same problems & have
>> >> > un-installed & reinstalled many times. Tried on the default port 80
>> >> > &
>> >> > the
>> >> > special 8530.
>> >
>>
>>
>>

I was having the exact same problem. I changed the identity in the wsus
app pool to local system and it worked. Obviously you wouldn't want to
keep this as a permanent solution as the local system account is very
open. Hope this helps. Now I have to go and figure out where my default
account is lacking in permissions