Last post May 05, 2015 03:25 PM by davidan
May 05, 2015 10:57 AM|davidan|LINK
We imported a new web projects ASPNETDB..MDF into an enterprise SQL DB. When I attempt to connect to the DB and log into my web app though, I am getting a lengthy ASP.net error message (that I am having a hard time parsing for the cause of the crash).
The DB seems to have been migrated OK, I can open the DB from SQL Studio and see the tables;
I am attempting to tweak a new connection string to point to the enterprise version of the DB, (trying to get it to look like connection strings that we use for our other enterprise DBs) but I can't get connected.
source=.\SQLEXPRESS;Integrated Security=SSPI;AttachDBFilename=|DataDirectory|\aspnetdb.mdf;User Instance=true"providerName="System.Data.SqlClient"
Source=(Removed);Initial Catalog=ASPNetDB;Persist Security Info=True;User;ID=(removed)Password=(removed);User Instance=true"
Has anyone published a how-to on using the ASP.Net membership provider with a non-local SQL DB?
May 05, 2015 01:38 PM|PatriceSc|LINK
So it seems you are using an enterprise grade SQL Server so I would say you are not using SQL Server Express? Assuming you are using the 2nd connection string, remove the User Instance=true part and see what happens.
If it doesn't hrelp, it seems best to show the exact connection string you are currently using as well as the error message you have (of if this is the generic ASP.NET message see the event log to see the actual message).
It's always easier to tell how to fix an issue when knowing exactly what it is.
May 05, 2015 03:25 PM|davidan|LINK
Eureka That Was IT!!!!
...and, in our case, the final answer was...
Source=(REMOVED);Initial Catalog=ASPNetDB;Persist Security Info=True;User ID=(REMOVED);Password=(REMOVED);"