[DUG] Terminal server and FlashFiler
Conor Boyd
Conor.Boyd at trimble.co.nz
Thu Dec 21 10:47:29 NZDT 2006
Yeah, 50 days sounds like the key.
The Windows API function that returns the number of seconds (?) since
the PC started wraps round to 0 after about 49 days. So whatever your
application or database is doing, it may be using that function
somewhere?
I can't remember the name of the API call, if I do, I'll post it later.
Ah, found it. GetTickCount(). Wraps round to 0 after 49.7 days.
HTH, and Happy Christmas to you all too...
Conor
________________________________
From: delphi-bounces at ns3.123.co.nz [mailto:delphi-bounces at ns3.123.co.nz]
On Behalf Of Leigh Wanstead
Hello everyone,
Merry Christmas and happy new year ;-)
I have a question regarding to Terminal server and TurboPower FlashFiler
2. I am developing a delphi 7 application using open source FlashFiler
database server. FlashFiler database server is embedded inside my
application. If I run my application since the Terminal server reboot,
everything works fine. But somehow only happens to one particular
terminal server after running for 50 days, my application can't restart.
It report the error time out or database file can't be opened. I closed
my application and the database file can be renamed which proves that no
one has locked the file. The only solution I know of is rebooting the
terminal server. I can start flashfiler database server ffserver.exe and
ffe.exe in the open source package without problem even when my
application failed. I used database FFVerify.exe to verify the database.
There is no error in the database file. The terminal server is running
windows 2003 build 3790. The free memory left on that terminal server
machine is around 200mb.
I can't recreate the problem in my own terminal server.
Do you know what to look at?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://ns3.123.co.nz/pipermail/delphi/attachments/20061221/0246a4f7/attachment.html
More information about the Delphi
mailing list