Good night,
I upgraded from OTRS version 2.4.7 to OTRS version 3.0.2 the following steps:
1 - I made a backup of your system configuration and database.
2 - I uninstalled the old version and I installed the new.
3 - I replaced the file "Config.pm" new for the old.
4 - I created the database.
5 - I have given permissions to the user over the entire database.
6 - I dump the backup to the database.
7 - Updating the database to the latest version:
1. mysql -uroot DB_OTRS < DBUpdate-to-3.0.mysql.sql OK
2. perl DBUpdate-to-3.0.pl
a. Out the following:
Migration of the system completed!
(in cleanup) Can't call method "Dump" on an undefined value at C:/Archivos de programa/OTRS/OTRS/Kernel/System/SysConfig.pm line 590 during global destruction.
I continued anyway.
3. mysql -uroot BD_OTRS < DBUpdate-to-3.0-post.mysql.sql OK
8 - Reboot
9 - When I try to authenticate with the admin user I get the following message:
Software error:
Got no TicketObject! at C:/ARCHIV~1/OTRS/OTRS//Kernel/Output/HTML/NavBarModuleAdmin.pm line 29.
I await your response.
Thank you.
Greetings
Got no TicketObject!
Moderator: crythias
-
- Znuny newbie
- Posts: 8
- Joined: 23 Nov 2010, 21:19
- Znuny Version: 3.0.2
Re: Got no TicketObject!
Please run the RebuildConfig script
"Production": OTRS™ 8, OTRS™ 7, STORM powered by OTRS
"Testing": ((OTRS Community Edition)) and git Master
Never change Defaults.pm! :: Blog
Professional Services:: http://www.otrs.com :: enjoy@otrs.com
"Testing": ((OTRS Community Edition)) and git Master
Never change Defaults.pm! :: Blog
Professional Services:: http://www.otrs.com :: enjoy@otrs.com
-
- Znuny newbie
- Posts: 8
- Joined: 23 Nov 2010, 21:19
- Znuny Version: 3.0.2
Re: Got no TicketObject!
Good morning,
Thanks for responding.
Where is this script and as I run the scritpt?.
I forgot to tell you that I use Windows.
Thank you very much
Greetings
Thanks for responding.
Where is this script and as I run the scritpt?.
I forgot to tell you that I use Windows.
Thank you very much
Greetings
Re: Got no TicketObject!
it is a Perl script in the OTRS bin directory (otrs.RebuildConfig.pl)
so you need to run it in the CMD CLI: perl otrs.RebuildConfig.pl
so you need to run it in the CMD CLI: perl otrs.RebuildConfig.pl
"Production": OTRS™ 8, OTRS™ 7, STORM powered by OTRS
"Testing": ((OTRS Community Edition)) and git Master
Never change Defaults.pm! :: Blog
Professional Services:: http://www.otrs.com :: enjoy@otrs.com
"Testing": ((OTRS Community Edition)) and git Master
Never change Defaults.pm! :: Blog
Professional Services:: http://www.otrs.com :: enjoy@otrs.com
-
- Znuny newbie
- Posts: 55
- Joined: 08 Feb 2010, 12:44
- Znuny Version: 5.0.9
- Company: Zürich
- Location: Zürich
Re: Got no TicketObject!
ich habe es exakt gleich durchgespielt wie Conasi_OTRS und bei mir kommt die fehlermeldung weiterhin. was könnte noch helfen?
gruss
ccamel
gruss
ccamel
OTRS 5.0.9, Ubuntu 14.04 Server, i386
-
- Znuny newbie
- Posts: 55
- Joined: 08 Feb 2010, 12:44
- Znuny Version: 5.0.9
- Company: Zürich
- Location: Zürich
Re: Got no TicketObject!
hi Conasi_OTRS
don't do this steps and it will works:
I don't know how important the db-update.pl is. So do anybody know?
ccamel
don't do this steps and it will works:
Code: Select all
[i]2. perl DBUpdate-to-3.0.pl
a. Out the following:
Migration of the system completed!
(in cleanup) Can't call method "Dump" on an undefined value at C:/Archivos de programa/OTRS/OTRS/Kernel/System/SysConfig.pm line 590 during global destruction.
I continued anyway.
3. mysql -uroot BD_OTRS < DBUpdate-to-3.0-post.mysql.sql OK[/i]
ccamel
OTRS 5.0.9, Ubuntu 14.04 Server, i386
Re: Got no TicketObject!
i've had the same issue (Got no Ticket Object!).
solved it with the following steps:
change otrs.www-data to your otrs user and group (keep in mind that the webserver group needs access too, in my setup the apache group is www-data and otrs is a member of that)
make sure ZZZAAuto.pm has perms 0644.
solved it with the following steps:
Code: Select all
root@otrs> cp /opt/otrs-2.4.9/Kernel/Config/Files/ZZZAAuto.pm /opt/otrs-3.0.1/Kernel/Config/Files/.
root@otrs> chown otrs.www-data /opt/otrs-3.0.1/Kernel/Config/ZZZAAuto.pm
make sure ZZZAAuto.pm has perms 0644.