302: document moved issue at first logon

[Sofia]

Hi all,

I'm new to OTRS and are currently setting 2.4.11 up in an Win/IIS6/MSSQL environment. I have got everything up and running technically, by following the instructions at http://blog.afsharm.com/2009/03/install ... ndows.html.

When I now try to log on as root for the first time, I get an issue with a 302 document moved message from http://localhost/index.pl:

Code: Select all

Content-Type: text/html; charset=utf-8; Status: 302 Moved location: http://localhost//index.pl? document moved

When clicking the document moved-link, I get redirected back to the http://localhost//index.pl? and then the loop goes on forever. I have noticed the redirect URL has an extra slash between localhost and index, both in the 302-message as well as in the adress-bar. But the URL for the file displaying the message has only one simple / so I think there might be a problem here with how the virtual directories has been set up.

I have googled this and get lots of hits that indiciates this could be a problem with the HTTP location headers that are missing, but I can't figure out where to alter these in the source-code. I have some previous experience with website configuration, but only in *nix and that was a long time ago. I'm new to IIS and Perl so I'm really in the dark here and would appreciate some help!

Thanks in advance!

[Sofia]

It seems the redirect comes from index.html in the htdocs-folder. However, when I alter it (in any way) it doesn't have any impact which makes me believe IIS just doen't care about the redirect in the code and does this on its own...

Any ideas/hints/tips would be most welcome - I'm really stuck here and need to get the OTRS up and running asap!

Thanks in advance!

[Sofia]

Just wanted to post how I solved this - or not really solved, but worked around;

1. Did a local installation on my personal laptop, using the Windows installation package.
2. Configured OTRS to use the already existing MsSQL DB.
3. Fired OTRS up and checked everything worked
4. Uninstalled the IIS service on the server
5. Installed the Windows installer package on the server (to get the apache up and running etc)
6. Removed the OTRS-folder on the server and replaced it with a copy of my local installation (only OTRS-folder containing the web-parts) to get my configuration.
7. Configured the config.pm to use the proper settings for the server
8. Rebooted the server.
9. Started the OTRS service and voila! Now it works like a charm - almost (some issues with poor performance I still need to deal with, but now it works anyway)

Maybe there was a smoother way to deal with this, but this was pretty quick and worked just fine