Hi,
I get the following exception when a remoting client hosted in IIS talks
to a remoting server also hosted in IIS. They're both using IWA and only
IWA:
[RemotingException: Remoting configuration failed with the exception
'System.Runtime.Remoting.RemotingException: Host the service in IIS with
Integrated Windows Authentication to secure the server
at
System.Runtime.Remoting.Channels.Http.HttpServerChannel.set_IsSecured(Boolean
value)
at
System.Runtime.Remoting.Channels.Http.HttpChannel.set_IsSecured(Boolean
value)
at
System.Runtime.Remoting.Channels.ChannelServices.RegisterChannelInternal(IChannel
chnl, Boolean ensureSecurity)
at
System.Runtime.Remoting.Channels.ChannelServices.RegisterChannel(IChannel
chnl, Boolean ensureSecurity)
at
System.Runtime.Remoting.RemotingConfigHandler.ConfigureChannels(RemotingXmlConfigFileData
configData, Boolean ensureSecurity)
at
System.Runtime.Remoting.RemotingConfigHandler.ConfigureRemoting(RemotingXmlConfigFileData
configData, Boolean ensureSecurity)'.]
System.Runtime.Remoting.RemotingConfigHandler.ConfigureRemoting(RemotingXmlConfigFileData
configData, Boolean ensureSecurity) +450
System.Runtime.Remoting.RemotingConfigHandler.DoConfiguration(String
filename, Boolean ensureSecurity) +36
System.Runtime.Remoting.RemotingConfiguration.Configure(String
filename, Boolean ensureSecurity) +42
ASP.global_asax.Application_Start(Object sender, EventArgs e) in
e:\wms-root\MemberSite\Global.asax:10
Further, if I refresh the page one or two times, the exception goes away
and the page works properly.
Thanks,
Seth Livingston
Seth Livingston - 29 Nov 2005 01:59 GMT
> I get the following exception when a remoting client hosted in IIS talks
> to a remoting server also hosted in IIS. They're both using IWA and only
[quoted text clipped - 6 lines]
> Further, if I refresh the page one or two times, the exception goes away
> and the page works properly.
I think I found the problem. The two applications were running under a
single web site... that web site had anonymous access turned on in
addition to IWA. I don't know why it was able to figure things out
sometimes and not others. Either way, I haven't seen the exception since
I modified the parent web site to use IWA and only IWA.