Within one of our environments the Exchanger engine keeps going down for what seems like for no reason. We then have to manually go in and start the engine. Is there any reason for the Exchange engine to go down? This is Windows 2003 environment, non-clustered. This is happening two to three times a day, at what seem to be random times.
Solved : Exchanger Engine Idle
Started by Comm. of Pa L&I, Dec 23 2009 03:23 PM
3 replies to this topic
#1
Posted 23 December 2009 - 03:23 PM
#2
Posted 23 December 2009 - 04:42 PM
try to get some logs and events in the log files and in the windows event viewer
#3
Posted 23 December 2009 - 05:25 PM
Hello,
If you don't get any lead through the log files (system log file, network alarm, Dollar Universe log files), one way to check if the issue is linked to the exchange data is to reinitialize those 2 files (u_fecd50.*, u_fecl50.* in the data folder of the appropriate Area).
You may reinitialize those files - to do so contact Tech Support. If the issue reappears or if you'd prefer not to reinitialize data files, run a uxtrace with options s, c & f9, open a ticket at Tech Support and attach the results so they can investigate.
Michel
If you don't get any lead through the log files (system log file, network alarm, Dollar Universe log files), one way to check if the issue is linked to the exchange data is to reinitialize those 2 files (u_fecd50.*, u_fecl50.* in the data folder of the appropriate Area).
You may reinitialize those files - to do so contact Tech Support. If the issue reappears or if you'd prefer not to reinitialize data files, run a uxtrace with options s, c & f9, open a ticket at Tech Support and attach the results so they can investigate.
Michel
#4
Posted 20 January 2010 - 08:53 AM
Hello,
I would add as well : check if you have any error messages in the windows event log
And check if you have a workflow running at each of the occurency or if a user does a distribution... those kinds of manipulation.
Cheers,
Guillaume
I would add as well : check if you have any error messages in the windows event log
And check if you have a workflow running at each of the occurency or if a user does a distribution... those kinds of manipulation.
Cheers,
Guillaume
ORSYP R&D Integration
1 user(s) are reading this topic
0 members, 1 guests, 0 anonymous users













