Try TT Now

Error Messages

You may encounter error messages while using FMDS. The severity of these messages varies. Some may require you to take action, while others might just be informational. Tables of these error messages are listed below. They are categorized by whether or not the error requires you to take action:

Always Needs Action

Error

Responder will not serve a TradeCalendar document, because "-t" wasn't specified on the command line.

  • Affects

    : TTFMDSResp
  • Cause

    : The service's startup parameters are not correct.
  • Action

    : Edit the "ImagePath" setting in the registry for the TTFMDSResp service.
Error

Messaging_ilb detected unknown exception inside TTM mainloop.

  • Affects

    : TTFMDSResp
  • Cause

    : Internal error processing a request or update from the feed.
  • Action

    : Escalate to Engineering.
Error

Could not recover database.

  • Affects

    : TTFMDSResp
  • Cause

    : Responder could not recover the database after a crash.
  • Action

    : Check for permissions problems or disk full state. Once you identify and correct the issue, you can manually edit the SafeStore.dat file to force FMDS to think the database is in the "CLEAN" state.
Error

FMDSAuth child reports "Error" and msg "TTM problem".

  • Affects

    : TTFMDSResp
  • Cause

    : TTM daemon configures in Guardian is wrong or unreachable.
  • Action

    : Check remote daemon settings in Guardian. Chack local daemon status if not in remote. Restart responder.
Error

Parsing trade calendar XML file: An exception occurred!

  • Affects

    : TTFMDSResp
  • Cause

    : There are permissions or ownership errors on the TradeCalendar.xml file.
  • Action

    : Verify the TradeCalendar files have correct permissions.
Error

Responder main caught unknown exception.

  • Affects

    : TTFMDSResp
  • Cause

    : Internal error.
  • Action

    : Restart FMDS and escalate to engineering.
Error

Responder will exit, because it couldn't either load or parse TradeCalendar.xml.

  • Affects

    : TTFMDSResp
  • Cause

    : There is a syntax or semantic error in a TradeCalendar.xml file.
  • Action

    : Fix the TradeCalendar.xml file.
Error

Application's pre-loop fn threw: Error 0002: Can not create session: OS Error 01060: Can not connect to daemon.

  • Affects

    : TTFMDSFeed
  • Cause

    : The daemon settings for the TTFMDSFeed process are incorrect, or the ttmd process is down.
  • Action

    : Check service startup parameters in the services application or registry and ensure that the daemon string matches the desired location of the ttmd.
Error

Login rejected.

  • Affects

    : TTFMDSFeed
  • Cause

    : There is a gateway login issue. FMDS will lose data because it cannot get the INTERNAL login to the gateway.
  • Action

    : Restart TTFMDSFeed service. Check price server for errors. Escalate to engineering if price server is configured correctly.

Often Needs Action

Error

FMDS appears to have terminated unexpectedly, and has probably lost data that had not yet been written to disk. The FMDS database is otherwise intact.

  • Affects

    : TTFMDSResp
  • Cause

    : FMDS has recovered from a crash and may have lost some data just prior to the crash.
  • Action

    : Collect logs and minidumps to investigate the crash. The Responder is running and new data is being collected.
Error

Do not have write permissions for key "HKEY_LOCAL_MACHINESOFTWARETrading TechnologiesServicesTTFMDSResp”.

  • Affects

    : TTFMDSResp
  • Cause

    : FMDS is starting up or shutting down. There was an installation error. The registry tree for FMDS isn't as expected. ttchron will likely not be able to restart FMDS.
  • Action

    : Restart FMDS manually if necessary and escalate to engineering.
Error

Ignoring invalid instrument 9153 (ICE_IPE.ICE Brent-WTI Spr Sep09.iSpread ICEOTCSchedule) on line 705 of fmds.cfg.

  • Affects

    : TTFMDSFeed
  • Cause

    : There is a syntax error in the fmds.cfg file.
  • Action

    : Check the syntax of the specified entry in the fmds.cfg file. It is located here: <rootdrive>:ttconfigfmds.cfg
Error

Can't find TTFMDSFeedParametersAppDirectory registry setting for service.

  • Affects

    : TTFMDSFeed
  • Cause

    : There is a syntax error in the fmds.cfg file.
  • Action

    : Check the syntax of the specified entry in the fmds.cfg file. It is located here: <rootdrive>:ttconfigfmds.cfg

Sometimes Needs Action

Error

Can't find TTFMDSFeedParametersAppDirectory registry setting for service.

  • Affects

    : TTFMDSFeed
  • Cause

    : Either the feed process is running intentionally without being properly installed, there is an installation error, or the registry has been tampered with.
  • Action

    : Check registry settings for TTFMDSFeed service.

Seldom Needs Action

Error

TTFMDSResp Service was requested to stop.

  • Affects

    : TTFMDSResp
  • Cause

    :Somebody stopped the responder service.
  • Action

    : If unintentional, restart the responder.
Error

Neg qty (-24) seen (setting to 0); chk GAL flags.

  • Affects

    : TTFMDSResp
  • Cause

    : A gateway might have the wrong GAL setting for "Has non-accumulating LTQ", the feed was restarted, it's the beginning of a trading day, or a gateway has just come up.
  • Action

    : If you aren't getting complaints from XT users about LTQ values, this is totally benign.

Never Needs Action

Error

Not computing "last minute" remainder; data is complete.

  • Affects

    : TTFMDSResp
  • Cause

    : Not an error.
  • Action

    : N/A
Error

Archiving datfiles/fmdssafe/Warm.h5 to datfiles/fmdssafe/archive_2009-11-30-0009.h5.

  • Affects

    : TTFMDSResp
  • Cause

    : The Warm.h5 file has grown past either the size or total records threshold and is being demoted to an archive.
  • Action

    : N/A
Error

TTFMDSResp Service stopping b/c system is shutting down.

  • Affects

    : TTFMDSResp
  • Cause

    : The system is rebooting.
  • Action

    : N/A
Error

Couldn't prime accumulator for this request; leading data loss could occur.

  • Affects

    : TTFMDSResp
  • Cause

    : The lower time bound of a request was at or near the beginning of recorded data.
  • Action

    : N/A
Error

Saw LTQ before LTP in price update for instrId 104.

  • Affects

    : TTFMDSFeed
  • Cause

    : Some gatways have inconsistent price update publication, but TTFMDSFeed handles this properly.
  • Action

    : N/A
Error

Found series for eCBOT-A.ZN Dec06.Future, key=FFZN 061200000F.

  • Affects

    : TTFMDSFeed
  • Cause

    : Indicates a configured contract was found in the product table, and gives its series key.
  • Action

    : N/A
Error

Requesting contracts (delayed) for: (product = 6E-TT, type = FUTURE).

  • Affects

    : TTFMDSFeed
  • Cause

    :The feed is retrieving product table information from a gateway in response to some event.
  • Action

    : N/A

Diagnostics

Error

There were no non-default feed queue threshold values configured.

  • Affects

    : TTFMDSResp
  • Cause

    : FMDS is using the default values for feed queue thresholds.
  • Action

    : None. This is normal unless the client should be using special settings due to higher than usual volume or a larger than usual amount of available memory.
Error

Overriding performance reporting interval to 10.

  • Affects

    : TTFMDSResp
  • Cause

    : Someone has edited the registry setting for the performance reporting interval.
  • Action

    : More or fewer performance log messages than normal will be logged; the default is 300 sec (five minutes).
Error

Request from user qa01@TE11-BC-4B-065.

  • Affects

    : TTFMDSResp
  • Cause

    : An X_STUDY client or FMDSConsole user made a request to FMDS.
  • Action

    : For diagnostics, every request is logged along with the user name and the machine.
Error

Received Market Profile request for CME.6E Jun09.Future (logic:MP01).

  • Affects

    : TTFMDSResp
  • Cause

    : An X_STUDY client or FMDSConsole user made a data request to FMDS.
  • Action

    : For diagnostics, every request is logged along with its parameters. Look earlier in the log to see who made the request.
Error

Took 00:00:00.006832 to compute 200 points in range 2009-Feb-09 11:32:00 to 2009-Feb-10 15:56:00.

  • Affects

    : TTFMDSResp
  • Cause

    : Computation for a request is complete.
  • Action

    : Shows how long the previously logged request took to process, not including communication of the results back to the client; useful for diagnosing response time issues (slow chart loading).
Error

Nothing to flush.

  • Affects

    : TTFMDSResp
  • Cause

    : Special diagnostic enabled.
  • Action

    : N/A
Error

2009-Dec-04 05:59:51.355099,13344,13343,13344,5,9,3,11303,Unchanged,Buy,1.

  • Affects

    : TTFMDSFeed
  • Cause

    : The feed is running with the "-v" (verbose) option set.
  • Action

    : If this is not intentional, check the options on the "ImagePath" setting for the TTFMDSFeed service in the registry.