Forums & Blog

A SmarterTools-sponsored community.
Welcome to Forums & Blog Sign in | Join | Help
in Search

Webmail problem after upgrade from v3 to v4

Last post 02-12-2008 1:37 AM by holiam. 5 replies.
Page 1 of 1 (6 items)
Sort Posts: Previous Next
  • 12-15-2007 12:36 PM

    • holiam
    • Not Ranked
    • Joined on 12-15-2007
    • Posts 7

    Webmail problem after upgrade from v3 to v4

    Hi Guys, I wonder if anyone can help me with this - I have spent many hours trying to get this working and have thus far failed miserably.

    I upgraded from v3 to v4(latest) of Smartermail and for the most part, everything seems to be working fine apart from the webmail.

    If I log on to webmail using the internal mail server (port 9998) everything is good, but when I tried using IIS instead (which I did for V3) the format looks ok at the login screen, but when you go to the next screen the page is a total mess - see attached word document for screen print. The menus appear at the top of the page and the page is completely unusable.

    I have uninstalled and re-installed asp.net v2 and also smartermail4. The IIS settings look ok! Web Server extensions settings look ok and asp V2 enabled.

    Any suggestions?
  • 12-17-2007 8:45 AM In reply to

    Re: Webmail problem after upgrade from v3 to v4

    Sounds like you are experiencing the problem in this KB: http://support.smartertools.com/Customer/KBArticle.aspx?articleid=168

    Which will just tell you to go here and follow the steps: http://www.telerik.com/help/aspnet/tabstrip/tabstrip_ControlRendersAsBulletList.html

    James Lance
    SmarterTools
  • 12-17-2007 3:18 PM In reply to

    • holiam
    • Not Ranked
    • Joined on 12-15-2007
    • Posts 7

    Re: Webmail problem after upgrade from v3 to v4

     No, checked the above but, that's not it.  I have just noticed something a little strange though.  I thought I had cracked it last night, logged onto webmail and everything looked ok, then this afternoon the wierd format returned. 

     When I changed the port settings on IIS to use :9998, the sites seem to work ok, when they are set to :80 - they sometimes work, but more commonly they are a mess. 

    Does this help to diagnose?  

  • 12-17-2007 6:40 PM In reply to

    Re: Webmail problem after upgrade from v3 to v4

    Hi,

     Here are a few things you can try:

    1)On IIS: make a separate Application Pool, if you already have an application pool for websites using .NET 2.0 then you are OK.

    2)On IIS: Set the SmarterMail website to work under .NET 2.0

    3)On IIS: Set the SmarterMail Application Pool to the SmarterMail's application pool, or your current .NET application pool.

    4)On Services:  Since you are running the SmarterMail web interface from IIS go to your services, STOP and DISABLE the "SmarterMail Web Service"

    Hope this helps

     

    Damian Z., MCP
    Enterhost Support Team
    www.enterhost.com
  • 12-18-2007 1:36 PM In reply to

    • holiam
    • Not Ranked
    • Joined on 12-15-2007
    • Posts 7

    Re: Webmail problem after upgrade from v3 to v4

    Thanks for that. 

    1.  Already done this

    2. Done

    3. Done

    4. SM internal web server disabled

     

    I can't explain this, but when I try to run the new IIS web mail service on port 80, it sometimes works, but most opten than not (which means the webmail screen is a total mess and unusable).  However, if I change smartermail IIS website to use any other port (9998 for example), then it seems to work.  There are no  other web pages on this server other than the standard default page.  I have tried stopping this and deleting it, but the smartermail webmail site still does not work.

    Any other suggestions?  It's driving me insane, and I hope there is a really simple reason for it. 

  • 02-12-2008 1:37 AM In reply to

    • holiam
    • Not Ranked
    • Joined on 12-15-2007
    • Posts 7

    Re: Webmail problem after upgrade from v3 to v4

     H, thought I would write in to let you know that this problem has been resolved.  After a discussion with the technical support guys at Smarter Mail, they helped pin point the problem to my firewall.  

    On further investigation, I found out that the http filters were blocking the .AXD extension, so a quick change to this setting and everything is now ok.

    This explains why under any other port than port 80, this was working fine.

    Thanks to everyone for taking the time to offer assistance and especially Daniel and the team at Smarter Mail for their wisdom!

    Graham. 

Page 1 of 1 (6 items)