Home » Support » Telligent Evolution Platform » Telligent Enterprise » Discussions

Forums

Open Support Ticket

Call Support:
Direct: (214) 420-1337
Toll Free: (877) 522-6334

Monday through Friday
8 a.m. to 6 p.m. Central (GMT-6)

Join our Community
Details
  • 1 Reply
  • 3 Subscribers
  • Postedover 2 years ago
Options

Redirection loop when installing on a Windows 2003 Server

This question is answered
Bruno Lopes
Posted by
on Thu, Mar 11 2010 1:05 PM

Hello,

I'm trying to install a telligent community 2.5 site on a Windows 2003 Server with IIS 6, and trying to access it throws the browser into a permanent redirection loop (accessing the site with firefox tells me so directly: "Firefox has detected that the server is redirecting the request for this address in a way that will never complete." ).

The problem seems that it can't find any page, and try to redirect to /error-notfound.aspx, which it can't find and tries to redirect again to the same page.

The site can serve static pages like error.htm, which means that IIS is pointing to the correct path.

Is there any step in configuring IIS that I may have missed? What can be the problem?

server2003 2003 iis6 iis
Verified Answer
  • Bruno Lopes
    Posted by
    on Thu, Mar 11 2010 8:26 PM
    Verified Answer
    Verified by

    Apparently the problem was with the defaultTheme and defaultGroupTheme attributes of the Core node in communityserver.config.

    We have a custom theme for both, and when it was set to that custom theme I was unable to access anything. After changing both attributes to "evolution2" I was able to login.

    After logging-in, I replaced both attributes again with the name of our custom theme and the site kept working. So it seemed like there was some initialization that was needed by the standard theme.

    Anyone has any idea why this is?
All Replies
  • Bruno Lopes
    Posted by
    on Thu, Mar 11 2010 8:26 PM
    Verified Answer
    Verified by

    Apparently the problem was with the defaultTheme and defaultGroupTheme attributes of the Core node in communityserver.config.

    We have a custom theme for both, and when it was set to that custom theme I was unable to access anything. After changing both attributes to "evolution2" I was able to login.

    After logging-in, I replaced both attributes again with the name of our custom theme and the site kept working. So it seemed like there was some initialization that was needed by the standard theme.

    Anyone has any idea why this is?