April 07, 2006, 04:08 AMTony Howes
DM533 Edaprint problems ...
We have experienced a problem where the DM533 Edaprint stops logging entries. For example:
04/05/2006 22:10:00 accepting FDS connection 04/06/2006 08:30:22 accepting xxxxxx
The edaprint stopped logging entries at 22:10 and didnt continue logging again until I manually logged in to the DM533 client the following morning (08:30).
Additionally when logging in to the client after this problem has occurred I am able to view Flows but if I try to run a job deferred a dialogue box appears and the time counts infinitely (looking on the console at this point and no job is recorded in the agents or deferred list). This also happens if I try to view the statistics table within the client (DM Reports).
The net result is that we have to logon to the console, restart the workspace and re-create the log and statistics table. We are then able to run our schedule successfully and view the reports.
For info we are running:
Data Management Console
Config date 09/24/2004
Build date 12/14/2004
Gen Number 07.01
Source Date 12/14/2004 11:53:50
We have raised this with our local IB CRC. We would appreciate any help and advice.
April 11, 2006, 03:59 PMnewtofocus
Here might the possible causes:
1) Your DFM listner is not running.
2) Check if your FDS listner and scheduler are active
3) Is it possible that you are writing too much into your etllog.foc file?. This could bring down FDS, which inturn needs them to be recreated.
If this is not the case plese let me know why it is happening, I would be interested.