Matt, all that I cam say is that I have your same environment (Debian Etch) and I've migrated succesfully from 2.2.7 to 2.3.2 on my test environment, just by following the standard instructions. I've experienced some minor drawback solved by rewriting Config.pm from scratch starting from Defaults.pm of 2.3.2. FYI, I use Active Directory authentication and an LDAP customer backend. Maybe you missed the part where you have to execute some script as otrs user and not as root? Ciao, d. -----Messaggio originale----- Da: otrs-bounces@otrs.org [mailto:otrs-bounces@otrs.org] Per conto di mattm Inviato: giovedì 25 settembre 2008 23.18 A: otrs@otrs.org Oggetto: [otrs] Upgrading from 2.27 to 2.32 I have been recently hired into the IT department of my company. As the new guy one of my first jobs has been to upgrade our Otrs install on our Debian Etch server from 2.27 to 2.32. I tried it on a test server at first and was able to get the latest version installed and was able to log in but did not test the system any further after this. Then I ran the scripts to update the DB files as per the instructions and now I am no longer able to log in. None of the user names are valid any more. If someone could tell me an easier way to get this up and working or where I might have gone wrong migrating the database it would be greatly appreciated. Once again this is a Debian 4.0 install using a mysql database. Thanks MattM _______________________________________________ OTRS mailing list: otrs - Webpage: http://otrs.org/ Archive: http://lists.otrs.org/pipermail/otrs To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs