Dec26Written by:Will
12/26/2008
Every once in a while, I face an error installing DotNetNuke that completely frustrates me. It is only because it forces me to start over with the installation process.
Installing DotNetNuke has become a very easy task these days, thanks to the installation wizard. That is one of the best features in the project, as the biggest problem with most web applications is getting the installation completed. There is one problem with it though.
One of the steps in the installation shows you the status of the database scripts as they are getting executed on the database. Typically, you would see a completed database script listing as shown in the following image.
However, everyone once in a while, you'll see a listing more like the next image, where an error is just repeated over and over until you stop the website. The error is "undefined...Success".
I do not know exactly where this happens, but I have narrowed down the fix to this problem. Well, it is more of a work-around. Basically, the permissions for the entire website have not yet propogated to all of the child folders and files in your website directory. The initial file permissions check doesn't validate all files and folders, just the first level. Getting around this and having a clean and successful DNN installation is quite easy though.
- Delete all of the files in the website directory.
- Unzip the installation files back into the website directory.
- Right click on the root folder of your website, and choose the Properties option in the context menu.
- When the properties dialogue opens, choose the Security tab.
- Click the Advanced button.
- Check the check box to "replace permissions on child objects".
You will likely need to delete your database instance, and create a new one as well. I always delete the database as a rule. But if you want to be sure, check to see if any tables or stored procedures were created.
Technorati Tags: DNN, DotNetNuke, DNN Blog, 4.09.01, Installation
Copyright ©2008 Will Strohl
13 comment(s) so far...
Hi Will,
This problem also happens (for me, anyway) when I fail to remember to set appropriate permissions on the database, and skip the verification step. Since I have the world's strangest dev database setup, I assumed it was just me and didn't log it.
Do you have a Gemini work item open? If so, I'll note this there.
By Brandon Haynes on
6/15/2009 |
I haven't been able to completely track this down yet, but I am able to correctly go through database and file verification. So, a child folder somewhere doesn't have this problem.
I have not yet entered this into Gemini. Usually, when I have this little bit of information and it is not always able to be duplicated, it gets closed. But since you have verified my findings, I feel a little better about doing this now.
By Will on
12/27/2008 |
|
These all are just because of database collation guys. try Latin1_General_CI_AS as db collation for dnn database..all your headache will be gone..these problems are source just because of bad dnn documentation..cheers
By inanc on
6/15/2009 |
The collation is not the problem. I set the collation to Latin1_General_CI_AS and it made no difference in regards to this error. The inherited permissions fix had no effect on my installation. I am still getting the undefined...success and then undefined...FAILURE-
By Rockn on
9/11/2009 |
This is an error related to permissions in your file system. You need to double check your file permissions on your entire DNN folder and file collection.
By Will on
9/11/2009 |
All of my permissions are correct for the root of the web site and I am still having issues with this. I have jumped through thousands of hoops to get this to work on my Windows 2003 server with little or no luck and different advice from everyone and their brother with no luck.
By Rockn on
9/21/2009 |
Hmmm... Permissions have always been the root of the problems in my experience.
By Will on
9/21/2009 |
I have tried as suggested by will...i m trying to install version 4.09.03 and am always getting this error. I am trying to install it on my local computer in IIS and have given full control permissions to the entire files and folders in the main folder(DNN Folder too)Please help and suggest how to overcome this issue...
By Soumyo Chatterjee on
12/21/2009 |
I have to first ask, "why are you trying to install v4.09.03 at this point?" Even if you want to stay in the version 4 series of DNN, I must suggest that you move to version 4.09.05 for security and stability reasons.
By Will on
12/21/2009 |
Friends just change the DB and login.. Update the same in web.config. Its working for me after a long research.
By ven on
8/4/2010 |
Can someone please consolidate all of this thread and write up the real solution to the problem? I have lost an entire day looking for the solution to this.
Lost time is lost money. At some point, DNN will be deemed unusable by the community if a simple install cannot be achieved without serious pain.
By Mark Fresa on
8/27/2010 |
@Mark: The solution for this problem is VERY simple. Ensure your permissions are completely propogated BEFORE installing. That's it. I thought I summed this up in the post itself, but I guess it wasn't clear enough.
Honestly though, I haven't seen this error for a couple of years. And to say people won't use it is quite a polarizing statement. Actually, the opposite is happening, literally by the thousands each month. I am one of the few people that have physically demo'd various CMS's side by side, and DNN beats everyone in features and ease of install.
Just to be clear through, the installation is not perfect. We all know that. Like the other areas of the platform, you will continue to see improvements as new releases become available.
By Will on
8/27/2010 |