The first thing I would do is inquire with
[EMAIL PROTECTED] to see if you can
get the latest build of the server for testing. The reason I say this is
because depending on the version you currently have, this situation might have
already been fixed. Keep in mind that versions of the server which may be
available through this method are not considered release product, and you
should carefully weigh your options for using such software.
I also suggest that you verify that all
linked libraries are loading properly, and their latest versions. I run a
windows server so while this still applies, I can’t give you specifics
about your configuration.
Robert
From: Susan Brkich
[mailto:[EMAIL PROTECTED]
Sent: Tuesday, October 10, 2006
12:17 PM
To: [email protected]
Subject: Witango-Talk:
Client/Plug-in Error on Mac Tiger Server, Witango Server 5.5
Hi,
Just this past week, we've suddenly been having our Witango server crash
repeatedly, with the following error message:
Client/Plug-in Error
Error Code: 605
The client encountered problems in communicating with the application server.
Please check witangoevents.log for further information.
----------
There's nothing in the witangoevents.log (it apparently hasn't logged a thing
since we set up this server last December, not sure if that's normal).
Only recent change is that about a month or so ago, I upgraded the Tiger Server
from 10.4.4 to 10.4.7 (after researching and not finding any reports of
problems doing this).
The Witango Server seems to be crashing at one specific point in a taf file,
from what I can figure out so far. At that point, a click of a link in the taf
is supposed to load detailed biographical data on a designated person, pulling
that data from 10 different Filemaker databases, some of which have over 50,000
records. We've been using this taf file and these FileMaker databases in this
format for several years, with minor updates to the files and periodic
refreshes of the FileMaker databases. Never had this problem before.
I researched the Witango Talk archive files and found some advice from Phil to
another user with the above plug-in error, saying to set the CLIENTIOTIMEOUT to
600 in the clients. ini file. I did that, with no effect.
I've also noticed that the witangod.crash.log reports a link error, saying that
the libjs32.dylib is not loaded and referenced from witangod. (Apparently it
hasn't been loading since we upgraded Witango to 5.5 last December.) This file
does exist in the WitangoServer/5.5 folder, same level as witangod. Could this
be my problem, and if so, anyone know how to fix it?
Again, our configuration is Mac OS X Server 10.4.7, Witango Server 5.5.
Thanks for any help anyone can offer.
Regards,
--
Susan A. Brkich '86
Web Administrator
Alumnae and Alumni of Vassar
College
161 College Avenue
Poughkeepsie, NY 12603-2804
Phone: 845.437.5449
Fax: 845.437.7425
Email: [EMAIL PROTECTED]
On the web: http://www.aavc.vassar.edu
AAVC's Online Community allows the more than
35,000 Vassar alumnae/i
to reconnect with their Vassar experience. Alumnae/i can register at
www.aavc.vassar.edu.
