Hi Bernd,
Actually, there's another thread about my upgrade problems. I got
preoccupied with other issues at work and thus still haven't discerned
the reason for being unable to upgrade. I believe the next step was
to try rewriting the config file from scratch (using the 2.3.1 default
as a template), in the hope that it would fix the issues.
I'll get around to continuing the other thread eventually.
Thanks,
DK
On Apr 10, 2008, at 1:10 AM, Bernd Fondermann wrote:
Dain Kaplan wrote:
Mike,
I'm no JAMES expert, but we had the same problem with James 2.2
(upgrading has been a challenge for us thus far), and though our
solution was less than elegant, it did work.
Hi Dain,
concerning upgrading James. Is there anything we can do to help you
make it easier to upgrade?
Bernd
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
