ozzie
Nuke Newbie Posts:3
|
04/15/2010 7:20 AM |
|
gday
I had to reformat my server 2003, but had backed up my DNN data before proceding
when I reinstalled server 2003 and all its componets , I proceded top restore my .bak file which was successful (I checked the tables) but when trying to load my dnn web site it tells me this site is currently unavailable.
im using same url and database names etc in the web config
I have and can install a new DNN but I really do want to restore all the data I have on the old site
I am running .net 3.5 and sqlserver 2008.
any help please |
|
|
|
|
ozzie
Nuke Newbie Posts:3
|
04/15/2010 8:08 AM |
|
ok I think the problem is a permission issue but ive been everywhere to find it but cant seem to locate the problem. when I try and log on I get this http://www.campinginwa.com/Install/...uction.htm in teh address bar I delete everything after install then I get this web page this website requires you to log in as most likley cause This error (HTTP 403 Forbidden) means that Internet Explorer was able to connect to the website, but it does not have permission to view the webpage. For more information about HTTP errors, see Help. The website declined to show this webpage HTTP 403 Most likely causes: •This website requires you to log in. |
|
|
|
|
kaushal
Nuke Ace Posts:42
|
04/15/2010 8:29 AM |
|
I have some work-a-round when I faced this issue in past: check out Even Viewer (Start > Run > eventvwr) you might get more information on the err you are facing. Also check that Sql Server Browser Services are On or not (Start > Run > services.msc and see status of this services) |
|
Mocrosoft MVP [.NET/ASP.NET] |
|
|
ozzie
Nuke Newbie Posts:3
|
04/15/2010 8:57 AM |
|
thanks for the reply but no indication in the event logs that tells me the problem and teh Sql Server browser is running ok |
|
|
|
|
Joseph Craig DNN MVP Posts:11667
|
04/15/2010 10:43 AM |
|
Start by placing an index.htm file in the root of your web directory. If you can see that when you browse to your site, you know that IIS is reaching it correctly.
Once you have done that, rename index.htm to app_offline.htm. If that is served, then ASP.NET is also working.
If both of those work, but your site doesn't work when they are removed, there is some sort of error with the DotNetNuke installation. Triple-check that the ASP.NET worker task has full permissions in your website's directory.
If this isn't enough, ask again.
|
|
Joe Craig, Patapsco Research Group Complete DNN Support |
|
|
ozzie
Nuke Newbie Posts:4
|
04/15/2010 6:47 PM |
|
sorry my bad I should have mentioned that IIS and asp.net are both working , and I have quadtriple checked that the DNN instalation is working, I have 3 DNN sites up and all have given me the same problem on restore, I did create a script to check the ASP and it returns witht he version I have. Im no dummy with DNN but im sure missing somethink here. |
|
|
|
|
ozzie
Nuke Newbie Posts:4
|
04/15/2010 10:54 PM |
|
I have fixed the issue after much swearing at the server ,( I think the swearing did the trick) modified the reg code slightly, but now I have another issue, I have a application error, for which it tells me to turn CustomerErrors Mode Off, which had all ready been done, but only now get this Runtime Error Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). It could, however, be viewed by browsers running on the local server machine. Details: To enable the details of this specific error message to be viewable on remote machines, please create a tag within a "web.config" configuration file located in the root directory of the current web application. This tag should then have its "mode" attribute set to "Off". <!-- Web.Config Configuration File --> Notes: The current error page you are seeing can be replaced by a custom error page by modifying the "defaultRedirect" attribute of the application's configuration tag to point to a custom error page URL. <!-- Web.Config Configuration File --> Do you think a little bit more swearing at the server will fix it
Sorry guys the error message would not paste but I think you know what I mean |
|
|
|
|
Joseph Craig DNN MVP Posts:11667
|
04/16/2010 11:14 AM |
|
Swearing never hurts!
Is there any chance that you are using an Object Qualifier in your database and have lost that in your web.config? (I only ask because that kept me up last night until I figured it out.)
Often, the message about the site not being available is related to a database access issue.
Are you sure that it's connecting to the database? Maybe you can run the Profiler and verify? |
|
Joe Craig, Patapsco Research Group Complete DNN Support |
|
|
ozzie
Nuke Newbie Posts:4
|
04/16/2010 3:47 PM |
|
I think you are onto somethink here , I did swap from sql server 2005 to 2008, will scan web config see if there is anything changed or missing Thanks |
|
|
|
|
ozzie
Nuke Newbie Posts:4
|
04/17/2010 10:07 PM |
|
well I fixed the problem after more swearing at the computer a simple thing (dont ya hate that) I simply recreated new database names and logins (different from the origianla names)and changed the web config reset the DBO owners restored the .bak file and they came straight up |
|
|
|
|
Ken Florian
Nuke Newbie Posts:1
|
04/08/2011 11:37 AM |
|
I'm now working my way through the "This site is currently Unavailable" issue and have worked through the various scenarios in this thread but I am still overlooking something. I'm moving dnn from external host to internal. What does it mean if app_offline.htm does not load but index.htm does? I used Mike van der Meulen's "setup dnn" to get an initial install of dnn 4.9.5 running. I then restored my db over the one created by that setup and copied in the files. The "new" sql database name is the same as the old, web.config connection strings are, I believe correct. I have, for the time being, a portal alias for localhost. Any additional guidance appreciated. Ken
|
|
|
|
|
Joseph Craig DNN MVP Posts:11667
|
04/08/2011 6:23 PM |
|
If putting an index.htm file in the directory results in that loading, but putting an app_offline.htm will not load, that would seem to imply that there is something wrong with ASP.NET. That's because index.htm is loaded normally, but ASP.NET is what loads app_offline.htm. That doesn't go with the fact that 4.9.5 was working. I would: 1. re-restore your db. You might want to delete what's there, create and empty database and then do the restore. 2. Delete everything in your web directory and then recopy the files and fix the connection strings. What happens then? |
|
Joe Craig, Patapsco Research Group Complete DNN Support |
|
|