BugNET

Thanks. I'm being particularly dense

The only connexion string I can see here is the "BugNet" one, which of course points to my defects database (SQL Server 2008 etc etc). I copied this from my previous install and it's definitely correct. I thought you were using something else for membership/ roles. I just fired up MSSMS and the BugNet database (same connexion string...) doesn't look like it's got asp.net membership stuff in it to me. I don't have the tools to check myself, but surely the membership database is separate.

This error looks like it's *membership* database related. I followed the upgrade instructions, but there's nothing there about copying the user database over to the new install, so I can't see how those instructions could work. Hence my earlier question: does anyone know where the membership/ roles database for BugNet lives? If I can find out where that is, then I can move it from the old installation to the new, and then it may work. I think there must be something I'm missing, or something which is missing.

I note that it says: "[delete all the old stuff except] Your App_Data folder (if you are using sql express)". I'm still not using SQL express, but is this statement imprecise? Is that where the membership database lives? I don't think that's it as I went back and tried to dick with this, but it may have been that by then it had written stuff to the web.config and got its nicks in a knot already.

Hence my question: where is the membership database because the installation script is presumably looking for it. So am I.

Thanks - I checked those but they're all BugNet. It's a bank-holiday weekend here so I may be able to have another go at this over that without upsetting anyone and maybe I can make it work.

Some thoughts:

(1) Do I have to move the "installation date" setting from the old web.config before running the upgrade scripts? I see no specific instruction on this, and as that was written at the time of last installation I did not move it initially. Is this important?

(2) I do not have SQL Server Express. Do I need to have anything in my App_Data folder or not? The instructions are ambiguous on this point, but it takes me several hours for each backup/ restore cycle so I can't really test it both ways and be sure that this matters.

I'm following the instructions, but it's not working => either I missed an instruction, or there's something implied there which I don't know. Has anyone else upgraded this following the instructions and if so were there anythings you had to do in addition to the instructions?

Are there any ways other than by the instructions to do this upgrade?

Not sure what to try next. So my connexion string is (changed to protect the guilty):

add name="BugNET" connectionString="Server=BB-PC\SQLEXPRESS;Database=BugNet;User ID=BugUser;Password=233!flart.wA1ng;"

So let's see where that's used in the web.config, in case I'm missing something. Searching for the string, I find:

DataProvider defaultProvider="SqlDataProvider" providers add name="SqlDataProvider" type="BugNET.DataAccessLayer.SqlDataProvider, BugNET" connectionStringName="BugNET"
Looks ok, all cases match etc. That's used before it's declared, but that should not matter I think.

Next up, the membership provider.

membership defaultProvider="ExtendedSqlMembershipProvider" providers clear/ add name="ExtendedSqlMembershipProvider" type="BugNET.Providers.MembershipProviders.ExtendedSqlMembershipProvider, BugNET.Providers.MembershipProviders.ExtendedSqlMembershipProvider" connectionStringName="BugNET"

That points to the same thing, cases match etc.

And here we have the role provider:

profile enabled="true" automaticSaveEnabled="false" defaultProvider="MyProfileProvider" providers clear / add name="MyProfileProvider" type="Altairis.Web.Providers.SimpleSqlProfileProvider, Altairis.Web.Providers" connectionStringName="BugNET" tableName="BugNet_UserProfiles" keyColumnName="UserName" lastUpdateColumnName="LastUpdate"

Again, it's all good as far as I can tell. Hmm.

So let me stomp on my connexion string, I'll replace the database name with garbage.... precisely the same error comes up. So maybe this error means:

"for some reason I cannot ascertain I cannot find your database from that connexion string. It's not the user name or password, it's something else which is stopping me from connecting to the thing. "

That's odd though, as I can connect neither to the database on Rackspace nor to my local copy of it. I could make a typing error with one, but both is highly unlikely.