I have had my site up and running for a while now (thanks to the help of a lot of you in these Forums) but seem to have an issue arise randonly where I get the following message when trying to go to the main page:

Server Application Unavailable

The web application you are attempting to access on this web server is currently unavailable.  Please hit the "Refresh" button in your web browser to retry your request.

Administrator Note: An error message detailing the cause of this specific request failure can be found in the application event log of the web server. Please review this log entry to discover what caused this error to occur.

Obviously I have Go Daddy involved as they say there is an issue with the ASP virtual instance and it has hung.  They also mentioned some potential code issues.  I have been through everything and haven't found anything yet, but keep looking.  I hope to get the logs from Go Daddy soon.

Has anyone else seen tis or a similar issue?

Thanks!

Bob

A quck search would have found you the GoDaddy Walkthrough:

http://forums.asp.net/thread/1220730.aspx

Jeff

Jeff,

Great!  Thanks!   I read that some time ago and found it very useful.  It was instrumental in getting my site up and running @ Go Daddy.

My issue is a little beyond the walk through however.  Site is posted and running, but I have had two random issues as described in my initial post.  Go Daddy initially reported it as a "hung" ASP instance and reset it.  Everything was fine for a few days, then it appeared again.  Being a repeat issue, they (Go Daddy) have escalated it and suggested I give the code a look through one more time.    Go Daddy has been very responsive in helping isolate the issue.  I have completed pass two and am working pass 3. of the code review

I am hoping someone may have experienced a similar issue and would have a recommendation for me.

Thanks for your input and suggestion and I'll read through the walkthrough again!

Bob

Shane,

Thanks for the info.  I will use your site as a reference.  Nice site by the way.

Go Daddy emailed me yesterday and they have moved my site to a different ASP application pool to see what happens.  Everything they discussed pointed to an issue on the server, but they requested I look through the code jsut to be sure.

I haven't modded the code a great deal from the original.  Implemented the fixes found, added the Forums (latest version) and the Admin pages, and of course content changes, but left everyhting else, even color for now, the default.

I have had very good service and luck with Go Daddy thus far and feel comfortable they will help correct the issue.

Again, thanks for the reference and all the input in the forums.  I have found them invaluable.

Bob

Here is an update from Go Daddy as my issue appeared again after the moved my site to its own asp application pool.

They suggest this is a scripting issue where I am not closing ASP objects (scripts and databases) after I am through using them.  As a newbie to ASP, I have no clue even where to start looking.

Any suggestions, thoughts or similar issues.  As a refresh, here are the site specs:

• Base Club Starter Kit with all corrections to issues listed in this forum added
• Added Forums module
• Added Web Admin module
• Changed some text

www.prccsoccer.com

Bob

Hiya Bob - did you get the actual log entries from Godaddy describing the error? I doubt it's a leak - even if you forgot to close db connections (or they didn't get closed because of some other error), they still get garbage collected in asp.net 2.

Just a thought, did these errors happen right after you had updated an aspx file or a code file? If you hit the site right after that, when it's still rebuilding the changes, you'll get that sort of error. Then it goes away after a few seconds. You didn't mention whether this error brings everything to a halt, or if it's just transient.

Hey Mark,

Go Daddy couldn't / wouldn't provide the logs so there was no help there.  I went through the code and made sure that there was a close connection for every open connection and that was all OK.  I took a clean install of the kit, made all the fixes and looked at all the DB connections. 

I did find some areas where I may have used the incorrect SQL script to install either the Forums package or the WebAdmin package so I changed all of that, rebuilt the site and posted it again into production.  I have been in and out of it all day, made numerous additions and updates to Events and  Locations and no issues so far.  THis only seems to appear every few days and per GO Daddy has something to do with the virtual ASP instance.  I'll check the exact error message in my email at hone and post it.

So, my changes to the site were minimal after speaking with Go Daddy:

1.  removed dbo from some SQL statements like dbo.events (replaced them with nulls).
2.  Changed the conn.open and conn.closed commands to be connection.open and connection.close
3.  Rebuilt and Posted site

I really don't believe that steps 1 or 2 were/are the culprits, and would tend to think 3 would be a better candidate (sometimes compiling and transferring just don't work).  Only time will tell.

The errors I was getting were happening after days since the last post.  My indication was the error message.  It never even loaded the default.aspx page.  I could however laod the welcome.html that came with the started kit and the stats pages you get from Go Daddy.

Let me kow if you have any other thoughts.

Bob

I have been the Godaddy route with a VDS (Virtual Dedicated Server) and the Club App.  And even after I got it working (actually I had 2 separate Club apps running at the same time) my VDS would run slow and I seemed to constantly have to reboot it.

I know Godaddy's prices are low, but their hassle factor is extremely high and I finally left them for HostMySite.com.  They have 24/7 support with real people answering the phone and they are very helpful.  They are just now starting to offer SQL Server 2005 Express packages.  Whether they fit in your price range or not I don't know, but I saved $5.00 per month when I switched to their VDS (they call it a VPS - Virtual Private Server).

Use Godaddy for your DNS management (their prices can't be beat and it's kinda tough for them to screw that up), but find some other hosting company for your Club App.  It will keep the veins in your head from bursting.

BTW, if you would like the web.config that I used on Godaddy, I would be more than happy to email it to you or paste it on this forum.  But I strongly urge you to abandon Godaddy post-haste.

John