This content has been marked as final. Show 4 replies
This is the output I get what ever I try to do with ttDaemonAdmin:
TimesTen Release 188.8.131.52.1 (64 bit NT) (tt1122_64:53396) 2012-10-30T06:32:14Z
Instance admin: nikola.bajic
Instance home directory: C:\TimesTen\TT1122~1\
Daemon home directory: C:\TimesTen\TT1122~1\srv\info
Failed to determine TimesTen Server process information.
Error code: TT799. Unable to connect to daemon; check daemon status)
TimesTen status report as of Thu Nov 22 15:14:16 2012
Daemon pid 5092 port 53396 instance tt1122_64
No TimesTen server running
Accessible by any group
End of report
I use TimesTen on Windows 7 Professional 64-bit every day and it works fine so there is something specific in your setup. Do you have a 3rd party firewall or security solution that intercepts communication installed? Is something else already using the port (53396)that the dameon is using?
It looks like the main daemon has started - using port 53396, but the main ttcserver process, which uses port 53397 by default, has not been spawned by the main daemon.
It's probably best to try to do
then check the ttmesg.log file in
to see what errors it reports when the main daemon tries to spawn the main ttcserver.
We've seen before that 32bit TT on Windows has dependencies on some old .dlls which were missing. It might be something similar to this for 64bit. This was diagnosed before by running the ttcserver executable manually and see the Windows error dialogue. In 11.2.2. this is C:\TimesTen\tt1122_64\bin\ttcserver1122
I know that it shouldn't be Win7 problem, I installed it on home computer without any problems. Also, I installed X-NetStat and listed all ports used by applications but none of them is using same port as tt main daemon. So, the only thing that might be a problem here is firewall or security system, so I'll talk to administrators and hopefully they will make it work. ;) Thanks for quick reply
ttcserver process is started, I can see it in Windows Task Manager, but comunnication with the daemon is problem. I cannot even execute ttDaemonAdmin -stop command, it throws "Unable to connect to daemon" massage. If the daemon is not started I can start it with ttDaemonAdmin -start, but after that I can't comunicate with it anymore.