No Such Interface Supported

[Skark166]

I'm new to IIS and I'm trying to setup a web server on a system that is getting it's local security info from the domain. I'm certain this is playing some part in my problems. I just need to know where, and if there is some way I can work arround it.

When I try to load an ASP page specifically. I get the follwing browser error:

Server Application Error
The server has encountered an error while loading an application during the processing of your request. Please refer to the event log for more detail information. Please contact the server administrator for assistance.

I check the event log and it has the following:
The server failed to load application '/LM/W3SVC/1/ROOT'. The error was 'No such interface supported'.

For additional information specific to this message please visit the Microsoft Online Support site located at:

http://www.microsoft.com/contentredirect.asp.

I've checked MSKB, and found resolutions to some other issues I was having, but not this one. Any advice would be much appreciated.

Scarecrow

 

[WANguy2k]

I'm getting the same error (although it doesn't seem to be afftecting anything). I'm researchine it now, and will post any answers I find.

 

[JFBouchard]

Hi, try to modify the level isolation for your web site: default is "pooled". If this works, open component services console and change the identity of your com+ package "pooled applications" from "system" to interactive user.

This should do it.

Hope this helps. Please let know if this resolve your issue

Jeff

 

[WANguy2k]

JFB, thanks for your help. I went into the settings and changed the default domain, which for some reason was missing. Now I'm getting an error 537 every 30 seconds. I tried to find "pooled applications" in com+ components and I can't find it. I also noticed that I have "In process" but not "Out of Procees" IIS applications. I did a reinstall on Windows components just to check that com+ didn't have any errors, it looks like there's no problem. What am I missing?

 

[JFBouchard]

Hi, you mean default domain in basic authentication? Maybe that's the cause of your problem, try to use only NT challenge/response.

The change of the process isolation didn't help?

 

[Skark166]

My problem ended up being related to AD policies. You may want to check with your domain admin to see if this is the case for you.

Scarecrow

 

[WANguy2k]

OK, here's the deal: People outside the company use OWA to access their Exchange email on this server. When they get prompted for their user name an password, OWA tries to authenticate the user on the 2000 domain gany.com as opposed to the Goldman domain, which was our original NT4 domain (we're in mixed mode). So, I set the default domain to the older domain. I can turn on NT challenge, but I thought that would either force the user to enter the proper domain name every time, or produce a logon error if OWA tries to authenticate against the wrong domain.

As far as changing the isolation level, I'm on IIS5. Do I have the option of doing this? It's not in the IIS manager, and I didn't see it in component services either.