Installing DotNetBlogEngine on Win2008/IIS7

Discussion in 'Windows / IIS' started by EduardoSojo, Apr 10, 2008.

  1. Hi, i made a test with a site in my local machine using DNBE & II7 and it works perfect but when i upload the same one to my hosting account on DASP it does´nt work.

    The error message that system get is probably a problem with the web.config. My question is, does the web.config must be changed?

    Help me please :)

    Thanks a lot.
    Eduardo
     
  2. Several of us can help you with this but can you provide us with the error messages you get?
    Salute,
    Mark
     
  3. I resolved the problem parcially. I download the new version of DNBE and use only the web.config with my actual website. My website runs now but the application throws 404 error when i try to visit some posts. I am using XMLProvider to store the data.

    Thanks,
    Eduardo
     
  4. Bruce

    Bruce DiscountASP.NET Staff

    This usually means the xml data file is messed up. I would try a clean install.


    I have installed blogengine and use the XML data store and it worked fine. Let us know a clean install does not work.


    Bruce

    DiscountASP.NET
    www.DiscountASP.NET
     
  5. Bruce,


    I am having a problem with blogengine.net. I have it working on a dev machine under http://localhost/Blogengine.Web but when I deploy the app to my account: http://www.[mydomainname].com/Blogengine.web I cannnot post comments. Both the local dev instance and the discountasp instance are pointing to the same SQL Server 2005 instance (also at discountasp). So I am wondering, can this work within another web application? I am using theDB Providers for Blogengine and for the membership and role providers. the Blogengine guys said you App_Data folder does not write permissions, but I don't think its being used as everything is managed in the db. Any thoughts?


    thanks, Mike.
     
  6. Bruce

    Bruce DiscountASP.NET Staff

  7. No, not that I have detected anyway. The app just hangs at the Saving The Comment... message. Can you tell me if you have successfully installed BlogEngine.NET on these servers and how you did it? Was it its own application (e.g. at the app root), or was it inside another application (my case)?


    I also just tried switching to the XML providers and the problem is still occurring. It looks like I am on Windows 2003 - IIS 6.0


    thanks, Mike



    Post Edited (Mike Matthews) : 8/19/2008 4:02:56 PM GMT
     
  8. Bruce

    Bruce DiscountASP.NET Staff

  9. Ok good.I assume the code came from http://www.codeplex.com/blogengine/Release/ProjectReleases.aspx?ReleaseId=14988. Did you install the web version or the version from source code (i have the source and its 1.4.5.6)? Also, I assume your deployment is running against a discountasp.net SQL Server 2005 right?


    What do you think is different about my site? And again its curious it works at http://localhost/BlogEngine.WEB but not at http://www.webtiers.com/BlogEngine.WEB.


    I will try and fall back to 1.4.5.0 as well in the meantime.


    Ok. I just removed everything and have now deployed 1.4.5.0 (web) and I am having the same problem as before. I am now starting to wonder that the server hosting www.webtiers.com is different either with respect to .NET versions (I assume 2.0, 3.5) or Machine.config etc. Can you verify what may be different with this server than yours (the one you did the 1.4.5.0 test on successfully)? One difference I see is Win2003 vs. Win2008...and there must be something about this or something else that is different...


    the new 1.4.5.0site is at http://www.webtiers.com/Blog


    thanks, Mike



    Post Edited (Mike Matthews) : 8/19/2008 8:22:39 PM GMT
     
  10. Bruce

    Bruce DiscountASP.NET Staff

  11. I figured this out. It had to do withthe web.config in the root application. The child directory app, in this case the BlogEngine, was being impacted by the configuration settings in the root web.config.And not allowing comments to be submitted. For now, I have just diasbled the web.config in the root. With a bit more investigation, we could figure outwhat specific setting(s) in the BlogEngineweb.config are colliding. If anyone knows this please post it here.
     

Share This Page