SSPI context

[Farah Mansor]

Hi all, :) I just create one program using timer and it connect to database to process something. I try to leave my program running one day, but what I get next morning is it prompt out a dialog box say "Cannot generate SSPI context". I don't know what it is.:confused: + X| +:(( Can anybody help me to resolve on this?? I really appriate it. Thank you. :rose: FM

[Tomasz Sowinski]

I just create one program using timer and it connect to database to process something. This means that you open database, write something, and close database every XXX seconds? Tomasz Sowinski -- http://www.shooltz.com

[Farah Mansor]

Yes. But it will continue to loop after it finishing the task (open, write and close). This is done by using KillTimer and SetTimer back. :| Thanks in advance. p/s: My supervisor said it is because my program keep generating a user in the database until it exceeds the limit and gives me that dialog box saying "cannot generate SSPI context". Could this be the problem?? But I already check my code and I close every database that I open. X| +:confused: = :(( FM

[Tomasz Sowinski]

My supervisor said it is because my program keep generating a user in the database until it exceeds the limit and gives me that dialog box saying "cannot generate SSPI context". Could this be the problem?? Exactly, it looks like resource leak. SSPI == Security Support Provider Interface; it's used to "establish authenticated connections and to exchange data securely over those connections". To avoid problems with long period of time before error occurs, replace the timer and use database in a tight loop: you should see the problem much earlier. Tomasz Sowinski -- http://www.shooltz.com

[Farah Mansor]

:( How to replace the timer, and with what?? And can I know what do you mean by using database in a tight loop?? This application cannot be stopped or closed, unless there is a network connection error. Could be the network error?? X| Thank you so much for your help.:rose: FM

[Tomasz Sowinski]

To diagnose and fix the error you need to make it easier to reproduce - waiting many hours for SSPI context error is a waste of time, right? Two solutions are possible: 1) easier: set the timer elapse period to 10 msec. 2) create an infinite loop that repeatedly calls database code. This will be marginally 'faster', but application will not respond to menu selections, etc. I'm not sure if automatic error detection tools like BoundsChecker can detect problems with SSPI. If you have such a tool, give it a try. Tomasz Sowinski -- http://www.shooltz.com