Re: "Your request produced an error."

There are other apps on the same server (in different freebsd jails) that talk to the same db server.   (Both are VMs on the same HW).

As fasr as I can tell the app config file has not been corrupted.  Visually dumping out the text files as well as looking in the JavaMonitor it looks ok, and the eo connection dictionary is ok (that is how I got the info to log in to the db using sql92).

I have not tried using sql92 on the app server as it is not installed.  I'll see if I can install it (there was an issue that FB support for FreeBSD dropped and it did not work on newer versions of FreeBSD, though that might not affect the sql92 component).

I grabbed the latest frontbase jdbs driver and put that on the app server but it did not help.

I wish that WO would actually let me see the exception somewhere so I could see what it is complaining about.

I will go recheck all the config files and connection dictionaries etc, to make sure they are all 100% correct and my brain is not mentally seeing what it wants to see versus what is there...

Thanks for all your help
Chad


On Sep 19, 2013, at 9:40 AM, Chuck Hill <[email protected]> wrote:

> You are certain that no one has changed anything?  The app server can talk
> to the db server?  I might be worth trying to connect to the db server
> using sql92 on the app server.  Did the app's configuration file get
> corrupted?  I can't think of much else that would cause this.
> 
> 
> 
> Chuck
> 
> 
> On 13-09-18 8:48 PM, "objectwerks inc" <[email protected]>
> wrote:
> 
>> 
>> On Sep 18, 2013, at 9:09 PM, Chuck Hill <[email protected]> wrote:
>> 
>>> Hi Chad,
>>> 
>>> My first guess given that nothing has change is that the database is
>>> corrupt or stopped.  Can you connect with FrontBase Manager?
>>> 
>>> 
>>> Chuck
>>> 
>> 
>> 
>> Hi Chuck
>> 
>> Yes, I can log in to the db using FrontBase Manager (my FB manager is
>> messed up on my Mac so after logging in I don't get a window, but this
>> happens with all the DBs I have on the db server, and is not related I
>> think since the other DBs and apps work fine though they exhibit the same
>> issue when I log in throgh FB Manager -- I can log in using the command
>> line sql92 and it shows a FB Manager connection and I can also interact
>> with the DB using sql92 command line tool).
>> 
>> So the DB is running and does not appear to be corrupt since I can access
>> and query it in sql92.
>> 
>> I've been trying to get the app to show my whatever exception is causing
>> the error, to no avail.
>> 
>> Chad
>> 
>