IIS7, WAS, Vista 5308

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Has anyone been able to get IIS working in Vista build 5308? I've been able
to install IIS and whatnot through the command line in the Release Notes
Addendum, however (twice now under two different setups) I am unable to start
W3SVC. This is because I am unable to start Windows Activation Service
(WAS). If I try to start WAS, I get:

Could not start the Windows Activation Service on Local Computer
Error 50: The request is not supported.

Any pointers would be appreciated.
 
I installed IIS with no problem via "Add/Remove Programs".

To get there, click Start->Computer, then click on "Change or remove a program".

In the explorer bar above that says ">Control Panel > Programs > Installed Programs",
click the arrow after "Programs", then select "Advanced Options".

Double-click on "Windows Features", and you should be able to select what you need
in the "Windows Features" dialog, we're under "Internet Information Services".

Make sure you select *exactly* what you need.




Juan T. Llibre, asp.net MVP
aspnetfaq.com : http://www.aspnetfaq.com/
asp.net faq : http://asp.net.do/faq/
foros de asp.net, en español : http://asp.net.do/foros/
===================================
 
Make sure you run as local Administrator and not a user that is part of the
Administrators group.

What exact command did you use to install IIS. For simplicity, select and
install all IIS Components; we are still working through partial component
installations, dependencies, etc and some partial component combinations
don't work (yet).

--
//David
IIS
http://blogs.msdn.com/David.Wang
This posting is provided "AS IS" with no warranties, and confers no rights.
//
 
I tried it that way the first time (and via command line the second time).
Both times I ended up with the setup I described with all the necessary
components installed but unable to start Windows Activation Service.
 
Windows Activation Service has nothing to do with IIS.
You should be able to activate Windows and not affect IIS.

I haven't tried it, but I bet that IIS will run OK without activating Windows
(until Windows stops, that is ).

Expanding on this...

IIS installed fine, and static files ran OK.

ASP.NET was not registered with IIS, so it didn't run.

I tried running aspnet_regiis -i, but did not have sufficient permissions,
( even though I was logged in as the Administrator account ), so I added
my logged-in account ( the only account on the system and the Administrator)
to the Users which can execute aspnet_regiis.

After executing aspnet_regiis -i, I found that I didn't have a TEMP directory,
( the compiler complained about it not existing ) so I created one at
\Windows\ServiceProfiles\NetworkService\AppData\Local\temp\

Then, the Network Service account didn't have permissions to write
to the new temp directory, so I gave it full control over it.

Voila!

ASP.NET is working as it should.

btw, the ASP.NET build for 5308 is 2.0.50727.62.
The release version of ASP.NET is 2.0.50727.42.




Juan T. Llibre, asp.net MVP
aspnetfaq.com : http://www.aspnetfaq.com/
asp.net faq : http://asp.net.do/faq/
foros de asp.net, en español : http://asp.net.do/foros/
===================================
 
Activation Service in Vista is not for activating windows. I know little
about it, but IIS was abstracted out further to separate running component
service modules from WWW, so the Activation Service runs W3Svc, Ftp, in IIS,
etc. Or something like that :). WAS is the new daddy service for IIS, MSMQ,
and the lot. So if WAS doesn't start, neither do the rest as WAS is a
dependency for them.
 
Make sure you run as local Administrator and not a user that is part of the
Administrators group.
Click to expand...

I'm actually not sure how I would do that. How exactly do I log in as
Administrator in Vista? Earlier builds had a way to choose Administrator at
the login screen (I thought), but I haven't seen that in this CTP.
What exact command did you use to install IIS. For simplicity, select and
install all IIS Components; we are still working through partial component
installations, dependencies, etc and some partial component combinations
don't work (yet).
Click to expand...

After my first clean build, I used Windows Features and tried many different
IIS installation configurations, the first of which was everything. What I
would get is a setup where WAS wouldn't start and where launching the new IIS
Management Console would yield a null reference error. I then added and
removed components there until I got to the point where the Windows Features
dialog no longer worked at all. All it showed was the WinFX 3.0 item, and
the command line pkgmg no longer worked either.

Then I saw the post about the Release Notes Addendum and the command line
within for installing IIS and downloaded the notes from MSDN and then
upgraded over my existing copy of Vista hoping this would yield a working
pkgmgr and Windows Features dialog, which it did.

After I was up and running, I executed the command line, which,
incidentally, is:

start /w pkgmgr /l:c:\log.etw
/iu:IIS-WebServerRole;IIS-WebServer;IIS-CommonHttpFeatures;IIS-StaticContent;IIS-DefaultDocument;IIS-DirectoryBrowsing;IIS-HttpErrors;IIS-HttpRedirect;IIS-ApplicationDevelopment;IIS-ASPNET;IIS-NetFxExtensibility;IIS-ASP;IIS-CGI;IIS-ISAPIExtensions;IIS-ISAPIFilter;IIS-ServerSideIncludes;IIS-HealthAndDiagnostics;IIS-HttpLogging;IIS-LoggingLibraries;IIS-RequestMonitor;IIS-HttpTracing;IIS-CustomLogging;IIS-ODBCLogging;IIS-Security;IIS-BasicAuthentication;IIS-WindowsAuthentication;IIS-DigestAuthentication;IIS-ClientCertificateMappingAuthentication;IIS-IISCertificateMappingAuthentication;IIS-URLAuthorization;IIS-RequestFiltering;IIS-IPSecurity;IIS-Performance;IIS-HttpCompressionStatic;IIS-HttpCompressionDynamic;IIS-WebServerManagementTools;IIS-ManagementConsole;IIS-ManagementScriptingTools;IIS-ManagementService;IIS-IIS6ManagementCompatibility;IIS-Metabase;IIS-WMICompatibility;IIS-LegacyScripts;IIS-LegacySnapIn;IIS-FTPPublishingService;IIS-FTPServer;IIS-FTPManagement;WAS-WindowsActivationService;WAS-ProcessModel;WAS-NetFxEnvironment;WAS-ConfigurationAPI

This seems to run just fine, installed, everything, but I was left with the
same setup I had from using Windows Features, i.e. I could not (and cannot)
start WAS.
 
re:
Activation Service in Vista
Click to expand...

If that's the case, I don't know why it, simply, worked for me.
( after going through the procedures I posted... )

Activation is a Windows OS feature. Nothing else is called "activation", AFAIK.

Are you sure what you mean is not the "Turn Windows Features On or Off" ?

That's all I had to do to install IIS, although it only ran static files by default.
The procedures I posted worked for getting ASP.NET working.




Juan T. Llibre, asp.net MVP
aspnetfaq.com : http://www.aspnetfaq.com/
asp.net faq : http://asp.net.do/faq/
foros de asp.net, en español : http://asp.net.do/foros/
===================================
 
WAS is something to do with Indigo (WCF). IIS provides automatic activation
of Indigo services.

And then there is Windows activation itself, so perhaps you two ar talking
at cross purposes?

Cheers
Ken



: re:
: > Activation Service in Vista
:
: If that's the case, I don't know why it, simply, worked for me.
: ( after going through the procedures I posted... )
:
: Activation is a Windows OS feature. Nothing else is called "activation",
AFAIK.
:
: Are you sure what you mean is not the "Turn Windows Features On or Off" ?
:
: That's all I had to do to install IIS, although it only ran static files
by default.
: The procedures I posted worked for getting ASP.NET working.
:
:
:
:
: Juan T. Llibre, asp.net MVP
: aspnetfaq.com : http://www.aspnetfaq.com/
: asp.net faq : http://asp.net.do/faq/
: foros de asp.net, en español : http://asp.net.do/foros/
: ===================================
: : > Activation Service in Vista is not for activating windows. I know
little
: > about it, but IIS was abstracted out further to separate running
component
: > service modules from WWW, so the Activation Service runs W3Svc, Ftp, in
IIS,
: > etc. Or something like that :). WAS is the new daddy service for IIS,
MSMQ,
: > and the lot. So if WAS doesn't start, neither do the rest as WAS is a
: > dependency for them.
:
: > "Juan T. Llibre" wrote:
: >
: >> Windows Activation Service has nothing to do with IIS.
: >> You should be able to activate Windows and not affect IIS.
:
:
 
Format and clean install Vista 5308 and then run that exact pkgmgr command.
That will be *exactly* what we do daily.

We are still seeing some problems using the various UI/dialogs to install
IIS7. I am comfortable with the pkgmgr commandline since it is exactly what
the IIS team uses and works reliably; the various UI are less covered (and
mostly uncover non-IIS issues within Vista Componentization since IIS7 is
the most complicated and componentized part of Vista and push the boundaries
in Vista Componentization).

As a general rule, I do not upgrade Vista during beta. Just a warning --
IIS7 upgrade/migration isn't exactly working, and componentized
upgrade/uninstall isn't working, either. So, upgrade at your own risk if you
want to see a functioning IIS7. :-)

--
//David
IIS
http://blogs.msdn.com/David.Wang
This posting is provided "AS IS" with no warranties, and confers no rights.
//
 
re:
perhaps you two ar talking at cross purposes?
Click to expand...

Evidently... ;-)

This is part of the fun of running early betas.
What works for me may not work for others, in this case Nathaniel.

Except for the rigamarole registering ASP.NET with IIS,
I was good to go after using the "Install or Remove Windows Features" dialog.




Juan T. Llibre, asp.net MVP
aspnetfaq.com : http://www.aspnetfaq.com/
asp.net faq : http://asp.net.do/faq/
foros de asp.net, en español : http://asp.net.do/foros/
===================================
 
Thanks, that got me going. You were right, too much messing with the Windows
Features dialog is what messed up WAS. It turns out I did have IIS installed
"properly" the first time I tried, I just didn't think I did because a) IIS
6.0 Management Console didn't show websites and b) IIS 7.0 Management Console
raised a null exception error.

This did still leave me with an IIS Management Console which still throws a
null exception error. However, after reading the call stack and trying some
things I figured out why: if you run dual monitors AND the monitor on the
right is your primary monitor, launching the new IIS Management Console leads
to:

System.NullReferenceException: Object reference not set to an instance of an
object.
at System.Windows.Forms.DisplayInformation.get_LowResolution()

I reported this using the bug reporting tool. Disabling the secondary
monitor or setting the left hand monitor as primary allows IIS Management
Console to start.
 
Back
Top