Dear all, we just upgraded from 2.0.5 to 2.2.4, -> install 2.2.4 -> dump database from old 2.0.5 -> run sql upgrade scripts -> migrate settings from old to new otrs The users are authenticated against an Acitve Directory. After the upgrade all tickets in the frontend are missing, meaning no user can see his/her own tickets anymore. In the backend everything is fine, and we can see all tickets, Any ideas ? Regards Soeren
hi soeren, we have the same issue while upgrading from 1.3 -> 2.2 a solution is that the customer can click on the "search"-button to search their old tickets. -- Stefan Kulcsar On Thu, 2007-11-22 at 10:23 +0100, Sören Malchow wrote:
Dear all,
we just upgraded from 2.0.5 to 2.2.4,
-> install 2.2.4 -> dump database from old 2.0.5 -> run sql upgrade scripts -> migrate settings from old to new otrs
The users are authenticated against an Acitve Directory.
After the upgrade all tickets in the frontend are missing, meaning no user can see his/her own tickets anymore. In the backend everything is fine, and we can see all tickets,
Any ideas ?
Regards Soeren _______________________________________________ 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 Support or consulting for your OTRS system? => http://www.otrs.com/
Hi Stefan,
thanks for the answer, but that does not solve the problem for us.
When i search for old ticket under the customer account i do not find the
tickets. Surprisingly i can see all tickets in the backend being assinged
to the correct Active directory user ( Phonenumber, Location etc. is
correct )
It seems as if somewhere in the frontend is problem to associate the user
and the tickets, we are still investigating this problem. The strangest
thing is, that we had everything working with 2.0.5.
Can somebody send me a working Config example ( with 2.2.x ) when using an
LDAP Backend maybe i can find the error then.
Regards
Stefan Kulcsar
Dear all,
we just upgraded from 2.0.5 to 2.2.4,
-> install 2.2.4 -> dump database from old 2.0.5 -> run sql upgrade scripts -> migrate settings from old to new otrs
The users are authenticated against an Acitve Directory.
After the upgrade all tickets in the frontend are missing, meaning no user can see his/her own tickets anymore. In the backend everything is fine, and we can see all tickets,
Any ideas ?
Regards Soeren _______________________________________________ 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 Support or consulting for your OTRS system? => http://www.otrs.com/
_______________________________________________ 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 Support or consulting for your OTRS system? => http://www.otrs.com/
Hi Stefan,
i just wanted to give you an update, we solved the issue, we realized that
we have a non consistent "customer_user_id" field in the "ticket" table,
sometimes there were the users email addresses and sometimes the
sAMAccountName.
Though it worked in 2.0.5 it does not work in 2.2.4, we resolved this
through manually changing the database and inserting the sAMAccountName
where necessary.
Regards
Soeren
Stefan Kulcsar
Dear all,
we just upgraded from 2.0.5 to 2.2.4,
-> install 2.2.4 -> dump database from old 2.0.5 -> run sql upgrade scripts -> migrate settings from old to new otrs
The users are authenticated against an Acitve Directory.
After the upgrade all tickets in the frontend are missing, meaning no user can see his/her own tickets anymore. In the backend everything is fine, and we can see all tickets,
Any ideas ?
Regards Soeren _______________________________________________ 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 Support or consulting for your OTRS system? => http://www.otrs.com/
_______________________________________________ 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 Support or consulting for your OTRS system? => http://www.otrs.com/
participants (2)
-
Stefan Kulcsar -
Sören Malchow