Page 1 of 1

.net providers and IIS manager

Posted: Wed 20 Feb 2008 23:08
by KW
I'm getting this error when trying to set the default provider in the IIS7 manager:
-------------------------------------------------------------------------------------
This feature cannot be used because the default provider type could not be determined to check whether it is a trusted provider.

You can use this feature only when the default provider is a trusted provider. If you are a server administrator, you can make a provider a trusted provider by adding the provider type to the trusted providers listin the adminstration.config file. The provider has to be strongly typed and added to the GAC.
-------------------------------------------------------------------------------------

Can someone provide me a tutorial to circumvent this situation, I'd like to use the IIS7 manager to handle membership, roles, etc.

http://forums.iis.net/t/1147661.aspx

Posted: Fri 22 Feb 2008 16:51
by Alexey.mdr
We are investigating this problem.
Could you post the full name of your OS?

Hi

Posted: Fri 22 Feb 2008 17:48
by KW
I'm using Windows Server 2008.

Posted: Tue 26 Feb 2008 07:57
by Alexey.mdr
We are testing the problem.
It may take some time (about a week or two).
As soon as the first results will be available I will let you know.

Posted: Tue 26 Feb 2008 14:50
by Alexey.mdr
Could you specify which Windows Server 2008 do you use: 32-bit or 64-bit?

Posted: Tue 26 Feb 2008 17:45
by KW
Alexey.mdr wrote:Could you specify which Windows Server 2008 do you use: 32-bit or 64-bit?

Windows Server Standard
Service Pack 1, v.667
Intel processor
32-bit operating system

Posted: Wed 27 Feb 2008 11:10
by Alexey.mdr
Thank you for the information.
We will investigate this problem.
I'm afraid, this may take some time.
I will notify you when we fix it

Posted: Wed 27 Feb 2008 18:59
by KW
Alexey.mdr wrote:Thank you for the information.
We will investigate this problem.
I'm afraid, this may take some time.
I will notify you when we fix it
Well, in the blog post I linked:
To work around this, you can compile the provider into a strongly-named signed assembly, and register it in the GAC. Then, use the full assembly-qualified type in the provider's configuration to identify this provider. This will allow you to use IIS Manager, which is by far the easiest way to create and manage Membership users
I am not sure if you can simply provide a tutorial on how to do these things, this might fix the problem. But yes, it might take some time.

Posted: Thu 28 Feb 2008 16:29
by Alexey.mdr
We are working on the problem.
I will notify you on the first available result.

Posted: Fri 13 Feb 2009 21:04
by KW
Did anyone every fix this problem or resolve it with a tutorial?

Posted: Wed 18 Feb 2009 11:45
by Shalex
Tell us please the exact provider (Membership, Role, Profile, Session State, Site Map, Web Event or Personalization provider) you are experiencing difficulties with.

Posted: Wed 18 Feb 2009 17:36
by KW
Shalex wrote:Tell us please the exact provider (Membership, Role, Profile, Session State, Site Map, Web Event or Personalization provider) you are experiencing difficulties with.







I've noticed this error trying to use the .net users under the asp.net area, using IIS7 and the mmc snap in ( IIS manager)

Posted: Fri 20 Feb 2009 14:22
by Shalex
We will investigate the issue with the IIS7 manager of Windows Server 2008 and notify you about the results as soon as possible.

Posted: Wed 25 Feb 2009 18:56
by KW
Shalex wrote:We will investigate the issue with the IIS7 manager of Windows Server 2008 and notify you about the results as soon as possible.
Thats what the last guy said! :P

Posted: Wed 08 Apr 2009 15:56
by Shalex
KW, please specify the exact steps we should follow to reproduce the mentioned error. I added the WebProviders web site from our samples to IIS7 on Windows Server 2008 (the site was working fine), then I selected this site in IIS7, opened the Providers section from the ASP.NET area, selected the .NET Users feature, and there was AspNetMySqlMembershipProvider in the list. There were no any errors. How can we reproduce the problem?