Hello all, Since I turned debugging on, I realized my code wasn't as as perfect as I thought :-) ! So now I am using LOGGINGLEVEL=LogLevel1 and get occasionally errors ( [Error] 170, Error] -101, incorrect MSSQL operation in most of the cases ). The debugging information does not offer enough to pinpoint the offending code. I am under the impression that enabling higher logging levels would have a severe impact on a production server, and I cannot reproduce the error on the development system. So, I have modified the error.htx to record all errors, and I also provide an entry for the users to explain the event, but so far without success (they just don't bother entering the information). I am looking to get information similar to that displayed when debugging is enabled. My server is running: WindowsNT /SP4, Tango 2000/SP1, MSSQL 7
Questions: 1- Is there any way I can get more meaningful information to help in the debugging ? Or is there another way to gather more information about the problem? MSSQL problems of this sort can be solved by redesign, of course; so the solution should be applicable to any type of errors. 2- We are going to buy wiTango 5.0 next month. Is debugging any easier in witango 062 ? 3- Has anybody experienced the cookie buffer overflow problem? I am interested in what was recorded (in logging files) and if both the Tango Server and Tango ServerWatcher quitted working. Many thanks, Mihai. ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/maillist.taf
