Infralution Support

[Sputnik]

Something's changed and I'm not sure what.
I have my company's web site at the root (which is a web application), and it has a web.config.

Then, I have the Authenticate folder, with the AuthenticationService.asmx, and its web.config.

However, when I try to run the asmx directly, it's throwing an error now on the <pages> line - I have a theme set in that tag. (<pages>)

If I take out the theme attribute, it runs fine, but my website is screwed up.

Can anyone point me in the right direction?

[Infralution]

Can you give full details of the error message?

Is the Authenticate folder set up as an ASP.NET application root (or virtual directory)?
_________________
Infralution Support

[Sputnik]

I just checked, and it show to be set to an application/virtual directory.

asp.net error:
An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). It could, however, be viewed by browsers running on the local server machine.

or course it's hosted by a hosting company so I can't do that

the root site is also a virtual directory, and it works. This is a sub directory. I'm assuming I can still set it as a virtual directory?

[Infralution]

You need to add a customErrors element to your web.config (for the authentication server) and set the mode to off:

[Sputnik]

1. Custom Errors is set to "Off"
2. It is set to 'Application Root' although the folder is UNDER my main website, which is also set to Application Root.
3. Again - The error listed points to the web.config in the root (my main website) - the line listed is the 'Pages' section which lays out a theme. I take out the 'theme' attribute and the ASMX works, but my website falls apart.
4. It ran for a long time and worked well.

[Infralution]

OK - the problem appears to be because the Web.Config in your authentication directory is inheriting properties from your root Web.Config. Perhaps you had previously changed the Authentication Web.Config to overcome this?

The following article provides some guidance on how to avoid accidently inheriting settings.

http://weblogs.asp.net/jongalloway/10-things-asp-net-developers-should-know-about-web-config-inheritance-and-overrides

In particular you could either add a <pages> element to the Authentication Web.Config with <clear/> tag inside to remove the settings or you could modify your root Web.Config and add a inheritInChildApplication = false attribute to the pages element.
_________________
Infralution Support

[Sputnik]

just for the record, those suggestions didn't work, but it lead me to try something that finally did work

I just created a pages section and set theme=""