Hi all,

1 year ago I was a DNN-n00b. However, I have been putting some hours into DNN and now I have been a DNN module developer for some time. I had the standard setup of DNN running via VS2008 using SQL 2005 Express (using attachdbfile). Due to the new release, some basic mistakes and some mess I decided to make a clean install. So I uninstalled my DNN 4.8.0 development environment (deleted files and DB).

I have then downloaded DNN 4.9.0 (both install, starterkit, and source packages). I set up my DNN folder (with same permissions (also for ASPNET and NETWORK SERVICE)). I created myself a DB in SQL Express called DNN_Development. I created a DB login for dbo rights.

Everything should be ready to install DNN. However, while "installing database scripts" it just stalls. I see "dbo.Version" as the only table and also 3 stored procedures (dbo.FindDatabaseVersion, dbo.GetDatabaseVersion, dbo.UpdateDatabaseVersion). But here the installation stalls and nothing happens.

I have tried to bypass the problem by compromising security in any way. Giving full connection rights to SQL by named pipes and TCP. I have given all rights to the DNN folder for all. I have tried both using the default attachdbfile method for SQL Express and custom create using both integrated security and DB logins. I have tried to enable this mystery feature "user instances". However, no matter what I do it seems that DNN or SQL has simply decided to kill me or something. The DNN website runs (as always) via the Visual Studio  ASP.NET Development Server on port 1544, which has always worked fine.

The only thing I might come up with is that I am not sure if the 4.8.0 was running with my SQL 2005 Express without SQL 2005 SP2. I have since then updated SQL 2005 Express to SP2 via Microsoft Update. Is there a known issue with SP2?

Unless someone has a miracle up their sleeve, I guess I will have to try to reinstall SQL 2005 (no matter how much I hate to).

I always retry from a complete 100% blank database and reset folder :-)

It seems that I have overlooked a topic in the forum. However this topic does not ultmiately provide a solution.

Similar problem: http://www.dotnetnuke.com/Community/Forums/tabid/795/forumid/107/threadid/236041/scope/posts/Default.aspx

It seems that it may be a problem with installing DNN from the ASP.NET Development Server. An option would be to install DNN from IIS and then later use ASP.NET Development Server. However, I don't have IIS installed on my workstation and would like to avoid that. Besides, DNN should be installable from running CTRL+F5 in VS2008 ;-)

Are there any resolutions for this issue yet? .... please, without installing IIS.

There is no simple solution to this.

The problem is the following.

1. The Development Server (Cassini to use its previous codename) processes files differently to IIS.  IIS has a lot of configuration options and allows Administrators to determine which files get "sent" to .NET for processing (eg, aspx, ascx, ashx, asmx, axd - to name the most common), and which get sent to other file processors.  Cassini has no configuration options so sends eery request to .NET.
2. some js files and image files, if not all of them, throw exceptions when being processed as they are NOT .NET files.  This stops the file from being sent to the browser.
3. This explains the missing image - as it is not sent to the browser
4. It also explains the Wizard issue as the Wizard uses javascript and AJAX style callbacks during the database script processing.

The fix was to add "checks" in all of the various places where requests are processed to ensure that the file being processed was a valid .NET file.

I know I spent a lot of time on this issue a few months back - but at the time we were not planning a 4.9 release so all my fixes went into the 5.0 codebase. 

I will be confirming this today.