Hello, Timm.
With the push to get the release version of Cassini out of the door ASAP, we were unable to process all issues right away.
To update you on our progress: we looked into the web.config you provided and we see that there may be a SQL user mismatch that causes the connection refusal, because IIS processes usually run under "NETWORK SERVICE" or "ASPNET account, depending on Windows version, while Cassini runs under "LOCAL SYSTEM" by default. This clearly can create issues with SQL integrated auth. But as we are very busy with regressing last builds of Cassini, we didn't get to resolving the issue. It will take us about a week to release new version of Cassini. After that we should be able to tackle the issue you submitted. If anyone wants to try finding the answer, here's hint where to look:
- Change Cassini service's account to "ASPNET" and/or "NETWORK SERVICE" and see if DNN passes the phase where it can't connect to the DB;
- If it does, create another login in the SQL Express matching "LOCAL SYSTEM" account and map appropriate DNN DB user to the login;
That is what we are going to try once Cassini release is behind us.
All the best,
People of UltiDev.
Please donate at
http://www.ultidev.com/products/Donate.aspx to help us improve our products.