MaxEnt 5.1 SQL : transaction control error

Hi Patrice,

I'm not familiar with this specific problem. Error 19 is a write error and is possibly due to infufficent writes - I think maybe temp database size/log file space can also cause the error. The error 8 is probably just the result of the error 19.

I'm assuming the log file is from the server and I'm Guessing but at this stage in the update I think its trying to mark entries as finished with in the transation file and possibly it will be updating the counts in the distribution list. Particularly using email if there's a problem logging on to the email in box Max Echange can do the updates then fail to note in the distribution list its done them. Really with out seeing the system in more detail its hard to say more from your comments.

Regards,

Ian Wallace
CABC

Hi Ian!

We've some further testing: everything is working properly. Data is synchronized properly, information on packets sent and read is ok. In fact, Maximizer seems to be working fine! All, except these errors in SPDM.LOG when we activate the detailed logging options from the MaxExchange Server program.

I have successfully reproduced the error on 4 different systems up to now!!!

I have tried (unsuccessfully) to "trace" the SQL statements that get sent to MS SQL 7.0 (SP2) but I cannot see on which statement the errors occur... We have WinNT4 SP6a Workstation for the MaxExchange Server, with one remote as Win98 and one as Win NT4 workstation. The first time we synchronize the error doesn't appear, but once its there, if there for each sync containing data, and NOT there for sync with no data. BTW, I have had these errors in the log with Network Sync also!!!

Any chances it might be related to the way MaxExchange works ? Could it be "normal" to see those messages in the log ?

Many thanks for your help!
Patrice

Hi Again!

I have done some further testing with other setups (SQL 6.5 SP5a) and seen the same message arise! I 've done some further testing with SQL Trace and I've noticed that everytime there is a new entry in Maximizer (remote or local) and a packets are processed on the MaxExchange Server, the earliest record (by record_id) of the transactions table is erased!!! Why is that ? Shouldn't it be the last record ??? I think we're on to a (((bug))) here! Can you reproduce the error (set Logging options under View on the MaxEchange Server program to show server activity (SPDM.log) and log details set to high. Do more than one sync, and the error codes 19 and 8 are sure to show in the SPDM.LOG file (under maxechange directory on the maxechange server).

My question is: does that eventually affect adversly the proper working of Maximizer ???

Many thanks again!
Patrice