I can't get the simplest WFC app created by the VS2005 to work on the local machine!
Two - I have read and tried just about everything mentioned in any post about WFC and IIS.
This is NOT supposed to be this difficult I am sure.
My installation: Vista Beta 2 (build 5384), IIS 7 enabled, VS2005 with extensions (WF RC2, Orcas), Vista Windows SDK 5383.1.1
I ran the serviceModelReg.exe -i (no errors). I have copied other web services from IIS 6 to the IIS 7 and they work nominally. I can create, compile and execute aspx sites on the machine.
A step by step setup procedure would be helpfull. I hope someone at Microsoft actually has a configuration working... If not please say so. Been beating my head against the now bloody rock for several days and many posts to forums have not resulted in any response. I am beginning to wonder if WCF is just smoke.
At this point a discussion of what has been attempted is not useful, rather a concise setup procedure from ZERO would however be appreciated.
Larry
(Side-note: I absolutely HATE the new Explorer. 52 year-old eyes can't hit that stupid little tri-angle and then the crazy thing jumps off some place... drives me nuts!)

Vista IIS7 WCF - Has anyone got it working?
RaviKanthReddy
Steve,
I sent you the requested information. When we get this working I will certainly post the results.
Larry
knvb
Nothing worked to make it run. So the whole installation of Beta 2 and everything else was scrapped.
I have just completed the installation of the July CTP based on Tom Archer's blog. I have one problem now (could be more but since nothing is tested yet, I only have one for the moment.) That problem is, where are the WinFx Visual Studio templates They were there before.
Here is the order used in installation: (note: clean machine install)
Vista CTP July (checked for updates)
Used the control panel to turn on the IIS 7 web services.
Visual Studio 2005 (has the oldest code so I reasoned that some parts might be updated by the subsequent releases.)
Installed Vista Windows SDK July CTP.
Installed WF extensions RC4 per Tom Archer's blog http://blogs.msdn.com/tomarcher/
Fairly straight forward installation no glitches, except no WinFx VS extensions. I hope that I haven't been mislead by the following statement from his blog:
"Orcas" Tools for .NET 3.0 Development is only needed if you are writing Windows Presentation Foundation applications and are using a released (non beta) copy of Visual Studio 2005...
Because I am not doing any WPF, just WCF for now. So where did the extensions come from and how do I get them back
Larry Aultman
David Ing
Hi Larry,
I'm sorry to hear that you're having so many problems. Hopefully we can help you resolve your issue.
The 405 error is caused by the WCF HTTP handler not being correctly registered with IIS. This should be taken care of by our setup process but it looks like that's not happening in your case. If you could send the contents of the IIS7 ApplicatioHost.config file (c:\windows\system32\inetsrv\applicationHost.config) to my email address -- smaine (at) microsoft.com I can take a look.
A few other questions:
1) Did you do a clean Vista install or upgrade from XP/2003
2) When you migrated your sites from IIS6 to IIS7, how did you accomplish that
3) Are you running your WCF application in an IIS7 "Integrated Mode" appPool or an "ISAPI Mode" app pool
I'm hoping that with some more data we can get to the bottom of this
-steve
Kornfish
Yes, I know about beta. If my customer were listening to me we would not be having this discussion... I have been around the block a number of times in the past 25+ years of programming.
Ok, I have been working at this problem for about 4 days off and on and all day yesterday. Now it has reached the aggrivation level.
I have IIS7 working with no problems with "normal" aspx websites. It also works with no problems with .NET 2.0 web services. It does NOT work with WCF web services.
I created the "out of the box" WinFx service using VS2005. I added the Service Reference to a client application. I added a single label control to the form and called the service (which should return a "Hello" string) in the form-load event.
I get an error: 405 Method Not Allowed
The exception is thrown here:
public
string MyOperation1(string myValue1){
return base.InnerProxy.MyOperation1(myValue1); // <--- The error occures on this line in the auto-generated code class.
}
I have granted to Internet User, IIS_User, Network Service, Everybody accounts read, write, execute access to the folder. IIS Anonymous Authentication is enabled.
Thanks for taking time, I appreciate it very much.
Larry Aultman
JiltedCitizen
Christian,
Good to know that someone is out there... Star Trek NG: Episode where Data answers the little girl's question: "Is anybody out there " In this case I hope that the Microsoft Prime Directive "Do not have contact with developers or reveal working setups to developers" does not apply. You surely would think that they (those with the advanced technology) would reveal the secrets of these hidden truths to those of us mere developers. But alas, is that not the way of the universe past, present, and future.
Thanks, I have previously found the referenced articles and did so again to verify my configuration of IIS 7 in Vista. I am trying to adapt to the new interface with some problems in locating certain things but all in all I have found most of the settings so that I can verify them.
In the referenced article, the author mentions that one should logon as the "Administrator" which is not possible in Beta 2 except as the first account created which supposedly is the "local administrator". I believe that I am correct on this. However I still find it annoying to be restricted from accessing areas of my own computer. In any case I have elevated the privleges of VS2005 to run as administrator.
My problem is I can't get a WCF service to work - period - in IIS on Vista. One would think that the default project should compile and run. I does compile, but it will not access the WCF web service. I am at total loss as to why (not to mention a little aggrevated!)
No joy yet.
Larry
Hussain Saffar
No problem:
C:\Windows\WinFX\v3.0\Windows Communication Foundation>servicemodelreg -lv
Microsoft(R) Windows Communication Foundation Installation Utility
[Microsoftr .NET Framework, Version 3.0.3906.22]
Copyright (c) Microsoft Corporation. All rights reserved.
Installed versions of Machine.config Section Groups and Handlers:
system.serviceModel : 3.0.0.0
system.runtime.serialization : 3.0.0.0
system.serviceModel.activation : 3.0.0.0
Installed versions of Xws System.Web Build Provider:
3.0.0.0
Installed versions of Xws System.Web Compilation Assemblies:
System.Runtime.Serialization, Version=3.0.0.0, Culture=neutral, PublicKe
yToken=b77a5c561934e089, processorArchitecture=MSIL
System.IdentityModel, Version=3.0.0.0, Culture=neutral, PublicKeyToken=b
77a5c561934e089, processorArchitecture=MSIL
System.ServiceModel, Version=3.0.0.0, Culture=neutral, PublicKeyToken=b7
7a5c561934e089
Installed versions of Xws Http Handlers:
*.svc : 3.0.0.0
Installed versions of Xws Http Modules:
ServiceModel : 3.0.0.0
Installed versions of Xws ListenerAdapter node for protocol net.tcp:
Identity : S-1-5-80-3579033775-2824656752-1522793541-1960352512-46290708
6
Installed versions of Xws Protocol node for protocol net.tcp:
ProcessHandlerType : System.ServiceModel.WasHosting.TcpProcessProtocolHa
ndler, System.ServiceModel.WasHosting, Version=3.0.0.0, Culture=neutral, PublicK
eyToken=b77a5c561934e089
AppDomainHandlerType : System.ServiceModel.WasHosting.TcpAppDomainProtoc
olHandler, System.ServiceModel.WasHosting, Version=3.0.0.0, Culture=neutral, Pub
licKeyToken=b77a5c561934e089
Installed versions of Xws TransportConfiguration node for protocol net.tcp:
TransportConfigurationType : System.ServiceModel.Activation.TcpHostedTra
nsportConfiguration, System.ServiceModel, Version=3.0.0.0, Culture=neutral, Publ
icKeyToken=b77a5c561934e089
Installed versions of Xws ListenerAdapter node for protocol net.pipe:
Identity : S-1-5-80-2943419899-937267781-4189664001-1229628381-398211507
3
Installed versions of Xws Protocol node for protocol net.pipe:
ProcessHandlerType : System.ServiceModel.WasHosting.NamedPipeProcessProt
ocolHandler, System.ServiceModel.WasHosting, Version=3.0.0.0, Culture=neutral, P
ublicKeyToken=b77a5c561934e089
AppDomainHandlerType : System.ServiceModel.WasHosting.NamedPipeAppDomain
ProtocolHandler, System.ServiceModel.WasHosting, Version=3.0.0.0, Culture=neutra
l, PublicKeyToken=b77a5c561934e089
Installed versions of Xws TransportConfiguration node for protocol net.pipe:
TransportConfigurationType : System.ServiceModel.Activation.NamedPipeHos
tedTransportConfiguration, System.ServiceModel, Version=3.0.0.0, Culture=neutral
, PublicKeyToken=b77a5c561934e089
Installed versions of Xws ListenerAdapter node for protocol net.msmq:
Identity : S-1-5-80-89244771-1762554971-1007993102-348796144-2203111529
Installed versions of Xws Protocol node for protocol net.msmq:
ProcessHandlerType : System.ServiceModel.WasHosting.MsmqProcessProtocolH
andler, System.ServiceModel.WasHosting, Version=3.0.0.0, Culture=neutral, Public
KeyToken=b77a5c561934e089
AppDomainHandlerType : System.ServiceModel.WasHosting.MsmqAppDomainProto
colHandler, System.ServiceModel.WasHosting, Version=3.0.0.0, Culture=neutral, Pu
blicKeyToken=b77a5c561934e089
Installed versions of Xws TransportConfiguration node for protocol net.msmq:
TransportConfigurationType : System.ServiceModel.Activation.MsmqHostedTr
ansportConfiguration, System.ServiceModel, Version=3.0.0.0, Culture=neutral, Pub
licKeyToken=b77a5c561934e089
Installed versions of Xws ListenerAdapter node for protocol msmq.formatname:
Identity : S-1-5-80-89244771-1762554971-1007993102-348796144-2203111529
Installed versions of Xws Protocol node for protocol msmq.formatname:
ProcessHandlerType : System.ServiceModel.WasHosting.MsmqIntegrationProce
ssProtocolHandler, System.ServiceModel.WasHosting, Version=3.0.0.0, Culture=neut
ral, PublicKeyToken=b77a5c561934e089
AppDomainHandlerType : System.ServiceModel.WasHosting.MsmqIntegrationApp
DomainProtocolHandler, System.ServiceModel.WasHosting, Version=3.0.0.0, Culture=
neutral, PublicKeyToken=b77a5c561934e089
Installed versions of Xws TransportConfiguration node for protocol msmq.formatna
me:
TransportConfigurationType : System.ServiceModel.Activation.MsmqIntegrat
ionHostedTransportConfiguration, System.ServiceModel, Version=3.0.0.0, Culture=n
eutral, PublicKeyToken=b77a5c561934e089
Installed versions of Xws Http Modules (WAS):
ServiceModel : 3.0.0.0
Installed versions of Xws Http Handlers (WAS):
*.svc : 3.0.0.0 (integratedMode)
cdolor
Let's wait for the team - I try to ping them.
Cheers,
Dennis Mark Thorsen
Unsupported It's beta! I LOVE unsupported. That is why we all come here to this forum.
I knew that, as the commedian Gregory something... can't remember his name said as one of his lines, "Somewhere in the past..." In reference to all the tags on stuff you buy, like baby strollers, that "disclaim": DO NOT PLACE THIS DEVICE ON AN INCLINE OF MORE THAN 45 DEGREES WITH BABY UNATTENDED.
Those of us out here on the edege KNOW what we are doing. We are daring God, 'cause Microsoft has done told us it ain't supported.
Like Vikings we sail out into the Vista of the North Atlantic and we brave the tempest. Those of us who make it back to our shores all bloody and ravaged are allowed to speak the tall tales around our modern campfires while the young ones listen in rap awe of our adventures. And we beat upon our breast and sing praises of your glorious fights.
Fun isn't it!
Larry
Samyag1
First, calm down
Second, I do not like the Explorer either
Third...
Thomas Deml has a very recent article on this topic (and more):
http://www.iis.net/922/SinglePageArticle.ashx
Also make sure that your setup is OK:
http://www.iis.net/957/SinglePageArticle.ashx
Please let us all know whether this helps.
Cheers,
sandeep srivastava
Which build are you running What is your setup What did you do beyond installing IIS and ServiceModelReg.exe
Did you have to set access permissions to any accounts specifically
Can you host a service in IIS 7 on Vista with your configuration I am available via MSN IM.
Larry
Eric George
"C:\WINDOWS\Microsoft.NET\Framework\v3.0\Windows Communication Foundation\ServiceModelReg.exe" -lv
...and post the result
Cheers,
creaturita
There are no official Orcas tools for July CTP. But there is an unsupported (of course) way to make it work with June CTP, nevertheless.
Cheers,
markm75c
What do you see What is the error What do you mean by "but it will not access the WCF web service"
Sorry for having to cope with Beta software on Beta software. It sometimes is a bit... well, tough.
Cheers,