468,268 Members | 1,970 Online
Bytes | Developer Community
New Post

Home Posts Topics Members FAQ

Post your question to a community of 468,268 developers. It's quick & easy.

Configuration section membership not recognized

Hi,

I followed the instructions contained in the articles named :

Deploying ASP.Net 2.0 Web site to Production Server: Part I (URL : http://www.c-sharpcorner.com/uploadf...83052am/1.aspx)

Deploying ASP.NET 2 Web Site to Production Server: Part II (URL : http://www.c-sharpcorner.com/UploadF...22507AM/1.aspx)



These articles have been written by Moustafa Arafa. I followed these instructions in order to solve an issue which I have regarding the deployment of my website on a production server.



I wrote the following in my web.config
Expand|Select|Wrap|Line Numbers
  1. <connectionStrings>
  2.  
  3. <remove name="LocalSqlServer" />
  4.  
  5. <add name="MyDBConnectionString" connectionString="Data Source=(Local)\UNISQL2005;Initial Catalog=myTESTDB;Integrated Security=True" providerName="System.Data.SqlClient" />
  6.  
  7. <!-- DYNAMIC DEBUG COMPILATION
  8.  
  9. <add name="TestAConnectionString1" connectionString="Data Source=(Local)\UNISQL;Initial Catalog=TestA;Integrated Security=True" providerName="System.Data.SqlClient"/>
  10.  
  11. -->
  12.  
  13. </connectionStrings>
  14.  
  15. <system.web>
  16.  
  17. <membership>
  18.  
  19. <providers>
  20.  
  21. <remove name="AspNetSqlMembershipProvider" />
  22.  
  23. <add connectionStringName="MyDBConnectionString" enablePasswordRetrieval="false"
  24.  
  25. enablePasswordReset="true" requiresQuestionAndAnswer="true" applicationName="/"
  26.  
  27. requiresUniqueEmail="false" passwordFormat="Hashed" maxInvalidPasswordAttempts="5"
  28.  
  29. minRequiredPasswordLength="7" minRequiredNonalphanumericCharacters="1"
  30.  
  31. passwordAttemptWindow="10" passwordStrengthRegularExpression=""
  32.  
  33. name="AspNetSqlMembershipProvider" type="System.Web.Security.SqlMembershipProvider, System.Web, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" />
  34.  
  35. </providers>
  36.  
  37. </membership>
  38.  
  39.  
  40. <roleManager enabled="true">
  41.  
  42. <providers>
  43.  
  44. <remove name="AspNetSqlRoleProvider" />
  45.  
  46. <add connectionStringName="MyDBConnectionString" applicationName="/"
  47.  
  48. name="AspNetSqlRoleProvider" type="System.Web.Security.SqlRoleProvider, System.Web, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" />
  49.  
  50. <remove name="AspNetWindowsTokenRoleProvider" />
  51.  
  52. </providers>
  53.  
  54. </roleManager> />
  55.  
  56.  
  57. <webParts>
  58.  
  59. <personalization defaultProvider="AspNetSqlPersonalizationProvider">
  60.  
  61. <providers>
  62.  
  63. <remove name="AspNetSqlPersonalizationProvider" />
  64.  
  65. <add name="AspNetSqlPersonalizationProvider"
  66.  
  67. type="System.Web.UI.WebControls.WebParts.SqlPersonalizationProvider"
  68.  
  69. connectionStringName="MyDBConnectionString"
  70.  
  71. applicationName="/" />
  72.  
  73. </providers>
  74.  
  75. </personalization>
  76.  
  77. </webParts> 
  78.  
and following is the error message which I receive on my development server : Erreur 102 Section de configuration non reconnue membership. (c:\inetpub\wwwroot\univision\web.config line 9) (translated in English, this error message would look like : Error 102 Configuration section membership not recognized).



Could somebody help me ?



Many thanks,



Pierre
Jan 2 '08 #1
5 1877
Plater
7,872 Expert 4TB
Best I can figure, line 9 is this:
Expand|Select|Wrap|Line Numbers
  1. <add connectionStringName="MyDBConnectionString" enablePasswordRetrieval="false"
  2.  
  3. enablePasswordReset="true" requiresQuestionAndAnswer="true" applicationName="/"
  4.  
  5. requiresUniqueEmail="false" passwordFormat="Hashed" maxInvalidPasswordAttempts="5"
  6.  
  7. minRequiredPasswordLength="7" minRequiredNonalphanumericCharacters="1"
  8.  
  9. passwordAttemptWindow="10" passwordStrengthRegularExpression=""
  10.  
  11. name="AspNetSqlMembershipProvider" type="System.Web.Security.SqlMembershipProvider, System.Web, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" />
  12.  
I am confused as to why you have your connection string stuff in there multiple times.

Those articles only apply if you are not using the normal database for state/user management on your site. Is that what you are doing?
Jan 2 '08 #2
I have to transfer my WEB site from my development server to my production server.

My web site, either copied or published, does not work on my production server even if it works on my development server.

I made a research on Google relatively to my error message received on my production server and this article seemed to make sense. Yes, I wanted to not use the normal database for state/user management on my site because these articles are saying that it can not work using the normal database.

Below are the 2 error messages received from the event viewer :

Type : Error (with a stop sign)
Source : MSSQL$UNISQL
Category : 8
Event : 19011

Type : Error (with a stop sign)
Source : MSDTC Client
Category : 10
Event : 4427

Thank you,

Pierre
Jan 2 '08 #3
Plater
7,872 Expert 4TB
Did you create the tables and everything you needed on your production server's sql database?
Jan 3 '08 #4
Not yet because I am trying to have it working on my development server before pushing this solution to my production server.
Jan 4 '08 #5
Plater
7,872 Expert 4TB
Are they set up on the dev server then? they appear to be sql oriented errors?
Jan 4 '08 #6

Post your reply

Sign in to post your reply or Sign up for a free account.

Similar topics

8 posts views Thread by Shimon Sim | last post: by
2 posts views Thread by Xtreeme-G | last post: by
2 posts views Thread by Josh Collins | last post: by
2 posts views Thread by R.A.M. | last post: by
1 post views Thread by RAM | last post: by
3 posts views Thread by GaryDean | last post: by
6 posts views Thread by Jonathan Wood | last post: by
reply views Thread by kermitthefrogpy | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.