Help for troubleshooting installation on shared server

Topics: ASP.NET 2.0
Aug 17, 2007 at 7:25 PM
Greetings. I read everything I could find on installing BlogEngine.net on my goDaddy account. I did every steps I found.

aka :

1) Edited the web.config to take out the trust-related line.
2) Created a BLOG folder on my site, gave it Read/Root/Web permissions.
3) Created by hand the App_Data folder, gave it Read/Write/Web persmissions
4) Manually uploaded the content of the App_Data
5) Uploaded the rest of the site in the BLOG folder.

I keep getting "Server Application Unavailable" with a message about the event viewer but sadly I don't have access to it as it's a shared account.

I also tested locally and on one of my webserver at work, works #1

Can anybody help me out on that one ????

any input will be really appreciated. Thanks a lot.

Pat.
Checked in the ASP page of goDaddy that .NET 2.0 was up and running.
Made sure the frontPage extensions were off.

Aug 20, 2007 at 4:37 PM
Did you create a virtual directory or iis application to run the site? You would run into issues if you have a root web running and you put another web application in a sub directory with configuring the iis server. Try creating a virtual directory and point it to the blog application. Then you should be able to go to http://www.yourdomain.com/blog and see it in action.
Aug 20, 2007 at 6:29 PM
Greetings. I just found out this morning that the problem was due to an error on the Application Pool on the server itself. As I have a shared plan, I don't have access to IIS (or the events) what made my life much easier.

So now things seems to be working fine !

The only thing I was unable to circumvent is the fact that I can't run 2 blogengine on the server at the same time for some reason, even if they're both in their own virtual directory the 2nd engine somehow seems to see the web.config (my guess), but then again, as I can't test locally, that's hard to get the "exact" answer from the server.

Thanks a lot for your time.

Aug 21, 2007 at 8:54 PM
Ok, well I have a web server (Windows 2003, iis6) which has one web site with this running pretty well on it. I just added the same thing to a second site on the same server. All settings the same... result... I get prompted for ausername/ password (which I can't provide) on the new blog, but eventually I get the server unavailable error just as above.

The solution? I have two swimming? pools to choose from.. I had used the "default" for both blogs... if I set this second site to be the "MS Share Point" pool, then both blogs work as expected. Anyone care to point me at swimming pools 101? What's all that about then?
Aug 22, 2007 at 3:09 PM
Aaah. Basicaly that means I won't be able to make it work on godaddy. Pretty hard to ask a tech to configure something for you there. But thanks for the update, at least I have a better idea why it won't work without tuning up.

Thanks !
Aug 22, 2007 at 3:35 PM
Edited Aug 22, 2007 at 3:35 PM
Hi

I am having similar issues to you when trying to run BE on a shared host. I am getting "Server Application Unavailable" error.

I was wondering if you could detail how you fixed the problem, regrettably the following doesnt make much sense to me

"Greetings. I just found out this morning that the problem was due to an error on the Application Pool on the server itself. As I have a shared plan, I don't have access to IIS (or the events) what made my life much easier. "

Thanks
Aug 22, 2007 at 3:56 PM
You should be able to use the same application pool for all your sites provided they are asp.net 2.0.
I have three directories
-Webroot
---MainBlog - http://blogs.romanclarkson.com
-----SubBlog - http://blogs.romanclarkson.com/test3
---Test1Blog - http://blogs.romanclarkson.com/test1
---Test2Blog - http://blogs.romanclarkson.com/test2

Each are running in the same application pool. I changed the code in the web.config file for the authentication to have a unique name. .AUXBLOGENGINE, .AUXBLOGENGINE1, .AUXBLOGENGINE2, .AUXBLOGENGINE3.

<authentication mode="Forms">
<forms timeout="129600" name=".AUXBLOGENGINE" protection="All" slidingExpiration="true" loginUrl="~/login.aspx" />
</authentication>

They all work. Let me know if you need more.
Aug 22, 2007 at 4:09 PM
Ooh, I haven't toyed with the web.config, I'll give it a try tonight and let you know if it worked.

Thanks for the enlightement, I haven't thought of that.

Pat
Aug 22, 2007 at 6:52 PM
illogical_pizza :

Well I got lucky. Strangely godaddy don't have such a bad tech support. I sent them an email saying I had issue with an application and I thought it was IIS related. They replied about 2 hours after, they didn't tell me anything except "the problem with your website is now fixed", but somehow the title of the message was "Application pools errors" , so I assume IIS chocked on something. So my recommendation would be to email your hosting company and let them know there's something fishy with your account.

Pat
Aug 22, 2007 at 6:52 PM
see my reply in this thread. I forgot to click "reply"


illogical_pizza wrote:
Hi

I am having similar issues to you when trying to run BE on a shared host. I am getting "Server Application Unavailable" error.

I was wondering if you could detail how you fixed the problem, regrettably the following doesnt make much sense to me

"Greetings. I just found out this morning that the problem was due to an error on the Application Pool on the server itself. As I have a shared plan, I don't have access to IIS (or the events) what made my life much easier. "

Thanks

Aug 23, 2007 at 1:54 PM
Thanks a LOT, I changed the code in the web.config and the 2nd blog worked fine !

thanks a lot for your help. !!



rclarkson wrote:
You should be able to use the same application pool for all your sites provided they are asp.net 2.0.
I have three directories
-Webroot
---MainBlog - http://blogs.romanclarkson.com
-----SubBlog - http://blogs.romanclarkson.com/test3
---Test1Blog - http://blogs.romanclarkson.com/test1
---Test2Blog - http://blogs.romanclarkson.com/test2

Each are running in the same application pool. I changed the code in the web.config file for the authentication to have a unique name. .AUXBLOGENGINE, .AUXBLOGENGINE1, .AUXBLOGENGINE2, .AUXBLOGENGINE3.

<authentication mode="Forms">
<forms timeout="129600" name=".AUXBLOGENGINE" protection="All" slidingExpiration="true" loginUrl="~/login.aspx" />
</authentication>

They all work. Let me know if you need more.

Aug 30, 2007 at 10:46 PM

{quote}
patzblue wrote:
see my reply in this thread. I forgot to click "reply"


illogical_pizza wrote:
stuff :p



Thanks patzblue, I did the same with my hosting company, and they resolved "something" ...
One thing i did notice was problems logging in once i had got the blog running.... it appeared that the users.xml file was cached and i had to ask/wait for it to be uncached before i could login
Sep 1, 2007 at 4:47 PM
Wonder if it's possible to add some extention that recycles the app pool, hence restart the application and refresh all the content.