"The current configuration system does not support user-scoped settings"

We're getting a "The current configuration system does not support user-scoped settings" compilation exception being thrown when navigating to a WCF service on our staging server.

We're getting this exception through the app consuming th开发者_JS百科e WCF service and when we navigate to the .svc test page directly.

This works fine on our test servers - and the websites are setup in the same way (in IIS, in the filesystem etc. etc.).

Does anybody have an idea of what this would be?

My problem was simple, check in the project's Settings.setting page/file to see if the Scope column is set to User instead of Application:

This was bugging out because one of the settings in a project that the WCF webservice was referencing had its scope set to "user" rather than "application".

So I would recommend people being careful that they check the projects being referenced by the webservice project, as well as the webservice project itself, and make sure the scope of all the settings is application rather than user.

Hope it helps somebody who's trying to rack their brain about anything similar.

User scope settings are stored in a config file hidden away in the C:\Users\\AppData\Local\ folder. Maybe the setup of your server prohibits .Net to write files there?

Do you have any user-scope settings? I don't think these are necessary for a service? Maybe you should change the settings to Application Scope and your problem is fixed.

In my case the problem was that the Web Service reference had its "URL Behavior" property set to "Dynamic" instead of "Static". After setting it to Static the problem went away.