Hello Dan,
I've come across this using MS SQL server before. It seems to be a problem
when you set the isolation level to "Read/Write Exclusive".
Anotherwards, WiTango tries to open the MS SQL table in exclusive mode,
leaving the table to only be opened by others in Read mode only. So, if the
WiTango app is being executed by someone else, and tries to write to the
table at the same time, MS SQL returns an error saying that the table is
unable to be written to. This is where the problem lies.
Either MS SQL isn't returning a n error message that the WiTango server
understands, or WiTango doesn't understand the error and crashes.
I was using MS SQL server 7. When I updated to the latest service pack (I
believe it was SP 5) for MS SQL server, the WiTango server still crashed,
but randmoly and at the most frequency of once a month.
This error does not apply to Pervasive SQL and Oracle databases because
their database tables are seperate files, where as MS SQL tables are all
stored in one big mdf!
Best Regards,
Web Energy
Rick Sanders,
Tel: (514) 620-3006
Fax: (514) 620-3017
Email: [EMAIL PROTECTED]
Web: www.webenergy-sw.com
> This problem drives me crazy...
>
> It took my college and I ages to figure what happening:
>
> After developing a witango application on a developing machine on which
> everything works fine, we moved the whole thing to our server - Win 2000 /
> MS SQL. We're using the developing version on the first (developing)
> machine, the Witago server on the other.
> All seems to work but on every action than uses Begin Transaction ... End
> Transaction Witago Service crashes. The logs shows that the service
> unexpectedly terminated. The service is being restarted, but database
> connectivity doesn't work anymore... until the service is manually stopped
> and restarted again. When removing the transaction code things work as
> expected. Of course, leaving the transaction out in a production
environment
> is unacceptable. Anyone with similar experience or maybe even a solution?
>
> Dan
>
> ________________________________________________________________________
> TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED]
> with unsubscribe witango-talk in the message body
>
________________________________________________________________________
TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED]
with unsubscribe witango-talk in the message body
