Last post Jun 01, 2006 04:31 AM by techy_unknown
Nov 13, 2005 11:58 PM|shadowmaker89|LINK
Nov 15, 2005 11:32 PM|ethos42|LINK
Exact same problems here. I'll be poking around looking for a fix, if I find one I'll let you know.
Anyone else run into this, or know of a fix that has already been posted?
Nov 15, 2005 11:41 PM|ethos42|LINK
I think I fixed mine, check the inner exception message once you log in as host.
If it looks like this: The user instance login flag is not supported on this version of SQL Server. The connection will be closed.
Then you need to change your connection string in the web config. Keep in mind there are 2 connection strings, one which uses the .NET 2.0 style and one which supports the legacy modules directly below it.
Jun 01, 2006 04:31 AM|techy_unknown|LINK
I was facing the same problem. And as "ethos42" mentioned, i had already declared 2 connection strings in <connectionString/> and in <appSettings>, still I was facing same problem.
Then suddenly I observed the connection string which I provided in the <appConfig>, it was something like this:
I dont remember why I have added this attribute. But, it was killing parameter for me. I have removed the attribute TrustedConnection and site is working properly.
So, "ethos42" is pretty closer to the solution that what I feel. i.e. something "not-right" about connectionString.
Just make sure that you have been providing same set of connection string if you are working with MSSQL-2000. I dont know about Yukon. :(