Eric,

> I have Witango 5.01.062 on a Windows 2000 machine running IIS and MySQL
> (and the latest MySQL ODBC drivers).
> 
> Whenever I run a tango script that hits the database (I've only tested
> Search actions so far), the first ever action runs fine.  Every
> subsequent Search action fails with an "Unrecoverable OS Exception"
> error being written to the Application log.  This isn't limited to a
> single script, either.  That is to say, I have a login script that does
> a single search.  The first time I run it, I log in fine.  From that
> point on, every tango script that has a Search action, including that
> login script, fails.

This sounds like a library that is not playing nicely or a permission issue
stopping something loading correctly.  Your installation is the same config
as one of the servers in our lab which is working fine.  You have said that
you are using the MyODBC 3.51.06 driver.  Are you also using the latest
MySQL DB server 3.23.57 or 4.0.14 builds.  If not make sure that you upgrade
to them.  Have you installed MySQL into c:\mysql?

Also make sure that you are using the latest MDAC 2.7 SP1 or 2.8 which is
now available.  http://www.microsoft.com/data



> Also, when I then try to do a Stop/Start on the Witango 5 service, the
> Stop fails saying that it was unable to successfully stop the service
> "in a timely fashion" (and then it no longer gives me the option to
> stop or start).  I am forced to reboot the server for it to start
> working again.

The witango server process will wait for up to QUERYTIMEOUT (see witango.ini
file) second before shutting down to allow any active application files to
complete there execution.  Once all the app files have finished the service
will stop.  If you have an app file stuck communicating with the DB you may
need to wait for it to timeout.  Alternately there are kill tools that will
just terminate a process.  It is not a recommended thing to do over and over
again as it can leave memory in an unpredictable state, but the OS is pretty
good at releasing most the memory owned by a process these days.

At http://www.beyondlogic.org/consulting/processutil/processutil.htm is a
tool that is very useful for managing processes.  Just simply get the PID
from the process list and kill it and start the service again.  No need to
reboot.  It works outside of the processes security context so unlike the
task manager you can kill any process.

Also if you do not have the Windows 200x Resource Kit, this is the page to
go to:  http://www.petri.co.il/download_free_reskit_tools.htm  It is a
collection of very useful tools for Windows Server Sys Admins and includes
the kill tool.  A lot of these tools can be wrapped in a batch file and used
to remote admin your server via witango.


Phil

________________________________________________________________________
TO UNSUBSCRIBE: Go to http://www.witango.com/maillist.taf

Reply via email to