usman
Nuke Newbie Posts:4
|
07/04/2010 2:56 PM |
|
Hello, I am a beginner using dnn. I have successfully installed DNN on localhost from dnncreative tutorial. But now when I go to: localhost/dnn_site/Default.aspx I get this error: "This site is currently Unavailable Please check back later" I have checked the connection string and It is fine.. (One thing I did after installation is that I changed Autoupgrade in web.config file to false.) Now when I changed it to true it goes back to the installation page not the actual default.aspx page ) Confused Now this is letting me down.. I can't enter to website... Anyone????? DNN EXPERTS????? HELP NEEDED????? Thanks, USMAN |
|
|
|
|
Joseph Craig DNN MVP Posts:11667
|
07/04/2010 7:49 PM |
|
Did you check both versions of the connection string?
Did you install using the installation wizard?
|
|
Joe Craig, Patapsco Research Group Complete DNN Support |
|
|
usman
Nuke Newbie Posts:4
|
07/05/2010 3:21 AM |
|
Thanks for the reply, I have checked conn string and app settings in web.config file, both are right.. And I have installed dnn using installation wizard. But still getting the same problem. ?? |
|
|
|
|
Joseph Craig DNN MVP Posts:11667
|
07/05/2010 8:02 AM |
|
When you get the error, is it from the correct url? Is there a url that I can see?
|
|
Joe Craig, Patapsco Research Group Complete DNN Support |
|
|
usman
Nuke Newbie Posts:4
|
|
Joseph Craig DNN MVP Posts:11667
|
07/05/2010 10:14 AM |
|
As this is a new installation, I would reinstall it.
First, completely delete the website, the web directory, and the database. Then, create a new empty database, and reinstall DotNetNuke. Go through the steps carefully and watch for problems or errors.
|
|
Joe Craig, Patapsco Research Group Complete DNN Support |
|
|
usman
Nuke Newbie Posts:4
|
07/05/2010 10:17 AM |
|
Okay Thanks, I'll do that. |
|
|
|
|
L Douglas
Nuke Newbie Posts:2
|
07/06/2010 10:27 AM |
|
When I have had this issue, simply deleting: dnn_site/Install/UnderConstruction.htm, fixed the problem. This file is created from the template version when DNN comes across an issue. |
|
|
|
|
Yosief Kesete
Nuke Newbie Posts:8
|
11/28/2013 8:59 AM |
|
Hello I'm getting this error right after upgrading my DNN 5.6 site to 6.2. I can see there are no errors during the upgrade process. Any ideas?? |
|
|
|
|
Joseph Craig DNN MVP Posts:11667
|
11/28/2013 9:54 AM |
|
Most often, this means that the website is not able to connect to its database. So, check the connection strings in the web.config to make sure that they are correct (though, if the site was running before the upgrade, it's hard to see how this could have changed). You can also edit the customErrors line in web.config to read: This may provide more information. If you can't get anywhere with that, hopefully you have a backup copy of the site before you did the upgrade. If so, I'd restore it and try the backup again. Before doing the restore a second time, make sure that you have UNBLOCKED the upgrade file so that all files will be extracted. If that doesn't work, let me know. |
|
Joe Craig, Patapsco Research Group Complete DNN Support |
|
|
Yosief Kesete
Nuke Newbie Posts:8
|
11/29/2013 8:00 AM |
|
I've have the following in my web.config ...
<customErrors mode="Off" />
.. and I can't get specific details of the error. What do you mean by UNBLOCKING the upgrade files? Before I initiated the upgrade process, I ensured that none of the website files is read-only. If that's what you mean. Thank you |
|
|
|
|
Yosief Kesete
Nuke Newbie Posts:8
|
12/02/2013 7:50 AM |
|
Hello Joe I've set customErrors to Off in my web.config. It didn't help in anyway. (I've noticed any text pasted from web.config XML is invisible in this page :-) ) Could you please explain what you mean by UNBLOCK the upgrade files? I'm having no fun at all troubleshooting this error. Thank you Yosief Kesete |
|
|
|
|
Joseph Craig DNN MVP Posts:11667
|
12/02/2013 2:18 PM |
|
For "unblocking", right click on the upgrade zip file and select "properties." If you see an "unblock" button, click it and then extract files. |
|
Joe Craig, Patapsco Research Group Complete DNN Support |
|
|
Yosief Kesete
Nuke Newbie Posts:8
|
12/03/2013 6:51 AM |
|
Unfortunately, that didn't help either. I noticed the version of the database is still at 5.6 instead of the expected 6.2. Does the DB get upgraded the next time the site is running? Otherwise, I can't think of anything else that can cause a version mismatch between the DB and website files. To give more background, we decided to upgrade after realizing a third-party e-commerce module called SmithCart suddenly stopped working in production. After trying so many things, I've a serious doubt the upgrade error is related to/caused by this module. I can't conclusively prove this as there's no log that's being written inside the web folder, or the EventLog DB table or in Windows Event Viewer. |
|
|
|
|
Joseph Craig DNN MVP Posts:11667
|
12/03/2013 9:31 AM |
|
The first step in the upgrade process is upgrading the database. So, if this has not been done, something went badly wrong during the upgrade. There are log files created in the upgrade located in Providers\DataProviders\SqlDataProvider. Look for *.log.resources files. When you say that the database hasn't been upgraded, how did you check this? Did you look in the Versions table? Are you able to revert to the original version and do the whole upgrade process again? |
|
Joe Craig, Patapsco Research Group Complete DNN Support |
|
|
Joseph Craig DNN MVP Posts:11667
|
12/03/2013 9:31 AM |
|
The first step in the upgrade process is upgrading the database. So, if this has not been done, something went badly wrong during the upgrade. There are log files created in the upgrade located in Providers\DataProviders\SqlDataProvider. Look for *.log.resources files. When you say that the database hasn't been upgraded, how did you check this? Did you look in the Versions table? Are you able to revert to the original version and do the whole upgrade process again? |
|
Joe Craig, Patapsco Research Group Complete DNN Support |
|
|
Yosief Kesete
Nuke Newbie Posts:8
|
12/04/2013 9:27 AM |
|
It turned out I needed to upgrade my DNN 5.6.2 site to 5.6.8 first. I referred to the suggested upgrade path below but my assumption that I could upgrade from 5.6.2 to DNN 6 straight proved horribly wrong. After all, there is some significant upgrading that happens from 5.6.2 to 5.6.8 http://www.dnnsoftware.com/wiki/pag...grade_path What I've realized in the past few days is upgrading DNN to latest version is essentially a trial-and-error process. For the sake of sharing, here is the path that has worked for me so far: 5.6.2 >> 5.6.8 >> 6.2.8 >> 7.0.0 >> 7.0.6 I'm unable to take it further to DNN 7.1.2 because there is an error in the Install.aspx.cs in versions above 7.0.6. The error has been reported here: http://www.dnnsoftware.com/answers/cid/420868 Thank you very much for your assistance, Joe! |
|
|
|
|
Joseph Craig DNN MVP Posts:11667
|
12/04/2013 10:26 PM |
|
Did you see this comment: please make sure, app pool is running ASP.Net 4.0 integrated mode. I upgraded a site last night and today from 5.6 to 7.2 (7.2 was just released today). Following the suggest upgrade path is definitely the way to go, and it does reduce most of the "trial and error" part. Crossing major boundaries is always a big deal. What is the actual arror message you are receiving? There probably are clues there. |
|
Joe Craig, Patapsco Research Group Complete DNN Support |
|
|