Hi,
some points inline
"Graham T. Smith"
Some points of clarification.
You seem to be suggesting that you have a 1.3.1 otrs database backending for a 1.2.4 otrs system. As the database schema is different between 1.2.x and 1.3.x would suspect that this could cause a few problems. If on the otherhand you have a unupgraded 1.2.x database being accessed by a 1.3.x otrs setup the 1.3.x setup will tend fall apart. Both 1.2.4 and 1.3.1 accessing the same dataset sounds like one of those interesting experiences :-)
I have 1 Linux server and an XP vmware session. The Linux box has 1.31 (always has) and the XP box has 1.24. In order to get access to the tickets for billing purposes :) and troubleshooting I have pointed the XP install at the Linux database.
The problems you are reporting seems to be consistent with a 1.2.x database being used with 1.3.x (at least in my experience), it is possible that the database itself was not upgraded when you upgraded to the new distro if you were originally running 1.2.x. You do not report what version of otrs was installed before you upgraded the distro.
I have no functionality at the moment with otrs running on the linux box but will check the mod_perl suggestion above. OTRS was the same version before the upgrade to the linux box, and otrs has not been upgraded. So there is the possibility of corrupting the database if I work on it thru the XP otrs install but thats not an issue as I dont want to add any info to it at the moment, thanks for the help so far.
On Fri, 2005-06-17 at 10:09 +0100, Des Quinn wrote:
Hi and thanks for the reply.
I did not upgrade from 1.2 to 1.3.1, as the upgrade I performed was on the linux box. The otrs version stayed at 1.3.1 while apache, perl, and mysqls version changed. The current windows vmware session has otrs 1.2.4 on it at present but is pointing at a 1.3.1 database on the "broken" linux machine.
<snip>