I've had DNN 04.09.00 running for a couple of weeks and have been working on a module. After a re-complile with VWD today I can no longer get DNN to access the pre-existing database. Are the tools this fragile? Do the database access credentials somehow change?
When I start the VWD debugger the browser pops up with a message that I've read all too many times in these blogs ...
ERROR: Could not connect to database specified in connectionString for SqlDataProvider
or
the Website declined to show this webpage.
When I leave VWD and load a browser instance with the path localhost/.../default.aspx (which used to work) I get the all too familiar: [SqlException (0x80131904): Cannot open user default database. Login failed. Login failed for user 'MYCOMPUTER\ASPNET'.]
What worries me is the fact that I've had this working and I read that too many folks simply blow out everything and keep reinstalling until it works. In my book that isn't a solution. No, I haven't moved the code. It claims to successfully compile.
Tools: SQL Express 2008 and VS2008, and VWD 2008 version.
I used VWD Database explored and it can connect to my database... I can see the table extries. I can connect to the database using MS SQL Server management studio and see the table entries. I can run the test button connection string successfully.
I don't get it. Somehow my gut says this has to do with microsoft, but a severe problem exists.
I seek a solution, not just another installation attempt in hopes it will work and then wonder in the future should it break why and how.
Thanks,
David