im not sure if this helps but another part of this puzzle is that in the witango.log it says this when those errors are hit:
 
06/11/2003 10:15:38 156.3.113.43 [EMAIL PROTECTED] 3392 4 247312  [Error] -101 General error during data source operation.  
06/11/2003 10:15:41 156.3.113.43 [EMAIL PROTECTED] 3932 1 256  [Error] -109 This type of data source is not supported by the server license.  
06/11/2003 10:15:41 156.3.113.43 [EMAIL PROTECTED] 3932 1 257  [Error] -4 Unable to connect to the specified data source. Verify that data source is properly configured and that database server is online.
I attached the errors from the log in case that sheds any more light on things.
----- Original Message -----
From: Alan Wolfe
Sent: Thursday, November 06, 2003 11:05 AM
Subject: [RBASE-L] - strange errors

hey everyone,
 
About a year and a half ago or so, when we were using r:tango 2000 on NT 4, we started getting a couple wierd errors from oterro saying "general error during data source operation".
 
This is normaly pretty normal because usualy you have another error before that like it will say syntax error and then "general error...", but for these errors its 2 "general error..." messages with no further explanation.
 
Er...here i have an example of what i mean.  Normaly an error is like this, where it has an error message, then the general error message:
 
------------------------------------------------------------------------------------------
Error
An error occurred while processing your request:

APPFILE Path:/pvglobal/
APPFILE Name:ppo.taf
 Position: update_tranmaster_befo_acct_scr
Class: DBMS
Main Error Number: 122
Secondary Error Number: 0
Main Error Message: [RBTI][Oterro ODBC Driver][PVGLOBAL]-ERROR- Column needdate must be a valid DATE. ( 122)
Secondary Error Message: 22005

APPFILE Path:/pvglobal/
APPFILE Name:ppo.taf
 Position: update_tranmaster_befo_acct_scr
Class: Internal
Main Error Number: -101
Secondary Error Number: 0
Main Error Message: General error during data source operation.
Secondary Error Message:  

APPFILE Path:/pvglobal/
APPFILE Name:ppo.taf
 Position: update_tranmaster_befo_acct_scr
Class: Internal
Main Error Number: -101
Secondary Error Number: 0
Main Error Message: General error during data source operation.
Secondary Error Message: 
------------------------------------------------------------------------------------------
 
But these wierd errors we have been getting give no detail as to what the error is:
 
-------------------------------------------------------------------------------------------
 
Error
An error occurred while processing your request:

APPFILE Path:/
APPFILE Name:utils.tcf
 Position: sel_transfers
Class: Internal
Main Error Number: -101
Secondary Error Number: 0
Main Error Message: General error during data source operation.
Secondary Error Message: 

 
APPFILE Path:/
APPFILE Name:utils.tcf
 Position: sel_transfers
Class: Internal
Main Error Number: -101
Secondary Error Number: 0
Main Error Message: General error during data source operation.
Secondary Error Message: 
-------------------------------------------------------------------------------------------
 
the wierd thing about these errors too is that it doesnt seem to matter what the sql is when they error, it just happens randomly.
 
It works 99.999% of the time, which is really good except that small percent is starting to grow large enough to become a problem.
 
some example sql's its failed on are:
 
--------------------------------------------------------------------------------
sel sum(acctidamount) from tranacctid where acctid=87594 and transtate in ('A','B') and tranid not in (sel tranid from tranmaster where districtno='64436' and trantype='cty')
sel sum(acctidamount) from tranacctid where TranState='A' and acctid=113631 and tranid not in (sel tranid from tranmaster where trantype='CTY' and districtno='64436')
 
sel count(distinct tranid) from tranactions where (tranaction is null or tranaction='purchasing') and tranid in (sel tranid from tranmaster where districtno='64436') and userno=986
--------------------------------------------------------------------------------
 
but like i said, it works almost all the time, and when it fails, if we take the sql it failed on and paste it in at the R> prompt or something, it works fine, so i think it might be a configuration issue.
 
we were hoping r:tango 5 would clear this up, we are on windows 2003 server, and on new hardware but still have this same old problem.
 
a point of interest might be that we recently moved some common functionality (to get the balance of an account) into a tcf and since then, it has caused this error to happen more often in new places.
Anyone know what the problem might be or have any ideas?

Attachment: errors.log
Description: Binary data

Reply via email to