Does anyone have a clue what this means? Software error: Can't use an undefined value as a HASH reference at /opt/otrs//Kernel/System/Ticket/Article.pm line 1395. I cannot see view my tickets. Other then this it seems to work :) --Shawn
Shawn Beasley schrieb:
Does anyone have a clue what this means?
Software error:
Can't use an undefined value as a HASH reference at /opt/otrs//Kernel/System/Ticket/Article.pm line 1395.
I cannot see view my tickets. Other then this it seems to work :)
--Shawn
_______________________________________________ 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/
Sorry, I am too stupid to run the update script for the DB. After running this, everything is working again. --Shawn
Shawn Beasley schrieb am 05.07.2007 10:43 Uhr:
Shawn Beasley schrieb:
Does anyone have a clue what this means?
Software error:
Can't use an undefined value as a HASH reference at /opt/otrs//Kernel/System/Ticket/Article.pm line 1395.
Sorry, I am too stupid to run the update script for the DB. After running this, everything is working again.
--Shawn
Hello,
Had the same Error after upgrading from 2.0.4 to 2.2.1 - although i ran
the DBUpdate-to-2.2.* Skript.
That's not enough, one have to run _every_ DBUpdate Skript, so in the
case of Upgrading from 2.0.x to 2.2.x make sure to run:
DBUpdate-to-2.1.
I'm not having any success at all. I've done a SQL backup, grabbed the configs, uninstall 2.1.5. I install 2.2.1, restore the database, *AND* do run the 2.1->2.2 DB upgrade script. I still receive the following error: Software error: Can't use an undefined value as a HASH reference at C:/OTRS/otrs//Kernel/System/Ticket/Article.pm line 1395. I did notice an error when running the SQL upgrade script as well. ERROR 1050 (42S01) at line 15: Table 'customer_company' already exists Any suggestions? Confidentiality Warning: This message and any attachments are intended only for the use of the intended recipients (otrs@otrs.org), are confidential, and may be privileged. If you are not the intended recipient, you are hereby notified that any review, retransmission, conversion to hard copy, copying, circulation or other use of this message and any attachments is strictly prohibited. If you are not the intended recipient, please notify the sender (Frank Wakelin) immediately by return e-mail, and delete this message and any attachments from your system. Thank you. Information Confidentielle: Le present message, ainsi que tout fichier qui y est joint, est envoye a l'intention exclusive de son ou de ses destinataires (otrs@otrs.org); il est de nature confidentielle et peut constituer une information privilegiee. Nous avertissons toute personne autre que le destinataire prevu que tout examen, reacheminement, impression, copie, distribution ou autre utilisation de ce message et de tout fichier qui y est joint est strictement interdit. Si vous n'etes pas le destinataire prevu, veuillez en aviser immediatement l'expediteur (Frank Wakelin) par retour de courriel et supprimer ce message et tout document joint de votre systeme. Merci
Actually, after using the "force" option (sorry, missed that) I can see the tickets again. However I received a number of errors while running the upgrade script still - are these normal? ERROR 1050 (42S01) at line 15: Table 'customer_company' already exists ERROR 1050 (42S01) at line 49: Table 'ticket_type' already exists ERROR 1062 (23000) at line 60: Duplicate entry 'default' for key 2 ERROR 1050 (42S01) at line 107: Table 'service' already exists ERROR 1050 (42S01) at line 125: Table 'service_customer_user' already exists ERROR 1050 (42S01) at line 138: Table 'sla' already exists Are these normal, or can I expect other problems? -----Original Message----- From: Frank Wakelin Sent: July 16, 2007 08:50 To: 'User questions and discussions about OTRS.org' Subject: Upgrading 2.1.5 -> 2.2.1 I'm not having any success at all. I've done a SQL backup, grabbed the configs, uninstall 2.1.5. I install 2.2.1, restore the database, *AND* do run the 2.1->2.2 DB upgrade script. I still receive the following error: Software error: Can't use an undefined value as a HASH reference at C:/OTRS/otrs//Kernel/System/Ticket/Article.pm line 1395. I did notice an error when running the SQL upgrade script as well. ERROR 1050 (42S01) at line 15: Table 'customer_company' already exists Any suggestions? Confidentiality Warning: This message and any attachments are intended only for the use of the intended recipients (otrs@otrs.org), are confidential, and may be privileged. If you are not the intended recipient, you are hereby notified that any review, retransmission, conversion to hard copy, copying, circulation or other use of this message and any attachments is strictly prohibited. If you are not the intended recipient, please notify the sender (Frank Wakelin) immediately by return e-mail, and delete this message and any attachments from your system. Thank you. Information Confidentielle: Le present message, ainsi que tout fichier qui y est joint, est envoye a l'intention exclusive de son ou de ses destinataires (otrs@otrs.org); il est de nature confidentielle et peut constituer une information privilegiee. Nous avertissons toute personne autre que le destinataire prevu que tout examen, reacheminement, impression, copie, distribution ou autre utilisation de ce message et de tout fichier qui y est joint est strictement interdit. Si vous n'etes pas le destinataire prevu, veuillez en aviser immediatement l'expediteur (Frank Wakelin) par retour de courriel et supprimer ce message et tout document joint de votre systeme. Merci
Is there an easy way to restore just the FAQ's from the database dump? -----Original Message----- From: otrs-bounces@otrs.org [mailto:otrs-bounces@otrs.org] On Behalf Of Frank Wakelin Sent: July 16, 2007 09:04 To: User questions and discussions about OTRS.org Subject: [otrs] RE: Upgrading 2.1.5 -> 2.2.1 Actually, after using the "force" option (sorry, missed that) I can see the tickets again. However I received a number of errors while running the upgrade script still - are these normal? ERROR 1050 (42S01) at line 15: Table 'customer_company' already exists ERROR 1050 (42S01) at line 49: Table 'ticket_type' already exists ERROR 1062 (23000) at line 60: Duplicate entry 'default' for key 2 ERROR 1050 (42S01) at line 107: Table 'service' already exists ERROR 1050 (42S01) at line 125: Table 'service_customer_user' already exists ERROR 1050 (42S01) at line 138: Table 'sla' already exists Are these normal, or can I expect other problems? -----Original Message----- From: Frank Wakelin Sent: July 16, 2007 08:50 To: 'User questions and discussions about OTRS.org' Subject: Upgrading 2.1.5 -> 2.2.1 I'm not having any success at all. I've done a SQL backup, grabbed the configs, uninstall 2.1.5. I install 2.2.1, restore the database, *AND* do run the 2.1->2.2 DB upgrade script. I still receive the following error: Software error: Can't use an undefined value as a HASH reference at C:/OTRS/otrs//Kernel/System/Ticket/Article.pm line 1395. I did notice an error when running the SQL upgrade script as well. ERROR 1050 (42S01) at line 15: Table 'customer_company' already exists Any suggestions? Confidentiality Warning: This message and any attachments are intended only for the use of the intended recipients (otrs@otrs.org), are confidential, and may be privileged. If you are not the intended recipient, you are hereby notified that any review, retransmission, conversion to hard copy, copying, circulation or other use of this message and any attachments is strictly prohibited. If you are not the intended recipient, please notify the sender (Frank Wakelin) immediately by return e-mail, and delete this message and any attachments from your system. Thank you. Information Confidentielle: Le present message, ainsi que tout fichier qui y est joint, est envoye a l'intention exclusive de son ou de ses destinataires (otrs@otrs.org); il est de nature confidentielle et peut constituer une information privilegiee. Nous avertissons toute personne autre que le destinataire prevu que tout examen, reacheminement, impression, copie, distribution ou autre utilisation de ce message et de tout fichier qui y est joint est strictement interdit. Si vous n'etes pas le destinataire prevu, veuillez en aviser immediatement l'expediteur (Frank Wakelin) par retour de courriel et supprimer ce message et tout document joint de votre systeme. Merci _______________________________________________ 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/ Confidentiality Warning: This message and any attachments are intended only for the use of the intended recipients (otrs@otrs.org), are confidential, and may be privileged. If you are not the intended recipient, you are hereby notified that any review, retransmission, conversion to hard copy, copying, circulation or other use of this message and any attachments is strictly prohibited. If you are not the intended recipient, please notify the sender (Frank Wakelin) immediately by return e-mail, and delete this message and any attachments from your system. Thank you. Information Confidentielle: Le present message, ainsi que tout fichier qui y est joint, est envoye a l'intention exclusive de son ou de ses destinataires (otrs@otrs.org); il est de nature confidentielle et peut constituer une information privilegiee. Nous avertissons toute personne autre que le destinataire prevu que tout examen, reacheminement, impression, copie, distribution ou autre utilisation de ce message et de tout fichier qui y est joint est strictement interdit. Si vous n'etes pas le destinataire prevu, veuillez en aviser immediatement l'expediteur (Frank Wakelin) par retour de courriel et supprimer ce message et tout document joint de votre systeme. Merci
Frank Wakelin wrote:
Actually, after using the "force" option (sorry, missed that) I can see the tickets again. However I received a number of errors while running the upgrade script still - are these normal?
ERROR 1050 (42S01) at line 15: Table 'customer_company' already exists ERROR 1050 (42S01) at line 49: Table 'ticket_type' already exists ERROR 1062 (23000) at line 60: Duplicate entry 'default' for key 2 ERROR 1050 (42S01) at line 107: Table 'service' already exists ERROR 1050 (42S01) at line 125: Table 'service_customer_user' already exists ERROR 1050 (42S01) at line 138: Table 'sla' already exists
Are these normal, or can I expect other problems?
What installation method do you use? RPM? If so, I believe the postinstall scriplet already performs the database schema update, so if you run it again you can expect those 'already exists' messages. Nils Breunese.
participants (4)
-
Frank Wakelin -
Franz Ferdinand Esberger -
Nils Breunese (Lemonbit) -
Shawn Beasley