I am working with Sitecore 8.2(Sitecore 8.2 rev. 170614), i have installed exm (Email Experience Manager 3.4.2 rev. 170713). It has been completely installed and then sitecore client has restarted.
I have also followed the instruction written to follow when EXM installation completes but i am not able to see EXM option in Sitecore launchpad or dashboard.
Is there any other settings needs to be done?
You need to add the following entries in your connection string and need to create the database for exm.master and exm.web and generate key for exm.CryptographicKey and EXM.AuthenticationKey. Please let me know if this is not clear or need more info.
<add name="exm.master" connectionString="Data Source
<add name="exm.web" connectionString="Data Source=
<add name="EXM.CryptographicKey" connectionString= "
<add name="EXM.AuthenticationKey" connectionString=
Related
i have been requested to change the authentication mode in my mvc 4 project to be windows authentication, and i was using the asp.net configuration manager.
for us, it will be a major change in the code, so is there any workaround to link our outlook active directory to asp.net configuration manager ?
Try the following setting
<appSettings>
<add key="EnableSimpleMembership" value="false" />
</appSettings>
follow the link for more details
http://www.mikesdotnetting.com/article/216/windows-authentication-with-asp-net-web-pages
I am beginner in ASP.NET MVC. I have been trying to create a web application in ASP.NET MVC 4 by using Visual Studio 2012. I started with internet application and open with default template that has registration, login, home etc pages. I have tried to modify the code available for the registration form as I want and connect with SQL Server database, but it does not work and also only connected with local database it is not connected with my database table I have created in SQL Server. What will I do? Thank you for your help
Have you changed your default connection string in your web.config to point your sql server?
The default connection string will be like this
<add name="DefaultConnection" connectionString="Data Source=(LocalDb)\v11.0;Initial Catalog=aspnet-yourproj-timestamp;Integrated Security=SSPI;AttachDBFilename=|DataDirectory|\aspnet-yourproj-timestamp.mdf" providerName="System.Data.SqlClient" />
In your case you should have changed as follows,
<add name="DefaultConnection" connectionString="Data Source=localhost;Initial Catalog=aspnet-yourproj-timestamp;User Id = xxx;Password = xxxxxx" providerName="System.Data.SqlClient" />
I created a fresh simple ASP.NET MVC 4 Internet Project, then I have created models with the ADO.NET Entity Data Model designer and then I have installed System.Web.Providers (Universal Providers) and configured Web.config in order to have two different data sources, both using SQL CE 4.0.
These are my connection strings:
<add name="DefaultConnection" connectionString="Data Source=C:\maindb.sdf" providerName="System.Data.SqlServerCe.4.0" />
<add name="MyEntitiesModelContainer" connectionString="metadata=res://*/MyEntitiesModel.csdl|res://*/MyEntitiesModel.ssdl|res://*/MyEntities.msl;provider=System.Data.SqlServerCe.4.0;provider connection string="Data Source=C:\myentities.sdf"" providerName="System.Data.EntityClient" />
The application works. But when I try to login, this is the exception I get:
To call this method, the "Membership.Provider" property must be an instance of "ExtendedMembershipProvider".
I have also added <add key="enableSimpleMembership" value="true" /> in Web.config because someone on different forums solved the problem doing this. It wasn't my case, the same error remains.
Could anyone help me please?
ASP.NET MVC4 ships with simple membership, and simple membership works with SQL CE out of the box, you don't need (and in fact can't use) the universal providers with Simple Membership.
From this ASP.NET forum post:
Thanks for the hint. Now that I was able to see that the provider was
being hijacked, I added
<appSettings>
<add key="enableSimpleMembership" value="true" />
</appSettings>
Everything Seems to be working fine now.
I have develop MVC Web Application
I use ASP.Net authenticate to implement my login form
The problem is that i cannot deploy it to server.
In the first i use ASPNetDB.mdf which is a file store in AppData forlder
After that I change to store ASPNETDB as a database in SQlServer and also update the connectionstring to new database
In the development environment both of them work well
But when I deploy to IIS, I cannot login, it show me following error :
"Failed to generate a user instance of SQL Server due to failure in retrieving the user's local application data path. Please make sure the user has a local user profile on the computer. The connection will be closed."
Here is my connection string:
<connectionStrings>
<add name="ApplicationServices"
connectionString="Data Source=.\PHDatabase; Initial Catalog=aspnetdb;User ID=sa;Password=****" />
</connectionStrings>
I try to google a lot but until now, there is no result
Please help me to solve the problem
Regard
Try replacing machine name instead of a "."
Data Source=machinename\PHDatabase; Initial Catalog=aspnetdb;User ID=sa;Password=****
The other possibility is if you are using certain wizards like Linq2Sql etc., they might keep the connection string inside the code. Check for them as well..
In development environment, when you are using Attached Database file from App_Data folder with SQL Express, you should use the following connectionstring
<add name="YourConnectionStringName"
connectionString="data source=.\SQLEXPRESS;Integrated Security=SSPI;
AttachDBFilename=|DataDirectory|\YourDatabase.mdf;User Instance=true"
providerName="System.Data.SqlClient" />
But, when you testing or deploying with Database on the SQL Server, you should make use of following type of connectionstring
<add name="YourConnectionStringName"
connectionString="Data Source=db.YourhostedResourceName.com;
Initial Catalog=YourDbName;User ID=yourusername;Password='yourpassword';"
providerName="System.Data.SqlClient" />
I have implemented my own custom Role manager object. When I run my web app using the visual studio version of IIS, it works fine. I can see the username and I can drill into my Role Manager class and see what it's doing. When I debug the app using IIS 7, HttpContext.Current.User.Identity.Name is blank and it does not use my Role Manager class when determining what roles my user has. I've checked that all my dlls are in the bin directory.
I'm guessing that the problem is on IIS 7. What do I need to configure on IIS 7 to make this work and to make it use my Role manager?
Here is a snippet of the web.config that sets the role manager.
<membership>
<providers>
<clear />
</providers>
</membership>
<roleManager defaultProvider="HyperionRoleProvider" enabled="true">
<providers>
<clear />
<add name="HyperionRoleProvider" type="Census.BUD.Common.HyperionRoleProvider" applicationName="/" />
</providers>
</roleManager>
From:
http://learn.iis.net/page.aspx/528/how-to-use-the-sample-read-only-xml-membership-and-role-providers-with-iis-70/
"These samples are excellent for use with IIS 7.0 for demonstration or test Web sites, but they don't work as-written with IIS 7.0 because of the way that IIS 7.0's security is designed. The original instructions allowed you to deploy the sample membership/role providers into the App_Code folder of your Web site, but IIS 7.0 requires that providers are registered in the Global Assembly Cache (GAC) before they can be deployed. With that in mind, the following steps will walk you through compiling and deploying the read-only XML providers on a development system."
Make sure your assembly is in the GAC