Re: [otrs] Upgrade OTRS 3.0.7 to otrs 5

[Frank Thommen]

On 05/30/2016 06:38 PM, Alvaro Cordero wrote:

Hello,

You can go from one version to the latest of the next, for example if
you are in 3.0.9, you can go to latest 3.1.x -> 3.2.x -> 4.0.x -> 5.0.x

You don't need to do 4.0.1 and then all the minors, go directly to the
latest version on the step.


Great! Directly jumping from 4.0.1 (our current version) to 5.0.9 saves 
a lot of time.  I was afraid I had to do 26 updates...:-))


frank



Regards

2016-05-30 10:21 GMT-06:00 Frank Thommen >:

Yes, you can see this:
http://otrs.github.io/doc/manual/admin/stable/en/html/upgrading.html

If you are running a lower version of OTRS you have to follow
the upgrade
path to 4 first (3.0->3.1->3.2->3.3->4)! You need to perform a
full upgrade
to every version in between, including database changes and the
upgrading
Perl script.


What I don't understand: Does the sentence "You need to perform a
full upgrade to every version in between" only refer to the
situation when you start from a version lower than 4 or also for
start versions above 4?  From 4.0.1 -> 5.0.9 do I have to go through
4.0.1->4.0.2->4.0.3->...->5.0.9 or can I jump directly 4.0.1->5.0.9?

And if all intermediate steps are required: What do I use as 5.0:
5.0.0.rc1?  I'm using RPM packages and there is no 5.0.0 package on
ftp://ftp.otrs.org/pub/otrs/RPMS/rhel/6/.

frank



-
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




--
/Alvaro Cordero Retana
Consultor de Tecnologias/
/Tel: 22585757 ext 123/
/Email:/ alv...@gridshield.net 



-
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




-
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

Re: [otrs] Upgrade OTRS 3.0.7 to otrs 5

[Vogl, Yves]

Hi,


is this strict upgrade path the reason why there's no yum mirror?


Yves

Von meinem iPhone gesendet

Am 30.05.2016 um 18:39 schrieb Alvaro Cordero :




Hello, 


You can go from one version to the latest of the next, for example if you are in 3.0.9, you can go to latest 3.1.x -> 3.2.x -> 4.0.x -> 5.0.x 


You don't need to do 4.0.1 and then all the minors, go directly to the latest version on the step.


Regards 


2016-05-30 10:21 GMT-06:00 Frank Thommen 
:



Yes, you can see this:
http://otrs.github.io/doc/manual/admin/stable/en/html/upgrading.html

If you are running a lower version of OTRS you have to follow the upgrade
path to 4 first (3.0->3.1->3.2->3.3->4)! You need to perform a full upgrade
to every version in between, including database changes and the upgrading
Perl script.


What I don't understand: Does the sentence "You need to perform a full upgrade to every version in between" only refer to the situation when you start from a version lower than 4 or also for start versions above 4?  From 4.0.1 -> 5.0.9 do I have to go
 through 4.0.1->4.0.2->4.0.3->...->5.0.9 or can I jump directly 4.0.1->5.0.9?

And if all intermediate steps are required: What do I use as 5.0: 5.0.0.rc1?  I'm using RPM packages and there is no 5.0.0 package on

ftp://ftp.otrs.org/pub/otrs/RPMS/rhel/6/.

frank




-
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








-- 








Alvaro Cordero Retana
Consultor de Tecnologias
Tel: 22585757 ext 123
Email: 
alv...@gridshield.net














-
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


--- >>> business. people. technology. <<<---adesso AG mit Sitz in DortmundVorstand: Michael Kenfenheuer (Vors.), Christoph Junge, Andreas PrenneisVorsitzender des Aufsichtsrates: Prof. Dr. Volker GruhnAmtsgericht Dortmund HRB 20663























-
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

Re: [otrs] Upgrade OTRS 3.0.7 to otrs 5

[Alvaro Cordero]

Hello,

You can go from one version to the latest of the next, for example if you
are in 3.0.9, you can go to latest 3.1.x -> 3.2.x -> 4.0.x -> 5.0.x

You don't need to do 4.0.1 and then all the minors, go directly to the
latest version on the step.

Regards

2016-05-30 10:21 GMT-06:00 Frank Thommen :

> Yes, you can see this:
>> http://otrs.github.io/doc/manual/admin/stable/en/html/upgrading.html
>>
>> If you are running a lower version of OTRS you have to follow the upgrade
>> path to 4 first (3.0->3.1->3.2->3.3->4)! You need to perform a full
>> upgrade
>> to every version in between, including database changes and the upgrading
>> Perl script.
>>
>
> What I don't understand: Does the sentence "You need to perform a full
> upgrade to every version in between" only refer to the situation when you
> start from a version lower than 4 or also for start versions above 4?  From
> 4.0.1 -> 5.0.9 do I have to go through 4.0.1->4.0.2->4.0.3->...->5.0.9 or
> can I jump directly 4.0.1->5.0.9?
>
> And if all intermediate steps are required: What do I use as 5.0:
> 5.0.0.rc1?  I'm using RPM packages and there is no 5.0.0 package on
> ftp://ftp.otrs.org/pub/otrs/RPMS/rhel/6/.
>
> frank
>
>
>
> -
> 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
>



-- 

*Alvaro Cordero RetanaConsultor de Tecnologias*
*Tel: 22585757 ext 123*
*Email:* alv...@gridshield.net
-
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

Re: [otrs] Upgrade OTRS 3.0.7 to otrs 5

[Frank Thommen]

Yes, you can see this:
http://otrs.github.io/doc/manual/admin/stable/en/html/upgrading.html

If you are running a lower version of OTRS you have to follow the upgrade
path to 4 first (3.0->3.1->3.2->3.3->4)! You need to perform a full upgrade
to every version in between, including database changes and the upgrading
Perl script.


What I don't understand: Does the sentence "You need to perform a full 
upgrade to every version in between" only refer to the situation when 
you start from a version lower than 4 or also for start versions above 
4?  From 4.0.1 -> 5.0.9 do I have to go through 
4.0.1->4.0.2->4.0.3->...->5.0.9 or can I jump directly 4.0.1->5.0.9?


And if all intermediate steps are required: What do I use as 5.0: 
5.0.0.rc1?  I'm using RPM packages and there is no 5.0.0 package on 
ftp://ftp.otrs.org/pub/otrs/RPMS/rhel/6/.


frank


-
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

Re: [otrs] Upgrade OTRS 3.0.7 to otrs 5

[Never Min]

Hi Rose,

Yes, you can see this:
http://otrs.github.io/doc/manual/admin/stable/en/html/upgrading.html

If you are running a lower version of OTRS you have to follow the upgrade
path to 4 first (3.0->3.1->3.2->3.3->4)! You need to perform a full upgrade
to every version in between, including database changes and the upgrading
Perl script.


-NM


2016-05-26 15:49 GMT+08:00 Rose Dowson :

> Hi,
>
> It's possible to upgrade my otrs 3.0.7 to 5 version ?
> If not, do you have an idea if I should go through the version 4 or maybe
> 3.3 ?
>
> Thank you for the help.
> Best Regards,
>
> -
> 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
>
-
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

Re: [otrs] Upgrade failure with ITSM 3.3.5 --> 4.0.16

[Florian Edlhuber]

Hi,

25.04.2016 14:55 - jan.dre...@bertelsmann.de schrieb:

> I already posted this on otterhub, but I thought the audience
> may be bigger when writing to you, too:

opening more requests on many channels does not always help. It might be the
opposite.
   > No response to this yet. I cannot believe we there is no-one who
> was using free-text fields with ITSM 3.X and already upgraded to 4.X :-(

 This is a open source community. You can not *expect* answers and solutons
from volunteers.

If you need help, you should buy commercial support.

And no, I do not have an answer for your topic.

best regards
Florian
 -
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

Re: [otrs] Upgrade failure with ITSM 3.3.5 --> 4.0.16

[Jan.Dreyer]

Hi.

> Am 18.04.2016 um 10:31 schrieb Dreyer, Jan, SCM-IT 
> :
> 
> Hi @ll.
> 
> I already posted this on otterhub 
> , but I thought the 
> audience may be bigger when writing to you, too:
> 
> I'm facing the following problem when trying to upgrade our OTRS-ITSM from 
> 3.3.5 to 4.0.16:
> We are using some change_freetext fields for storing Meta information about a 
> change. When upgrading our test system the extra fields vanished.  I assume 
> they should get migrated like the old freetext fields in OTRS 3.0, but 
> nothing: neither the old freetext fields exist in the database, nor a 
> corresponding dynamic field.
> Is this a known issue? I couldn't find anything in web- or forum search. 
> Anyone her who is able to help with a hint to the right direction, so I don't 
> have to dig into the code of the migration scripts?!
> 
> Jan

No response to this yet. I cannot believe we there is no-one who was using 
free-text fields with ITSM 3.X and already upgraded to 4.X :-(

Regards
—
Jan Dreyer
IT Administrator — Operations — A-SCM-IT IOX Expert
This email may contain confidential and/or privileged information. If you are 
not the intended recipient (or have received this email in error) please notify 
the sender immediately and destroy this email. Any unauthorized copying, 
disclosure or distribution of the information in this email is strictly 
forbidden.




signature.asc
Description: Message signed with OpenPGP using GPGMail
-
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

Re: [otrs] Upgrade process from OTRS 3.1.3 -> 5

[Alex Zimmerman]

Thank you Florian!

[image: Everett Community College] 
Alex Zimmerman / Information Technology Specialist III
Web Data & Development Services / Enterprise Services / Information
Security
Direct line:(425) 259-8724 / Help Desk:(425)388 9333
email: azimmer...@everettcc.edu  [image: Twitter]
  [image: Linkedin]

*How did I do? Please take a minute to help us improve our IT service by
completing the *
*IT Feedback Survey.  (http://goo.gl/J3nGC
)*
*Thank you!*

On Tue, Oct 13, 2015 at 9:39 AM, Florian Edlhuber 
wrote:

> Hi,
>
> 13/10/2015 18:00 - Alex Zimmerman wrote:
> > I just inherited the job of updating our production IT HelpDesk server
> > from a IT tech that is no longer here.  Due to the nature of our setup
> > in cannot be down for very long, which is why it was left to get so
> > far behind.
>
> Typical (bad) scenario. Solution? Managed OTRS. Sorry that I am commercial
> on the mailing list, but actually this is an issue. And can be solved with
> a managed OTRS.
>
> > The server is currently running on OTRS 3.1.3 on a Ubuntu Linux
> > 12.04 LTS server.
> > (...)
> > It sounds like I have to update from to every subversion e.g.
> > 3.1.3 -> 3.1.4 -> 3.2.1 -> 3.2.2 etc..
>
> Nope. What you describe is "Patch Release" Updates...
>
> If you read the documentation carefully you'll find:
> ,---
> | Within a single minor version you can skip patch level releases if
> | you want to upgrade. For instance you can upgrade directly from
> | OTRS 4 patchlevel 2 to version 4 patchlevel 6.
> `---
>
> So you need to go to:
> 3.2.x -> 3.3.x -> 4.0.x -> 5.0.x
> (x = latest patch)
>
> > Is is possible to just perform fresh install of the latest OTRS
> > and import and upgrade the database?
>
> No. You have to follow the path. Good Luck. :)
>
>
> --
> Florian
>
>
> -
> 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
>
-
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

Re: [otrs] Upgrade process from OTRS 3.1.3 -> 5

[Florian Edlhuber]

Hi,

13/10/2015 18:00 - Alex Zimmerman wrote:
> I just inherited the job of updating our production IT HelpDesk server 
> from a IT tech that is no longer here.  Due to the nature of our setup 
> in cannot be down for very long, which is why it was left to get so 
> far behind.

Typical (bad) scenario. Solution? Managed OTRS. Sorry that I am commercial 
on the mailing list, but actually this is an issue. And can be solved with 
a managed OTRS.

> The server is currently running on OTRS 3.1.3 on a Ubuntu Linux 
> 12.04 LTS server.
> (...)
> It sounds like I have to update from to every subversion e.g.
> 3.1.3 -> 3.1.4 -> 3.2.1 -> 3.2.2 etc..

Nope. What you describe is "Patch Release" Updates...

If you read the documentation carefully you'll find:
,---
| Within a single minor version you can skip patch level releases if
| you want to upgrade. For instance you can upgrade directly from
| OTRS 4 patchlevel 2 to version 4 patchlevel 6.
`---

So you need to go to:
3.2.x -> 3.3.x -> 4.0.x -> 5.0.x
(x = latest patch)

> Is is possible to just perform fresh install of the latest OTRS 
> and import and upgrade the database?

No. You have to follow the path. Good Luck. :)

-- 
Florian

-
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

Re: [otrs] upgrade to a new patch level (from4.0.6 to 4.0.7)

[Rudolf Bargholz]

Hi,

I use the following to update

cd Downloads
cd otrs
md 4.0.7
cd 4.0.7
curl http://ftp.otrs.org/pub/otrs//RPMS/suse/11.0/otrs-4.0.7-01.noarch.rpm -o 
otrs-4.0.7-01.noarch.rpm
rpm -U --nodeps otrs-4.0.7-01.noarch.rpm
shutdown -r now

The restart of the server is probably not necessary, but I prefer to err on the 
side of caution. The above has served us well for many years and we have not 
had any problems updating using this method.

Regards

Rudolf Bargholz

Von: otrs-boun...@otrs.org [mailto:otrs-boun...@otrs.org] Im Auftrag von 
iga3...@yahoo.com
Gesendet: Dienstag, 7. April 2015 15:39
An: User questions and discussions about OTRS.
Betreff: [otrs] upgrade to a new patch level (from4.0.6 to 4.0.7)

Hi, we have running OTRS version 4.0.6. See:

[root@server tmp]# rpm -qa|grep otrs
otrs-4.0.6-01.noarch


Now I have downloaded new version 4.0.7
[root@server tmp] wget 
https://www.otrs.com/download-thank-you/thank-you-downloading-otrs-software/?download=/RPMS/rhel/6/otrs-4.0.7-01.noarch.rpm


In order to upgrade. Is enough to run:


rpm -Uvh  otrs-4.0.7-01.noarch.rpm


??


I have searched on OTRS manual and it only showed how to upgrade from an old 
version 2x, 3x to 4x. But I didn't found how to upgrade to a new patch level.



Thanks.



-
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

Re: [otrs] upgrade from otrs v3.1.6 to4 (Linux)

[iga3725]

Thanks Christoph,
In one step I meant make the upgrade in onbe phase and not make the upgrade 
from otrs 3.1.6 -- otrs to 3.2  -- otrs to 4.
Thanks again.
 

 El Martes 10 de marzo de 2015 12:56, Christoph Sandhaus 
sandh...@mus.awo-ol.de escribió:
   

 #yiv9651332396 p, #yiv9651332396 li {white-space:pre-wrap;}Before OTRS 4 there 
was a file UPGRADING.mdcontaining step by step upgrade instrctions. Actually 
(since version 4 afaik) this file contains a link to the upgrade instructions: 
http://otrs.github.io/doc/manual/admin/4.0/en/html/upgrading.html There is no 
single command or single step upgrade in Linux, even if you use a package 
manager. Sincere regards, Christoph  Am Dienstag, 10. März 2015, 11:45:00 
schrieb iga3...@yahoo.com: Hi, Can I make an upgrade from version otrs:itsm 
3.1.6 to 4 possible in one step (Linux)? Is there any upgrade documentation? 
 Thanks.  
-
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

   -
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

Re: [otrs] upgrade from otrs v3.1.6 to4 (Linux)

[Christoph Sandhaus]

Before OTRS 4 there was a file
  UPGRADING.md
containing step by step upgrade instrctions.

Actually (since version 4 afaik) this file contains a link to the upgrade 
instructions:
  http://otrs.github.io/doc/manual/admin/4.0/en/html/upgrading.html

There is no single command or single step upgrade in Linux, even if you use 
a package manager.

Sincere regards,
  Christoph


Am Dienstag, 10. März 2015, 11:45:00 schrieb iga3...@yahoo.com:
 Hi,
 Can I make an upgrade from version otrs:itsm 3.1.6 to 4 possible in one step 
 (Linux)?
 Is there any upgrade documentation?
 
 Thanks.
  

-
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

Re: [otrs] upgrade from 3.3.10 to 4.0.2

[Daniel Litzbach]

Hi Marco,

I think you have to install that using CPAN.

Regards

Daniel 


-Ursprüngliche Nachricht-
Von: otrs-boun...@otrs.org [mailto:otrs-boun...@otrs.org] Im Auftrag von Marco 
Borsani
Gesendet: Donnerstag, 4. Dezember 2014 12:03
An: User questions and discussions about OTRS.
Betreff: [otrs] upgrade from 3.3.10 to 4.0.2

Hi all

I am following the manual, but at the end I have some problems with the httpd 
restart.

It fails due the perl Apache2::Return (Can't locate Apache2/Reload.pm), but 
when I try to install it (like suggest form the otrs.CheckModules.pl) with yum 
install perl(Apache2::Reload) I don't find it anywhere.

Moreover, that module should be optional
OS: Centos 6.5

Any idea ?

Regards
Marco

-
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
-
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

Re: [otrs] upgrade from 3.3.10 to 4.0.2

[Sander Goudswaard]

Yes normally via CPAN, in some cases you can use a rpm

http://rpm.pbone.net/index.php3?stat=3search=perl-Apache2-Reloadsrodzaj=3

Sander
-
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

Re: [otrs] Upgrade path from 2.4.7 and up...

[Paul Simons]

Or you could setup a completely new system with the latest version of 
everything (OS, DB, OTRS, etc.) and test it thoroughly in your environment.
When you are ready make a concerted effort to close all the open tickets you 
have, swap to the new one starting at ticket number 1 on a fast system without 
all the baggage.
Find a freebee program to WEBify your old database by dumping into something 
searched function (have seen some) and 'Bob is your Uncle'...
Regards
Paul


-Original Message-
From: otrs-boun...@otrs.org [mailto:otrs-boun...@otrs.org] On Behalf Of Renee B
Sent: Wednesday, December 18, 2013 8:39 AM
To: otrs@otrs.org
Subject: Re: [otrs] Upgrade path from 2.4.7 and up...

Hello Charles,

you have to go the way 3.0.22 - 3.1.18 - 3.3.3

- Renée

On 18.12.2013 04:35, Lambrecht, Charles (Charles) wrote:
 Hello,
 I'm running OTRS 2.4.7 and I'm planning an upgrade.

 Do I need to upgrade throught 2.4.8, 2.4.9, etc. and all the way through 
 every release, security or patch?

 If not, should I jump to 3.0.1 or could I jump to 3.0.11?


 Regards,
 Charles



--
Perl / OTRS development: http://perl-services.de OTRS AddOn repository: 
http://opar.perl-services.de

-
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



Disclaimer: This e-mail (and any attachments to it) is confidential and 
intended solely for the named person/s to whom it is addressed. If you are not 
an intended recipient, please notify us immediately and delete the email from 
your system. Any review, dissemination or other use of it in these 
circumstances is prohibited.
-
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

Re: [otrs] : Upgrade path from 2.4.7 and up...

[Florian Edlhuber]

Hi Charles,
 
18.12.2013 04:47 - Lambrecht Charles schrieb:  I’m running OTRS 2.4.7 and I’m
planning an upgrade.
Do I need to upgrade throught 2.4.8, 2.4.9, etc. and all the way through every
release, security or patch?

Read the doc.otrs.org Upgrading section.

You don't need to follow the path of all patches, but you need the minor
releases.

2.4.x  3.0.x  3.1.x  3.2.x  3.3.x

I always use the latest available version (today is 3.0.22, 3.1.18, and so on)

Flo-
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

Re: [otrs] Upgrade path from 2.4.7 and up...

[Renee B]

Hello Charles,

you have to go the way 3.0.22 - 3.1.18 - 3.3.3

- Renée

On 18.12.2013 04:35, Lambrecht, Charles (Charles) wrote:
 Hello,
 I’m running OTRS 2.4.7 and I’m planning an upgrade.

 Do I need to upgrade throught 2.4.8, 2.4.9, etc. and all the way through 
 every release, security or patch?

 If not, should I jump to 3.0.1 or could I jump to 3.0.11?


 Regards,
 Charles



-- 
Perl / OTRS development: http://perl-services.de
OTRS AddOn repository: http://opar.perl-services.de

-
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

Re: [otrs] upgrade from 3.1 to 3.2: ITSM 3.1.4 packagenot correclty deployed

[Robson Kobayashi - TRE/MS]

There are some packages that are not listed in the site, but is listed in the 
ftp: 


http://ftp.otrs.org/pub/otrs/packages/ 


There are a ChangeManagement 3.2.9 that use framework 3.2. 


(Sorry for my poor English) 

!- 
Atenciosamente: Robson Massaki Kobayashi 
!- 

- Mensagem original -

De: Olivier Sallou olivier.sal...@irisa.fr 
Para: User questions and discussions about OTRS. otrs@otrs.org 
Enviadas: Sexta-feira, 27 de Setembro de 2013 6:28:22 
Assunto: [otrs] upgrade from 3.1 to 3.2: ITSM 3.1.4 packagenot correclty 
deployed 

Hi, 
I have upgraded my installation from 3.1 to 3.2 and upgraded my ITSM packages 
to via a remote repository. 

I still have an error on : ITSM 3.1.4 - Package not correctly deployed! Please 
reinstall the package. 

I have ITSMChangeManagement, Incident. all upgraded but I still have a 
component named ITSM in version 3.1.4 with no equivalent in 3.2. 

If I try to uninstall it, it is said it will delete all created tables 
(ChangeManagement etc...), and I do not want this 

How can I remove this error message or drop the ITSM package form my local 
repository? 

Thanks 

Olivier 


-- 


gpg key id: 4096R/326D8438  (keyring.debian.org)
Key fingerprint = 5FB4 6F83 D3B9 5204 6335  D26D 78DC 68DB 326D 8438 
-
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

Re: [otrs] Upgrade path from 3.0 to 3.2 - questions

[Martin Gruner]

No, please perform the full upgrade as described in UPGRADING.
Regards, mg

Am 25.07.13 15:11, schrieb Paul Simons:

 Hi Bogdan

 So your answer begs the question;

 Can I just do the upgrade path on the database and skip the 'app' bit?

  

 *___*

 *Paul Simons*

  


 

 Disclaimer: This e-mail (and any attachments to it) is confidential
 and intended solely for the named person/s to whom it is addressed. If
 you are not an intended recipient, please notify us immediately and
 delete the email from your system. Any review, dissemination or other
 use of it in these circumstances is prohibited.


 -
 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

-- 
Martin Gruner
Senior Developer RD

OTRS AG
Europaring 4
94315 Straubing

T: +49 (0)6172 681988 0
F: +49 (0)9421 56818 18
I:  www.otrs.com/

Geschäftssitz: Bad Homburg, Amtsgericht: Bad Homburg, HRB 10751, USt-Nr.: 
DE256610065
Aufsichtsratsvorsitzender: Burchard Steinbild, Vorstand: André Mindermann 
(Vorsitzender), Christopher Kuhn, Sabine Riedel

10 Jahre innovatives und flexibles Service Management - OTRS feiert sein 
Jubiläum am 12. September 2013 - Feiern Sie mit uns am Tag der offenen Tür und 
entdecken Sie, was OTRS alles kann
http://www.otrs.com/de/unternehmen/events/10-jahre-open-source-service-management-otrs-feiert-10-jaehriges-jubilaeum/

-
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

Re: [otrs] Upgrade path from 3.0 to 3.2 - questions

[Bogdan Iosif]

You must go through 3.1 at least for the database. Just to be safe, I would
perform a normal and complete upgrade to 3.1 as described in 3.1's
UPGRADING document. Then check the app runs OK - perhaps create a VM
snapshot at this point - and then proceed to upgrade to 3.2.

/bogdan


On Thu, Jul 25, 2013 at 4:03 PM, Paul Simons paul.sim...@onair.aero wrote:

  I am running version 3.0.1 (CentOS and PostgreSQL 8.1) and I want to
 upgrade to the latest version 3.2.9.

 In fact I am building a completely new system and decommissioning the old
 hardware.

 Do I have to follow the upgrade path 3.0  3.1  3.2 or is there an easier
 way?
 I only want to keep the ticket history.



 If I do have to follow the upgrade path has anyone documented how to do it
 and is willing to share :-) ?

 Regards

 *___*

 *Paul Simons*


 --

 Disclaimer: This e-mail (and any attachments to it) is confidential and
 intended solely for the named person/s to whom it is addressed. If you are
 not an intended recipient, please notify us immediately and delete the
 email from your system. Any review, dissemination or other use of it in
 these circumstances is prohibited.

 -
 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

-
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

Re: [otrs] Upgrade path from 3.0 to 3.2 - questions

[Paul Simons]

Hi Bogdan
So your answer begs the question;
Can I just do the upgrade path on the database and skip the ‘app’ bit?

___
Paul Simons





Disclaimer: This e-mail (and any attachments to it) is confidential and 
intended solely for the named person/s to whom it is addressed. If you are not 
an intended recipient, please notify us immediately and delete the email from 
your system. Any review, dissemination or other use of it in these 
circumstances is prohibited.
-
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

Re: [otrs] Upgrade path from 3.0 to 3.2 - questions

[Bogdan Iosif]

in theory it's possible. in practice... i don't know. i run on windows and
app upgrade takes 5 min. seems like a small price to pay in order to test
3.1 upgrade is valid.
On Jul 25, 2013 4:11 PM, Paul Simons paul.sim...@onair.aero wrote:

  Hi Bogdan

 So your answer begs the question;

 Can I just do the upgrade path on the database and skip the ‘app’ bit?



 *___*

 *Paul Simons*



 --

 Disclaimer: This e-mail (and any attachments to it) is confidential and
 intended solely for the named person/s to whom it is addressed. If you are
 not an intended recipient, please notify us immediately and delete the
 email from your system. Any review, dissemination or other use of it in
 these circumstances is prohibited.

 -
 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

-
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

Re: [otrs] Upgrade from 3.2.2 to a new instaled 3.2.7

[Claudio M.]

In data mercoledì 12 giugno 2013 14:36:43, Claudio M. ha scritto:
 Hi
 I had a 3.2.2 installed on a Opensuse by RPM. Now i've installed on a fresh
 server 3.2.7 from source, I've copied the DB with a new name and copied the
 Defaults.pm to the new installation. I've launched bin/otrs.RebuildConfig.pl
 and checked the permissions but whhen i reply to a ticket otrs reply me
 with
 
 Need ArticleType or ArticleTypeID!
 
 Backend ERROR: OTRS-CGI-01 Perl: 5.16.2 OS: linux Time: Wed Jun 12 14:35:11
 2013 Message: Need ArticleType or ArticleTypeID! RemoteAddress: 192.168.1.2
 RequestURI: /otrs/index.pl Traceback (3533): Module:
 Kernel::System::Ticket::Article::ArticleSend (OTRS 3.2.7) Line: 2022 Module:
 Kernel::Modules::AgentTicketCompose::Run (OTRS 3.2.7) Line: 763 Module:
 Kernel::System::Web::InterfaceAgent::Run (OTRS 3.2.7) Line: 863 Module:
 ModPerl::ROOT::ModPerl::Registry::shared_opt_otrs_bin_cgi_2dbin_index_2epl:
 :handler (unknown version) Line: 41 Module: (eval) (v1.99) Line: 204 Module:
 ModPerl::RegistryCooker::run (v1.99) Line: 204 Module:
 ModPerl::RegistryCooker::default_handler (v1.99) Line: 170 Module:
 ModPerl::Registry::handler (v1.99) Line: 31
 
 Where did I go wrong?

Nobody can help me? 

Best regards
Claudio
-
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

Re: [otrs] Upgrade to 3.2 problems and questions

[Martin Gruner]

Hi Massimo,

Am 31.01.13 18:35, schrieb Bianchi Massimo:

  

 Hi all,

 I did a test-upgrade from 3.1.11 to 3.2

  

 It looks great but I have two problems and one question:

  

 BLOCKING:

 1) missing new ticket in customer interface

 Apparently I have not the new ticket in customer web interface --
 quite strange !

 I tested it with standard theme

The Ticket menu in the customer interface is supposed to be clickable,
a submenu should open. If that is not the case, you might be missing
some JavaScript loaded on the page. That could be caused by your
permission problem with SysConfig.

  

 MINOR

 2) search for customer ID in customer -  customer information
 starts a query that never ends

it works if I search for customer user
 in the same screen

Do you get any JavaScript (Browser console) or OTRS errors (logfile)?

  

 Anyone else experiencing the same problems ?

  

 QUESTION

 Curiosity: I created a test process (really great! Compliments to OTRS
 Dev group), but I cannot find a way/button to start it. Even the
 manual is not clear to me.

 I thought there will be a process ticket or something like that..

If you created a new active process and synchronized it to disk, a new
menu item will be visible: Ticket - Create new process ticket. This
will let you select the process.

Best regards, mg

-- 
Martin Gruner
Senior Developer RD

OTRS AG
Europaring 4
94315 Straubing

T: +49 (0)6172 681988 0
F: +49 (0)9421 56818 18
I:  www.otrs.com/

Geschäftssitz: Bad Homburg, Amtsgericht: Bad Homburg, HRB 10751, USt-Nr.: 
DE256610065
Aufsichtsratsvorsitzender: Burchard Steinbild, Vorstand: André Mindermann 
(Vorsitzender), Christopher Kuhn, Sabine Riedel

Mehr als ein Help Desk-System -- Prozess- und Kundenmanagement mit OTRS 3.2 -- 
Jetzt Frühbucherrabatt sichern:
http://www.otrs.com/de/loesungen/promotion/otrs-help-desk-32-special/

-
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

Re: [otrs] Upgrade to 3.2 - another little problem

[Martin Gruner]

This is indeed a permission problem and could cause some of the other
errors you mentioned. Make sure no SELinux or AppArmor policies are
blocking things, if you executed otrs.SetPermissions.pl correctly.

Regards, mg


Am 31.01.13 19:04, schrieb Bianchi Massimo:
 Hi all,
 I think that I missed some step...

 Tryng to modify ANY item in sysconfig leads to an error:


 Error Message: Can't write ConfigItem!

-- 
Martin Gruner
Senior Developer RD

OTRS AG
Europaring 4
94315 Straubing

T: +49 (0)6172 681988 0
F: +49 (0)9421 56818 18
I:  www.otrs.com/

Geschäftssitz: Bad Homburg, Amtsgericht: Bad Homburg, HRB 10751, USt-Nr.: 
DE256610065
Aufsichtsratsvorsitzender: Burchard Steinbild, Vorstand: André Mindermann 
(Vorsitzender), Christopher Kuhn, Sabine Riedel

Mehr als ein Help Desk-System – Prozess- und Kundenmanagement mit OTRS 3.2 – 
Jetzt Frühbucherrabatt sichern:
http://www.otrs.com/de/loesungen/promotion/otrs-help-desk-32-special/

-
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

Re: [otrs] Upgrade to 3.2 problems and questions

[Michiel Beijen]

Hi,

On Fri, Feb 1, 2013 at 9:31 AM, Martin Gruner martin.gru...@otrs.comwrote:


 Am 31.01.13 18:35, schrieb Bianchi Massimo:

  1) missing new ticket in customer interface

 Apparently I have not the “new ticket” in customer web interface – quite
 strange !

 I tested it with standard theme….

 The Ticket menu in the customer interface is supposed to be clickable, a
 submenu should open. If that is not the case, you might be missing some
 JavaScript loaded on the page. That could be caused by your permission
 problem with SysConfig.


It could also be you customized one of the settings under
Frontend::Customer::ModuleRegistration in SysConfig. Navigate to Admin 
SysConfig  Ticket  Frontend::Customer::ModuleRegistration and click the
circular arrows to load the bundled settings. Can you let us know if this
fixes your issue?

Note that the New Ticket button is in a drop-down menu in OTRS 3.2.x:
[image: Inline image 1]
--
Mike
2013-02-01 09_51_41-MyTickets - Ticket - OTRS.png-
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

Re: [otrs] Upgrade to 3.2 - another little problem

[Matthew Pulliam]

The permissions issue trying to change anything in sysconfig, most 
likely means that for whatever reason you ZZZAuto.pm file is not 
writable by the user/group that you web server is running as.


Based on your listing for the parameters you passed to the permissions 
script, check that the permissions on 
/opt/otrs/Kernel/Config/Files/ZZZAuto.pm
should be at least 664 with ownership otrs:apache or apache:apache. If 
this file is not writable by the user the web server runs as then no 
changes to sysconfig can be saved via the web interface.

-
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

Re: [otrs] Upgrade to 3.2 - another little problem

[Gerald Young]

make sure /opt/otrs isn't a symlink. Permissions may not apply correctly if
it is.


On Thu, Jan 31, 2013 at 1:04 PM, Bianchi Massimo 
massimo.bian...@nposistemi.it wrote:

  Hi all,

 I think that I missed some step…

 ** **

 Tryng to modify ANY item in sysconfig leads to an error:

 ** **

 ** **

 Error Message: Can't write ConfigItem! ** **

 ** **

 . 

 ** **

 You can Send a bugreport or go back to the previous page. 

 Error Details

 Backend ERROR: OTRS-CGI-10 Perl: 5.10.1 OS: linux Time: Thu Jan 31
 18:59:40 2013 Message: Can't write ConfigItem! RemoteAddress: 172.22.21.11
 RequestURI: /otrs/index.pl Traceback (1940): Module:
 Kernel::Modules::AdminSysConfig::Run (v1.125) Line: 206 Module:
 Kernel::System::Web::InterfaceAgent::Run (v1.73) Line: 866 Module:
 ModPerl::ROOT::ModPerl::Registry::opt_otrs_bin_cgi_2dbin_index_2epl::handler
 (unknown version) Line: 46 Module: (eval) (v1.94) Line: 204 Module:
 ModPerl::RegistryCooker::run (v1.94) Line: 204 Module:
 ModPerl::RegistryCooker::default_handler (v1.94) Line: 170 Module:
 ModPerl::Registry::handler (v1.99) Line: 31

 ** **

 ** **

 Apparently permission at file level are correct and I run the upgrade
 script to verify/adapt permissions.. (Centos 6.2 64bit)

 ** **

 I also did a “chown –R 777 /opt/otrs”, just to be on safe side and test it
 properly, after a server restart – then it worked.

 But it’s a little too open.

 ** **

 What should be the correct permissions ?

 ** **

 My fix permission strings was:

 bin/otrs.SetPermissions.pl --otrs-user=otrs --web-user=apache
 --otrs-group=apache --web-group=apache --admin-user=root --admin-group=root
 /opt/otrs

 ** **

 Thanks,

   Massimo

 ** **

 ** **

 Massimo Bianchi

 ** **

 Npo Sistemi S.p.A. - Gruppo Npo

 S.S.11 Padana Superiore 28

 20063 Cernusco S/Naviglio MI

 Tel: +39 02 92596.322

 Cell: +39 348 5852275

 Fax: +39 02 92140548

 ** **

 Skype: massimo.bianchi

 Lync: massimo.bian...@nposistemi.it

 Mail: massimo.bian...@nposistemi.it

 Web: http://www.nposistemi.it

 ** **

 -
 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

-
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

Re: [otrs] Upgrade to 3.2 - another little problem

[Rainer Bendig]

Hm upgrade file says:

--- snip ---8---
5) Install the new release (tar or RPM)
   

   With the tarball:

shell cd /opt
shell tar -xzf otrs-x.x.x.tar.gz
shell ln -s otrs-x.x.x otrs
--- /snip ---8--

maybe this needs a patch ;(

Am 31.01.2013 20:16, schrieb Gerald Young:
 make sure /opt/otrs isn't a symlink. Permissions may not apply correctly
 if it is.
 
 
 On Thu, Jan 31, 2013 at 1:04 PM, Bianchi Massimo
 massimo.bian...@nposistemi.it mailto:massimo.bian...@nposistemi.it
 wrote:
 
 Hi all,
 
 I think that I missed some step…
 
 __ __
 
 Tryng to modify ANY item in sysconfig leads to an error:
 
 __ __
 
 __ __
 
 Error Message: Can't write ConfigItem! __ __
 
 __ __
 
 . 
 
 __ __
 
 You can Send a bugreport or go back to the previous page. 
 
 Error Details
 
 Backend ERROR: OTRS-CGI-10 Perl: 5.10.1 OS: linux Time: Thu Jan 31
 18:59:40 2013 Message: Can't write ConfigItem! RemoteAddress:
 172.22.21.11 RequestURI: /otrs/index.pl http://index.pl Traceback
 (1940): Module: Kernel::Modules::AdminSysConfig::Run (v1.125) Line:
 206 Module: Kernel::System::Web::InterfaceAgent::Run (v1.73) Line:
 866 Module:
 
 ModPerl::ROOT::ModPerl::Registry::opt_otrs_bin_cgi_2dbin_index_2epl::handler
 (unknown version) Line: 46 Module: (eval) (v1.94) Line: 204 Module:
 ModPerl::RegistryCooker::run (v1.94) Line: 204 Module:
 ModPerl::RegistryCooker::default_handler (v1.94) Line: 170 Module:
 ModPerl::Registry::handler (v1.99) Line: 31
 
 __ __
 
 __ __
 
 Apparently permission at file level are correct and I run the
 upgrade script to verify/adapt permissions.. (Centos 6.2 64bit)
 
 __ __
 
 I also did a “chown –R 777 /opt/otrs”, just to be on safe side and
 test it properly, after a server restart – then it worked.
 
 But it’s a little too open.
 
 __ __
 
 What should be the correct permissions ?
 
 __ __
 
 My fix permission strings was:
 
 bin/otrs.SetPermissions.pl http://otrs.SetPermissions.pl
 --otrs-user=otrs --web-user=apache --otrs-group=apache
 --web-group=apache --admin-user=root --admin-group=root /opt/otrs
 
 __ __
 
 Thanks,
 
   Massimo
 
 __ __
 
 __ __
 
 Massimo Bianchi
 
 __ __
 
 Npo Sistemi S.p.A. - Gruppo Npo
 
 S.S.11 Padana Superiore 28
 
 20063 Cernusco S/Naviglio MI
 
 Tel: +39 02 92596.322 tel:%2B39%2002%2092596.322
 
 Cell: +39 348 5852275 tel:%2B39%20348%205852275
 
 Fax: +39 02 92140548 tel:%2B39%2002%2092140548
 
 __ __
 
 Skype: massimo.bianchi
 
 Lync: massimo.bian...@nposistemi.it
 mailto:massimo.bian...@nposistemi.it
 
 Mail: massimo.bian...@nposistemi.it
 mailto:massimo.bian...@nposistemi.it
 
 Web: http://www.nposistemi.it http://www.nposistemi.it/
 
 __ __
 
 
 -
 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
 
 
 
 
 -
 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
 

-
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

Re: [otrs] Upgrade to 3.2 - another little problem

[Gerald Young]

So run perms against the otrs-x.x.x folder.
On Jan 31, 2013 11:44 PM, Rainer Bendig mrbendi...@gmail.com wrote:

 Hm upgrade file says:

 --- snip ---8---
 5) Install the new release (tar or RPM)


With the tarball:

 shell cd /opt
 shell tar -xzf otrs-x.x.x.tar.gz
 shell ln -s otrs-x.x.x otrs
 --- /snip ---8--

 maybe this needs a patch ;(

 Am 31.01.2013 20:16, schrieb Gerald Young:
  make sure /opt/otrs isn't a symlink. Permissions may not apply correctly
  if it is.
 
 
  On Thu, Jan 31, 2013 at 1:04 PM, Bianchi Massimo
  massimo.bian...@nposistemi.it mailto:massimo.bian...@nposistemi.it
  wrote:
 
  Hi all,
 
  I think that I missed some step…
 
  __ __
 
  Tryng to modify ANY item in sysconfig leads to an error:
 
  __ __
 
  __ __
 
  Error Message: Can't write ConfigItem! __ __
 
  __ __
 
  . 
 
  __ __
 
  You can Send a bugreport or go back to the previous page. 
 
  Error Details
 
  Backend ERROR: OTRS-CGI-10 Perl: 5.10.1 OS: linux Time: Thu Jan 31
  18:59:40 2013 Message: Can't write ConfigItem! RemoteAddress:
  172.22.21.11 RequestURI: /otrs/index.pl http://index.pl Traceback
  (1940): Module: Kernel::Modules::AdminSysConfig::Run (v1.125) Line:
  206 Module: Kernel::System::Web::InterfaceAgent::Run (v1.73) Line:
  866 Module:
 
 ModPerl::ROOT::ModPerl::Registry::opt_otrs_bin_cgi_2dbin_index_2epl::handler
  (unknown version) Line: 46 Module: (eval) (v1.94) Line: 204 Module:
  ModPerl::RegistryCooker::run (v1.94) Line: 204 Module:
  ModPerl::RegistryCooker::default_handler (v1.94) Line: 170 Module:
  ModPerl::Registry::handler (v1.99) Line: 31
 
  __ __
 
  __ __
 
  Apparently permission at file level are correct and I run the
  upgrade script to verify/adapt permissions.. (Centos 6.2 64bit)
 
  __ __
 
  I also did a “chown –R 777 /opt/otrs”, just to be on safe side and
  test it properly, after a server restart – then it worked.
 
  But it’s a little too open.
 
  __ __
 
  What should be the correct permissions ?
 
  __ __
 
  My fix permission strings was:
 
  bin/otrs.SetPermissions.pl http://otrs.SetPermissions.pl
  --otrs-user=otrs --web-user=apache --otrs-group=apache
  --web-group=apache --admin-user=root --admin-group=root /opt/otrs
 
  __ __
 
  Thanks,
 
Massimo
 
  __ __
 
  __ __
 
  Massimo Bianchi
 
  __ __
 
  Npo Sistemi S.p.A. - Gruppo Npo
 
  S.S.11 Padana Superiore 28
 
  20063 Cernusco S/Naviglio MI
 
  Tel: +39 02 92596.322 tel:%2B39%2002%2092596.322
 
  Cell: +39 348 5852275 tel:%2B39%20348%205852275
 
  Fax: +39 02 92140548 tel:%2B39%2002%2092140548
 
  __ __
 
  Skype: massimo.bianchi
 
  Lync: massimo.bian...@nposistemi.it
  mailto:massimo.bian...@nposistemi.it
 
  Mail: massimo.bian...@nposistemi.it
  mailto:massimo.bian...@nposistemi.it
 
  Web: http://www.nposistemi.it http://www.nposistemi.it/
 
  __ __
 
 
  -
  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
 
 
 
 
  -
  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
 

 -
 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

-
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

Re: [otrs] upgrade from 2.3 to 3.1 mysql character set UTF8

[Florian Edlhuber]

hi

i remember a script charset-convert.pl 

as far as i know, you must dump the database and convert the dump and then 
restore it


hth

florian

Am 27.12.2012 um 10:32 schrieb Coert Waagmeester lgro...@waagmeester.co.za:

 Hello all,
 
 I have successfully and carefully upgraded OTRS from 2.3 on a Centos 2.5 box 
 to 3.1 on a new Centos 6.3 box.
 
 So far everything seems to be working.
 
 According to Admin  Support Assessment,
 
 I have to set the database to use utf8 instead of latin1.
 
 Googled till I am blue in the face, and found the following:
 
 
 My otrs DB:
 mysql SELECT default_character_set_name FROM information_schema.SCHEMATA S 
 WHERE schema_name='otrs';
 ++
 | default_character_set_name |
 ++
 | latin1 |
 ++
 1 row in set (0.00 sec)
 
 
 This DB went through all the correct upgrade steps.
 I started by installing otrs 2.3 and restoring the data.
 Upgraded to 2.4, 3.0, and 3.1, and for each upgrade ran the appropriate 
 DBUpdate sql files and perl scripts.
 
 Is there a way to change the existing DB from latin1 to UTF8?
 
 according to google I have to for loop through each table?
 
 Any help would be greatly appreciated!
 
 Kind regards,
 -
 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
-
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

Re: [otrs] upgrade version otrs

[Steven Carr]

Download the tar.gz source file, extract it and read the UPGRADING document.

Steve



On 22 August 2012 15:30, Leon Carrasco, Daniel daniel.l...@surasistencia.cl
 wrote:

  Hi everybody,

 ** **

   Someone updated the version of OTRS from 3.1.5 to 3.1.8.

 The true is I am really new in this platform, and I cannot find a mini
 how-to. Us can help me?

 ** **

 Best Regards,

 Daniel León C.

 Administrador de Sistemas


-
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

Re: [otrs] Upgrade from 2.4.4 to 3.0.1 to 3.1.7

[Derek Kiely]

Hi Steve,

I have tried your suggestion and am now getting the following error on the
same page (Title/Properties), any ideas? I have tried re-run the bin/
otrs.RebuildConfig.pl but still the same.

[image: Inline images 1]

Derek Kiely
EMEA Support Team Leader
KEMP Technologies Limited http://www.kemptechnologies.com/
Mary Rosse Centre
Holland Road
National Technology Park
Limerick
Ireland
DDI: +353 61 260104
Office: +353 61 260101



On 5 July 2012 18:10, Steven Carr sjc...@gmail.com wrote:

 If a file is named .rpmsave then this is because it did not match the file
 distributed with the RPM and so when it was upgraded it moved your
 configuration to one side.

 You can try renaming otrs.conf.rpmsave to otrs.conf and restarting Apache
 - but there may be configuration being loaded from elsewhere in your Apache
 config, so check the rest of the Apache config files first incase there are
 any directives pointing to the old otrs scripts directory.

 Steve




 On 5 July 2012 18:02, Derek Kiely dki...@kemptechnologies.com wrote:

 Hi Steve,

 Thanks for the feedback, I checked in the /etc/httpd/conf.d directory and
 I see a file called otrs.conf.rpmsave - here it is

 # --
 # added for OTRS (http://otrs.org/)
 # $Id: apache2-httpd-new.include.conf,v 1.3 2007/04/16 12:11:53 martin
 Exp $
 # --

 # agent, admin and customer frontend
 ScriptAlias /otrs/ /opt/otrs/bin/cgi-bin/
 Alias /otrs-web/ /opt/otrs/var/httpd/htdocs/

 # if mod_perl is used
 #IfModule mod_perl.c

 # load all otrs modules
 Perlrequire /opt/otrs/scripts/apache2-perl-startup.pl

 # Apache::Reload - Reload Perl Modules when Changed on Disk
 PerlModule Apache2::Reload
 PerlInitHandler Apache2::Reload
 PerlModule Apache2::RequestRec

 # set mod_perl2 options
 Location /otrs
 #ErrorDocument 403 /otrs/customer.pl
 ErrorDocument 403 /otrs/index.pl
 SetHandler  perl-script
 PerlResponseHandler ModPerl::Registry
 Options +ExecCGI
 PerlOptions +ParseHeaders
 PerlOptions +SetupEnv
 Order allow,deny
 Allow from all
 /Location

 #/IfModule

 # directory settings
 Directory /opt/otrs/bin/cgi-bin/
 AllowOverride None
 Options +ExecCGI -Includes
 Order allow,deny
 Allow from all
 /Directory
 Directory /opt/otrs/var/httpd/htdocs/
 AllowOverride All
 Order allow,deny
 Allow from all
 /Directory

 What is the .rpmsave about and is this where my problem is coming from?
 Any ideas on how to fix it?

 Derek Kiely
 EMEA Support Team Leader
 KEMP Technologies Limited http://www.kemptechnologies.com/
 Mary Rosse Centre
 Holland Road
 National Technology Park
 Limerick
 Ireland
 DDI: +353 61 260104
 Office: +353 61 260101



 On 5 July 2012 17:33, Steven Carr sjc...@gmail.com wrote:

 Check your Apache configuration (possibly /etc/httpd/conf.d/otrs ?) and
 verify the otrs-web virtual directory is pointing to the correct location
 then bounce Apache.

 Steve



 On 5 July 2012 16:26, Derek Kiely dki...@kemptechnologies.com wrote:


 Hello I have updated our OTRS system from 2.4.4 to 3.17 in a two step
 increment,

 All appears to be OK except that when I click on ticket properties I
 get the following error message

 [image: Inline images 1]

 I followed the upgrade scripts exactly, it also looks like the
 js/js-cache is pointing to the wrong directory it is pointing to
 /opt/otrs-2.4.4//js-cache rather than /opt/otrs//js-cache/

 Any help would be greatly appreciated.

 Derek Kiely



 -
 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



 -
 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



 -
 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



 -
 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

image.png-
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

Re: [otrs] Upgrade from 2.4.4 to 3.0.1 to 3.1.7

[Steven Carr]

Not sure to be honest, it still looks like something is missing as the
browser hasn't been able to fully initialise all of the javascript. Might
be worth searching/posting on the dev list to see if they can help.

Steve



On 6 July 2012 10:33, Derek Kiely dki...@kemptechnologies.com wrote:

 Hi Steve,

 I have tried your suggestion and am now getting the following error on the
 same page (Title/Properties), any ideas? I have tried re-run the bin/
 otrs.RebuildConfig.pl but still the same.

 [image: Inline images 1]

 Derek Kiely
 EMEA Support Team Leader
 KEMP Technologies Limited http://www.kemptechnologies.com/
 Mary Rosse Centre
 Holland Road
 National Technology Park
 Limerick
 Ireland
 DDI: +353 61 260104
 Office: +353 61 260101



 On 5 July 2012 18:10, Steven Carr sjc...@gmail.com wrote:

 If a file is named .rpmsave then this is because it did not match the
 file distributed with the RPM and so when it was upgraded it moved your
 configuration to one side.

 You can try renaming otrs.conf.rpmsave to otrs.conf and restarting Apache
 - but there may be configuration being loaded from elsewhere in your Apache
 config, so check the rest of the Apache config files first incase there are
 any directives pointing to the old otrs scripts directory.

 Steve




 On 5 July 2012 18:02, Derek Kiely dki...@kemptechnologies.com wrote:

 Hi Steve,

 Thanks for the feedback, I checked in the /etc/httpd/conf.d directory
 and I see a file called otrs.conf.rpmsave - here it is

 # --
 # added for OTRS (http://otrs.org/)
 # $Id: apache2-httpd-new.include.conf,v 1.3 2007/04/16 12:11:53 martin
 Exp $
 # --

 # agent, admin and customer frontend
 ScriptAlias /otrs/ /opt/otrs/bin/cgi-bin/
 Alias /otrs-web/ /opt/otrs/var/httpd/htdocs/

 # if mod_perl is used
 #IfModule mod_perl.c

 # load all otrs modules
 Perlrequire /opt/otrs/scripts/apache2-perl-startup.pl

 # Apache::Reload - Reload Perl Modules when Changed on Disk
 PerlModule Apache2::Reload
 PerlInitHandler Apache2::Reload
 PerlModule Apache2::RequestRec

 # set mod_perl2 options
 Location /otrs
 #ErrorDocument 403 /otrs/customer.pl
 ErrorDocument 403 /otrs/index.pl
 SetHandler  perl-script
 PerlResponseHandler ModPerl::Registry
 Options +ExecCGI
 PerlOptions +ParseHeaders
 PerlOptions +SetupEnv
 Order allow,deny
 Allow from all
 /Location

 #/IfModule

 # directory settings
 Directory /opt/otrs/bin/cgi-bin/
 AllowOverride None
 Options +ExecCGI -Includes
 Order allow,deny
 Allow from all
 /Directory
 Directory /opt/otrs/var/httpd/htdocs/
 AllowOverride All
 Order allow,deny
 Allow from all
 /Directory

 What is the .rpmsave about and is this where my problem is coming from?
 Any ideas on how to fix it?

 Derek Kiely
 EMEA Support Team Leader
 KEMP Technologies Limited http://www.kemptechnologies.com/
 Mary Rosse Centre
 Holland Road
 National Technology Park
 Limerick
 Ireland
 DDI: +353 61 260104
 Office: +353 61 260101



 On 5 July 2012 17:33, Steven Carr sjc...@gmail.com wrote:

 Check your Apache configuration (possibly /etc/httpd/conf.d/otrs ?) and
 verify the otrs-web virtual directory is pointing to the correct location
 then bounce Apache.

 Steve



 On 5 July 2012 16:26, Derek Kiely dki...@kemptechnologies.com wrote:


 Hello I have updated our OTRS system from 2.4.4 to 3.17 in a two step
 increment,

 All appears to be OK except that when I click on ticket properties I
 get the following error message

 [image: Inline images 1]

 I followed the upgrade scripts exactly, it also looks like the
 js/js-cache is pointing to the wrong directory it is pointing to
 /opt/otrs-2.4.4//js-cache rather than /opt/otrs//js-cache/

 Any help would be greatly appreciated.

 Derek Kiely



 -
 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



 -
 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



 -
 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



 -
 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



 -
 OTRS mailing list: otrs - Webpage: http://otrs.org/
 Archive: http://lists.otrs.org/pipermail/otrs
 To unsubscribe: 

Re: [otrs] Upgrade from 2.4.4 to 3.0.1 to 3.1.7

[Derek Kiely]

Hi Steve,

Thanks for the feedback, I checked in the /etc/httpd/conf.d directory and I
see a file called otrs.conf.rpmsave - here it is

# --
# added for OTRS (http://otrs.org/)
# $Id: apache2-httpd-new.include.conf,v 1.3 2007/04/16 12:11:53 martin Exp $
# --

# agent, admin and customer frontend
ScriptAlias /otrs/ /opt/otrs/bin/cgi-bin/
Alias /otrs-web/ /opt/otrs/var/httpd/htdocs/

# if mod_perl is used
#IfModule mod_perl.c

# load all otrs modules
Perlrequire /opt/otrs/scripts/apache2-perl-startup.pl

# Apache::Reload - Reload Perl Modules when Changed on Disk
PerlModule Apache2::Reload
PerlInitHandler Apache2::Reload
PerlModule Apache2::RequestRec

# set mod_perl2 options
Location /otrs
#ErrorDocument 403 /otrs/customer.pl
ErrorDocument 403 /otrs/index.pl
SetHandler  perl-script
PerlResponseHandler ModPerl::Registry
Options +ExecCGI
PerlOptions +ParseHeaders
PerlOptions +SetupEnv
Order allow,deny
Allow from all
/Location

#/IfModule

# directory settings
Directory /opt/otrs/bin/cgi-bin/
AllowOverride None
Options +ExecCGI -Includes
Order allow,deny
Allow from all
/Directory
Directory /opt/otrs/var/httpd/htdocs/
AllowOverride All
Order allow,deny
Allow from all
/Directory

What is the .rpmsave about and is this where my problem is coming from? Any
ideas on how to fix it?

Derek Kiely
EMEA Support Team Leader
KEMP Technologies Limited http://www.kemptechnologies.com/
Mary Rosse Centre
Holland Road
National Technology Park
Limerick
Ireland
DDI: +353 61 260104
Office: +353 61 260101



On 5 July 2012 17:33, Steven Carr sjc...@gmail.com wrote:

 Check your Apache configuration (possibly /etc/httpd/conf.d/otrs ?) and
 verify the otrs-web virtual directory is pointing to the correct location
 then bounce Apache.

 Steve



 On 5 July 2012 16:26, Derek Kiely dki...@kemptechnologies.com wrote:


 Hello I have updated our OTRS system from 2.4.4 to 3.17 in a two step
 increment,

 All appears to be OK except that when I click on ticket properties I get
 the following error message

 [image: Inline images 1]

 I followed the upgrade scripts exactly, it also looks like the
 js/js-cache is pointing to the wrong directory it is pointing to
 /opt/otrs-2.4.4//js-cache rather than /opt/otrs//js-cache/

 Any help would be greatly appreciated.

 Derek Kiely



 -
 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



 -
 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

-
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

Re: [otrs] Upgrade from 2.4.4 to 3.0.1 to 3.1.7

[Steven Carr]

If a file is named .rpmsave then this is because it did not match the file
distributed with the RPM and so when it was upgraded it moved your
configuration to one side.

You can try renaming otrs.conf.rpmsave to otrs.conf and restarting Apache -
but there may be configuration being loaded from elsewhere in your Apache
config, so check the rest of the Apache config files first incase there are
any directives pointing to the old otrs scripts directory.

Steve



On 5 July 2012 18:02, Derek Kiely dki...@kemptechnologies.com wrote:

 Hi Steve,

 Thanks for the feedback, I checked in the /etc/httpd/conf.d directory and
 I see a file called otrs.conf.rpmsave - here it is

 # --
 # added for OTRS (http://otrs.org/)
 # $Id: apache2-httpd-new.include.conf,v 1.3 2007/04/16 12:11:53 martin Exp
 $
 # --

 # agent, admin and customer frontend
 ScriptAlias /otrs/ /opt/otrs/bin/cgi-bin/
 Alias /otrs-web/ /opt/otrs/var/httpd/htdocs/

 # if mod_perl is used
 #IfModule mod_perl.c

 # load all otrs modules
 Perlrequire /opt/otrs/scripts/apache2-perl-startup.pl

 # Apache::Reload - Reload Perl Modules when Changed on Disk
 PerlModule Apache2::Reload
 PerlInitHandler Apache2::Reload
 PerlModule Apache2::RequestRec

 # set mod_perl2 options
 Location /otrs
 #ErrorDocument 403 /otrs/customer.pl
 ErrorDocument 403 /otrs/index.pl
 SetHandler  perl-script
 PerlResponseHandler ModPerl::Registry
 Options +ExecCGI
 PerlOptions +ParseHeaders
 PerlOptions +SetupEnv
 Order allow,deny
 Allow from all
 /Location

 #/IfModule

 # directory settings
 Directory /opt/otrs/bin/cgi-bin/
 AllowOverride None
 Options +ExecCGI -Includes
 Order allow,deny
 Allow from all
 /Directory
 Directory /opt/otrs/var/httpd/htdocs/
 AllowOverride All
 Order allow,deny
 Allow from all
 /Directory

 What is the .rpmsave about and is this where my problem is coming from?
 Any ideas on how to fix it?

 Derek Kiely
 EMEA Support Team Leader
 KEMP Technologies Limited http://www.kemptechnologies.com/
 Mary Rosse Centre
 Holland Road
 National Technology Park
 Limerick
 Ireland
 DDI: +353 61 260104
 Office: +353 61 260101



 On 5 July 2012 17:33, Steven Carr sjc...@gmail.com wrote:

 Check your Apache configuration (possibly /etc/httpd/conf.d/otrs ?) and
 verify the otrs-web virtual directory is pointing to the correct location
 then bounce Apache.

 Steve



 On 5 July 2012 16:26, Derek Kiely dki...@kemptechnologies.com wrote:


 Hello I have updated our OTRS system from 2.4.4 to 3.17 in a two step
 increment,

 All appears to be OK except that when I click on ticket properties I
 get the following error message

 [image: Inline images 1]

 I followed the upgrade scripts exactly, it also looks like the
 js/js-cache is pointing to the wrong directory it is pointing to
 /opt/otrs-2.4.4//js-cache rather than /opt/otrs//js-cache/

 Any help would be greatly appreciated.

 Derek Kiely



 -
 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



 -
 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



 -
 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

-
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

Re: [otrs] Upgrade from 3.0.12 to 3.1.4

[ml ml]

Hello Nils,

sorry. I totally missed out an error on the previous Update from 2.4.5
to 3.0.12. I copied the otrs Box and i am trying to do the upgrades in
a virtual box where i am able to use snapshots to revert to the
original status.

Here is the error i get when i try to update from 2.4.5 to 3.0.12 (or
3.0.11). Can i go from 2.4.5 to 3.0.12 or do i have to go to 2.4.12
first?


+ su - otrs -c 'cd /opt/otrs/ ; scripts/DBUpdate-to-3.0.pl'

Migration started...

Step 1 of 5: Refresh configuration cache... done.

Step 2 of 5: Migrating theme configuration... done.

Step 3 of 5: Cleaning up the permission table... done.

Step 4 of 5: Cleanup pending time of tickets without pending state-type... done.

DBD::mysql::db do failed: Table 'virtual_fs' already exists at
/var/www/otrs-3.0.11/Kernel/System/DB.pm line 422.
ERROR: OTRS-DBUpdate-to-3.0-10 Perl: 5.10.1 OS: linux Time: Fri May 18
10:23:21 2012

 Message: Table 'virtual_fs' already exists, SQL: 'CREATE TABLE virtual_fs (
id BIGINT NOT NULL AUTO_INCREMENT,
filename TEXT NOT NULL,
backend VARCHAR (60) NOT NULL,
backend_key VARCHAR (160) NOT NULL,
create_time DATETIME NOT NULL,
PRIMARY KEY(id),
INDEX virtual_fs_backend (backend(60)),
INDEX virtual_fs_filename (filename(350))
)'

 Traceback (1587):
   Module: main::CreateVirtualFSTables (v1.5) Line: 350
   Module: scripts/DBUpdate-to-3.0.pl (v1.5) Line: 95

ERROR: OTRS-DBUpdate-to-3.0-10 Perl: 5.10.1 OS: linux Time: Fri May 18
10:23:21 2012

 Message: Error during table creation!

 Traceback (1587):
   Module: main::CreateVirtualFSTables (v1.5) Line: 352
   Module: scripts/DBUpdate-to-3.0.pl (v1.5) Line: 95

Step 5 of 5: Creating VirtualFS tables (if necessary)... Error!

Migration completed!


On Thu, May 17, 2012 at 10:44 PM, Nils Leideck nils.leid...@leidex.net wrote:
 Hi,

 you did not follow the UPGRADING file!

 Before you can run the perl upgrade script you have to execute a sql file on 
 your DB.

 Read the UPGRADING file carefully and try again!

 On 17.05.2012, at 18:29, ml ml wrote:

 when i try to upgrade from 3.0.12 to 3.1.4 i get:

 Step 2 of 24: Check framework version... done.

 DBD::mysql::db do failed: Table 'otrs2_4.dynamic_field' doesn't exist
 at /var/www/otrs-3.1.5/Kernel/System/DB.pm line 478.
 ERROR: OTRS-DBUpdate-to-3.1-10 Perl: 5.10.1 OS: linux Time: Thu May 17
 17:10:15 2012

 Message: Table 'otrs2_4.dynamic_field' doesn't exist, SQL: 'SELECT
 count(id) FROM dynamic_field'

 Traceback (2083):
   Module: main::_CheckDynamicFieldTables (v1.85) Line: 385
   Module: scripts/DBUpdate-to-3.1.pl (v1.85) Line: 86

 Check if dynamic_field table exists, failed! at
 scripts/DBUpdate-to-3.1.pl line 390.
 Step 3 of 24: Creating DynamicField tables (if necessary)...

 Is this something to worry about?

 Cheers, Nils
 --
 http://webint.cryptonode.de / a Fractal project

 -
 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
-
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

Re: [otrs] Upgrade from 3.0.12 to 3.1.4

[Nils Leideck]

Hi,

you did not follow the UPGRADING file! 

Before you can run the perl upgrade script you have to execute a sql file on 
your DB.

Read the UPGRADING file carefully and try again!

On 17.05.2012, at 18:29, ml ml wrote:

 when i try to upgrade from 3.0.12 to 3.1.4 i get:
 
 Step 2 of 24: Check framework version... done.
 
 DBD::mysql::db do failed: Table 'otrs2_4.dynamic_field' doesn't exist
 at /var/www/otrs-3.1.5/Kernel/System/DB.pm line 478.
 ERROR: OTRS-DBUpdate-to-3.1-10 Perl: 5.10.1 OS: linux Time: Thu May 17
 17:10:15 2012
 
 Message: Table 'otrs2_4.dynamic_field' doesn't exist, SQL: 'SELECT
 count(id) FROM dynamic_field'
 
 Traceback (2083):
   Module: main::_CheckDynamicFieldTables (v1.85) Line: 385
   Module: scripts/DBUpdate-to-3.1.pl (v1.85) Line: 86
 
 Check if dynamic_field table exists, failed! at
 scripts/DBUpdate-to-3.1.pl line 390.
 Step 3 of 24: Creating DynamicField tables (if necessary)...
 
 Is this something to worry about?

Cheers, Nils
-- 
http://webint.cryptonode.de / a Fractal project

-
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

Re: [otrs] upgrade from 3.0.11 to 3.1.2 error on: scripts/DBUpdate-to-3.1.mysql.sql

[Luca Domenella]

Hi all,

I also seen that the script create a table gi_webservice_config and try to add 
a FK. Awfully our DB is MyISAM… So its not supported

In the otrs3 db schema for mysql, do i need to change the default DB ENGINE 
from MyISAM to INNODB ?

Please let me know how to fix that

Br,

Luca Domenella
Storage Team Leader

P: +39 06 54070440 ext: 16
E: luca.domene...@bwinparty.com

bwin Italia
Via Adolfo Ravà, 124
00142 Roma (rm)
Italy
www.bwinparty.com
This email and any attachments are confidential, and may be legally privileged 
and protected by copyright. If you are not the intended recipient dissemination 
or copying of this email is prohibited. If you have received this in error, 
please notify the sender by replying by email and then delete the email 
completely from your system.

Any views or opinions are solely those of the sender.  This communication is 
not intended to form a binding contract unless expressly indicated to the 
contrary and properly authorised. Any actions taken on the basis of this email 
are at the recipient's own risk.


Da: Luca Domenella 
luca.domene...@bwinparty.commailto:luca.domene...@bwinparty.com
Risposta: otrs@otrs.orgmailto:otrs@otrs.org 
otrs@otrs.orgmailto:otrs@otrs.org
Data: Wed, 7 Mar 2012 11:22:22 +
A: otrs@otrs.orgmailto:otrs@otrs.org otrs@otrs.orgmailto:otrs@otrs.org
Oggetto: [otrs] upgrade from 3.0.11 to 3.1.2 error on: 
scripts/DBUpdate-to-3.1.mysql.sql

Hi,

Im testing the upgrade procedure from out ours 2.0.4 to 3.1.2.
I passed thought all the steps:
2.0.4 - 2.1.x
2.1.x - 2.2.x
2.2.x - 2.3.x
2.3.x - 2.4.x
2.4.x – 3.0.11

And from 3.0.11 to 3.1.2 when i do the following: cat 
scripts/DBUpdate-to-3.1.mysql.sql | mysql -p -f -u root otrs

I get this error:
ERROR 1050 (42S01) at line 169: Table 'smime_signer_cert_relations' already 
exists

Our DBA looked at the sql script and also seen the the instructions go ahead 
but they stopped when they are trying to create a table with foreign keys.

The problem looks to be that the engine is MyISAM and that myisam do not 
support foreign keys. We are using mysql 5.5 (stable)

Now the question is: how can i go ahead ? I change the engine from myisam to 
innodb for this table or did i miss something ?

Please let me know.

Best regards,


Luca Domenella
Storage Team Leader

P: +39 06 54070440 ext: 16
E: luca.domene...@bwinparty.com

bwin Italia
Via Adolfo Ravà, 124
00142 Roma (rm)
Italy
www.bwinparty.com
This email and any attachments are confidential, and may be legally privileged 
and protected by copyright. If you are not the intended recipient dissemination 
or copying of this email is prohibited. If you have received this in error, 
please notify the sender by replying by email and then delete the email 
completely from your system.

Any views or opinions are solely those of the sender.  This communication is 
not intended to form a binding contract unless expressly indicated to the 
contrary and properly authorised. Any actions taken on the basis of this email 
are at the recipient's own risk.

- 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
-
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

Re: [otrs] upgrade from 3.0.11 to 3.1.2 error on: scripts/DBUpdate-to-3.1.mysql.sql

[Ugo Bellavance]

On 2012-03-07 06:43, Luca Domenella wrote:

Hi all,

I also seen that the script create a table gi_webservice_config and try
to add a FK. Awfully our DB is MyISAM… So its not supported

In the otrs3 db schema for mysql, do i need to change the default DB
ENGINE from MyISAM to INNODB ?


So that is why my upgrade to 3.1 didn't work :).

I haven't seen anything related to INNODB in the install notes or doc. 
Even a google search didn't show up much, except for a guy that says 
that he changed to INNODB for its engine in 2008.


Ugo

-
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

Re: [otrs] upgrade from 3.0.11 to 3.1.2 error on: scripts/DBUpdate-to-3.1.mysql.sql

[Luca Domenella]

Hi Ugo,

Have you done the upgrade in some way bypassing this problem or not ?

Br,

Luca Domenella
Storage Team Leader



P: +39 06 54070440 ext: 16
E: luca.domene...@bwinparty.com


bwin Italia
Via Adolfo Ravà, 124
00142 Roma (rm)
Italy

www.bwinparty.com


This email and any attachments are confidential, and may be legally
privileged and protected by copyright. If you are not the intended
recipient dissemination or copying of this email is prohibited. If you
have received this in error, please notify the sender by replying by email
and then delete the email completely from your system.
 
Any views or opinions are solely those of the sender.  This communication
is not intended to form a binding contract unless expressly indicated to
the contrary and properly authorised. Any actions taken on the basis of
this email are at the recipient's own risk.






Il giorno 3/7/12 1:45 PM, Ugo Bellavance u...@lubik.ca ha scritto:

On 2012-03-07 06:43, Luca Domenella wrote:
 Hi all,

 I also seen that the script create a table gi_webservice_config and try
 to add a FK. Awfully our DB is MyISAMŠ So its not supported

 In the otrs3 db schema for mysql, do i need to change the default DB
 ENGINE from MyISAM to INNODB ?

So that is why my upgrade to 3.1 didn't work :).

I haven't seen anything related to INNODB in the install notes or doc.
Even a google search didn't show up much, except for a guy that says
that he changed to INNODB for its engine in 2008.

Ugo

-
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

-
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

Re: [otrs] upgrade from 3.0.11 to 3.1.2 error on: scripts/DBUpdate-to-3.1.mysql.sql

[Steven Carr]

My OTRS install (3.0.11) seems to have a mix of MyISAM/InnoDB - would be
nice if developers stuck to one engine, and if they are going to change to
use relationship features in InnoDB, then change all tables.

Steve

+--++---+---+-+
| Table Name   | Engine | Rows  | Size  |
Collation   |
+--++---+---+-+
| article  | MyISAM | 1593  | 129.74 Mb |
utf8_general_ci |
| article_attachment   | MyISAM | 0 | 0.00 Mb   |
utf8_general_ci |
| article_flag | MyISAM | 1467  | 0.13 Mb   |
utf8_general_ci |
| article_plain| MyISAM | 0 | 0.00 Mb   |
utf8_general_ci |
| article_search   | MyISAM | 0 | 0.00 Mb   |
utf8_general_ci |
| article_sender_type  | MyISAM | 3 | 0.01 Mb   |
utf8_general_ci |
| article_type | MyISAM | 11| 0.01 Mb   |
utf8_general_ci |
| auto_response| MyISAM | 4 | 0.02 Mb   |
utf8_general_ci |
| auto_response_type   | MyISAM | 5 | 0.01 Mb   |
utf8_general_ci |
| customer_company | MyISAM | 3 | 0.01 Mb   |
utf8_general_ci |
| customer_preferences | MyISAM | 30| 0.01 Mb   |
utf8_general_ci |
| customer_user| MyISAM | 4 | 0.01 Mb   |
utf8_general_ci |
| faq_attachment   | MyISAM | 1 | 0.05 Mb   |
utf8_general_ci |
| faq_category | MyISAM | 2 | 0.00 Mb   |
utf8_general_ci |
| faq_category_group   | MyISAM | 4 | 0.00 Mb   |
utf8_general_ci |
| faq_history  | MyISAM | 19| 0.00 Mb   |
utf8_general_ci |
| faq_item | MyISAM | 4 | 0.01 Mb   |
utf8_general_ci |
| faq_language | MyISAM | 2 | 0.01 Mb   |
utf8_general_ci |
| faq_log  | MyISAM | 94| 0.02 Mb   |
utf8_general_ci |
| faq_state| MyISAM | 3 | 0.01 Mb   |
utf8_general_ci |
| faq_state_type   | MyISAM | 3 | 0.01 Mb   |
utf8_general_ci |
| faq_voting   | MyISAM | 0 | 0.00 Mb   |
utf8_general_ci |
| follow_up_possible   | MyISAM | 3 | 0.01 Mb   |
utf8_general_ci |
| generic_agent_jobs   | MyISAM | 0 | 0.00 Mb   |
utf8_general_ci |
| groups   | MyISAM | 9 | 0.01 Mb   |
utf8_general_ci |
| group_customer_user  | MyISAM | 0 | 0.00 Mb   |
utf8_general_ci |
| group_role   | MyISAM | 18| 0.01 Mb   |
utf8_general_ci |
| group_user   | MyISAM | 1 | 0.00 Mb   |
utf8_general_ci |
| link_object  | MyISAM | 2 | 0.00 Mb   |
utf8_general_ci |
| link_relation| MyISAM | 7 | 0.01 Mb   |
utf8_general_ci |
| link_state   | MyISAM | 2 | 0.01 Mb   |
utf8_general_ci |
| link_type| MyISAM | 2 | 0.01 Mb   |
utf8_general_ci |
| mail_account | MyISAM | 3 | 0.01 Mb   |
utf8_general_ci |
| notifications| MyISAM | 20| 0.01 Mb   |
utf8_general_ci |
| notification_event   | MyISAM | 2 | 0.01 Mb   |
utf8_general_ci |
| notification_event_item  | MyISAM | 12| 0.01 Mb   |
utf8_general_ci |
| package_repository   | MyISAM | 5 | 8.44 Mb   |
utf8_general_ci |
| personal_queues  | MyISAM | 4 | 0.00 Mb   |
utf8_general_ci |
| postmaster_filter| MyISAM | 14| 0.01 Mb   |
utf8_general_ci |
| process_id   | MyISAM | 0 | 0.00 Mb   |
utf8_general_ci |
| queue| MyISAM | 8 | 0.02 Mb   |
utf8_general_ci |
| queue_auto_response  | MyISAM | 4 | 0.01 Mb   |
utf8_general_ci |
| queue_preferences| MyISAM | 0 | 0.00 Mb   |
utf8_general_ci |
| queue_standard_response  | MyISAM | 5 | 0.01 Mb   |
utf8_general_ci |
| roles| MyISAM | 6 | 0.01 Mb   |
utf8_general_ci |
| role_user| MyISAM | 6 | 0.01 Mb   |
utf8_general_ci |
| salutation   | MyISAM | 1 | 0.01 Mb   |
utf8_general_ci |
| search_profile   | MyISAM | 26| 0.01 Mb   |
utf8_general_ci |
| service  | MyISAM | 0 | 0.00 Mb   |
utf8_general_ci |
| service_customer_user| MyISAM | 0 | 0.00 Mb   |
utf8_general_ci |
| service_preferences  | MyISAM | 0 | 0.00 Mb   |
utf8_general_ci |
| service_sla  | MyISAM | 0 | 0.00 Mb   |
utf8_general_ci |
| sessions | MyISAM | 0 | 0.01 Mb   |
utf8_general_ci |
| signature| MyISAM | 1 | 0.01 Mb   |
utf8_general_ci |
| sla  | MyISAM | 0 | 0.00 Mb   |
utf8_general_ci |
| sla_preferences  | MyISAM | 0 | 0.00 Mb   |
utf8_general_ci |
| standard_attachment  | MyISAM | 0 | 0.00 Mb   |

Re: [otrs] upgrade from 3.0.11 to 3.1.2 error on: scripts/DBUpdate-to-3.1.mysql.sql

[Michiel Beijen]

Hi Steven,

We do not use a specific engine. This means that we'll use whatever
engine your MySQL uses as default. For instance on Windows the default
engine is InnoDB, and I guess more and more InnoDB is becoming the
default storage engine for MySQL.

So I guess you simply set up MySQL with MyISAM as a storage engine,
then installed OTRS, then the MySQL default storage engine switched to
InnoDB beause of an OS or MySQL upgrade, then you upgraded OTRS and
now you'll have tables with different storage engines in one database.

So I'll understand your issue but you should probably complain with
your OS vendor, and not with OTRS.

As for the foreign keys: MyISAM does not USE foreign keys but you can
specify one. It will just not be enforced. This to support people like
us who have ONE create table statement for MySQL regardless of the
storage engine. Ref:
http://dev.mysql.com/doc/refman/5.1/en/ansi-diff-foreign-keys.html

The error message you have is that the table
smime_signer_cert_relations is already there, and the upgrade script
tries to create it a second time and then fails. This table is added
in OTRS 3.1, and you should really only have that after you ran the
update script DBUpdate-to-3.1.mysql.sql -- my idea is you simply
tried to run this script two times.

If you can reproduce this error, obviously I would be interested to
know how you got this.

-
Mike

On Wed, Mar 7, 2012 at 15:11, Steven Carr sjc...@gmail.com wrote:
 My OTRS install (3.0.11) seems to have a mix of MyISAM/InnoDB - would be
 nice if developers stuck to one engine, and if they are going to change to
 use relationship features in InnoDB, then change all tables.

 Steve

 +--++---+---+-+
 | Table Name   | Engine | Rows  | Size  |
 Collation   |
 +--++---+---+-+
 | article  | MyISAM | 1593  | 129.74 Mb |
 utf8_general_ci |
 | article_attachment   | MyISAM | 0 | 0.00 Mb   |
 utf8_general_ci |
 | article_flag | MyISAM | 1467  | 0.13 Mb   |
 utf8_general_ci |
 | article_plain    | MyISAM | 0 | 0.00 Mb   |
 utf8_general_ci |
 | article_search   | MyISAM | 0 | 0.00 Mb   |
 utf8_general_ci |
 | article_sender_type  | MyISAM | 3 | 0.01 Mb   |
 utf8_general_ci |
 | article_type | MyISAM | 11    | 0.01 Mb   |
 utf8_general_ci |
 | auto_response    | MyISAM | 4 | 0.02 Mb   |
 utf8_general_ci |
 | auto_response_type   | MyISAM | 5 | 0.01 Mb   |
 utf8_general_ci |
 | customer_company | MyISAM | 3 | 0.01 Mb   |
 utf8_general_ci |
 | customer_preferences | MyISAM | 30    | 0.01 Mb   |
 utf8_general_ci |
 | customer_user    | MyISAM | 4 | 0.01 Mb   |
 utf8_general_ci |
 | faq_attachment   | MyISAM | 1 | 0.05 Mb   |
 utf8_general_ci |
 | faq_category | MyISAM | 2 | 0.00 Mb   |
 utf8_general_ci |
 | faq_category_group   | MyISAM | 4 | 0.00 Mb   |
 utf8_general_ci |
 | faq_history  | MyISAM | 19    | 0.00 Mb   |
 utf8_general_ci |
 | faq_item | MyISAM | 4 | 0.01 Mb   |
 utf8_general_ci |
 | faq_language | MyISAM | 2 | 0.01 Mb   |
 utf8_general_ci |
 | faq_log  | MyISAM | 94    | 0.02 Mb   |
 utf8_general_ci |
 | faq_state    | MyISAM | 3 | 0.01 Mb   |
 utf8_general_ci |
 | faq_state_type   | MyISAM | 3 | 0.01 Mb   |
 utf8_general_ci |
 | faq_voting   | MyISAM | 0 | 0.00 Mb   |
 utf8_general_ci |
 | follow_up_possible   | MyISAM | 3 | 0.01 Mb   |
 utf8_general_ci |
 | generic_agent_jobs   | MyISAM | 0 | 0.00 Mb   |
 utf8_general_ci |
 | groups   | MyISAM | 9 | 0.01 Mb   |
 utf8_general_ci |
 | group_customer_user  | MyISAM | 0 | 0.00 Mb   |
 utf8_general_ci |
 | group_role   | MyISAM | 18    | 0.01 Mb   |
 utf8_general_ci |
 | group_user   | MyISAM | 1 | 0.00 Mb   |
 utf8_general_ci |
 | link_object  | MyISAM | 2 | 0.00 Mb   |
 utf8_general_ci |
 | link_relation    | MyISAM | 7 | 0.01 Mb   |
 utf8_general_ci |
 | link_state   | MyISAM | 2 | 0.01 Mb   |
 utf8_general_ci |
 | link_type    | MyISAM | 2 | 0.01 Mb   |
 utf8_general_ci |
 | mail_account | MyISAM | 3 | 0.01 Mb   |
 utf8_general_ci |
 | notifications    | MyISAM | 20    | 0.01 Mb   |
 utf8_general_ci |
 | notification_event   | MyISAM | 2 | 0.01 Mb   |
 utf8_general_ci |
 | notification_event_item  | MyISAM | 12    | 0.01 Mb   |
 utf8_general_ci |
 | package_repository   | MyISAM | 5 | 8.44 Mb   |
 utf8_general_ci |
 | personal_queues  | MyISAM | 4

Re: [otrs] upgrade from 3.0.11 to 3.1.2 error on: scripts/DBUpdate-to-3.1.mysql.sql

[Ugo Bellavance]

On 2012-03-07 12:21, Michiel Beijen wrote:

Hi Steven,

We do not use a specific engine. This means that we'll use whatever
engine your MySQL uses as default. For instance on Windows the default
engine is InnoDB, and I guess more and more InnoDB is becoming the
default storage engine for MySQL.

So I guess you simply set up MySQL with MyISAM as a storage engine,
then installed OTRS, then the MySQL default storage engine switched to
InnoDB beause of an OS or MySQL upgrade, then you upgraded OTRS and
now you'll have tables with different storage engines in one database.

So I'll understand your issue but you should probably complain with
your OS vendor, and not with OTRS.

As for the foreign keys: MyISAM does not USE foreign keys but you can
specify one. It will just not be enforced. This to support people like
us who have ONE create table statement for MySQL regardless of the
storage engine. Ref:
http://dev.mysql.com/doc/refman/5.1/en/ansi-diff-foreign-keys.html

The error message you have is that the table
smime_signer_cert_relations is already there, and the upgrade script
tries to create it a second time and then fails. This table is added
in OTRS 3.1, and you should really only have that after you ran the
update script DBUpdate-to-3.1.mysql.sql -- my idea is you simply
tried to run this script two times.

If you can reproduce this error, obviously I would be interested to
know how you got this.


I'll definitely try to reproduce the issue I got.

Thanks,

Ugo

-
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

Re: [otrs] upgrade from 3.0.11 to 3.1.2 error on: scripts/DBUpdate-to-3.1.mysql.sql

[Michiel Beijen]

Nils told me how to reproduce:

The problem was, one of our devs added the smime_signer_cert tables to
2.4 after we already released 2.4.11, then rolled it back because it
should not be added on a patch level release. He failed to roll back
the database upgrade files however.. We created 2.4.12 which contained
these new database files, and now there is an issue if you do the
upgrade from 2.3  2.4  3.0  3.1.

I rolled back his changes. If you'll use the database upgrade files from
http://source.otrs.org/viewvc.cgi/otrs/scripts/?hideattic=1sortby=datepathrev=rel-2_4
you would be good.

I vcreated a bug report for it:
http://bugs.otrs.org/show_bug.cgi?id=8300 - Database upgrade issue
when upgrading from 2.3  2.4  3.0  3.1: table
smime_signer_cert_relations' already exists.

thanks!
-- 
Mike

On Thu, Mar 8, 2012 at 03:04, Ugo Bellavance u...@lubik.ca wrote:
 On 2012-03-07 12:21, Michiel Beijen wrote:

 Hi Steven,

 We do not use a specific engine. This means that we'll use whatever
 engine your MySQL uses as default. For instance on Windows the default
 engine is InnoDB, and I guess more and more InnoDB is becoming the
 default storage engine for MySQL.

 So I guess you simply set up MySQL with MyISAM as a storage engine,
 then installed OTRS, then the MySQL default storage engine switched to
 InnoDB beause of an OS or MySQL upgrade, then you upgraded OTRS and
 now you'll have tables with different storage engines in one database.

 So I'll understand your issue but you should probably complain with
 your OS vendor, and not with OTRS.

 As for the foreign keys: MyISAM does not USE foreign keys but you can
 specify one. It will just not be enforced. This to support people like
 us who have ONE create table statement for MySQL regardless of the
 storage engine. Ref:
 http://dev.mysql.com/doc/refman/5.1/en/ansi-diff-foreign-keys.html

 The error message you have is that the table
 smime_signer_cert_relations is already there, and the upgrade script
 tries to create it a second time and then fails. This table is added
 in OTRS 3.1, and you should really only have that after you ran the
 update script DBUpdate-to-3.1.mysql.sql -- my idea is you simply
 tried to run this script two times.

 If you can reproduce this error, obviously I would be interested to
 know how you got this.


 I'll definitely try to reproduce the issue I got.

 Thanks,

 Ugo


 -
 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
-
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

Re: [otrs] Upgrade from 3.0.11 to 3.1.1

[James Michael DuPont]

HI,
I have done a test upgrade myself following the instructions in the source
code UPGRADING, I did not have a problem but also did not test all the
functionality.
I would suggest to try this on a copy of the database, just in case.

thanks,
mike

On Wed, Feb 15, 2012 at 1:51 PM, Erik van Ast erik.van@suzohapp.nlwrote:

 Hi everyone,

 ** **

 We have been using OTRS for a couple of years now and we are currently
 using 3.0.11 as the newest version. OTRS 3.1.1 is now available however and
 I wanted to know if there are any special things I have to think of before
 upgrading? We are using OpenSUSE 11.2 as an OS, but I’m not an expert in
 Linux so I wanted to double-check before upgrading.

 I have upgraded the 3.0.X versions every time by running the following
 commands:

 ** **

 rpm –Uvh otrs-3.0.11*

 otrs.RebuildConfig.pl

 otrs.DeleteCache.pl

 apache2 restart

 ** **

 Can I use the same commands (otrs-3.1* instead of otrs-3.0.11* in the
 first line) for this upgrade from 3.0.11 to 3.1.1?

 Kind regards,
 Erik van Ast

 ** **

 Please visit our new ecommerce website http://eu.suzohapp.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




-- 
James Michael DuPont
Custom Engineering/Research  Development

OTRS AG
Norsk-Data-Straße 1
D-61352 Bad Homburg

T: +49 (0) 9421 56818 0
F: +49 (0) 9421 56818 18
I: http://www.otrs.com/

Geschäftssitz: Bad Homburg, Amtsgericht Bad Homburg, HRB 10751, USt-Nr.:
DE256610065
Aufsichtsratsvorsitzender: Burchard Steinbild, Vorstand: André Mindermann
(Vorsitzender), Christopher Kuhn
-
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

Re: [otrs] Upgrade from 3.0.11 to 3.1.1

[Edlhuber Florian]

Hi Erik

Your steps are correct (it's the absolute minimum), but I think you should go 
trough it step by step as described here
http://doc.otrs.org/3.1/en/html/upgrading.html

(stop services, start upgrade, start services, tests)

I recommend a fullbackup of your system before upgrading, better clone it 
first, test your upgrade
and then start your upgrade

Regards
Florian

Von: otrs-boun...@otrs.org [mailto:otrs-boun...@otrs.org] Im Auftrag von Erik 
van Ast
Gesendet: Mittwoch, 15. Februar 2012 13:51
An: otrs@otrs.org
Betreff: [otrs] Upgrade from 3.0.11 to 3.1.1

Hi everyone,

We have been using OTRS for a couple of years now and we are currently using 
3.0.11 as the newest version. OTRS 3.1.1 is now available however and I wanted 
to know if there are any special things I have to think of before upgrading? We 
are using OpenSUSE 11.2 as an OS, but I'm not an expert in Linux so I wanted to 
double-check before upgrading.
I have upgraded the 3.0.X versions every time by running the following commands:

rpm -Uvh otrs-3.0.11*
otrs.RebuildConfig.pl
otrs.DeleteCache.pl
apache2 restart

Can I use the same commands (otrs-3.1* instead of otrs-3.0.11* in the first 
line) for this upgrade from 3.0.11 to 3.1.1?
Kind regards,
Erik van Ast

Please visit our new ecommerce website http://eu.suzohapp.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

Re: [otrs] upgrade to otrs 3.0.9

[Edlhuber Florian]

Hi,

I had the same Problem updating to an 3.0.x version. I had the effect, that 
some .pm files were not updated correctly.

you can check the files for example Kernel/Modules/AgentTicketCompose.pm and 
check, if the version
is the correct one.

My correct files (3.0.x versions)  were named 
AgentTicketCompose.pm.custom_backup with an custom_backup at the end.

I renamed the old AgentTicketCompose.pm in AgentTicketCompose.pm-old-version
And the AgentTicketCompose.pm.custom_backup in AgentTicketCompose.pm and 
everything works fine
(remember to delete Browser Cache if necessary)

HTH

Regards
Florian

Von: otrs-boun...@otrs.org [mailto:otrs-boun...@otrs.org] Im Auftrag von Andrew 
Meyer
Gesendet: Mittwoch, 17. August 2011 04:30
An: otrs@otrs.org
Betreff: [otrs] upgrade to otrs 3.0.9

I just upgraded to Fedora 15 and OTRS 3.0.9 now when I got to reply to ticket, 
the message body disappears... this is on all browsers.  When I go to add 
another empty response, the body of it is gone as well.


Any ideas?


Andrew Meyer
ame...@precisionpractice.com
Unix Systems Administrator
Precision Practice Management
689 Craig Rd.
Saint Louis, MO 63141
314-787-0681 (Main Line)
314-881-5265 (Direct)
314-881-5365 (Fax)
314-565-0868 (cell)

After Hours Emergency  314-576-9146

-
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

Re: [otrs] Upgrade from 2.2.x to 3.0.8

[Michiel Beijen]

Hi Arnold,

If upgrading from 2.2 or earlier you'll have to take an extra step,
see http://bugs.otrs.org/show_bug.cgi?id=6798

(it's referred to in UPGRADING:
http://source.otrs.org/viewvc.cgi/otrs/UPGRADING?revision=1.49.2.3view=co)

--
Michiel


On Tue, Jun 21, 2011 at 15:35,  arn...@ligtvoet.org wrote:
 Hi,

 I'm currently upgrading a system from 2.2.7 to 3.0.8. When I run the mysql
 upgrade scripts automatically not all commands are executed, but if I run
 the commands manually then the database seems to update fine. The perl
 update scripts however generate a lot of errors (unknow column
 st.archive_flag and 'need id or name'). This is the upgrade from 2.2 to 2.3
 running the DBUpdate-to-3.0.pl script.

 It seems the errors are related to the otrs/Kernel/System/Ticket.pm and
 DB.pm. These are of course version 3.0.8 already as I installed 3.0.8 on the
 new server. Should these files also be 2.3 or can I ignore the errors?

 In other words: when I upgrade the db over multiple versions do I also need
 to install the complete otrs versions or will running the upgrade scripts
 from the newest version work as well? It's a 14Gb database, so near
 impossible to manually check if all upgrades succeeded.

 Regards,
 Arnold.
 -
 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

-
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

Re: [otrs] Upgrade from 2.2.x to 3.0.8

[Arnold Ligtvoet]

Hi Michiel,

thanks! It looks like this problem only exists in the 2.2 - 2.3 upgrade 
when using a 3.0 OTRS. The problem I'm having is that I am on Windows (I 
know don't get me started).


I'm guessing that unzipping the tarball and using the Kernel directory 
should work as well.


Thanks,
Arnold.

Op 21-6-2011 16:17, Michiel Beijen schreef:

Hi Arnold,

If upgrading from 2.2 or earlier you'll have to take an extra step,
see http://bugs.otrs.org/show_bug.cgi?id=6798

(it's referred to in UPGRADING:
http://source.otrs.org/viewvc.cgi/otrs/UPGRADING?revision=1.49.2.3view=co)

--
Michiel


On Tue, Jun 21, 2011 at 15:35,arn...@ligtvoet.org  wrote:

Hi,

I'm currently upgrading a system from 2.2.7 to 3.0.8. When I run the mysql
upgrade scripts automatically not all commands are executed, but if I run
the commands manually then the database seems to update fine. The perl
update scripts however generate a lot of errors (unknow column
st.archive_flag and 'need id or name'). This is the upgrade from 2.2 to 2.3
running the DBUpdate-to-3.0.pl script.

It seems the errors are related to the otrs/Kernel/System/Ticket.pm and
DB.pm. These are of course version 3.0.8 already as I installed 3.0.8 on the
new server. Should these files also be 2.3 or can I ignore the errors?

In other words: when I upgrade the db over multiple versions do I also need
to install the complete otrs versions or will running the upgrade scripts
from the newest version work as well? It's a 14Gb database, so near
impossible to manually check if all upgrades succeeded.

Regards,
Arnold.
-
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


-
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


-
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

Re: [otrs] Upgrade 2.4.7 questions

[Jan.Dreyer]

Hi,

the UPGRADING file on 2.4.x (I only looked on 2.4.9) does contain this
passage though:
---8 ---
These instructions are for people upgrading OTRS from 2.3 to 2.4.
---8 ---

So there are no recommended steps for doing a patch upgrade, as the OP has
already mentioned.

Gruß
Jan Dreyer


-Original Message-
From: otrs-boun...@otrs.org [mailto:otrs-boun...@otrs.org] On Behalf Of
Michiel Beijen
Sent: Wednesday, May 11, 2011 9:53 PM
To: User questions and discussions about OTRS.
Subject: Re: [otrs] Upgrade 2.4.7 questions

On Wed, May 11, 2011 at 10:37 AM, Nils Leideck nils.leid...@leidex.net
wrote:
 Basically these are just patches and therefor just file replacements.
 But anyway, you should read the UPGRADING and CHANGES carefully before
 upgrading to the next version.

So actually, the UPGRADING file on the 2.4 platform does not specify
that you can skip the database upgrade section when installing a patch
level upgrade. From 3.0 on the UPGRADING now indicates which steps you
should skip when performing a patch level upgrade.
--
Mike.
-
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


smime.p7s
Description: S/MIME cryptographic signature
-
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

Re: [otrs] Upgrade 2.4.7 questions

[Andy Wodfer]

Thanks for all emails!

I wish there were packages of changed files only... Seems to be a lot of
work to restore config files and permissions after overwriting when going
from source.tar.gz.

Anyone know which files I need to restore from my backup after 2.4.10 is
uploaded?

Cheers,
Andy

On Thu, May 12, 2011 at 9:48 AM, jan.dre...@bertelsmann.de wrote:

 Hi,

 the UPGRADING file on 2.4.x (I only looked on 2.4.9) does contain this
 passage though:
 ---8 ---
 These instructions are for people upgrading OTRS from 2.3 to 2.4.
 ---8 ---

 So there are no recommended steps for doing a patch upgrade, as the OP
 has
 already mentioned.

 Gruß
 Jan Dreyer


 -Original Message-
 From: otrs-boun...@otrs.org [mailto:otrs-boun...@otrs.org] On Behalf Of
 Michiel Beijen
 Sent: Wednesday, May 11, 2011 9:53 PM
 To: User questions and discussions about OTRS.
 Subject: Re: [otrs] Upgrade 2.4.7 questions

 On Wed, May 11, 2011 at 10:37 AM, Nils Leideck nils.leid...@leidex.net
 wrote:
  Basically these are just patches and therefor just file replacements.
  But anyway, you should read the UPGRADING and CHANGES carefully before
  upgrading to the next version.

 So actually, the UPGRADING file on the 2.4 platform does not specify
 that you can skip the database upgrade section when installing a patch
 level upgrade. From 3.0 on the UPGRADING now indicates which steps you
 should skip when performing a patch level upgrade.
 --
 Mike.
 -
 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

 -
 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

-
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

Re: [otrs] Upgrade 2.4.7 questions

[Nils Leideck]

On 12.05.2011, at 13:28, Andy Wodfer wrote:

 I wish there were packages of changed files only... Seems to be a lot of work 
 to restore config files and permissions after overwriting when going from 
 source.tar.gz.


https://otrsteam.ideascale.com/a/dtd/Schedules-patches-for-installation/100568-10369

Cheers, Nils

-- 
Nils Leideck
http://webint.cryptonode.de / a Fractal project

-
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

Re: [otrs] Upgrade 2.4.7 questions

[Olivier Sallou]

 Kernel/Config.pm, Kernel/Config/GenericAgent.pm,
Kernel/Config/Files/ZZZAuto.pm

those files should not be overwritten, by default a file xxx.pm.dist is
installed, so your files are not impacted.
You should however make a diff between files to detect new attributes
etc


Olivier

Le 5/12/11 1:28 PM, Andy Wodfer a écrit :
 Thanks for all emails!

 I wish there were packages of changed files only... Seems to be a lot of
 work to restore config files and permissions after overwriting when going
 from source.tar.gz.

 Anyone know which files I need to restore from my backup after 2.4.10 is
 uploaded?

 Cheers,
 Andy

 On Thu, May 12, 2011 at 9:48 AM, jan.dre...@bertelsmann.de wrote:

 Hi,

 the UPGRADING file on 2.4.x (I only looked on 2.4.9) does contain this
 passage though:
 ---8 ---
 These instructions are for people upgrading OTRS from 2.3 to 2.4.
 ---8 ---

 So there are no recommended steps for doing a patch upgrade, as the OP
 has
 already mentioned.

 Gruß
 Jan Dreyer


 -Original Message-
 From: otrs-boun...@otrs.org [mailto:otrs-boun...@otrs.org] On Behalf Of
 Michiel Beijen
 Sent: Wednesday, May 11, 2011 9:53 PM
 To: User questions and discussions about OTRS.
 Subject: Re: [otrs] Upgrade 2.4.7 questions

 On Wed, May 11, 2011 at 10:37 AM, Nils Leideck nils.leid...@leidex.net
 wrote:
 Basically these are just patches and therefor just file replacements.
 But anyway, you should read the UPGRADING and CHANGES carefully before
 upgrading to the next version.
 So actually, the UPGRADING file on the 2.4 platform does not specify
 that you can skip the database upgrade section when installing a patch
 level upgrade. From 3.0 on the UPGRADING now indicates which steps you
 should skip when performing a patch level upgrade.
 --
 Mike.
 -
 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

 -
 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



 -
 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

-- 
gpg key id: 4096R/326D8438  (pgp.mit.edu)
Key fingerprint = 5FB4 6F83 D3B9 5204 6335  D26D 78DC 68DB 326D 8438


-
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

Re: [otrs] Upgrade 2.4.7 questions

[Nils Leideck]

On 11.05.2011, at 09:48, Andy Wodfer wrote:

 1. How do we upgrade? Just overwrite files?
 2. Can we go from 2.4.7 directly to .10 or do we have to follow the numbers?
 
 Any other useful tips are very much appreciated.
 Btw. Our OTRS system runs on a FreeBSD 8 server.


Basically these are just patches and therefor just file replacements.
But anyway, you should read the UPGRADING and CHANGES carefully before 
upgrading to the next version.

And yes, you can go to 2.4.10 directly.

Cheers, Nils

-- 
Nils Leideck
http://webint.cryptonode.de / a Fractal project

-
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

Re: [otrs] Upgrade 2.4.7 questions

[Olivier Sallou]

Usually, upgrading to last version for minor upgrades is ok.

You should really care for major version upgrades  ( 2.4.x - 2.4.y is ok).


Olivier

Le 5/11/11 9:48 AM, Andy Wodfer a écrit :
 Hi,
 We're still running OTRS 2.4.7 and I thought it was about time to upgrade to
 2.4.10. (I'm currently testing OTRS 3 on a test server, but we're not ready
 to make the move yet).

 So, I can't find any instructions on how to upgrade 2.4.7 to .8 .9 and .10
 in the documentation.

 My questions are:

 1. How do we upgrade? Just overwrite files?
 2. Can we go from 2.4.7 directly to .10 or do we have to follow the numbers?

 Any other useful tips are very much appreciated.

 Btw. Our OTRS system runs on a FreeBSD 8 server.

 Thanks!
 Andy



 -
 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

-- 
gpg key id: 4096R/326D8438  (pgp.mit.edu)
Key fingerprint = 5FB4 6F83 D3B9 5204 6335  D26D 78DC 68DB 326D 8438


-
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

Re: [otrs] Upgrade issues

[Lars Jørgensen]

Hi Steve,

otrs.RebuildTicketIndex.pl fixed the problem, thanks. I don't know if I missed 
that step in the UPGRADING file, or if it's not mentioned there. 

Just checked - it's not mentioned. Someone should fix.


Lars

-Original Message-
From: otrs-boun...@otrs.org [mailto:otrs-boun...@otrs.org] On Behalf Of Steve 
Durbin
Sent: Tuesday, January 25, 2011 4:50 PM
To: otrs@otrs.org
Subject: Re: [otrs] Upgrade issues

Lars and others,

Freetext search and ticket number search work fine here following upgrade on 
our test system, for all tickets before and after. However, I did run

bin/otrs.RebuildTicketIndex.pl

Following upgrade - have you tried that?

I also did OPTIMIZE TABLE on each table, but I doubt that would have affected 
anything.

Cheers,
--
Steve Durbin
Group Manager: Applications Delivery/Cyfarwyddwr Grŵp: Trosglwyddo Rhaglenni
Bridgend County Borough Council/Cyngor Bwrdeistref Sirol Pen-y-Bont ar Ogwr
Tel/Rhif ffon: 01656 642113
Mob/ffon symudol: 07976 271559
Fax/Ffacs: 01656 642125
Web/We: http://www.bridgend.gov.uk

-
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

Re: [otrs] Upgrade issues

[Lars Jørgensen]

Just did a quick check, and yes I have the problem too. I can't freetext search 
for tickets created before the upgrade.

From: otrs-boun...@otrs.org [mailto:otrs-boun...@otrs.org] On Behalf Of Hugh 
Kelley
Sent: Monday, January 24, 2011 10:51 PM
To: User questions and discussions about OTRS.
Subject: Re: [otrs] Upgrade issues

I have been running some version of OTRS 3 from beta up until 3.0.3.   I'm not 
sure when this search (for ticket number) stopped working, but I have the same 
experience as Gazizov.

For what it's worth, we've been using the Static DB all along.

Hugh
On Mon, Jan 24, 2011 at 10:32 AM, Gazizov Andrey 
moonshi...@retn.netmailto:moonshi...@retn.net wrote:
Hi Lars,

I run that script. Without any results unfortunately :-(


Gazizov Andrey wrote:
Hello to all,

After upgrade to 3 version of OTRS I faced with strange problem - can not found 
any ticket by ticket number using standard search feature. All tickets that 
created in 2nd OTRS version affected. Tickets that has been created in 3rd 
version are searchable. Does anybody know what is this and how I can solve this 
problem?

Thanks in advance.

--
Best regards,
Andrey Gazizov
RETN
-
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

-
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

Re: [otrs] Upgrade issues

[Gazizov Andrey]

Hi!

As for my experience - I can search tickets by freetext field, but 
searching tickets by they number give me no results. Very strange...


Lars J?rgensen wrote:
Just did a quick check, and yes I have the problem too. I can't freetext 
search for tickets created before the upgrade.


 

*From:* otrs-boun...@otrs.org [mailto:otrs-boun...@otrs.org] *On Behalf 
Of *Hugh Kelley

*Sent:* Monday, January 24, 2011 10:51 PM
*To:* User questions and discussions about OTRS.
*Subject:* Re: [otrs] Upgrade issues

 

I have been running some version of OTRS 3 from beta up until 3.0.3.   
I'm not sure when this search (for ticket number) stopped working, but I 
have the same experience as Gazizov.


For what it's worth, we've been using the Static DB all along.

Hugh

On Mon, Jan 24, 2011 at 10:32 AM, Gazizov Andrey moonshi...@retn.net 
mailto:moonshi...@retn.net wrote:


Hi Lars,

I run that script. Without any results unfortunately :-(



Gazizov Andrey wrote:

Hello to all,

After upgrade to 3 version of OTRS I faced with strange problem - can 
not found any ticket by ticket number using standard search feature. All 
tickets that created in 2nd OTRS version affected. Tickets that has been 
created in 3rd version are searchable. Does anybody know what is this 
and how I can solve this problem?


Thanks in advance.


--
Best regards,
Andrey Gazizov
RETN
-
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

 





-
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


--
Best regards,
Andrey Gazizov
RETN
-
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

Re: [otrs] Upgrade issues

[Steve Durbin]

Lars and others,

Freetext search and ticket number search work fine here following upgrade on 
our test system, for all tickets before and after. However, I did run

bin/otrs.RebuildTicketIndex.pl

Following upgrade - have you tried that?

I also did OPTIMIZE TABLE on each table, but I doubt that would have affected 
anything.

Cheers,
--
Steve Durbin
Group Manager: Applications Delivery/Cyfarwyddwr Grŵp: Trosglwyddo Rhaglenni
Bridgend County Borough Council/Cyngor Bwrdeistref Sirol Pen-y-Bont ar Ogwr
Tel/Rhif ffon: 01656 642113
Mob/ffon symudol: 07976 271559
Fax/Ffacs: 01656 642125
Web/We: http://www.bridgend.gov.uk

E-mail may be automatically logged, monitored and/or recorded for legal 
purposes.
Please do not print this email unless absolutely necessary.
E-bost yn cael ei logio, ei monitro a/neu ei chofnodi yn awtomatig am resymau 
cyfreithiol
Peidiwch ag argraffu’r neges e-bost hon oni bai fod hynny’n gwbl angenrheidiol.


This e-mail and any attachments transmitted with it represents the
views of the individual(s) who sent them and should not be regarded
as the official view of Bridgend County Borough Council.  The contents
are confidential and intended solely for the use of the addressee.  If
you have received it in error, please inform the system administrator
on (+44) 01656 642111.

This e-mail and any attachments have been scanned with 'MessageLabs SkyScan'  - 
http://www.messagelabs.com/


Mae'r e-bost hwn ac unrhyw atodiadau a drosglwyddir gydag ef yn cynrychioli 
safbwyntiau'r unigolyn a'i anfonodd (unigolion a'u hanfonodd) ac ni ddylid eu 
hystyried fel safbwynt swyddogol Cyngor Bwrdeistref Sirol Pen-y-bont ar Ogwr.  
Mae'r cynnwys yn gyfrinachol ac wedi'i fwriadu ar gyfer y sawl y'i cyfeiriwyd 
ato yn unig.  Os ydych wedi ei dderbyn mewn camgymeriad, rhowch wybod i 
weinyddwr y system ar (+44) 01656 642111.

Mae'r e-bost hwn ac unrhyw atodiadau wedi cael eu sganio gyda 'MessageLabs 
SkyScan'  - http://www.messagelabs.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

Re: [otrs] Upgrade issues

[Hugh Kelley]

I ran the rebuild last night and my searches are back to normal now.  Is
this normally required after a rebuild?

Hugh

On Tue, Jan 25, 2011 at 10:50 AM, Steve Durbin steve.dur...@bridgend.gov.uk
 wrote:

 Lars and others,

 Freetext search and ticket number search work fine here following upgrade
 on our test system, for all tickets before and after. However, I did run

 bin/otrs.RebuildTicketIndex.pl

 Following upgrade - have you tried that?

 I also did OPTIMIZE TABLE on each table, but I doubt that would have
 affected anything.

 Cheers,
 --
 Steve Durbin
 Group Manager: Applications Delivery/Cyfarwyddwr Grŵp: Trosglwyddo
 Rhaglenni
 Bridgend County Borough Council/Cyngor Bwrdeistref Sirol Pen-y-Bont ar Ogwr
 Tel/Rhif ffon: 01656 642113
 Mob/ffon symudol: 07976 271559
 Fax/Ffacs: 01656 642125
 Web/We: http://www.bridgend.gov.uk

 E-mail may be automatically logged, monitored and/or recorded for legal
 purposes.
 Please do not print this email unless absolutely necessary.
 E-bost yn cael ei logio, ei monitro a/neu ei chofnodi yn awtomatig am
 resymau cyfreithiol
 Peidiwch ag argraffu’r neges e-bost hon oni bai fod hynny’n gwbl
 angenrheidiol.

 
 This e-mail and any attachments transmitted with it represents the
 views of the individual(s) who sent them and should not be regarded
 as the official view of Bridgend County Borough Council.  The contents
 are confidential and intended solely for the use of the addressee.  If
 you have received it in error, please inform the system administrator
 on (+44) 01656 642111.

 This e-mail and any attachments have been scanned with 'MessageLabs
 SkyScan'  - http://www.messagelabs.com/

 
 Mae'r e-bost hwn ac unrhyw atodiadau a drosglwyddir gydag ef yn cynrychioli
 safbwyntiau'r unigolyn a'i anfonodd (unigolion a'u hanfonodd) ac ni ddylid
 eu hystyried fel safbwynt swyddogol Cyngor Bwrdeistref Sirol Pen-y-bont ar
 Ogwr.  Mae'r cynnwys yn gyfrinachol ac wedi'i fwriadu ar gyfer y sawl y'i
 cyfeiriwyd ato yn unig.  Os ydych wedi ei dderbyn mewn camgymeriad, rhowch
 wybod i weinyddwr y system ar (+44) 01656 642111.

 Mae'r e-bost hwn ac unrhyw atodiadau wedi cael eu sganio gyda 'MessageLabs
 SkyScan'  - http://www.messagelabs.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

-
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

Re: [otrs] Upgrade issues

[Andrey Gazizov]

Hi Steve,

I done all steps that described in upgrade manual..It is serious problem 
for me, because users can't search tickets that they need and I am 
forced to use MySQL for this...It is very inconvenient and takes a lot 
of time.


25.01.2011 18:50, Steve Durbin пишет:

Lars and others,

Freetext search and ticket number search work fine here following upgrade on 
our test system, for all tickets before and after. However, I did run

bin/otrs.RebuildTicketIndex.pl

Following upgrade - have you tried that?

I also did OPTIMIZE TABLE on each table, but I doubt that would have affected 
anything.

Cheers,
--
Steve Durbin
Group Manager: Applications Delivery/Cyfarwyddwr Grŵp: Trosglwyddo Rhaglenni
Bridgend County Borough Council/Cyngor Bwrdeistref Sirol Pen-y-Bont ar Ogwr
Tel/Rhif ffon: 01656 642113
Mob/ffon symudol: 07976 271559
Fax/Ffacs: 01656 642125
Web/We: http://www.bridgend.gov.uk

E-mail may be automatically logged, monitored and/or recorded for legal 
purposes.
Please do not print this email unless absolutely necessary.
E-bost yn cael ei logio, ei monitro a/neu ei chofnodi yn awtomatig am resymau 
cyfreithiol
Peidiwch ag argraffu’r neges e-bost hon oni bai fod hynny’n gwbl angenrheidiol.


This e-mail and any attachments transmitted with it represents the
views of the individual(s) who sent them and should not be regarded
as the official view of Bridgend County Borough Council.  The contents
are confidential and intended solely for the use of the addressee.  If
you have received it in error, please inform the system administrator
on (+44) 01656 642111.

This e-mail and any attachments have been scanned with 'MessageLabs SkyScan'  - 
http://www.messagelabs.com/


Mae'r e-bost hwn ac unrhyw atodiadau a drosglwyddir gydag ef yn cynrychioli 
safbwyntiau'r unigolyn a'i anfonodd (unigolion a'u hanfonodd) ac ni ddylid eu 
hystyried fel safbwynt swyddogol Cyngor Bwrdeistref Sirol Pen-y-bont ar Ogwr.  
Mae'r cynnwys yn gyfrinachol ac wedi'i fwriadu ar gyfer y sawl y'i cyfeiriwyd 
ato yn unig.  Os ydych wedi ei dderbyn mewn camgymeriad, rhowch wybod i 
weinyddwr y system ar (+44) 01656 642111.

Mae'r e-bost hwn ac unrhyw atodiadau wedi cael eu sganio gyda 'MessageLabs 
SkyScan'  - http://www.messagelabs.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


-
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

Re: [otrs] Upgrade issues

[Lars Jørgensen]

Hi Gazizov,

If you're using fulltext search, it sounds like you have switched from runtime 
to static. Try running bin/otrs.RebuildFulltextIndex.pl


Lars

-Original Message-
From: otrs-boun...@otrs.org [mailto:otrs-boun...@otrs.org] On Behalf Of Gazizov 
Andrey
Sent: Monday, January 24, 2011 1:35 PM
To: User questions and discussions about OTRS.
Subject: [otrs] Upgrade issues

Hello to all,

After upgrade to 3 version of OTRS I faced with strange problem - can 
not found any ticket by ticket number using standard search feature. All 
tickets that created in 2nd OTRS version affected. Tickets that has been 
created in 3rd version are searchable. Does anybody know what is this 
and how I can solve this problem?

Thanks in advance.
-- 
Best regards,
Andrey Gazizov
RETN
-
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
-
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

Re: [otrs] Upgrade issues

[Gazizov Andrey]

Hi Lars,

I run that script. Without any results unfortunately :-(

Gazizov Andrey wrote:

Hello to all,

After upgrade to 3 version of OTRS I faced with strange problem - can 
not found any ticket by ticket number using standard search feature. All 
tickets that created in 2nd OTRS version affected. Tickets that has been 
created in 3rd version are searchable. Does anybody know what is this 
and how I can solve this problem?


Thanks in advance.


--
Best regards,
Andrey Gazizov
RETN
-
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

Re: [otrs] Upgrade issues

[Hugh Kelley]

I have been running some version of OTRS 3 from beta up until 3.0.3.   I'm
not sure when this search (for ticket number) stopped working, but I have
the same experience as Gazizov.

For what it's worth, we've been using the Static DB all along.

Hugh

On Mon, Jan 24, 2011 at 10:32 AM, Gazizov Andrey moonshi...@retn.netwrote:

 Hi Lars,

 I run that script. Without any results unfortunately :-(


 Gazizov Andrey wrote:

 Hello to all,

 After upgrade to 3 version of OTRS I faced with strange problem - can not
 found any ticket by ticket number using standard search feature. All tickets
 that created in 2nd OTRS version affected. Tickets that has been created in
 3rd version are searchable. Does anybody know what is this and how I can
 solve this problem?

 Thanks in advance.


 --
 Best regards,
 Andrey Gazizov
 RETN
 -
 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

-
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

Re: [otrs] upgrade from 2.4.7 to 2.4.9 with ITSM installed

[Steve Clark]

On 10/28/2010 09:52 AM, Steve Clark wrote:

Hello,

anyone tried to upgrade from 2.4.7 to 2.4.9 with ITSM installed.

I got the following:
  1:otrs   warning: 
/opt/otrs/Kernel/Output/HTML/Standard/AgentTicketClose.dtl created as 
/opt/otrs/Kernel/Output/HTML/Standard/AgentTicketClose.dtl.rpmnew
warning: /opt/otrs/Kernel/Output/HTML/Standard/AgentTicketEmail.dtl 
created as 
/opt/otrs/Kernel/Output/HTML/Standard/AgentTicketEmail.dtl.rpmnew
warning: /opt/otrs/Kernel/Output/HTML/Standard/AgentTicketFreeText.dtl 
created as 
/opt/otrs/Kernel/Output/HTML/Standard/AgentTicketFreeText.dtl.rpmnew
warning: /opt/otrs/Kernel/Output/HTML/Standard/AgentTicketNote.dtl 
created as 
/opt/otrs/Kernel/Output/HTML/Standard/AgentTicketNote.dtl.rpmnew
warning: /opt/otrs/Kernel/Output/HTML/Standard/AgentTicketOwner.dtl 
created as 
/opt/otrs/Kernel/Output/HTML/Standard/AgentTicketOwner.dtl.rpmnew
warning: /opt/otrs/Kernel/Output/HTML/Standard/AgentTicketPending.dtl 
created as 
/opt/otrs/Kernel/Output/HTML/Standard/AgentTicketPending.dtl.rpmnew
warning: /opt/otrs/Kernel/Output/HTML/Standard/AgentTicketPriority.dtl 
created as 
/opt/otrs/Kernel/Output/HTML/Standard/AgentTicketPriority.dtl.rpmnew
warning: 
/opt/otrs/Kernel/Output/HTML/Standard/AgentTicketResponsible.dtl 
created as 
/opt/otrs/Kernel/Output/HTML/Standard/AgentTicketResponsible.dtl.rpmnew


In doing a diff between the files it looks like ITSM changed these 
files and now the upgrade didn't work correctly???
I cp the *.dtl.rpmnew to the corresponding .dtl then reinstalled the 
ITSM modules that said needed to be re-installed.

Was this the correct procedure?

Thanks,

--
Stephen Clark
*NetWolves*
Sr. Software Engineer III
Phone: 813-579-3200
Fax: 813-882-0209
Email: steve.cl...@netwolves.com
http://www.netwolves.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

Re: [otrs] upgrade from 2.4.7 to 2.4.9 with ITSM installed

[Marco Vannini]

Hi, this is a rpm's problem deal with
http://www.linux.com/archive/feed/121476, btw yes it should be the right
procedure

(there were some thread some times ago on that, look at
http://www.mail-archive.com/otrs@otrs.org)

On Thu, Oct 28, 2010 at 4:18 PM, Steve Clark scl...@netwolves.com wrote:

  On 10/28/2010 09:52 AM, Steve Clark wrote:

 Hello,

 anyone tried to upgrade from 2.4.7 to 2.4.9 with ITSM installed.

 I got the following:
   1:otrs   warning:
 /opt/otrs/Kernel/Output/HTML/Standard/AgentTicketClose.dtl created as
 /opt/otrs/Kernel/Output/HTML/Standard/AgentTicketClose.dtl.rpmnew
 warning: /opt/otrs/Kernel/Output/HTML/Standard/AgentTicketEmail.dtl created
 as /opt/otrs/Kernel/Output/HTML/Standard/AgentTicketEmail.dtl.rpmnew
 warning: /opt/otrs/Kernel/Output/HTML/Standard/AgentTicketFreeText.dtl
 created as
 /opt/otrs/Kernel/Output/HTML/Standard/AgentTicketFreeText.dtl.rpmnew
 warning: /opt/otrs/Kernel/Output/HTML/Standard/AgentTicketNote.dtl created
 as /opt/otrs/Kernel/Output/HTML/Standard/AgentTicketNote.dtl.rpmnew
 warning: /opt/otrs/Kernel/Output/HTML/Standard/AgentTicketOwner.dtl created
 as /opt/otrs/Kernel/Output/HTML/Standard/AgentTicketOwner.dtl.rpmnew
 warning: /opt/otrs/Kernel/Output/HTML/Standard/AgentTicketPending.dtl
 created as
 /opt/otrs/Kernel/Output/HTML/Standard/AgentTicketPending.dtl.rpmnew
 warning: /opt/otrs/Kernel/Output/HTML/Standard/AgentTicketPriority.dtl
 created as
 /opt/otrs/Kernel/Output/HTML/Standard/AgentTicketPriority.dtl.rpmnew
 warning: /opt/otrs/Kernel/Output/HTML/Standard/AgentTicketResponsible.dtl
 created as
 /opt/otrs/Kernel/Output/HTML/Standard/AgentTicketResponsible.dtl.rpmnew

 In doing a diff between the files it looks like ITSM changed these files
 and now the upgrade didn't work correctly???

 I cp the *.dtl.rpmnew to the corresponding .dtl then reinstalled the ITSM
 modules that said needed to be re-installed.
 Was this the correct procedure?

 Thanks,

 --
 Stephen Clark
 *NetWolves*
 Sr. Software Engineer III
 Phone: 813-579-3200
 Fax: 813-882-0209
 Email: steve.cl...@netwolves.com
 http://www.netwolves.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

-
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

Re: [otrs] upgrade from 2.4.7 to 2.4.9 with ITSM installed

[Michiel Beijen]

Hi Stephen,

These files are modified by installing ITSM; which means they're
different than in the original RPM.
The upgrade worked perfectly!

You copied them back to the original location, then re-installed ITSM
(which in turn overwrites the files); those steps were superfluous.
--
Mike


On Thu, Oct 28, 2010 at 4:18 PM, Steve Clark scl...@netwolves.com wrote:
 On 10/28/2010 09:52 AM, Steve Clark wrote:

 Hello,

 anyone tried to upgrade from 2.4.7 to 2.4.9 with ITSM installed.

 I got the following:
   1:otrs   warning:
 /opt/otrs/Kernel/Output/HTML/Standard/AgentTicketClose.dtl created as
 /opt/otrs/Kernel/Output/HTML/Standard/AgentTicketClose.dtl.rpmnew
 warning: /opt/otrs/Kernel/Output/HTML/Standard/AgentTicketEmail.dtl created
 as /opt/otrs/Kernel/Output/HTML/Standard/AgentTicketEmail.dtl.rpmnew
 warning: /opt/otrs/Kernel/Output/HTML/Standard/AgentTicketFreeText.dtl
 created as
 /opt/otrs/Kernel/Output/HTML/Standard/AgentTicketFreeText.dtl.rpmnew
 warning: /opt/otrs/Kernel/Output/HTML/Standard/AgentTicketNote.dtl created
 as /opt/otrs/Kernel/Output/HTML/Standard/AgentTicketNote.dtl.rpmnew
 warning: /opt/otrs/Kernel/Output/HTML/Standard/AgentTicketOwner.dtl created
 as /opt/otrs/Kernel/Output/HTML/Standard/AgentTicketOwner.dtl.rpmnew
 warning: /opt/otrs/Kernel/Output/HTML/Standard/AgentTicketPending.dtl
 created as
 /opt/otrs/Kernel/Output/HTML/Standard/AgentTicketPending.dtl.rpmnew
 warning: /opt/otrs/Kernel/Output/HTML/Standard/AgentTicketPriority.dtl
 created as
 /opt/otrs/Kernel/Output/HTML/Standard/AgentTicketPriority.dtl.rpmnew
 warning: /opt/otrs/Kernel/Output/HTML/Standard/AgentTicketResponsible.dtl
 created as
 /opt/otrs/Kernel/Output/HTML/Standard/AgentTicketResponsible.dtl.rpmnew

 In doing a diff between the files it looks like ITSM changed these files and
 now the upgrade didn't work correctly???

 I cp the *.dtl.rpmnew to the corresponding .dtl then reinstalled the ITSM
 modules that said needed to be re-installed.
 Was this the correct procedure?

 Thanks,

 --
 Stephen Clark
 NetWolves
 Sr. Software Engineer III
 Phone: 813-579-3200
 Fax: 813-882-0209
 Email: steve.cl...@netwolves.com
 http://www.netwolves.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

-
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

Re: [otrs] upgrade from 2.4.7 to 2.4.9 with ITSM installed

[Steve Clark]

Hmmm

I had messages in the admin-package manager screen that said 3 of the 
ITSM modules

needed to be reinstalled???

Also I am using fedora and centos - could the
/etc/init.d/otrs script be changed to

...

  # --
  # check mysql, mysql init script does not have a status check...
  # --
  if test $OTRS_DB_RUNNING -gt 0; then
echo -n  Checking $OTRS_USED_DB ...
if $OTRS_USED_DB_TEST /dev/null 21; then
  echo  done.
else
  echo  failed.
  echo   -- Please start the database at first! (service 
$OTRS_USED_DB start) --

  exit 1;
fi
  else
  echo  Disabled: $OTRS_USED_DB check!
  fi
...

in the echo -n  Checking ...  line use the variable from
the /etc/sysconfig/otrs file for the database used instead
of hardcoding MySQL.

Steve



On 10/28/2010 10:22 AM, Michiel Beijen wrote:

Hi Stephen,

These files are modified by installing ITSM; which means they're
different than in the original RPM.
The upgrade worked perfectly!

You copied them back to the original location, then re-installed ITSM
(which in turn overwrites the files); those steps were superfluous.
--
Mike


On Thu, Oct 28, 2010 at 4:18 PM, Steve Clarkscl...@netwolves.com  wrote:
   

On 10/28/2010 09:52 AM, Steve Clark wrote:

Hello,

anyone tried to upgrade from 2.4.7 to 2.4.9 with ITSM installed.

I got the following:
   1:otrs   warning:
/opt/otrs/Kernel/Output/HTML/Standard/AgentTicketClose.dtl created as
/opt/otrs/Kernel/Output/HTML/Standard/AgentTicketClose.dtl.rpmnew
warning: /opt/otrs/Kernel/Output/HTML/Standard/AgentTicketEmail.dtl created
as /opt/otrs/Kernel/Output/HTML/Standard/AgentTicketEmail.dtl.rpmnew
warning: /opt/otrs/Kernel/Output/HTML/Standard/AgentTicketFreeText.dtl
created as
/opt/otrs/Kernel/Output/HTML/Standard/AgentTicketFreeText.dtl.rpmnew
warning: /opt/otrs/Kernel/Output/HTML/Standard/AgentTicketNote.dtl created
as /opt/otrs/Kernel/Output/HTML/Standard/AgentTicketNote.dtl.rpmnew
warning: /opt/otrs/Kernel/Output/HTML/Standard/AgentTicketOwner.dtl created
as /opt/otrs/Kernel/Output/HTML/Standard/AgentTicketOwner.dtl.rpmnew
warning: /opt/otrs/Kernel/Output/HTML/Standard/AgentTicketPending.dtl
created as
/opt/otrs/Kernel/Output/HTML/Standard/AgentTicketPending.dtl.rpmnew
warning: /opt/otrs/Kernel/Output/HTML/Standard/AgentTicketPriority.dtl
created as
/opt/otrs/Kernel/Output/HTML/Standard/AgentTicketPriority.dtl.rpmnew
warning: /opt/otrs/Kernel/Output/HTML/Standard/AgentTicketResponsible.dtl
created as
/opt/otrs/Kernel/Output/HTML/Standard/AgentTicketResponsible.dtl.rpmnew

In doing a diff between the files it looks like ITSM changed these files and
now the upgrade didn't work correctly???

I cp the *.dtl.rpmnew to the corresponding .dtl then reinstalled the ITSM
modules that said needed to be re-installed.
Was this the correct procedure?

Thanks,

--
Stephen Clark
NetWolves
Sr. Software Engineer III
Phone: 813-579-3200
Fax: 813-882-0209
Email: steve.cl...@netwolves.com
http://www.netwolves.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

 

-
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

   



--
Stephen Clark
*NetWolves*
Sr. Software Engineer III
Phone: 813-579-3200
Fax: 813-882-0209
Email: steve.cl...@netwolves.com
http://www.netwolves.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

Re: [otrs] upgrade 3.0 notes

[Udo Bretz]

Hi Jason,

the first beta of OTRS::ITSM 3.0 will come out at the end of November,
and the final version in February 2011.

Best regards,
Udo


On 02.08.2010 17:19, Jason B. Loven wrote:
 What is the timeframe for ITSM with OTRS 3.0?
 
  
 
 We have installed the ITSM features on our OTRS but have not
 implemented. Would it be possible to “downgrade” back to OTRS without
 ITSM and then use 3.0 when it’s out of beta?
 
  
 
 Thank you,
 Jason Loven
 Manager - Technical Services
 
 Computer Associates, Inc.
 36 Thurber Blvd, Smithfield RI 02917
 Phone: (401)232-2600, Fax: (401)232-7778
 Email: jlo...@caisoft.com mailto:jlo...@caisoft.com
 Web: http://www.caisoft.com/ blocked::http://www.cainetserv.com/
 
  
 
 *From:* otrs-boun...@otrs.org [mailto:otrs-boun...@otrs.org] *On Behalf
 Of *Martin Edenhofer
 *Sent:* Monday, August 02, 2010 4:26 AM
 *To:* User questions and discussions about OTRS.
 *Subject:* Re: [otrs] upgrade 3.0 notes
 
  
 
 Hi Marco,
 
  
 
 can it be, that you use OTRS 2.4.7 with ITSM?
 
  
 
 ITSM is not ready for OTRS 3.0 at this moment.
 
  
 
  -Martin
 
  
 
 On 02.08.2010, at 10:21, Marco Vannini wrote:
 
 
 
 Hi all,
 
  
 
 Some notes during the update process. In test I'm using a gentoo having
 a production copy of OTRS 2.4.7 (that is on a fedora 11 though).
 
  
 
 preupgrade script:
 
  
 
 cadreghino otrs # cat scripts/DBUpdate-to-3.0.mysql.sql | mysql -p -f -u
 root otrs
 
 Enter password: 
 
 ERROR 1061 (42000) at line 12: Duplicate key name 'ticket_until_time'
 
 ERROR 1050 (42S01) at line 50: Table 'virtual_fs' already exists
 
 ERROR 1050 (42S01) at line 63: Table 'virtual_fs_preferences' already exists
 
 ERROR 1050 (42S01) at line 73: Table 'virtual_fs_db' already exists
 
 ERROR 1101 (42000) at line 343: BLOB/TEXT column 'content_type' can't
 have a default value
 
  
 
 (can be not considered ?) 
 
  
 
 pl command:
 
  
 
 cadreghino otrs # scripts/DBUpdate-to-3.0.pl http://DBUpdate-to-3.0.pl/ 
 
 Start migration of the system...
 
  
 
 Need Ticket::ViewableStateType in Kernel/Config.pm!
 
  
 
  
 
 after a system restart, accessing with a Chrome 6b, I get :
 
  
 
 
 Browser Warning
 
 The browser you are using is too old. OTRS runs with a huge lists of
 browsers, please upgrade to one of these. Please see the documentation
 or ask your admin for further information.
 
  
 
  
 
  
 
 Going on testing with another browser. I'll update this if I'll get
 something else strange. 
 
  
 
  
 
 Ciao ! 
 
  
 
 MV
 
 -
 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
 
 NEW! ENTERPRISE SUBSCRIPTION - Get more information NOW!
 http://www.otrs.com/en/support/enterprise-subscription/
 
  
 
 
 
 -
 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
 
 NEW! ENTERPRISE SUBSCRIPTION - Get more information NOW!
 http://www.otrs.com/en/support/enterprise-subscription/

-
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

NEW! ENTERPRISE SUBSCRIPTION - Get more information NOW!
http://www.otrs.com/en/support/enterprise-subscription/

Re: [otrs] upgrade 3.0 notes

[Martin Edenhofer]

Hi Marco,

can it be, that you use OTRS 2.4.7 with ITSM?

ITSM is not ready for OTRS 3.0 at this moment.

 -Martin

On 02.08.2010, at 10:21, Marco Vannini wrote:

 Hi all,
 
 Some notes during the update process. In test I'm using a gentoo having a 
 production copy of OTRS 2.4.7 (that is on a fedora 11 though).
 
 preupgrade script:
 
 cadreghino otrs # cat scripts/DBUpdate-to-3.0.mysql.sql | mysql -p -f -u root 
 otrs
 Enter password: 
 ERROR 1061 (42000) at line 12: Duplicate key name 'ticket_until_time'
 ERROR 1050 (42S01) at line 50: Table 'virtual_fs' already exists
 ERROR 1050 (42S01) at line 63: Table 'virtual_fs_preferences' already exists
 ERROR 1050 (42S01) at line 73: Table 'virtual_fs_db' already exists
 ERROR 1101 (42000) at line 343: BLOB/TEXT column 'content_type' can't have a 
 default value
 
 (can be not considered ?) 
 
 pl command:
 
 cadreghino otrs # scripts/DBUpdate-to-3.0.pl 
 Start migration of the system...
 
 Need Ticket::ViewableStateType in Kernel/Config.pm!
 
 
 after a system restart, accessing with a Chrome 6b, I get :
 
 Browser Warning
 
 The browser you are using is too old. OTRS runs with a huge lists of 
 browsers, please upgrade to one of these. Please see the documentation or ask 
 your admin for further information.
 
 
 
 
 Going on testing with another browser. I'll update this if I'll get something 
 else strange. 
 
 
 Ciao ! 
 
 MV
 -
 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
 
 NEW! ENTERPRISE SUBSCRIPTION - Get more information NOW!
 http://www.otrs.com/en/support/enterprise-subscription/

-
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

NEW! ENTERPRISE SUBSCRIPTION - Get more information NOW!
http://www.otrs.com/en/support/enterprise-subscription/

Re: [otrs] upgrade 3.0 notes

[Marco Vannini]

Sure... :( sorry. I've read it too...

So... coming back to test 3.0 upgrade on a clean 2.4.7 installation ...

Thank you !

MV

On Mon, Aug 2, 2010 at 10:25 AM, Martin Edenhofer mar...@otrs.org wrote:

 Hi Marco,

 can it be, that you use OTRS 2.4.7 with ITSM?

 ITSM is not ready for OTRS 3.0 at this moment.

  -Martin

 On 02.08.2010, at 10:21, Marco Vannini wrote:

 Hi all,

 Some notes during the update process. In test I'm using a gentoo having a
 production copy of OTRS 2.4.7 (that is on a fedora 11 though).

 preupgrade script:

 cadreghino otrs # cat scripts/DBUpdate-to-3.0.mysql.sql | mysql -p -f -u
 root otrs
 Enter password:
 ERROR 1061 (42000) at line 12: Duplicate key name 'ticket_until_time'
 ERROR 1050 (42S01) at line 50: Table 'virtual_fs' already exists
 ERROR 1050 (42S01) at line 63: Table 'virtual_fs_preferences' already
 exists
 ERROR 1050 (42S01) at line 73: Table 'virtual_fs_db' already exists
 ERROR 1101 (42000) at line 343: BLOB/TEXT column 'content_type' can't have
 a default value

 (can be not considered ?)

 pl command:

 cadreghino otrs # scripts/DBUpdate-to-3.0.pl
 Start migration of the system...

 Need Ticket::ViewableStateType in Kernel/Config.pm!


 after a system restart, accessing with a Chrome 6b, I get :

 Browser Warning

 The browser you are using is too old. OTRS runs with a huge lists of
 browsers, please upgrade to one of these. Please see the documentation or
 ask your admin for further information.



 Going on testing with another browser. I'll update this if I'll get
 something else strange.


 Ciao !

 MV
 -
 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

 NEW! ENTERPRISE SUBSCRIPTION - Get more information NOW!
 http://www.otrs.com/en/support/enterprise-subscription/



 -
 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

 NEW! ENTERPRISE SUBSCRIPTION - Get more information NOW!
 http://www.otrs.com/en/support/enterprise-subscription/

-
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

NEW! ENTERPRISE SUBSCRIPTION - Get more information NOW!
http://www.otrs.com/en/support/enterprise-subscription/

Re: [otrs] upgrade 3.0 notes

[Marco Vannini]

browser issue was solved running a right otrs.SetPermission.pl ( variou
Permission Denied errors in apache logs)

MV

On Mon, Aug 2, 2010 at 10:30 AM, Marco Vannini marco.vann...@gmail.comwrote:

 Sure... :( sorry. I've read it too...

 So... coming back to test 3.0 upgrade on a clean 2.4.7 installation ...

 Thank you !

 MV


 On Mon, Aug 2, 2010 at 10:25 AM, Martin Edenhofer mar...@otrs.org wrote:

 Hi Marco,

 can it be, that you use OTRS 2.4.7 with ITSM?

 ITSM is not ready for OTRS 3.0 at this moment.

  -Martin

 On 02.08.2010, at 10:21, Marco Vannini wrote:

 Hi all,

 Some notes during the update process. In test I'm using a gentoo having a
 production copy of OTRS 2.4.7 (that is on a fedora 11 though).

 preupgrade script:

 cadreghino otrs # cat scripts/DBUpdate-to-3.0.mysql.sql | mysql -p -f -u
 root otrs
 Enter password:
 ERROR 1061 (42000) at line 12: Duplicate key name 'ticket_until_time'
 ERROR 1050 (42S01) at line 50: Table 'virtual_fs' already exists
 ERROR 1050 (42S01) at line 63: Table 'virtual_fs_preferences' already
 exists
 ERROR 1050 (42S01) at line 73: Table 'virtual_fs_db' already exists
 ERROR 1101 (42000) at line 343: BLOB/TEXT column 'content_type' can't have
 a default value

 (can be not considered ?)

 pl command:

 cadreghino otrs # scripts/DBUpdate-to-3.0.pl
 Start migration of the system...

 Need Ticket::ViewableStateType in Kernel/Config.pm!


 after a system restart, accessing with a Chrome 6b, I get :

 Browser Warning

 The browser you are using is too old. OTRS runs with a huge lists of
 browsers, please upgrade to one of these. Please see the documentation or
 ask your admin for further information.



 Going on testing with another browser. I'll update this if I'll get
 something else strange.


 Ciao !

 MV
 -
 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

 NEW! ENTERPRISE SUBSCRIPTION - Get more information NOW!
 http://www.otrs.com/en/support/enterprise-subscription/



 -
 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

 NEW! ENTERPRISE SUBSCRIPTION - Get more information NOW!
 http://www.otrs.com/en/support/enterprise-subscription/



-
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

NEW! ENTERPRISE SUBSCRIPTION - Get more information NOW!
http://www.otrs.com/en/support/enterprise-subscription/

Re: [otrs] upgrade 3.0 notes

[Jason B. Loven]

What is the timeframe for ITSM with OTRS 3.0?

We have installed the ITSM features on our OTRS but have not implemented. Would 
it be possible to downgrade back to OTRS without ITSM and then use 3.0 when 
it's out of beta?

Thank you,
Jason Loven
Manager - Technical Services
Computer Associates, Inc.
36 Thurber Blvd, Smithfield RI 02917
Phone: (401)232-2600, Fax: (401)232-7778
Email: jlo...@caisoft.commailto:jlo...@caisoft.com
Web: http://www.caisoft.com/blocked::http://www.cainetserv.com/

From: otrs-boun...@otrs.org [mailto:otrs-boun...@otrs.org] On Behalf Of Martin 
Edenhofer
Sent: Monday, August 02, 2010 4:26 AM
To: User questions and discussions about OTRS.
Subject: Re: [otrs] upgrade 3.0 notes

Hi Marco,

can it be, that you use OTRS 2.4.7 with ITSM?

ITSM is not ready for OTRS 3.0 at this moment.

 -Martin

On 02.08.2010, at 10:21, Marco Vannini wrote:


Hi all,

Some notes during the update process. In test I'm using a gentoo having a 
production copy of OTRS 2.4.7 (that is on a fedora 11 though).

preupgrade script:

cadreghino otrs # cat scripts/DBUpdate-to-3.0.mysql.sql | mysql -p -f -u root 
otrs
Enter password:
ERROR 1061 (42000) at line 12: Duplicate key name 'ticket_until_time'
ERROR 1050 (42S01) at line 50: Table 'virtual_fs' already exists
ERROR 1050 (42S01) at line 63: Table 'virtual_fs_preferences' already exists
ERROR 1050 (42S01) at line 73: Table 'virtual_fs_db' already exists
ERROR 1101 (42000) at line 343: BLOB/TEXT column 'content_type' can't have a 
default value

(can be not considered ?)

pl command:

cadreghino otrs # scripts/DBUpdate-to-3.0.plhttp://DBUpdate-to-3.0.pl/
Start migration of the system...

Need Ticket::ViewableStateType in Kernel/Config.pm!


after a system restart, accessing with a Chrome 6b, I get :

Browser Warning

The browser you are using is too old. OTRS runs with a huge lists of browsers, 
please upgrade to one of these. Please see the documentation or ask your admin 
for further information.



Going on testing with another browser. I'll update this if I'll get something 
else strange.


Ciao !

MV
-
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

NEW! ENTERPRISE SUBSCRIPTION - Get more information NOW!
http://www.otrs.com/en/support/enterprise-subscription/

-
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

NEW! ENTERPRISE SUBSCRIPTION - Get more information NOW!
http://www.otrs.com/en/support/enterprise-subscription/

Re: [otrs] upgrade issues from 2.2.x to 2.4.x

[Isaac Gonzalez]

For anyone that cared, I resolved this by changing all of the tables
needing the foreign key mapping to innodb. All new tables are config'd
for innodb storage and the references table below were myisam(left over
from old install). Thus the script created new innodb tables and
couldn't create foreign keys to myisam tablesthey need to be the
same...

 

Up and running with otrs 2.3.5 for a couple of daysthen plan to go
to 2.4.7yay yay!!!

 

From: otrs-boun...@otrs.org [mailto:otrs-boun...@otrs.org] On Behalf Of
Isaac Gonzalez
Sent: Sunday, July 11, 2010 12:45 AM
To: User questions and discussions about OTRS.
Subject: Re: [otrs] upgrade issues from 2.2.x to 2.4.x

 

After a bit more investigation here are the real errors from sql...


---

Upgrading from 2.2.x to 2.4.x(cent os 5, mysql 4.1.18)

 

I ran into some errors during the db upgrade for mysql for 2.2 to 2.3

The first error was on line 4 for the statement

 

ALTER TABLE sla DROP FOREIGN KEY FK_sla_service_id_id;

There is no foreign key in that table in my 2.2.4 install!

Gave the error of rename of dbname\sla to #sql2-25000-b

 

 

And then every alter statement below that tried to add a constraint also
gave back an error cannot create table \dbname\#sql - 2500_b.frm

All of the below really give the error:

100711  0:16:57 Error in foreign key constraint of table
otrsnew/#sql-19a8_39:

 FOREIGN KEY (ticket_id) REFERENCES ticket (id):

Cannot resolve table name close to:

 (id)

And similar for each Reference the foreign key is trying to make via
each statement

ALTER TABLE ticket_watcher ADD CONSTRAINT FK_ticket_watcher_ticket_id_id
FOREIGN KEY (ticket_id) REFERENCES ticket (id);

ALTER TABLE ticket_watcher ADD CONSTRAINT FK_ticket_watcher_user_id_id
FOREIGN KEY (user_id) REFERENCES users (id);

ALTER TABLE ticket_watcher ADD CONSTRAINT FK_ticket_watcher_create_by_id
FOREIGN KEY (create_by) REFERENCES users (id);

ALTER TABLE ticket_watcher ADD CONSTRAINT FK_ticket_watcher_change_by_id
FOREIGN KEY (change_by) REFERENCES users (id);

ALTER TABLE queue_preferences ADD CONSTRAINT
FK_queue_preferences_queue_id_id FOREIGN KEY (queue_id) REFERENCES queue
(id);

ALTER TABLE service_sla ADD CONSTRAINT FK_service_sla_service_id_id
FOREIGN KEY (service_id) REFERENCES service (id);

ALTER TABLE service_sla ADD CONSTRAINT FK_service_sla_sla_id_id FOREIGN
KEY (sla_id) REFERENCES sla (id);

ALTER TABLE link_type ADD CONSTRAINT FK_link_type_create_by_id FOREIGN
KEY (create_by) REFERENCES users (id);

ALTER TABLE link_type ADD CONSTRAINT FK_link_type_change_by_id FOREIGN
KEY (change_by) REFERENCES users (id);

ALTER TABLE link_type ADD CONSTRAINT FK_link_type_valid_id_id FOREIGN
KEY (valid_id) REFERENCES valid (id);

ALTER TABLE link_state ADD CONSTRAINT FK_link_state_create_by_id FOREIGN
KEY (create_by) REFERENCES users (id);

ALTER TABLE link_state ADD CONSTRAINT FK_link_state_change_by_id FOREIGN
KEY (change_by) REFERENCES users (id);

ALTER TABLE link_state ADD CONSTRAINT FK_link_state_valid_id_id FOREIGN
KEY (valid_id) REFERENCES valid (id);

ALTER TABLE link_relation ADD CONSTRAINT
FK_link_relation_source_object_id_id FOREIGN KEY (source_object_id)
REFERENCES link_object (id);

ALTER TABLE link_relation ADD CONSTRAINT
FK_link_relation_target_object_id_id FOREIGN KEY (target_object_id)
REFERENCES link_object (id);

ALTER TABLE link_relation ADD CONSTRAINT FK_link_relation_state_id_id
FOREIGN KEY (state_id) REFERENCES link_state (id);

ALTER TABLE link_relation ADD CONSTRAINT FK_link_relation_type_id_id
FOREIGN KEY (type_id) REFERENCES link_type (id);

ALTER TABLE link_relation ADD CONSTRAINT FK_link_relation_create_by_id
FOREIGN KEY (create_by) REFERENCES users (id);

ALTER TABLE article_search ADD CONSTRAINT
FK_article_search_article_sender_type_id_id FOREIGN KEY
(article_sender_type_id) REFERENCES article_sender_type (id);

ALTER TABLE article_search ADD CONSTRAINT
FK_article_search_article_type_id_id FOREIGN KEY (article_type_id)
REFERENCES article_type (id);

ALTER TABLE article_search ADD CONSTRAINT FK_article_search_ticket_id_id
FOREIGN KEY (ticket_id) REFERENCES ticket (id);

-
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

NEW! ENTERPRISE SUBSCRIPTION - Get more information NOW!
http://www.otrs.com/en/support/enterprise-subscription/

Re: [otrs] upgrade issues from 2.2.x to 2.4.x

[Isaac Gonzalez]

I think I figured out my problem but am not sure how to solve.

 

All those alter table statements that fail with error besides the first
drop statement that cannot resolve table name, are because the new
tables that the script created that its trying to make a foreign key
restraint are of type innodb. The table that its trying to alter are of
type myisam! Thus it cannot resolve it since the tables are not in
concert.

 

http://forums.mysql.com/read.php?136,159805,214625#msg-214625 

 

I imagine I can change all those tables that its trying to alter to be
of type innodb, but am not sure if this will mess anything up(and my
knowledge of innodb vs myisam is limited)...

 

Can anyone give me some direction here?

 

Thanks,

Isaac

 

From: otrs-boun...@otrs.org [mailto:otrs-boun...@otrs.org] On Behalf Of
Isaac Gonzalez
Sent: Sunday, July 11, 2010 12:45 AM
To: User questions and discussions about OTRS.
Subject: Re: [otrs] upgrade issues from 2.2.x to 2.4.x

 

After a bit more investigation here are the real errors from sql...


---

Upgrading from 2.2.x to 2.4.x(cent os 5, mysql 4.1.18)

 

I ran into some errors during the db upgrade for mysql for 2.2 to 2.3

The first error was on line 4 for the statement

 

ALTER TABLE sla DROP FOREIGN KEY FK_sla_service_id_id;

There is no foreign key in that table in my 2.2.4 install!

Gave the error of rename of dbname\sla to #sql2-25000-b

 

 

And then every alter statement below that tried to add a constraint also
gave back an error cannot create table \dbname\#sql - 2500_b.frm

All of the below really give the error:

100711  0:16:57 Error in foreign key constraint of table
otrsnew/#sql-19a8_39:

 FOREIGN KEY (ticket_id) REFERENCES ticket (id):

Cannot resolve table name close to:

 (id)

And similar for each Reference the foreign key is trying to make via
each statement

ALTER TABLE ticket_watcher ADD CONSTRAINT FK_ticket_watcher_ticket_id_id
FOREIGN KEY (ticket_id) REFERENCES ticket (id);

ALTER TABLE ticket_watcher ADD CONSTRAINT FK_ticket_watcher_user_id_id
FOREIGN KEY (user_id) REFERENCES users (id);

ALTER TABLE ticket_watcher ADD CONSTRAINT FK_ticket_watcher_create_by_id
FOREIGN KEY (create_by) REFERENCES users (id);

ALTER TABLE ticket_watcher ADD CONSTRAINT FK_ticket_watcher_change_by_id
FOREIGN KEY (change_by) REFERENCES users (id);

ALTER TABLE queue_preferences ADD CONSTRAINT
FK_queue_preferences_queue_id_id FOREIGN KEY (queue_id) REFERENCES queue
(id);

ALTER TABLE service_sla ADD CONSTRAINT FK_service_sla_service_id_id
FOREIGN KEY (service_id) REFERENCES service (id);

ALTER TABLE service_sla ADD CONSTRAINT FK_service_sla_sla_id_id FOREIGN
KEY (sla_id) REFERENCES sla (id);

ALTER TABLE link_type ADD CONSTRAINT FK_link_type_create_by_id FOREIGN
KEY (create_by) REFERENCES users (id);

ALTER TABLE link_type ADD CONSTRAINT FK_link_type_change_by_id FOREIGN
KEY (change_by) REFERENCES users (id);

ALTER TABLE link_type ADD CONSTRAINT FK_link_type_valid_id_id FOREIGN
KEY (valid_id) REFERENCES valid (id);

ALTER TABLE link_state ADD CONSTRAINT FK_link_state_create_by_id FOREIGN
KEY (create_by) REFERENCES users (id);

ALTER TABLE link_state ADD CONSTRAINT FK_link_state_change_by_id FOREIGN
KEY (change_by) REFERENCES users (id);

ALTER TABLE link_state ADD CONSTRAINT FK_link_state_valid_id_id FOREIGN
KEY (valid_id) REFERENCES valid (id);

ALTER TABLE link_relation ADD CONSTRAINT
FK_link_relation_source_object_id_id FOREIGN KEY (source_object_id)
REFERENCES link_object (id);

ALTER TABLE link_relation ADD CONSTRAINT
FK_link_relation_target_object_id_id FOREIGN KEY (target_object_id)
REFERENCES link_object (id);

ALTER TABLE link_relation ADD CONSTRAINT FK_link_relation_state_id_id
FOREIGN KEY (state_id) REFERENCES link_state (id);

ALTER TABLE link_relation ADD CONSTRAINT FK_link_relation_type_id_id
FOREIGN KEY (type_id) REFERENCES link_type (id);

ALTER TABLE link_relation ADD CONSTRAINT FK_link_relation_create_by_id
FOREIGN KEY (create_by) REFERENCES users (id);

ALTER TABLE article_search ADD CONSTRAINT
FK_article_search_article_sender_type_id_id FOREIGN KEY
(article_sender_type_id) REFERENCES article_sender_type (id);

ALTER TABLE article_search ADD CONSTRAINT
FK_article_search_article_type_id_id FOREIGN KEY (article_type_id)
REFERENCES article_type (id);

ALTER TABLE article_search ADD CONSTRAINT FK_article_search_ticket_id_id
FOREIGN KEY (ticket_id) REFERENCES ticket (id);

-
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

NEW! ENTERPRISE SUBSCRIPTION - Get more information NOW!
http://www.otrs.com/en/support/enterprise-subscription/

Re: [otrs] upgrade issues from 2.2.x to 2.4.x

[Isaac Gonzalez]

After a bit more investigation here are the real errors from sql...


---

Upgrading from 2.2.x to 2.4.x(cent os 5, mysql 4.1.18)

 

I ran into some errors during the db upgrade for mysql for 2.2 to 2.3

The first error was on line 4 for the statement

 

ALTER TABLE sla DROP FOREIGN KEY FK_sla_service_id_id;

There is no foreign key in that table in my 2.2.4 install!

Gave the error of rename of dbname\sla to #sql2-25000-b

 

 

And then every alter statement below that tried to add a constraint also
gave back an error cannot create table \dbname\#sql - 2500_b.frm

All of the below really give the error:

100711  0:16:57 Error in foreign key constraint of table
otrsnew/#sql-19a8_39:

 FOREIGN KEY (ticket_id) REFERENCES ticket (id):

Cannot resolve table name close to:

 (id)

And similar for each Reference the foreign key is trying to make via
each statement

ALTER TABLE ticket_watcher ADD CONSTRAINT FK_ticket_watcher_ticket_id_id
FOREIGN KEY (ticket_id) REFERENCES ticket (id);

ALTER TABLE ticket_watcher ADD CONSTRAINT FK_ticket_watcher_user_id_id
FOREIGN KEY (user_id) REFERENCES users (id);

ALTER TABLE ticket_watcher ADD CONSTRAINT FK_ticket_watcher_create_by_id
FOREIGN KEY (create_by) REFERENCES users (id);

ALTER TABLE ticket_watcher ADD CONSTRAINT FK_ticket_watcher_change_by_id
FOREIGN KEY (change_by) REFERENCES users (id);

ALTER TABLE queue_preferences ADD CONSTRAINT
FK_queue_preferences_queue_id_id FOREIGN KEY (queue_id) REFERENCES queue
(id);

ALTER TABLE service_sla ADD CONSTRAINT FK_service_sla_service_id_id
FOREIGN KEY (service_id) REFERENCES service (id);

ALTER TABLE service_sla ADD CONSTRAINT FK_service_sla_sla_id_id FOREIGN
KEY (sla_id) REFERENCES sla (id);

ALTER TABLE link_type ADD CONSTRAINT FK_link_type_create_by_id FOREIGN
KEY (create_by) REFERENCES users (id);

ALTER TABLE link_type ADD CONSTRAINT FK_link_type_change_by_id FOREIGN
KEY (change_by) REFERENCES users (id);

ALTER TABLE link_type ADD CONSTRAINT FK_link_type_valid_id_id FOREIGN
KEY (valid_id) REFERENCES valid (id);

ALTER TABLE link_state ADD CONSTRAINT FK_link_state_create_by_id FOREIGN
KEY (create_by) REFERENCES users (id);

ALTER TABLE link_state ADD CONSTRAINT FK_link_state_change_by_id FOREIGN
KEY (change_by) REFERENCES users (id);

ALTER TABLE link_state ADD CONSTRAINT FK_link_state_valid_id_id FOREIGN
KEY (valid_id) REFERENCES valid (id);

ALTER TABLE link_relation ADD CONSTRAINT
FK_link_relation_source_object_id_id FOREIGN KEY (source_object_id)
REFERENCES link_object (id);

ALTER TABLE link_relation ADD CONSTRAINT
FK_link_relation_target_object_id_id FOREIGN KEY (target_object_id)
REFERENCES link_object (id);

ALTER TABLE link_relation ADD CONSTRAINT FK_link_relation_state_id_id
FOREIGN KEY (state_id) REFERENCES link_state (id);

ALTER TABLE link_relation ADD CONSTRAINT FK_link_relation_type_id_id
FOREIGN KEY (type_id) REFERENCES link_type (id);

ALTER TABLE link_relation ADD CONSTRAINT FK_link_relation_create_by_id
FOREIGN KEY (create_by) REFERENCES users (id);

ALTER TABLE article_search ADD CONSTRAINT
FK_article_search_article_sender_type_id_id FOREIGN KEY
(article_sender_type_id) REFERENCES article_sender_type (id);

ALTER TABLE article_search ADD CONSTRAINT
FK_article_search_article_type_id_id FOREIGN KEY (article_type_id)
REFERENCES article_type (id);

ALTER TABLE article_search ADD CONSTRAINT FK_article_search_ticket_id_id
FOREIGN KEY (ticket_id) REFERENCES ticket (id);

-
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

NEW! ENTERPRISE SUBSCRIPTION - Get more information NOW!
http://www.otrs.com/en/support/enterprise-subscription/

Re: [otrs] upgrade issues from 2.2.x to 2.4.x

[Manuel Fernández Panzuela]

How are you trying upgrade, are you following any reference?

Un saludo

Manuel Fernández Panzuela
www.mfernandez.es

2010/7/10 Isaac Gonzalez igonza...@autoreturn.com

  Upgrading from 2.2.x to 2.4.x(cent os 5, mysql 4.1.18)



 I ran into some errors during the db upgrade for mysql for 2.2 to 2.3

 The first error was on line 4 for the statement



 ALTER TABLE sla DROP FOREIGN KEY FK_sla_service_id_id;



 Gave the “error of rename of dbname\sla to #sql2-25000-b”





 And then every alter statement below that tried to add a constraint also
 gave back an error cannot create table \dbname\#sql – 2500_b.frm….can I
 just safely ignore this?...i have rolled everything back to how it was with
 2.2, but would love to complete the upgrade process….





 ALTER TABLE ticket_watcher ADD CONSTRAINT FK_ticket_watcher_ticket_id_id
 FOREIGN KEY (ticket_id) REFERENCES ticket (id);

 ALTER TABLE ticket_watcher ADD CONSTRAINT FK_ticket_watcher_user_id_id
 FOREIGN KEY (user_id) REFERENCES users (id);

 ALTER TABLE ticket_watcher ADD CONSTRAINT FK_ticket_watcher_create_by_id
 FOREIGN KEY (create_by) REFERENCES users (id);

 ALTER TABLE ticket_watcher ADD CONSTRAINT FK_ticket_watcher_change_by_id
 FOREIGN KEY (change_by) REFERENCES users (id);

 ALTER TABLE queue_preferences ADD CONSTRAINT
 FK_queue_preferences_queue_id_id FOREIGN KEY (queue_id) REFERENCES queue
 (id);

 ALTER TABLE service_sla ADD CONSTRAINT FK_service_sla_service_id_id FOREIGN
 KEY (service_id) REFERENCES service (id);

 ALTER TABLE service_sla ADD CONSTRAINT FK_service_sla_sla_id_id FOREIGN KEY
 (sla_id) REFERENCES sla (id);

 ALTER TABLE link_type ADD CONSTRAINT FK_link_type_create_by_id FOREIGN KEY
 (create_by) REFERENCES users (id);

 ALTER TABLE link_type ADD CONSTRAINT FK_link_type_change_by_id FOREIGN KEY
 (change_by) REFERENCES users (id);

 ALTER TABLE link_type ADD CONSTRAINT FK_link_type_valid_id_id FOREIGN KEY
 (valid_id) REFERENCES valid (id);

 ALTER TABLE link_state ADD CONSTRAINT FK_link_state_create_by_id FOREIGN
 KEY (create_by) REFERENCES users (id);

 ALTER TABLE link_state ADD CONSTRAINT FK_link_state_change_by_id FOREIGN
 KEY (change_by) REFERENCES users (id);

 ALTER TABLE link_state ADD CONSTRAINT FK_link_state_valid_id_id FOREIGN KEY
 (valid_id) REFERENCES valid (id);

 ALTER TABLE link_relation ADD CONSTRAINT
 FK_link_relation_source_object_id_id FOREIGN KEY (source_object_id)
 REFERENCES link_object (id);

 ALTER TABLE link_relation ADD CONSTRAINT
 FK_link_relation_target_object_id_id FOREIGN KEY (target_object_id)
 REFERENCES link_object (id);

 ALTER TABLE link_relation ADD CONSTRAINT FK_link_relation_state_id_id
 FOREIGN KEY (state_id) REFERENCES link_state (id);

 ALTER TABLE link_relation ADD CONSTRAINT FK_link_relation_type_id_id
 FOREIGN KEY (type_id) REFERENCES link_type (id);

 ALTER TABLE link_relation ADD CONSTRAINT FK_link_relation_create_by_id
 FOREIGN KEY (create_by) REFERENCES users (id);

 ALTER TABLE article_search ADD CONSTRAINT
 FK_article_search_article_sender_type_id_id FOREIGN KEY
 (article_sender_type_id) REFERENCES article_sender_type (id);

 ALTER TABLE article_search ADD CONSTRAINT
 FK_article_search_article_type_id_id FOREIGN KEY (article_type_id)
 REFERENCES article_type (id);

 ALTER TABLE article_search ADD CONSTRAINT FK_article_search_ticket_id_id
 FOREIGN KEY (ticket_id) REFERENCES ticket (id);

 -
 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

 NEW! ENTERPRISE SUBSCRIPTION - Get more information NOW!
 http://www.otrs.com/en/support/enterprise-subscription/

-
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

NEW! ENTERPRISE SUBSCRIPTION - Get more information NOW!
http://www.otrs.com/en/support/enterprise-subscription/

Re: [otrs] upgrade issues from 2.2.x to 2.4.x

[Isaac Gonzalez]

I'm following the upgrade guide from the source tar.I get the errors
running the first DB 2.3 MySQL script

Manuel Fernández Panzuela manuelfernandezpanzu...@gmail.com wrote:

How are you trying upgrade, are you following any reference?

Un saludo

Manuel Fernández Panzuela
www.mfernandez.es

2010/7/10 Isaac Gonzalez igonza...@autoreturn.com

  Upgrading from 2.2.x to 2.4.x(cent os 5, mysql 4.1.18)



 I ran into some errors during the db upgrade for mysql for 2.2 to 2.3

 The first error was on line 4 for the statement



 ALTER TABLE sla DROP FOREIGN KEY FK_sla_service_id_id;



 Gave the “error of rename of dbname\sla to #sql2-25000-b”





 And then every alter statement below that tried to add a constraint also
 gave back an error cannot create table \dbname\#sql – 2500_b.frm….can I
 just safely ignore this?...i have rolled everything back to how it was
with
 2.2, but would love to complete the upgrade process….





 ALTER TABLE ticket_watcher ADD CONSTRAINT FK_ticket_watcher_ticket_id_id
 FOREIGN KEY (ticket_id) REFERENCES ticket (id);

 ALTER TABLE ticket_watcher ADD CONSTRAINT FK_ticket_watcher_user_id_id
 FOREIGN KEY (user_id) REFERENCES users (id);

 ALTER TABLE ticket_watcher ADD CONSTRAINT FK_ticket_watcher_create_by_id
 FOREIGN KEY (create_by) REFERENCES users (id);

 ALTER TABLE ticket_watcher ADD CONSTRAINT FK_ticket_watcher_change_by_id
 FOREIGN KEY (change_by) REFERENCES users (id);

 ALTER TABLE queue_preferences ADD CONSTRAINT
 FK_queue_preferences_queue_id_id FOREIGN KEY (queue_id) REFERENCES queue
 (id);

 ALTER TABLE service_sla ADD CONSTRAINT FK_service_sla_service_id_id
FOREIGN
 KEY (service_id) REFERENCES service (id);

 ALTER TABLE service_sla ADD CONSTRAINT FK_service_sla_sla_id_id FOREIGN
KEY
 (sla_id) REFERENCES sla (id);

 ALTER TABLE link_type ADD CONSTRAINT FK_link_type_create_by_id FOREIGN
KEY
 (create_by) REFERENCES users (id);

 ALTER TABLE link_type ADD CONSTRAINT FK_link_type_change_by_id FOREIGN
KEY
 (change_by) REFERENCES users (id);

 ALTER TABLE link_type ADD CONSTRAINT FK_link_type_valid_id_id FOREIGN
KEY
 (valid_id) REFERENCES valid (id);

 ALTER TABLE link_state ADD CONSTRAINT FK_link_state_create_by_id FOREIGN
 KEY (create_by) REFERENCES users (id);

 ALTER TABLE link_state ADD CONSTRAINT FK_link_state_change_by_id FOREIGN
 KEY (change_by) REFERENCES users (id);

 ALTER TABLE link_state ADD CONSTRAINT FK_link_state_valid_id_id FOREIGN
KEY
 (valid_id) REFERENCES valid (id);

 ALTER TABLE link_relation ADD CONSTRAINT
 FK_link_relation_source_object_id_id FOREIGN KEY (source_object_id)
 REFERENCES link_object (id);

 ALTER TABLE link_relation ADD CONSTRAINT
 FK_link_relation_target_object_id_id FOREIGN KEY (target_object_id)
 REFERENCES link_object (id);

 ALTER TABLE link_relation ADD CONSTRAINT FK_link_relation_state_id_id
 FOREIGN KEY (state_id) REFERENCES link_state (id);

 ALTER TABLE link_relation ADD CONSTRAINT FK_link_relation_type_id_id
 FOREIGN KEY (type_id) REFERENCES link_type (id);

 ALTER TABLE link_relation ADD CONSTRAINT FK_link_relation_create_by_id
 FOREIGN KEY (create_by) REFERENCES users (id);

 ALTER TABLE article_search ADD CONSTRAINT
 FK_article_search_article_sender_type_id_id FOREIGN KEY
 (article_sender_type_id) REFERENCES article_sender_type (id);

 ALTER TABLE article_search ADD CONSTRAINT
 FK_article_search_article_type_id_id FOREIGN KEY (article_type_id)
 REFERENCES article_type (id);

 ALTER TABLE article_search ADD CONSTRAINT FK_article_search_ticket_id_id
 FOREIGN KEY (ticket_id) REFERENCES ticket (id);

 -
 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

 NEW! ENTERPRISE SUBSCRIPTION - Get more information NOW!
 http://www.otrs.com/en/support/enterprise-subscription/


-
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

NEW! ENTERPRISE SUBSCRIPTION - Get more information NOW!
http://www.otrs.com/en/support/enterprise-subscription/

Re: [otrs] upgrade issues from 2.2.x to 2.4.x

[Manuel Fernández Panzuela]

Which is your inicial version before upgrade process ?
If you are working with 2.2.7 version before upgrade to 2.3.1 version you
need upgrade to 2.2.8, 2.2.9 and finally version 2.3.1

Are you doing it ?

Un saludo

Manuel Fernández Panzuela
www.mfernandez.es
-
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

NEW! ENTERPRISE SUBSCRIPTION - Get more information NOW!
http://www.otrs.com/en/support/enterprise-subscription/

Re: [otrs] upgrade issues from 2.2.x to 2.4.x

[Isaac Gonzalez]

Initial version is 2.2.4

Manuel Fernández Panzuela manuelfernandezpanzu...@gmail.com wrote:

Which is your inicial version before upgrade process ?
If you are working with 2.2.7 version before upgrade to 2.3.1 version you
need upgrade to 2.2.8, 2.2.9 and finally version 2.3.1

Are you doing it ?

Un saludo

Manuel Fernández Panzuela
www.mfernandez.es

-
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

NEW! ENTERPRISE SUBSCRIPTION - Get more information NOW!
http://www.otrs.com/en/support/enterprise-subscription/

Re: [otrs] upgrade issues from 2.2.x to 2.4.x

[Manuel Fernández Panzuela]

Then you must upgrade your Revision, and after that you can upgrade your
version.
did you tried it ?

Un saludo

Manuel Fernández Panzuela
www.mfernandez.es

2010/7/10 Isaac Gonzalez igonza...@autoreturn.com

 Initial version is 2.2.4

 Manuel Fernández Panzuela manuelfernandezpanzu...@gmail.com wrote:

 Which is your inicial version before upgrade process ?
 If you are working with 2.2.7 version before upgrade to 2.3.1 version you
 need upgrade to 2.2.8, 2.2.9 and finally version 2.3.1

 Are you doing it ?

 Un saludo

 Manuel Fernández Panzuela
 www.mfernandez.es


 -
 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

 NEW! ENTERPRISE SUBSCRIPTION - Get more information NOW!
 http://www.otrs.com/en/support/enterprise-subscription/

-
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

NEW! ENTERPRISE SUBSCRIPTION - Get more information NOW!
http://www.otrs.com/en/support/enterprise-subscription/

Re: [otrs] upgrade issues from 2.2.x to 2.4.x

[Isaac Gonzalez]

 
Then you must upgrade your Revision, and after that you can upgrade your 
version.
did you tried it ?

I don't think you are understanding the issue i am running into.i'm not 
running into an issue with the rpm per se, I am running into an issue running 
the db update script for 2.3 for mysql. As far as i can tell, there is no db 
upgrade from 2.2.4 to any version of 2.2.x that is higher than 2.2.4. There is 
only db upgrade from  2.2.4 to 2.3 and 2.4.
 
 Directory of C:\Documents and Settings\igonzalez\My 
Documents\Downloads\otrs-2.4.7\otrs-2.4.7\scrip
07/09/2010  01:09 PMDIR  .
07/09/2010  01:09 PMDIR  ..
07/13/2005  04:46 PM16,061 apache-httpd.conf
04/16/2007  05:11 AM   962 apache-httpd.include.conf
08/25/2009  07:45 AM 7,214 apache-perl-startup.pl
11/10/2008  04:08 AM 1,295 apache2-httpd-new.include.conf
04/16/2007  05:11 AM 1,249 apache2-httpd.include.conf
08/25/2009  07:45 AM 7,272 apache2-perl-startup.pl
07/09/2010  01:09 PMDIR  auto_build
01/11/2010  12:25 PM16,435 auto_build.sh
02/26/2009  04:10 AM 4,047 auto_docbuild.sh
04/16/2009  04:20 AM 7,646 backup.pl
07/09/2010  01:09 PMDIR  database
02/26/2009  04:10 AM 9,811 DBUpdate-to-1.0.mysql.sql
02/26/2009  04:10 AM 9,317 DBUpdate-to-1.0.postgresql.sql
02/26/2009  04:10 AM 4,908 DBUpdate-to-1.1.mysql.sql
02/26/2009  04:10 AM 4,838 DBUpdate-to-1.1.postgresql.sql
02/26/2009  04:10 AM17,840 DBUpdate-to-1.2.mysql.sql
02/26/2009  04:10 AM17,608 DBUpdate-to-1.2.postgresql.sql
02/26/2009  04:10 AM 6,599 DBUpdate-to-1.3.mysql.sql
02/26/2009  04:10 AM 6,799 DBUpdate-to-1.3.postgresql.sql
02/26/2009  04:10 AM20,159 DBUpdate-to-2.0.mysql.sql
02/26/2009  04:10 AM20,639 DBUpdate-to-2.0.postgresql.sql
02/26/2009  04:10 AM 5,036 DBUpdate-to-2.1.mysql.sql
02/26/2009  04:10 AM 5,620 DBUpdate-to-2.1.oracle.sql
02/26/2009  04:10 AM 5,490 DBUpdate-to-2.1.postgresql.sql
02/26/2009  04:10 AM   543 DBUpdate-to-2.2.2.sql
07/26/2007  06:01 AM 6,949 DBUpdate-to-2.2.maxdb.sql
07/26/2007  06:01 AM 7,110 DBUpdate-to-2.2.mssql.sql
02/26/2009  04:10 AM 4,858 DBUpdate-to-2.2.mysql.sql
02/26/2009  04:10 AM 5,779 DBUpdate-to-2.2.oracle.sql
02/26/2009  04:10 AM 4,751 DBUpdate-to-2.2.postgresql.sql
05/15/2008  10:35 AM   420 DBUpdate-to-2.3-post.db2.sql
05/15/2008  10:35 AM   379 DBUpdate-to-2.3-post.maxdb.sql
07/21/2008  12:38 AM 1,413 DBUpdate-to-2.3-post.mssql.sql
05/15/2008  10:35 AM   379 DBUpdate-to-2.3-post.mysql.sql
05/15/2008  10:35 AM   435 DBUpdate-to-2.3-post.oracle.sql
05/15/2008  10:35 AM   380 DBUpdate-to-2.3-post.postgresql.sql
07/23/2008  03:54 PM17,076 DBUpdate-to-2.3.db2.sql
07/23/2008  03:54 PM10,905 DBUpdate-to-2.3.maxdb.sql
07/23/2008  03:54 PM15,870 DBUpdate-to-2.3.mssql.sql
07/23/2008  03:54 PM15,824 DBUpdate-to-2.3.mysql.sql
07/23/2008  03:54 PM17,496 DBUpdate-to-2.3.oracle.sql
02/26/2009  04:10 AM22,094 DBUpdate-to-2.3.pl
07/23/2008  03:54 PM16,195 DBUpdate-to-2.3.postgresql.sql
05/15/2009  02:47 AM 1,093 DBUpdate-to-2.4-post.db2.sql
05/15/2009  02:47 AM   977 DBUpdate-to-2.4-post.ingres.sql
05/15/2009  02:47 AM   336 DBUpdate-to-2.4-post.maxdb.sql
05/15/2009  02:47 AM 5,172 DBUpdate-to-2.4-post.mssql.sql
05/15/2009  02:47 AM   889 DBUpdate-to-2.4-post.mysql.sql
05/15/2009  02:47 AM   965 DBUpdate-to-2.4-post.oracle.sql
05/15/2009  02:47 AM   909 DBUpdate-to-2.4-post.postgresql.sql
07/13/2009  05:51 AM 7,656 DBUpdate-to-2.4.db2.sql
07/13/2009  05:51 AM 6,679 DBUpdate-to-2.4.ingres.sql
07/13/2009  05:51 AM 7,462 DBUpdate-to-2.4.mssql.sql
07/13/2009  05:51 AM 7,448 DBUpdate-to-2.4.mysql.sql
07/13/2009  05:51 AM 7,954 DBUpdate-to-2.4.oracle.sql
02/02/2010  09:07 AM 6,968 DBUpdate-to-2.4.pl
07/13/2009  05:51 AM 7,641 DBUpdate-to-2.4.postgresql.sql
 
care to point me to db upgrade for 2.2.7 or 2.2.8 ??
winmail.dat-
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

NEW! ENTERPRISE SUBSCRIPTION - Get more information NOW!
http://www.otrs.com/en/support/enterprise-subscription/

Re: [otrs] upgrade issues from 2.2.x to 2.4.x

[Manuel Fernández Panzuela]

Answering your first question about:

And then every alter statement below that tried to add a constraint also
gave back an error cannot create table \dbname\#sql – 2500_b.frm….can I just
safely ignore this?...i have rolled everything back to how it was with 2.2,
but would love to complete the upgrade process….

You must not ignore errors, because all functionalities could not be
correct.

Un saludo

Manuel Fernández Panzuela
www.mfernandez.es
-
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

NEW! ENTERPRISE SUBSCRIPTION - Get more information NOW!
http://www.otrs.com/en/support/enterprise-subscription/

Re: [otrs] upgrade issues from 2.2.x to 2.4.x

[Isaac Gonzalez]

And then every alter statement below that tried to add a constraint also gave 
back an error cannot create table \dbname\#sql - 2500_b.frmcan I just 
safely ignore this?...i have rolled everything back to how it was with 2.2, 
but would love to complete the upgrade process

You must not ignore errors, because all functionalities could not be correct.
 
ok. So i wonder why i'm getting those errors on the db upgrade 
script..anyone know?
winmail.dat-
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

NEW! ENTERPRISE SUBSCRIPTION - Get more information NOW!
http://www.otrs.com/en/support/enterprise-subscription/

Re: [otrs] upgrade issues from 2.2.x to 2.4.x

[Isaac Gonzalez]

Could this be an issue with mysql 4.1? I tried upgrading mysql from
4.1.18 to 4.1.22 and tried the dbupgrade to 2.3 for otrs and it fails
with the same errors at the exact same lines...either a limitation in
mysql 4.1 or a setting that I don't have enabled. I looked at the
software reqs for otrs 2.4 and it says mysql 4.1 is supported.

Either way I need someone on here like Nils or a db expert to give his
thoughts on thisthanks, Isaac

 


---

Upgrading from 2.2.x to 2.4.x(cent os 5, mysql 4.1.18)

 

I ran into some errors during the db upgrade for mysql for 2.2 to 2.3

The first error was on line 4 for the statement

 

ALTER TABLE sla DROP FOREIGN KEY FK_sla_service_id_id;

 

Gave the error of rename of dbname\sla to #sql2-25000-b

 

 

And then every alter statement below that tried to add a constraint also
gave back an error cannot create table \dbname\#sql - 2500_b.frm

 

 

ALTER TABLE ticket_watcher ADD CONSTRAINT FK_ticket_watcher_ticket_id_id
FOREIGN KEY (ticket_id) REFERENCES ticket (id);

ALTER TABLE ticket_watcher ADD CONSTRAINT FK_ticket_watcher_user_id_id
FOREIGN KEY (user_id) REFERENCES users (id);

ALTER TABLE ticket_watcher ADD CONSTRAINT FK_ticket_watcher_create_by_id
FOREIGN KEY (create_by) REFERENCES users (id);

ALTER TABLE ticket_watcher ADD CONSTRAINT FK_ticket_watcher_change_by_id
FOREIGN KEY (change_by) REFERENCES users (id);

ALTER TABLE queue_preferences ADD CONSTRAINT
FK_queue_preferences_queue_id_id FOREIGN KEY (queue_id) REFERENCES queue
(id);

ALTER TABLE service_sla ADD CONSTRAINT FK_service_sla_service_id_id
FOREIGN KEY (service_id) REFERENCES service (id);

ALTER TABLE service_sla ADD CONSTRAINT FK_service_sla_sla_id_id FOREIGN
KEY (sla_id) REFERENCES sla (id);

ALTER TABLE link_type ADD CONSTRAINT FK_link_type_create_by_id FOREIGN
KEY (create_by) REFERENCES users (id);

ALTER TABLE link_type ADD CONSTRAINT FK_link_type_change_by_id FOREIGN
KEY (change_by) REFERENCES users (id);

ALTER TABLE link_type ADD CONSTRAINT FK_link_type_valid_id_id FOREIGN
KEY (valid_id) REFERENCES valid (id);

ALTER TABLE link_state ADD CONSTRAINT FK_link_state_create_by_id FOREIGN
KEY (create_by) REFERENCES users (id);

ALTER TABLE link_state ADD CONSTRAINT FK_link_state_change_by_id FOREIGN
KEY (change_by) REFERENCES users (id);

ALTER TABLE link_state ADD CONSTRAINT FK_link_state_valid_id_id FOREIGN
KEY (valid_id) REFERENCES valid (id);

ALTER TABLE link_relation ADD CONSTRAINT
FK_link_relation_source_object_id_id FOREIGN KEY (source_object_id)
REFERENCES link_object (id);

ALTER TABLE link_relation ADD CONSTRAINT
FK_link_relation_target_object_id_id FOREIGN KEY (target_object_id)
REFERENCES link_object (id);

ALTER TABLE link_relation ADD CONSTRAINT FK_link_relation_state_id_id
FOREIGN KEY (state_id) REFERENCES link_state (id);

ALTER TABLE link_relation ADD CONSTRAINT FK_link_relation_type_id_id
FOREIGN KEY (type_id) REFERENCES link_type (id);

ALTER TABLE link_relation ADD CONSTRAINT FK_link_relation_create_by_id
FOREIGN KEY (create_by) REFERENCES users (id);

ALTER TABLE article_search ADD CONSTRAINT
FK_article_search_article_sender_type_id_id FOREIGN KEY
(article_sender_type_id) REFERENCES article_sender_type (id);

ALTER TABLE article_search ADD CONSTRAINT
FK_article_search_article_type_id_id FOREIGN KEY (article_type_id)
REFERENCES article_type (id);

ALTER TABLE article_search ADD CONSTRAINT FK_article_search_ticket_id_id
FOREIGN KEY (ticket_id) REFERENCES ticket (id);

-
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

NEW! ENTERPRISE SUBSCRIPTION - Get more information NOW!
http://www.otrs.com/en/support/enterprise-subscription/

Re: [otrs] Upgrade 2.4.5 to 2.4.7 Windows

[Sebastien Bory]

Dear all

I try this morning to do anothet upgrade (2.4.5 to 2.4.7) but when I do this
command line

C:\Documents and Settings\cmoimysql -uroot -e GRANT all ON otrs.* TO
'otrs'@'localhost' INDENTIFIED BY 'test'  mysql -uroot -e FLUSH
PRIVILLEGES

I have this messages

ERROR 1064 (42000) at line 1: You have an error in your SQL syntax; check
the manual that corresponds to your MySQL server version for the right
syntax to use near 'INDENTIFIED BY 'test'' at line 1

 

 

Sébastien  Bory
Administrateur réseaux
NCI-les centres d'affaires
Bienvenue chez vous - Just welcome !
59 Rue des Petits Champs 75001 Paris
Tel  33(0) 1 73 77 53 41
Fax  33(0) 1 73 77 55 56
Port: 33(0) 6 78 93 28 66 
Mail : mailto:s...@groupenci.com s.b...@groupenci.com
Web:  http://www.groupenci.com/ www.groupenci.com

 

cid:image001.gif@01C9F35E.16F7E530

Ce message et toutes les pièces jointes sont établis a l'intention exclusive
de ses destinataires et sont confidentiels. Si vous recevez ce message par
erreur, merci de le détruire et d'en avertir immédiatement l'expéditeur.
Toute utilisation de ce message non conforme à sa destination, toute
diffusion ou toute publication, totale ou partielle, est interdite, sauf
autorisation expresse. L'internet ne permettant pas d'assurer l'intégrité de
ce message, NCI décline toute responsabilité au titre de ce message, dans
l'hypothèse ou il aurait été modifié. This message and any attachments are
intended solely for the addressees and is confidential. If you receive this
message in error, please delete it and immediately notify the sender. Any
use not in accord with its purpose, any dissemination or disclosure, either
whole or partial, is prohibited except formal approval. The internet can not
guarantee the integrity of this message. NCI shall not therefore be liable
for the message if modified.

 

De : otrs-boun...@otrs.org [mailto:otrs-boun...@otrs.org] De la part de
Sebastien Bory
Envoyé : jeudi 25 mars 2010 16:33
À : otrs@otrs.org
Objet : [otrs] Upgrade 2.4.5 to 2.4.7 Windows

 

Dear all

Does anyone have a simple procedure to upgrade OTRS 2.4.5 to 2.4.7 on
Windows Server?

I watch the video on YouTube but that not work and I don’t understand all.

I have poor knowledge about mysql.

Can you help me

Thanks

 

 

Sébastien  Bory
Administrateur réseaux
NCI-les centres d'affaires
Bienvenue chez vous - Just welcome !
59 Rue des Petits Champs 75001 Paris
Tel  33(0) 1 73 77 53 41
Fax  33(0) 1 73 77 55 56
Port: 33(0) 6 78 93 28 66 
Mail : mailto:s...@groupenci.com s.b...@groupenci.com
Web:  http://www.groupenci.com/ www.groupenci.com

 

cid:image001.gif@01C9F35E.16F7E530

Ce message et toutes les pièces jointes sont établis a l'intention exclusive
de ses destinataires et sont confidentiels. Si vous recevez ce message par
erreur, merci de le détruire et d'en avertir immédiatement l'expéditeur.
Toute utilisation de ce message non conforme à sa destination, toute
diffusion ou toute publication, totale ou partielle, est interdite, sauf
autorisation expresse. L'internet ne permettant pas d'assurer l'intégrité de
ce message, NCI décline toute responsabilité au titre de ce message, dans
l'hypothèse ou il aurait été modifié. This message and any attachments are
intended solely for the addressees and is confidential. If you receive this
message in error, please delete it and immediately notify the sender. Any
use not in accord with its purpose, any dissemination or disclosure, either
whole or partial, is prohibited except formal approval. The internet can not
guarantee the integrity of this message. NCI shall not therefore be liable
for the message if modified.

 

image001.gif-
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

NEW! ENTERPRISE SUBSCRIPTION - Get more information NOW!
http://www.otrs.com/en/support/enterprise-subscription/

Re: [otrs] Upgrade 2.4.5 to 2.4.7 Windows

[volker . lipper]

shouldn't it be IDENTIFIED?


Li





Sebastien Bory
s.b...@groupenci.com 
Sent by: otrs-boun...@otrs.org
26.03.2010 08:43



Please respond to
User questions and discussions about OTRS. otrs@otrs.org





To
'User questions and discussions
about OTRS.' otrs@otrs.org


cc



Subject
Re: [otrs] Upgrade 2.4.5 to 2.4.7 Windows








Dear all
I try this morning to do anothet
upgrade (2.4.5 to 2.4.7) but when I do this command line
C:\Documents and Settings\cmoimysql
-uroot -e GRANT all ON otrs.* TO 'otrs'@'localhost' INDENTIFIED BY
'test'  mysql -uroot -e FLUSH PRIVILLEGES
I have this messages
ERROR 1064 (42000) at line
1: You have an error in your SQL syntax; check the manual that corresponds
to your MySQL server version for the right syntax to use near 'INDENTIFIED
BY 'test'' at line 1


Sébastien Bory
Administrateur réseaux
NCI-les centres d'affaires
Bienvenue chez vous - Just welcome !
59 Rue des Petits Champs 75001 Paris
Tel 33(0) 1 73 77 53 41
Fax 33(0) 1 73 77 55 56
Port: 33(0) 6 78 93 28 66 
Mail :s.b...@groupenci.com
Web:
www.groupenci.com


Ce message et toutes les
pièces jointes sont établis a l'intention exclusive de ses destinataires
et sont confidentiels. Si vous recevez ce message par erreur, merci de
le détruire et d'en avertir immédiatement l'expéditeur. Toute utilisation
de ce message non conforme à sa destination, toute diffusion ou toute publication,
totale ou partielle, est interdite, sauf autorisation expresse. L'internet
ne permettant pas d'assurer l'intégrité de ce message, NCI décline toute
responsabilité au titre de ce message, dans l'hypothèse ou il aurait été
modifié. This message and any attachments are intended solely for the addressees
and is confidential. If you receive this message in error, please delete
it and immediately notify the sender. Any use not in accord with its purpose,
any dissemination or disclosure, either whole or partial, is prohibited
except formal approval. The internet can not guarantee the integrity of
this message. NCI shall not therefore be liable for the message if modified.

De : otrs-boun...@otrs.org [mailto:otrs-boun...@otrs.org]
De la part de Sebastien Bory
Envoyé : jeudi 25 mars 2010 16:33
À : otrs@otrs.org
Objet : [otrs] Upgrade 2.4.5 to 2.4.7 Windows

Dear all
Does anyone have a simple procedure to
upgrade OTRS 2.4.5 to 2.4.7 on Windows Server?
I watch the video on YouTube but that not
work and I dont understand all.
I have poor knowledge about mysql.
Can you help me
Thanks


Sébastien Bory
Administrateur réseaux
NCI-les centres d'affaires
Bienvenue chez vous - Just welcome !
59 Rue des Petits Champs 75001 Paris
Tel 33(0) 1 73 77 53 41
Fax 33(0) 1 73 77 55 56
Port: 33(0) 6 78 93 28 66 
Mail :s.b...@groupenci.com
Web:
www.groupenci.com


Ce message et toutes les
pièces jointes sont établis a l'intention exclusive de ses destinataires
et sont confidentiels. Si vous recevez ce message par erreur, merci de
le détruire et d'en avertir immédiatement l'expéditeur. Toute utilisation
de ce message non conforme à sa destination, toute diffusion ou toute publication,
totale ou partielle, est interdite, sauf autorisation expresse. L'internet
ne permettant pas d'assurer l'intégrité de ce message, NCI décline toute
responsabilité au titre de ce message, dans l'hypothèse ou il aurait été
modifié. This message and any attachments are intended solely for the addressees
and is confidential. If you receive this message in error, please delete
it and immediately notify the sender. Any use not in accord with its purpose,
any dissemination or disclosure, either whole or partial, is prohibited
except formal approval. The internet can not guarantee the integrity of
this message. NCI shall not therefore be liable for the message if modified.
-
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

NEW! ENTERPRISE SUBSCRIPTION - Get more information NOW!
http://www.otrs.com/en/support/enterprise-subscription/

Privileged/Confidential Information may be contained in this message. If you
are not the addressee indicated in this message (or responsible for delivery
of the message to such person), you may not copy or deliver this message to 
anyone. In such case, you should destroy this message and kindly notify the
sender by reply email. Please advise immediately if you or your employer
does not consent to email for messages of this kind. Opinions, conclusions
and other information in this message that do not relate to the official
business of the GroupM companies shall be understood as neither given nor
endorsed by it.   GroupM companies are a member of WPP plc. For more
information on our business ethical standards and Corporate Responsibility 
policies please refer to our website at
http://www.wpp.com/WPP/About/

-
OTRS mailing list

Re: [otrs] Upgrade 2.4.5 to 2.4.7 Windows

[Adam Bator]

If you are just upgrading then you do not need to grant access to any user.
The password for user is set when tou create him not when you grant access.
If you use GRANT comand you do not need to flush privillages.

You can take a look at:
http://dev.mysql.com/doc/refman/5.1/en/adding-users.html

So in outher words if the system is not working - then the problem is 
not in mysql


Regards
Ada

Sebastien Bory pisze:


Dear all

I try this morning to do anothet upgrade (2.4.5 to 2.4.7) but when I 
do this command line


C:\Documents and Settings\cmoimysql -uroot -e GRANT all ON otrs.* TO 
'otrs'@'localhost' INDENTIFIED BY 'test'  mysql -uroot -e FLUSH 
PRIVILLEGES


I have this messages

ERROR 1064 (42000) at line 1: You have an error in your SQL syntax; 
check the manual that corresponds to your MySQL server version for the 
right syntax to use near 'INDENTIFIED BY 'test'' at line 1


* *

*Sébastien Bory
*Administrateur réseaux
*NCI-les centres d'affaires*
*Bienvenue chez vous - Just welcome !*
59 Rue des Petits Champs 75001 Paris
Tel 33(0) 1 73 77 53 41
Fax 33(0) 1 73 77 55 56
Port: 33(0) 6 78 93 28 66
Mail :s.b...@groupenci.com mailto:s...@groupenci.com
Web: www.groupenci.com http://www.groupenci.com/

cid:image001.gif@01C9F35E.16F7E530

/Ce message et toutes les pièces jointes sont établis a l'intention 
exclusive de ses destinataires et sont confidentiels. Si vous recevez 
ce message par erreur, merci de le détruire et d'en avertir 
immédiatement l'expéditeur. Toute utilisation de ce message non 
conforme à sa destination, toute diffusion ou toute publication, 
totale ou partielle, est interdite, sauf autorisation expresse. 
L'internet ne permettant pas d'assurer l'intégrité de ce message, NCI 
décline toute responsabilité au titre de ce message, dans l'hypothèse 
ou il aurait été modifié. //This message and any attachments are 
intended solely for the addressees and is confidential. If you receive 
this message in error, please delete it and immediately notify the 
sender. Any use not in accord with its purpose, any dissemination or 
disclosure, either whole or partial, is prohibited except formal 
approval. The internet can not guarantee the integrity of this 
message. NCI shall not therefore be liable for the message if modified./


*De :* otrs-boun...@otrs.org [mailto:otrs-boun...@otrs.org] *De la 
part de* Sebastien Bory

*Envoyé :* jeudi 25 mars 2010 16:33
*À :* otrs@otrs.org
*Objet :* [otrs] Upgrade 2.4.5 to 2.4.7 Windows

Dear all

Does anyone have a simple procedure to upgrade OTRS 2.4.5 to 2.4.7 on 
Windows Server?


I watch the video on YouTube but that not work and I don’t understand all.

I have poor knowledge about mysql.

Can you help me

Thanks

* *

*Sébastien Bory
*Administrateur réseaux
*NCI-les centres d'affaires*
*Bienvenue chez vous - Just welcome !*
59 Rue des Petits Champs 75001 Paris
Tel 33(0) 1 73 77 53 41
Fax 33(0) 1 73 77 55 56
Port: 33(0) 6 78 93 28 66
Mail :s.b...@groupenci.com mailto:s...@groupenci.com
Web: www.groupenci.com http://www.groupenci.com/

cid:image001.gif@01C9F35E.16F7E530

/Ce message et toutes les pièces jointes sont établis a l'intention 
exclusive de ses destinataires et sont confidentiels. Si vous recevez 
ce message par erreur, merci de le détruire et d'en avertir 
immédiatement l'expéditeur. Toute utilisation de ce message non 
conforme à sa destination, toute diffusion ou toute publication, 
totale ou partielle, est interdite, sauf autorisation expresse. 
L'internet ne permettant pas d'assurer l'intégrité de ce message, NCI 
décline toute responsabilité au titre de ce message, dans l'hypothèse 
ou il aurait été modifié. //This message and any attachments are 
intended solely for the addressees and is confidential. If you receive 
this message in error, please delete it and immediately notify the 
sender. Any use not in accord with its purpose, any dissemination or 
disclosure, either whole or partial, is prohibited except formal 
approval. The internet can not guarantee the integrity of this 
message. NCI shall not therefore be liable for the message if modified./




-
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

NEW! ENTERPRISE SUBSCRIPTION - Get more information NOW!
http://www.otrs.com/en/support/enterprise-subscription/

-
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

NEW! ENTERPRISE SUBSCRIPTION - Get more information NOW!
http://www.otrs.com/en/support/enterprise-subscription/

Re: [otrs] Upgrade 2.4.5 to 2.4.7 Windows

[Adam Bator]

IDENTIFIED is enered when you CREATE USER.
So when GRANT you do not need to enter IDENTIFIED.

But Again if you had version 2.4.5 running and you are just upgrading 
you do NOT need to touche mysql at all.


Regards
Adam

volker.lip...@groupm.com pisze:


shouldn't it be IDENTIFIED?


Li


*Sebastien Bory s.b...@groupenci.com*
Sent by: otrs-boun...@otrs.org

26.03.2010 08:43
Please respond to
User questions and discussions about OTRS. otrs@otrs.org



To
'User questions and discussions about OTRS.' otrs@otrs.org
cc

Subject
Re: [otrs] Upgrade 2.4.5 to 2.4.7 Windows









Dear all
I try this morning to do anothet upgrade (2.4.5 to 2.4.7) but when I 
do this command line
C:\Documents and Settings\cmoimysql -uroot -e GRANT all ON otrs.* TO 
'otrs'@'localhost' INDENTIFIED BY 'test'  mysql -uroot -e FLUSH 
PRIVILLEGES

I have this messages
ERROR 1064 (42000) at line 1: You have an error in your SQL syntax; 
check the manual that corresponds to your MySQL server version for the 
right syntax to use near 'INDENTIFIED BY 'test'' at line 1


* *
*Sébastien Bory*
Administrateur réseaux*
NCI-les centres d'affaires
Bienvenue chez vous - Just welcome !*
59 Rue des Petits Champs 75001 Paris
Tel 33(0) 1 73 77 53 41
Fax 33(0) 1 73 77 55 56
Port: 33(0) 6 78 93 28 66
Mail :_s.b...@groupenci.com_ mailto:s...@groupenci.com
Web: _www.groupenci.com_ http://www.groupenci.com/

cid:image001.gif@01C9F35E.16F7E530
/Ce message et toutes les pièces jointes sont établis a l'intention 
exclusive de ses destinataires et sont confidentiels. Si vous recevez 
ce message par erreur, merci de le détruire et d'en avertir 
immédiatement l'expéditeur. Toute utilisation de ce message non 
conforme à sa destination, toute diffusion ou toute publication, 
totale ou partielle, est interdite, sauf autorisation expresse. 
L'internet ne permettant pas d'assurer l'intégrité de ce message, NCI 
décline toute responsabilité au titre de ce message, dans l'hypothèse 
ou il aurait été modifié. This message and any attachments are 
intended solely for the addressees and is confidential. If you receive 
this message in error, please delete it and immediately notify the 
sender. Any use not in accord with its purpose, any dissemination or 
disclosure, either whole or partial, is prohibited except formal 
approval. The internet can not guarantee the integrity of this 
message. NCI shall not therefore be liable for the message if modified./


*De :* otrs-boun...@otrs.org [mailto:otrs-boun...@otrs.org] *De la 
part de* Sebastien Bory*

Envoyé :* jeudi 25 mars 2010 16:33*
À :* o...@otrs.org*
Objet :* [otrs] Upgrade 2.4.5 to 2.4.7 Windows

Dear all
Does anyone have a simple procedure to upgrade OTRS 2.4.5 to 2.4.7 on 
Windows Server?
I watch the video on YouTube but that not work and I don’t understand 
all.

I have poor knowledge about mysql.
Can you help me
Thanks

* *
*Sébastien Bory*
Administrateur réseaux*
NCI-les centres d'affaires
Bienvenue chez vous - Just welcome !*
59 Rue des Petits Champs 75001 Paris
Tel 33(0) 1 73 77 53 41
Fax 33(0) 1 73 77 55 56
Port: 33(0) 6 78 93 28 66
Mail :_s.b...@groupenci.com_ mailto:s...@groupenci.com
Web: _www.groupenci.com_ http://www.groupenci.com/

cid:image001.gif@01C9F35E.16F7E530
/Ce message et toutes les pièces jointes sont établis a l'intention 
exclusive de ses destinataires et sont confidentiels. Si vous recevez 
ce message par erreur, merci de le détruire et d'en avertir 
immédiatement l'expéditeur. Toute utilisation de ce message non 
conforme à sa destination, toute diffusion ou toute publication, 
totale ou partielle, est interdite, sauf autorisation expresse. 
L'internet ne permettant pas d'assurer l'intégrité de ce message, NCI 
décline toute responsabilité au titre de ce message, dans l'hypothèse 
ou il aurait été modifié. This message and any attachments are 
intended solely for the addressees and is confidential. If you receive 
this message in error, please delete it and immediately notify the 
sender. Any use not in accord with its purpose, any dissemination or 
disclosure, either whole or partial, is prohibited except formal 
approval. The internet can not guarantee the integrity of this 
message. NCI shall not therefore be liable for the message if modified./

-
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

NEW! ENTERPRISE SUBSCRIPTION - Get more information NOW!
http://www.otrs.com/en/support/enterprise-subscription/
Privileged/Confidential Information may be contained in this message. If you
are not the addressee indicated in this message (or responsible for delivery
of the message to such person), you may not copy or deliver this message to 
anyone. In such case, you should destroy this message and kindly notify the

sender by reply email. Please advise immediately if you or your

Re: [otrs] Upgrade 2.4.5 to 2.4.7 Windows

[Sebastien Bory]

Yes sorry I have 2 error in my syntax, 

Thanks

 

 

Cordialement

 

Sébastien  Bory
Administrateur réseaux
NCI-les centres d'affaires
Bienvenue chez vous - Just welcome !
59 Rue des Petits Champs 75001 Paris
Tel  33(0) 1 73 77 53 41
Fax  33(0) 1 73 77 55 56
Port: 33(0) 6 78 93 28 66 
Mail : mailto:s...@groupenci.com s.b...@groupenci.com
Web:  http://www.groupenci.com/ www.groupenci.com

 

cid:image001.gif@01C9F35E.16F7E530

Ce message et toutes les pièces jointes sont établis a l'intention exclusive
de ses destinataires et sont confidentiels. Si vous recevez ce message par
erreur, merci de le détruire et d'en avertir immédiatement l'expéditeur.
Toute utilisation de ce message non conforme à sa destination, toute
diffusion ou toute publication, totale ou partielle, est interdite, sauf
autorisation expresse. L'internet ne permettant pas d'assurer l'intégrité de
ce message, NCI décline toute responsabilité au titre de ce message, dans
l'hypothèse ou il aurait été modifié. This message and any attachments are
intended solely for the addressees and is confidential. If you receive this
message in error, please delete it and immediately notify the sender. Any
use not in accord with its purpose, any dissemination or disclosure, either
whole or partial, is prohibited except formal approval. The internet can not
guarantee the integrity of this message. NCI shall not therefore be liable
for the message if modified.

 

De : otrs-boun...@otrs.org [mailto:otrs-boun...@otrs.org] De la part de
volker.lip...@groupm.com
Envoyé : vendredi 26 mars 2010 08:50
À : User questions and discussions about OTRS.
Objet : Re: [otrs] Upgrade 2.4.5 to 2.4.7 Windows

 


shouldn't it be IDENTIFIED? 


Li 




Sebastien Bory s.b...@groupenci.com 
Sent by: otrs-boun...@otrs.org 

26.03.2010 08:43 


Please respond to
User questions and discussions about OTRS. otrs@otrs.org


To

'User questions and discussions about OTRS.' otrs@otrs.org 


cc



Subject

Re: [otrs] Upgrade 2.4.5 to 2.4.7 Windows

 






Dear all 
I try this morning to do anothet upgrade (2.4.5 to 2.4.7) but when I do this
command line 
C:\Documents and Settings\cmoimysql -uroot -e GRANT all ON otrs.* TO
'otrs'@'localhost' INDENTIFIED BY 'test'  mysql -uroot -e FLUSH
PRIVILLEGES 
I have this messages 
ERROR 1064 (42000) at line 1: You have an error in your SQL syntax; check
the manual that corresponds to your MySQL server version for the right
syntax to use near 'INDENTIFIED BY 'test'' at line 1 
  
  
Sébastien  Bory
Administrateur réseaux
NCI-les centres d'affaires
Bienvenue chez vous - Just welcome !
59 Rue des Petits Champs 75001 Paris
Tel  33(0) 1 73 77 53 41
Fax  33(0) 1 73 77 55 56
Port: 33(0) 6 78 93 28 66 
Mail : mailto:s...@groupenci.com s.b...@groupenci.com
Web:  http://www.groupenci.com/ www.groupenci.com 
  
cid:image001.gif@01C9F35E.16F7E530
Ce message et toutes les pièces jointes sont établis a l'intention exclusive
de ses destinataires et sont confidentiels. Si vous recevez ce message par
erreur, merci de le détruire et d'en avertir immédiatement l'expéditeur.
Toute utilisation de ce message non conforme à sa destination, toute
diffusion ou toute publication, totale ou partielle, est interdite, sauf
autorisation expresse. L'internet ne permettant pas d'assurer l'intégrité de
ce message, NCI décline toute responsabilité au titre de ce message, dans
l'hypothèse ou il aurait été modifié. This message and any attachments are
intended solely for the addressees and is confidential. If you receive this
message in error, please delete it and immediately notify the sender. Any
use not in accord with its purpose, any dissemination or disclosure, either
whole or partial, is prohibited except formal approval. The internet can not
guarantee the integrity of this message. NCI shall not therefore be liable
for the message if modified. 
  
De : otrs-boun...@otrs.org [mailto:otrs-boun...@otrs.org] De la part de
Sebastien Bory
Envoyé : jeudi 25 mars 2010 16:33
À : otrs@otrs.org
Objet : [otrs] Upgrade 2.4.5 to 2.4.7 Windows 
  
Dear all 
Does anyone have a simple procedure to upgrade OTRS 2.4.5 to 2.4.7 on
Windows Server? 
I watch the video on YouTube but that not work and I don’t understand all. 
I have poor knowledge about mysql. 
Can you help me 
Thanks 
  
  
Sébastien  Bory
Administrateur réseaux
NCI-les centres d'affaires
Bienvenue chez vous - Just welcome !
59 Rue des Petits Champs 75001 Paris
Tel  33(0) 1 73 77 53 41
Fax  33(0) 1 73 77 55 56
Port: 33(0) 6 78 93 28 66 
Mail : mailto:s...@groupenci.com s.b...@groupenci.com
Web:  http://www.groupenci.com/ www.groupenci.com 
  
cid:image001.gif@01C9F35E.16F7E530
Ce message et toutes les pièces jointes sont établis a l'intention exclusive
de ses destinataires et sont confidentiels. Si vous recevez ce message par
erreur, merci de le détruire et d'en avertir immédiatement l'expéditeur.
Toute utilisation de ce message non conforme à sa destination, toute
diffusion ou toute publication, totale ou

Re: [otrs] Upgrade 2.4.5 to 2.4.7 Windows

[Sebastien Bory]

I continue to watch the video and after they run some scripts:
dbupdate-to-2.4.mysql.sql and Perl DBupadate-to-2.4.pl and another one
I think it's for upgrade the version database but I have already a OTRS
2.4.5 version so I need to use this scripts?
I not do that and when I want to log on the agent interfaces with
r...@localhost with my old password I don't have any access


Cordialement

Sébastien  Bory
Administrateur réseaux
NCI-les centres d'affaires
Bienvenue chez vous - Just welcome !
59 Rue des Petits Champs 75001 Paris
Tel  33(0) 1 73 77 53 41
Fax  33(0) 1 73 77 55 56
Port: 33(0) 6 78 93 28 66 
Mail :s.b...@groupenci.com
Web: www.groupenci.com


Ce message et toutes les pièces jointes sont établis a l'intention exclusive
de ses destinataires et sont confidentiels. Si vous recevez ce message par
erreur, merci de le détruire et d'en avertir immédiatement l'expéditeur.
Toute utilisation de ce message non conforme à sa destination, toute
diffusion ou toute publication, totale ou partielle, est interdite, sauf
autorisation expresse. L'internet ne permettant pas d'assurer l'intégrité de
ce message, NCI décline toute responsabilité au titre de ce message, dans
l'hypothèse ou il aurait été modifié. This message and any attachments are
intended solely for the addressees and is confidential. If you receive this
message in error, please delete it and immediately notify the sender. Any
use not in accord with its purpose, any dissemination or disclosure, either
whole or partial, is prohibited except formal approval. The internet can not
guarantee the integrity of this message. NCI shall not therefore be liable
for the message if modified.

-Message d'origine-
De : otrs-boun...@otrs.org [mailto:otrs-boun...@otrs.org] De la part de Adam
Bator
Envoyé : vendredi 26 mars 2010 09:12
À : User questions and discussions about OTRS.
Objet : Re: [otrs] Upgrade 2.4.5 to 2.4.7 Windows

IDENTIFIED is enered when you CREATE USER.
So when GRANT you do not need to enter IDENTIFIED.

But Again if you had version 2.4.5 running and you are just upgrading 
you do NOT need to touche mysql at all.

Regards
Adam

volker.lip...@groupm.com pisze:

 shouldn't it be IDENTIFIED?


 Li


 *Sebastien Bory s.b...@groupenci.com*
 Sent by: otrs-boun...@otrs.org

 26.03.2010 08:43
 Please respond to
 User questions and discussions about OTRS. otrs@otrs.org


   
 To
   'User questions and discussions about OTRS.' otrs@otrs.org
 cc
   
 Subject
   Re: [otrs] Upgrade 2.4.5 to 2.4.7 Windows



   





 Dear all
 I try this morning to do anothet upgrade (2.4.5 to 2.4.7) but when I 
 do this command line
 C:\Documents and Settings\cmoimysql -uroot -e GRANT all ON otrs.* TO 
 'otrs'@'localhost' INDENTIFIED BY 'test'  mysql -uroot -e FLUSH 
 PRIVILLEGES
 I have this messages
 ERROR 1064 (42000) at line 1: You have an error in your SQL syntax; 
 check the manual that corresponds to your MySQL server version for the 
 right syntax to use near 'INDENTIFIED BY 'test'' at line 1

 * *
 *Sébastien Bory*
 Administrateur réseaux*
 NCI-les centres d'affaires
 Bienvenue chez vous - Just welcome !*
 59 Rue des Petits Champs 75001 Paris
 Tel 33(0) 1 73 77 53 41
 Fax 33(0) 1 73 77 55 56
 Port: 33(0) 6 78 93 28 66
 Mail :_s.b...@groupenci.com_ mailto:s...@groupenci.com
 Web: _www.groupenci.com_ http://www.groupenci.com/

 cid:image001.gif@01C9F35E.16F7E530
 /Ce message et toutes les pièces jointes sont établis a l'intention 
 exclusive de ses destinataires et sont confidentiels. Si vous recevez 
 ce message par erreur, merci de le détruire et d'en avertir 
 immédiatement l'expéditeur. Toute utilisation de ce message non 
 conforme à sa destination, toute diffusion ou toute publication, 
 totale ou partielle, est interdite, sauf autorisation expresse. 
 L'internet ne permettant pas d'assurer l'intégrité de ce message, NCI 
 décline toute responsabilité au titre de ce message, dans l'hypothèse 
 ou il aurait été modifié. This message and any attachments are 
 intended solely for the addressees and is confidential. If you receive 
 this message in error, please delete it and immediately notify the 
 sender. Any use not in accord with its purpose, any dissemination or 
 disclosure, either whole or partial, is prohibited except formal 
 approval. The internet can not guarantee the integrity of this 
 message. NCI shall not therefore be liable for the message if modified./

 *De :* otrs-boun...@otrs.org [mailto:otrs-boun...@otrs.org] *De la 
 part de* Sebastien Bory*
 Envoyé :* jeudi 25 mars 2010 16:33*
 À :* o...@otrs.org*
 Objet :* [otrs] Upgrade 2.4.5 to 2.4.7 Windows

 Dear all
 Does anyone have a simple procedure to upgrade OTRS 2.4.5 to 2.4.7 on 
 Windows Server?
 I watch the video on YouTube but that not work and I don’t understand 
 all.
 I have poor knowledge about mysql.
 Can you help me
 Thanks

 * *
 *Sébastien Bory*
 Administrateur réseaux*
 NCI-les centres d'affaires
 Bienvenue chez vous - Just welcome !*
 59 Rue des Petits

Re: [otrs] Upgrade 2.4.7

[Sebastien Bory]

After this upgrade I can’t log on root or another agent, and it’s the same
for customer interfaces.

How I can verify with mysql the user’ table?

I have no knowledge about Mysql

 

Cordialement

 

Sébastien  Bory
Administrateur réseaux
NCI-les centres d'affaires
Bienvenue chez vous - Just welcome !
59 Rue des Petits Champs 75001 Paris
Tel  33(0) 1 73 77 53 41
Fax  33(0) 1 73 77 55 56
Port: 33(0) 6 78 93 28 66 
Mail : mailto:s...@groupenci.com s.b...@groupenci.com
Web:  http://www.groupenci.com/ www.groupenci.com

 

cid:image001.gif@01C9F35E.16F7E530

Ce message et toutes les pièces jointes sont établis a l'intention exclusive
de ses destinataires et sont confidentiels. Si vous recevez ce message par
erreur, merci de le détruire et d'en avertir immédiatement l'expéditeur.
Toute utilisation de ce message non conforme à sa destination, toute
diffusion ou toute publication, totale ou partielle, est interdite, sauf
autorisation expresse. L'internet ne permettant pas d'assurer l'intégrité de
ce message, NCI décline toute responsabilité au titre de ce message, dans
l'hypothèse ou il aurait été modifié. This message and any attachments are
intended solely for the addressees and is confidential. If you receive this
message in error, please delete it and immediately notify the sender. Any
use not in accord with its purpose, any dissemination or disclosure, either
whole or partial, is prohibited except formal approval. The internet can not
guarantee the integrity of this message. NCI shall not therefore be liable
for the message if modified.

 

De : otrs-boun...@otrs.org [mailto:otrs-boun...@otrs.org] De la part de
Sebastien Bory
Envoyé : vendredi 26 mars 2010 13:47
À : 'User questions and discussions about OTRS.'
Objet : [otrs] Upgrade 2.4.7

 

Dear,

I do an upgrade for otrs 2.4.5 to otrs 2.4.7

When I want to log it with r...@localhost  I have this message “the user or
password are wrong”

And I look in this files otrs.log and I see that:

Fri Mar 26 13:42:17 2010][Error][Kernel::System::Valid::ValidIDsGet][195]
Table 'otrs.valid' doesn't exist, SQL: 'SELECT id FROM valid WHERE name =
'valid''

[Fri Mar 26 13:42:17 2010][Error][Kernel::System::Auth::DB::Auth][94] You
have an error in your SQL syntax; check the manual that corresponds to your
MySQL server version for the right syntax to use near ') AND  login =
'r...@localhost'' at line 1, SQL: 'SELECT pw, id  FROM  users  WHERE
valid_id IN (  ) AND  login = 'r...@localhost''

[Fri Mar 26 13:42:17 2010][Notice][Kernel::System::Auth::DB::Auth] User:
r...@localhost doesn't exist or is invalid!!! (REMOTE_ADDR: 127.0.0.1)

[Fri Mar 26 13:42:17 2010][Error][Kernel::System::User::UserLookup][680]
Table 'otrs.users' doesn't exist, SQL: 'SELECT id FROM users  WHERE
LOWER(login) = ?'

 

Can you help me

thanks

 

Cordialement

 

Sébastien  Bory
Administrateur réseaux
NCI-les centres d'affaires
Bienvenue chez vous - Just welcome !
59 Rue des Petits Champs 75001 Paris
Tel  33(0) 1 73 77 53 41
Fax  33(0) 1 73 77 55 56
Port: 33(0) 6 78 93 28 66 
Mail : mailto:s...@groupenci.com s.b...@groupenci.com
Web:  http://www.groupenci.com/ www.groupenci.com

 

cid:image001.gif@01C9F35E.16F7E530

Ce message et toutes les pièces jointes sont établis a l'intention exclusive
de ses destinataires et sont confidentiels. Si vous recevez ce message par
erreur, merci de le détruire et d'en avertir immédiatement l'expéditeur.
Toute utilisation de ce message non conforme à sa destination, toute
diffusion ou toute publication, totale ou partielle, est interdite, sauf
autorisation expresse. L'internet ne permettant pas d'assurer l'intégrité de
ce message, NCI décline toute responsabilité au titre de ce message, dans
l'hypothèse ou il aurait été modifié. This message and any attachments are
intended solely for the addressees and is confidential. If you receive this
message in error, please delete it and immediately notify the sender. Any
use not in accord with its purpose, any dissemination or disclosure, either
whole or partial, is prohibited except formal approval. The internet can not
guarantee the integrity of this message. NCI shall not therefore be liable
for the message if modified.

 

image001.gif-
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

NEW! ENTERPRISE SUBSCRIPTION - Get more information NOW!
http://www.otrs.com/en/support/enterprise-subscription/

Re: [otrs] Upgrade 2.4.7

[Nathan Campbell]

Make sure your config.pm file was not overwritten during the upgrade.

If you ran the windows installer then it would have created a new config.pm and 
your connection and login settings could be messed up.

 

Good luck,

 

Nathan Campbell 
Dallas Symphony Orchestra 



From: otrs-boun...@otrs.org [mailto:otrs-boun...@otrs.org] On Behalf Of 
Sebastien Bory
Sent: Friday, March 26, 2010 9:45 AM
To: 'User questions and discussions about OTRS.'
Subject: Re: [otrs] Upgrade 2.4.7

 

After this upgrade I can't log on root or another agent, and it's the same for 
customer interfaces.

How I can verify with mysql the user' table?

I have no knowledge about Mysql

 

Cordialement

 

Sébastien  Bory
Administrateur réseaux
NCI-les centres d'affaires
Bienvenue chez vous - Just welcome !
59 Rue des Petits Champs 75001 Paris
Tel  33(0) 1 73 77 53 41
Fax  33(0) 1 73 77 55 56
Port: 33(0) 6 78 93 28 66 
Mail :s.b...@groupenci.com mailto:s...@groupenci.com 
Web: www.groupenci.com http://www.groupenci.com/ 

 

 

Ce message et toutes les pièces jointes sont établis a l'intention exclusive de 
ses destinataires et sont confidentiels. Si vous recevez ce message par erreur, 
merci de le détruire et d'en avertir immédiatement l'expéditeur. Toute 
utilisation de ce message non conforme à sa destination, toute diffusion ou 
toute publication, totale ou partielle, est interdite, sauf autorisation 
expresse. L'internet ne permettant pas d'assurer l'intégrité de ce message, NCI 
décline toute responsabilité au titre de ce message, dans l'hypothèse ou il 
aurait été modifié. This message and any attachments are intended solely for 
the addressees and is confidential. If you receive this message in error, 
please delete it and immediately notify the sender. Any use not in accord with 
its purpose, any dissemination or disclosure, either whole or partial, is 
prohibited except formal approval. The internet can not guarantee the integrity 
of this message. NCI shall not therefore be liable for the message if modified.

 

De : otrs-boun...@otrs.org [mailto:otrs-boun...@otrs.org] De la part de 
Sebastien Bory
Envoyé : vendredi 26 mars 2010 13:47
À : 'User questions and discussions about OTRS.'
Objet : [otrs] Upgrade 2.4.7

 

Dear,

I do an upgrade for otrs 2.4.5 to otrs 2.4.7

When I want to log it with r...@localhost  I have this message the user or 
password are wrong

And I look in this files otrs.log and I see that:

Fri Mar 26 13:42:17 2010][Error][Kernel::System::Valid::ValidIDsGet][195] Table 
'otrs.valid' doesn't exist, SQL: 'SELECT id FROM valid WHERE name = 'valid''

[Fri Mar 26 13:42:17 2010][Error][Kernel::System::Auth::DB::Auth][94] You have 
an error in your SQL syntax; check the manual that corresponds to your MySQL 
server version for the right syntax to use near ') AND  login = 
'r...@localhost'' at line 1, SQL: 'SELECT pw, id  FROM  users  WHERE  valid_id 
IN (  ) AND  login = 'r...@localhost''

[Fri Mar 26 13:42:17 2010][Notice][Kernel::System::Auth::DB::Auth] User: 
r...@localhost doesn't exist or is invalid!!! (REMOTE_ADDR: 127.0.0.1)

[Fri Mar 26 13:42:17 2010][Error][Kernel::System::User::UserLookup][680] Table 
'otrs.users' doesn't exist, SQL: 'SELECT id FROM users  WHERE LOWER(login) = ?'

 

Can you help me

thanks

 

Cordialement

 

Sébastien  Bory
Administrateur réseaux
NCI-les centres d'affaires
Bienvenue chez vous - Just welcome !
59 Rue des Petits Champs 75001 Paris
Tel  33(0) 1 73 77 53 41
Fax  33(0) 1 73 77 55 56
Port: 33(0) 6 78 93 28 66 
Mail :s.b...@groupenci.com mailto:s...@groupenci.com 
Web: www.groupenci.com http://www.groupenci.com/ 

 



Ce message et toutes les pièces jointes sont établis a l'intention exclusive de 
ses destinataires et sont confidentiels. Si vous recevez ce message par erreur, 
merci de le détruire et d'en avertir immédiatement l'expéditeur. Toute 
utilisation de ce message non conforme à sa destination, toute diffusion ou 
toute publication, totale ou partielle, est interdite, sauf autorisation 
expresse. L'internet ne permettant pas d'assurer l'intégrité de ce message, NCI 
décline toute responsabilité au titre de ce message, dans l'hypothèse ou il 
aurait été modifié. This message and any attachments are intended solely for 
the addressees and is confidential. If you receive this message in error, 
please delete it and immediately notify the sender. Any use not in accord with 
its purpose, any dissemination or disclosure, either whole or partial, is 
prohibited except formal approval. The internet can not guarantee the integrity 
of this message. NCI shall not therefore be liable for the message if modified.

 

image001.gif-
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

NEW! ENTERPRISE SUBSCRIPTION - Get more information NOW!
http://www.otrs.com/en/support/enterprise-subscription/

Re: [otrs] Upgrade 2.4.7

[Sebastien Bory]

Thank Nathan,

I do upgrade with windows installer, but my config .pm files is close and I
save the old config.pm (before upgrade) and I replace it after run windows
installer 2.4.7.

 

Cordialement

 

Sébastien  Bory
Administrateur réseaux
NCI-les centres d'affaires
Bienvenue chez vous - Just welcome !
59 Rue des Petits Champs 75001 Paris
Tel  33(0) 1 73 77 53 41
Fax  33(0) 1 73 77 55 56
Port: 33(0) 6 78 93 28 66 
Mail : mailto:s...@groupenci.com s.b...@groupenci.com
Web:  http://www.groupenci.com/ www.groupenci.com

 

cid:image001.gif@01C9F35E.16F7E530

Ce message et toutes les pièces jointes sont établis a l'intention exclusive
de ses destinataires et sont confidentiels. Si vous recevez ce message par
erreur, merci de le détruire et d'en avertir immédiatement l'expéditeur.
Toute utilisation de ce message non conforme à sa destination, toute
diffusion ou toute publication, totale ou partielle, est interdite, sauf
autorisation expresse. L'internet ne permettant pas d'assurer l'intégrité de
ce message, NCI décline toute responsabilité au titre de ce message, dans
l'hypothèse ou il aurait été modifié. This message and any attachments are
intended solely for the addressees and is confidential. If you receive this
message in error, please delete it and immediately notify the sender. Any
use not in accord with its purpose, any dissemination or disclosure, either
whole or partial, is prohibited except formal approval. The internet can not
guarantee the integrity of this message. NCI shall not therefore be liable
for the message if modified.

 

De : otrs-boun...@otrs.org [mailto:otrs-boun...@otrs.org] De la part de
Nathan Campbell
Envoyé : vendredi 26 mars 2010 15:51
À : User questions and discussions about OTRS.
Objet : Re: [otrs] Upgrade 2.4.7

 

Make sure your config.pm file was not overwritten during the upgrade.

If you ran the windows installer then it would have created a new config.pm
and your connection and login settings could be messed up.

 

Good luck,

 

Nathan Campbell 
Dallas Symphony Orchestra 

From: otrs-boun...@otrs.org [mailto:otrs-boun...@otrs.org] On Behalf Of
Sebastien Bory
Sent: Friday, March 26, 2010 9:45 AM
To: 'User questions and discussions about OTRS.'
Subject: Re: [otrs] Upgrade 2.4.7

 

After this upgrade I can’t log on root or another agent, and it’s the same
for customer interfaces.

How I can verify with mysql the user’ table?

I have no knowledge about Mysql

 

Cordialement

 

Sébastien  Bory
Administrateur réseaux
NCI-les centres d'affaires
Bienvenue chez vous - Just welcome !
59 Rue des Petits Champs 75001 Paris
Tel  33(0) 1 73 77 53 41
Fax  33(0) 1 73 77 55 56
Port: 33(0) 6 78 93 28 66 
Mail : mailto:s...@groupenci.com s.b...@groupenci.com
Web:  http://www.groupenci.com/ www.groupenci.com

 

cid:image001.gif@01C9F35E.16F7E530

Ce message et toutes les pièces jointes sont établis a l'intention exclusive
de ses destinataires et sont confidentiels. Si vous recevez ce message par
erreur, merci de le détruire et d'en avertir immédiatement l'expéditeur.
Toute utilisation de ce message non conforme à sa destination, toute
diffusion ou toute publication, totale ou partielle, est interdite, sauf
autorisation expresse. L'internet ne permettant pas d'assurer l'intégrité de
ce message, NCI décline toute responsabilité au titre de ce message, dans
l'hypothèse ou il aurait été modifié. This message and any attachments are
intended solely for the addressees and is confidential. If you receive this
message in error, please delete it and immediately notify the sender. Any
use not in accord with its purpose, any dissemination or disclosure, either
whole or partial, is prohibited except formal approval. The internet can not
guarantee the integrity of this message. NCI shall not therefore be liable
for the message if modified.

 

De : otrs-boun...@otrs.org [mailto:otrs-boun...@otrs.org] De la part de
Sebastien Bory
Envoyé : vendredi 26 mars 2010 13:47
À : 'User questions and discussions about OTRS.'
Objet : [otrs] Upgrade 2.4.7

 

Dear,

I do an upgrade for otrs 2.4.5 to otrs 2.4.7

When I want to log it with r...@localhost  I have this message “the user or
password are wrong”

And I look in this files otrs.log and I see that:

Fri Mar 26 13:42:17 2010][Error][Kernel::System::Valid::ValidIDsGet][195]
Table 'otrs.valid' doesn't exist, SQL: 'SELECT id FROM valid WHERE name =
'valid''

[Fri Mar 26 13:42:17 2010][Error][Kernel::System::Auth::DB::Auth][94] You
have an error in your SQL syntax; check the manual that corresponds to your
MySQL server version for the right syntax to use near ') AND  login =
'r...@localhost'' at line 1, SQL: 'SELECT pw, id  FROM  users  WHERE
valid_id IN (  ) AND  login = 'r...@localhost''

[Fri Mar 26 13:42:17 2010][Notice][Kernel::System::Auth::DB::Auth] User:
r...@localhost doesn't exist or is invalid!!! (REMOTE_ADDR: 127.0.0.1)

[Fri Mar 26 13:42:17 2010][Error][Kernel::System::User::UserLookup][680]
Table 'otrs.users' doesn't exist, SQL: 'SELECT id

Re: [otrs] Upgrade 2.4.7

[Sebastien Bory]

I think I have a problem when I save my otrs databases before upgrade,

Because I save it before upgrade with mysql dump –uroot otrs  otrs_dump.sql

After upgrade I recreate it an import the old database (mysql –uroot otrs 
otrs_dump.sql

But when I see the tables on otrs database I have 2 table.

mysql use otrs

Database changed

mysql show tables;

+---

| Tables_in_otrs

+---

| notification_event

| notification_event_ite

+---

2 rows in set (0.02 sec)

Can you confirm they are more 2 table?

 

Cordialement

 

Sébastien  Bory
Administrateur réseaux
NCI-les centres d'affaires
Bienvenue chez vous - Just welcome !
59 Rue des Petits Champs 75001 Paris
Tel  33(0) 1 73 77 53 41
Fax  33(0) 1 73 77 55 56
Port: 33(0) 6 78 93 28 66 
Mail : mailto:s...@groupenci.com s.b...@groupenci.com
Web:  http://www.groupenci.com/ www.groupenci.com

 

cid:image001.gif@01C9F35E.16F7E530

Ce message et toutes les pièces jointes sont établis a l'intention exclusive
de ses destinataires et sont confidentiels. Si vous recevez ce message par
erreur, merci de le détruire et d'en avertir immédiatement l'expéditeur.
Toute utilisation de ce message non conforme à sa destination, toute
diffusion ou toute publication, totale ou partielle, est interdite, sauf
autorisation expresse. L'internet ne permettant pas d'assurer l'intégrité de
ce message, NCI décline toute responsabilité au titre de ce message, dans
l'hypothèse ou il aurait été modifié. This message and any attachments are
intended solely for the addressees and is confidential. If you receive this
message in error, please delete it and immediately notify the sender. Any
use not in accord with its purpose, any dissemination or disclosure, either
whole or partial, is prohibited except formal approval. The internet can not
guarantee the integrity of this message. NCI shall not therefore be liable
for the message if modified.

 

De : otrs-boun...@otrs.org [mailto:otrs-boun...@otrs.org] De la part de
Sebastien Bory
Envoyé : vendredi 26 mars 2010 15:45
À : 'User questions and discussions about OTRS.'
Objet : Re: [otrs] Upgrade 2.4.7

 

After this upgrade I can’t log on root or another agent, and it’s the same
for customer interfaces.

How I can verify with mysql the user’ table?

I have no knowledge about Mysql

 

Cordialement

 

Sébastien  Bory
Administrateur réseaux
NCI-les centres d'affaires
Bienvenue chez vous - Just welcome !
59 Rue des Petits Champs 75001 Paris
Tel  33(0) 1 73 77 53 41
Fax  33(0) 1 73 77 55 56
Port: 33(0) 6 78 93 28 66 
Mail : mailto:s...@groupenci.com s.b...@groupenci.com
Web:  http://www.groupenci.com/ www.groupenci.com

 

cid:image001.gif@01C9F35E.16F7E530

Ce message et toutes les pièces jointes sont établis a l'intention exclusive
de ses destinataires et sont confidentiels. Si vous recevez ce message par
erreur, merci de le détruire et d'en avertir immédiatement l'expéditeur.
Toute utilisation de ce message non conforme à sa destination, toute
diffusion ou toute publication, totale ou partielle, est interdite, sauf
autorisation expresse. L'internet ne permettant pas d'assurer l'intégrité de
ce message, NCI décline toute responsabilité au titre de ce message, dans
l'hypothèse ou il aurait été modifié. This message and any attachments are
intended solely for the addressees and is confidential. If you receive this
message in error, please delete it and immediately notify the sender. Any
use not in accord with its purpose, any dissemination or disclosure, either
whole or partial, is prohibited except formal approval. The internet can not
guarantee the integrity of this message. NCI shall not therefore be liable
for the message if modified.

 

De : otrs-boun...@otrs.org [mailto:otrs-boun...@otrs.org] De la part de
Sebastien Bory
Envoyé : vendredi 26 mars 2010 13:47
À : 'User questions and discussions about OTRS.'
Objet : [otrs] Upgrade 2.4.7

 

Dear,

I do an upgrade for otrs 2.4.5 to otrs 2.4.7

When I want to log it with r...@localhost  I have this message “the user or
password are wrong”

And I look in this files otrs.log and I see that:

Fri Mar 26 13:42:17 2010][Error][Kernel::System::Valid::ValidIDsGet][195]
Table 'otrs.valid' doesn't exist, SQL: 'SELECT id FROM valid WHERE name =
'valid''

[Fri Mar 26 13:42:17 2010][Error][Kernel::System::Auth::DB::Auth][94] You
have an error in your SQL syntax; check the manual that corresponds to your
MySQL server version for the right syntax to use near ') AND  login =
'r...@localhost'' at line 1, SQL: 'SELECT pw, id  FROM  users  WHERE
valid_id IN (  ) AND  login = 'r...@localhost''

[Fri Mar 26 13:42:17 2010][Notice][Kernel::System::Auth::DB::Auth] User:
r...@localhost doesn't exist or is invalid!!! (REMOTE_ADDR: 127.0.0.1)

[Fri Mar 26 13:42:17 2010][Error][Kernel::System::User::UserLookup][680]
Table 'otrs.users' doesn't exist, SQL: 'SELECT id FROM users  WHERE
LOWER(login) = ?'

 

Can you help me

thanks

 

Cordialement

 

Sébastien  Bory

Re: [otrs] Upgrade 2.4.7

[volker . lipper]

So you say there are just two tables in your db?
I am on the road so i cant look, but there should be around 70 i think.

Just 2 ct,

Li
 Sent bai mohbeil


- Originalnachricht -
Von: Sebastien Bory [s.b...@groupenci.com]
Gesendet: 26/03/2010 16:35 CET
An: 'User questions and discussions about OTRS.' otrs@otrs.org
Betreff: Re: [otrs] Upgrade 2.4.7



I think I have a problem when I save my otrs databases before upgrade,

Because I save it before upgrade with mysql dump –uroot otrs  otrs_dump.sql

After upgrade I recreate it an import the old database (mysql –uroot otrs 
otrs_dump.sql

But when I see the tables on otrs database I have 2 table.

mysql use otrs

Database changed

mysql show tables;

+---

| Tables_in_otrs

+---

| notification_event

| notification_event_ite

+---

2 rows in set (0.02 sec)

Can you confirm they are more 2 table?



Cordialement



Sébastien  Bory
Administrateur réseaux
NCI-les centres d'affaires
Bienvenue chez vous - Just welcome !
59 Rue des Petits Champs 75001 Paris
Tel  33(0) 1 73 77 53 41
Fax  33(0) 1 73 77 55 56
Port: 33(0) 6 78 93 28 66
Mail : mailto:s...@groupenci.com s.b...@groupenci.com
Web:  http://www.groupenci.com/ www.groupenci.com



cid:image001.gif@01C9F35E.16F7E530

Ce message et toutes les pièces jointes sont établis a l'intention exclusive
de ses destinataires et sont confidentiels. Si vous recevez ce message par
erreur, merci de le détruire et d'en avertir immédiatement l'expéditeur.
Toute utilisation de ce message non conforme à sa destination, toute
diffusion ou toute publication, totale ou partielle, est interdite, sauf
autorisation expresse. L'internet ne permettant pas d'assurer l'intégrité de
ce message, NCI décline toute responsabilité au titre de ce message, dans
l'hypothèse ou il aurait été modifié. This message and any attachments are
intended solely for the addressees and is confidential. If you receive this
message in error, please delete it and immediately notify the sender. Any
use not in accord with its purpose, any dissemination or disclosure, either
whole or partial, is prohibited except formal approval. The internet can not
guarantee the integrity of this message. NCI shall not therefore be liable
for the message if modified.



De : otrs-boun...@otrs.org [mailto:otrs-boun...@otrs.org] De la part de
Sebastien Bory
Envoyé : vendredi 26 mars 2010 15:45
À : 'User questions and discussions about OTRS.'
Objet : Re: [otrs] Upgrade 2.4.7



After this upgrade I can’t log on root or another agent, and it’s the same
for customer interfaces.

How I can verify with mysql the user’ table?

I have no knowledge about Mysql



Cordialement



Sébastien  Bory
Administrateur réseaux
NCI-les centres d'affaires
Bienvenue chez vous - Just welcome !
59 Rue des Petits Champs 75001 Paris
Tel  33(0) 1 73 77 53 41
Fax  33(0) 1 73 77 55 56
Port: 33(0) 6 78 93 28 66
Mail : mailto:s...@groupenci.com s.b...@groupenci.com
Web:  http://www.groupenci.com/ www.groupenci.com



cid:image001.gif@01C9F35E.16F7E530

Ce message et toutes les pièces jointes sont établis a l'intention exclusive
de ses destinataires et sont confidentiels. Si vous recevez ce message par
erreur, merci de le détruire et d'en avertir immédiatement l'expéditeur.
Toute utilisation de ce message non conforme à sa destination, toute
diffusion ou toute publication, totale ou partielle, est interdite, sauf
autorisation expresse. L'internet ne permettant pas d'assurer l'intégrité de
ce message, NCI décline toute responsabilité au titre de ce message, dans
l'hypothèse ou il aurait été modifié. This message and any attachments are
intended solely for the addressees and is confidential. If you receive this
message in error, please delete it and immediately notify the sender. Any
use not in accord with its purpose, any dissemination or disclosure, either
whole or partial, is prohibited except formal approval. The internet can not
guarantee the integrity of this message. NCI shall not therefore be liable
for the message if modified.



De : otrs-boun...@otrs.org [mailto:otrs-boun...@otrs.org] De la part de
Sebastien Bory
Envoyé : vendredi 26 mars 2010 13:47
À : 'User questions and discussions about OTRS.'
Objet : [otrs] Upgrade 2.4.7



Dear,

I do an upgrade for otrs 2.4.5 to otrs 2.4.7

When I want to log it with r...@localhost  I have this message “the user or
password are wrong”

And I look in this files otrs.log and I see that:

Fri Mar 26 13:42:17 2010][Error][Kernel::System::Valid::ValidIDsGet][195]
Table 'otrs.valid' doesn't exist, SQL: 'SELECT id FROM valid WHERE name =
'valid''

[Fri Mar 26 13:42:17 2010][Error][Kernel::System::Auth::DB::Auth][94] You
have an error in your SQL syntax; check the manual that corresponds to your
MySQL server version for the right syntax to use near ') AND  login =
'r...@localhost'' at line 1, SQL: 'SELECT pw, id  FROM  users  WHERE
valid_id IN (  ) AND  login = 'r...@localhost''

[Fri Mar 26 13:42:17

Re: [otrs] upgrade issue - no tickets displayed anymore

[Guillaume Rehm]

Can you track css files ? Use firebug to check wich css is called by 
your dtl files and check if css  files are in good place and if it's the 
latest version.


Le 16/03/2010 18:33, Gator SLP a écrit :

Ok, i replaced the entire HTML folder and i still am no further.

Please see screenshot of whats occuring 
http://img175.imageshack.us/img175/249/ticketissue.jpg


Appreciate the help so far.

thanks for any help.

Neil



On Tue, Mar 16, 2010 at 6:03 PM, Gator SLP nad...@gmail.com 
mailto:nad...@gmail.com wrote:


Hello,




On Tue, Mar 16, 2010 at 4:56 PM, Guillaume Rehm
guillaume.r...@bnu.fr mailto:guillaume.r...@bnu.fr wrote:

Normally, if you upgrade by RPM files, you have a report after
rpm -Uvh and you have list of warnings.

An other way is to delete all /opt/otrs/Kernel/Output/HTML
files and to copy it from tar ball. But you will lost all your
theme modifications. Not settings.

Le 16/03/2010 16:28, Gator SLP a écrit :

Hello,

Thansk for reply. Can you be a bit more specific as to what
steps you took to resolve. What files did you replace.  All i
can find is that the theme's are not supported from 2.3 to
2.4 so i set theme to standard but that has not fixed issue.
still getting empty tickets. i also removed the
AgentTicketQueue.pm and replaced it. That gave me the ticket
frames but no contents within each ticket are shown. Must be
something else that needs renewed.

thanks for any help.

On Tue, Mar 16, 2010 at 12:17 PM, Gator SLP nad...@gmail.com
mailto:nad...@gmail.com wrote:

Hello friends,
today on our test system i tried to upgrade OTRS. i went
from ITSM Core 1.2.2 to 1.2.3 using the packet manager.
Then i installed OTRS 2.4.7. Restarted OTRS. went back to
packet manager and it now allowed me to upgrade all
packages to 1.3.2 (general catalog, itsm core, and
addtional packages).  Did another restart of otrs.
Now when i log in i have the new dashboard which shows
the brief display of the tickets but when i go to any of
our queues or click on any ticket from the dashboard i
see nothing. I just have the queue at the top and a blank
display below.
Appreciate any help or ideas as to whats gone wrong, im
unable to find anything in support doc's, hence why i ask
for your experience and knowledge.
Neil Simpson



-
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 NEW! ENTERPRISE
SUBSCRIPTION - Get more information NOW!
http://www.otrs.com/en/support/enterprise-subscription/


-- 
Guillaume REHM

Centre de Ressources Informatiques
Responsable Sécurité du Système d'Information (RSSI)

Bibliothèque Nationale et Universitaire de Strasbourg
5 rue du Maréchal Joffre
BP 51029
67070 Strasbourg

tél: 03 88 25 28 23
fax: 03 88 25 28 03
mail:guillaume.r...@bnu.fr  mailto:guillaume.r...@bnu.fr
web:http://www.bnu.fr


-
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

NEW! ENTERPRISE SUBSCRIPTION - Get more information NOW!
http://www.otrs.com/en/support/enterprise-subscription/




-
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

NEW! ENTERPRISE SUBSCRIPTION - Get more information NOW!
http://www.otrs.com/en/support/enterprise-subscription/


--
Guillaume REHM
Centre de Ressources Informatiques
Responsable Sécurité du Système d'Information (RSSI)

Bibliothèque Nationale et Universitaire de Strasbourg
5 rue du Maréchal Joffre
BP 51029
67070 Strasbourg

tél: 03 88 25 28 23
fax: 03 88 25 28 03
mail: guillaume.r...@bnu.fr
web: http://www.bnu.fr

-
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

NEW! ENTERPRISE SUBSCRIPTION - Get more information NOW!
http://www.otrs.com/en/support/enterprise-subscription/

Re: [otrs] upgrade issue - no tickets displayed anymore

[Guillaume Rehm]

Did you upgrade OTRS with targz or RPM ? I have upgraded with RPM and 
some files wasn't put in directory with the good name (because hand 
modification). So, ajax lookfeel was bugy.


I delete old previous version and put newest files. And now it works.

Hope this help.

Le 16/03/2010 12:17, Gator SLP a écrit :

Hello friends,
today on our test system i tried to upgrade OTRS. i went from ITSM 
Core 1.2.2 to 1.2.3 using the packet manager. Then i installed OTRS 
2.4.7. Restarted OTRS. went back to packet manager and it now allowed 
me to upgrade all packages to 1.3.2 (general catalog, itsm core, and 
addtional packages).  Did another restart of otrs.
Now when i log in i have the new dashboard which shows the brief 
display of the tickets but when i go to any of our queues or click on 
any ticket from the dashboard i see nothing. I just have the queue at 
the top and a blank display below.
Appreciate any help or ideas as to whats gone wrong, im unable to find 
anything in support doc's, hence why i ask for your experience and 
knowledge.

Neil Simpson


-
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

NEW! ENTERPRISE SUBSCRIPTION - Get more information NOW!
http://www.otrs.com/en/support/enterprise-subscription/


--
Guillaume REHM
Centre de Ressources Informatiques
Responsable Sécurité du Système d'Information (RSSI)

Bibliothèque Nationale et Universitaire de Strasbourg
5 rue du Maréchal Joffre
BP 51029
67070 Strasbourg

tél: 03 88 25 28 23
fax: 03 88 25 28 03
mail: guillaume.r...@bnu.fr
web: http://www.bnu.fr

-
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

NEW! ENTERPRISE SUBSCRIPTION - Get more information NOW!
http://www.otrs.com/en/support/enterprise-subscription/

Re: [otrs] upgrade issue - no tickets displayed anymore

[Gator SLP]

Hello,

Thansk for reply. Can you be a bit more specific as to what steps you took
to resolve. What files did you replace.  All i can find is that the theme's
are not supported from 2.3 to 2.4 so i set theme to standard but that has
not fixed issue. still getting empty tickets. i also removed the
AgentTicketQueue.pm and replaced it. That gave me the ticket frames but no
contents within each ticket are shown. Must be something else that needs
renewed.

thanks for any help.

On Tue, Mar 16, 2010 at 12:17 PM, Gator SLP nad...@gmail.com wrote:

 Hello friends,

 today on our test system i tried to upgrade OTRS. i went from ITSM Core
 1.2.2 to 1.2.3 using the packet manager. Then i installed OTRS 2.4.7.
 Restarted OTRS. went back to packet manager and it now allowed me to upgrade
 all packages to 1.3.2 (general catalog, itsm core, and addtional packages).
 Did another restart of otrs.

 Now when i log in i have the new dashboard which shows the brief display of
 the tickets but when i go to any of our queues or click on any ticket from
 the dashboard i see nothing. I just have the queue at the top and a blank
 display below.

 Appreciate any help or ideas as to whats gone wrong, im unable to find
 anything in support doc's, hence why i ask for your experience and
 knowledge.

 Neil Simpson

-
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

NEW! ENTERPRISE SUBSCRIPTION - Get more information NOW!
http://www.otrs.com/en/support/enterprise-subscription/