We were experiencing errors with one of our web methods on a test web server. The main error was:
"access to path" e: \ websites \ discovery \ profile service \ App_Data 'is deprecated "
Stack trace slightly more Returns the information:
"Web.DataAccess.SqlConnectionHelper.CreateMdfFile ... on System" "System.Web.DataAccess.SqlConnectionHelper.EnsureSqlExpressDBFile ..." "System.Web.DataAccess .SqlConnectionHelper.GetConnection ... "" on System.Web.Security.SqlMembershipProvider.GetUser ... "" on the system.squirite.manyhip.GETUser ... "" on the WebSub Subscriptions.Getusur .. . "
It appears B membership provider was trying to find a connection string to subscribe call. Upon failing to find this entry, he tried to create a new local membership database and failed to do so with permission error.
We checked the connection string and they looked ok, although they were encrypted. We then saved the config to the connection strings section decrypted - the call is now working!
We know that the connection string was correct because other service methods were working properly. Even stranger is that some aspects of membership have to be worked with encryption.
Has anyone seen this before or how did this work with encrypted connection wires?
In your code, are you decrypting the connection string before making a SQL call?
An error trace from the stack is possible that your app is not allowed to write in that directory.
Comments
Post a Comment