Hello.
We have several different Decision Stream process that run at different times during the day. (the time is due to extracting data from the ERP tool from different countries).
One runs at 6:00pm. One at 2:30am. One at 5:30am. The last at 12:05pm.
On any given day, all processes from any job stream are completed within 45-60 minutes of starting, so there is no overlap of the job streams. They populate different tables in different datamarts housed in different named SQL databases on a single occurrance of SQL 2000.
We have Decision Stream logging set to the most detailed level for every step in every job stream. ALL steps run to completion SUCCESSFULLY. No Failures, no error messages.
If we check the list of processes in TASK MANAGER after each individual job stream completes, there are no RUNDSNODE.EXE still running. If we let all processes run without checking Task Manager in between, the next day we find a RUNDSNODE process still listed as ACTIVE - but we have no way of knowing which job stream spawned it. If we look through the logs, all is as it should be and everything ran successfully.
If we run each and every process during the day, in Production or development, no processes remain in Task Manager - we cannot duplicate this situation manually.
Does anyone have a clue as to what would cause the semminly hung RUNDSNODE process?
Or how to tell from TASK MANAGER what time it entered the system?
Thanks.
We have several different Decision Stream process that run at different times during the day. (the time is due to extracting data from the ERP tool from different countries).
One runs at 6:00pm. One at 2:30am. One at 5:30am. The last at 12:05pm.
On any given day, all processes from any job stream are completed within 45-60 minutes of starting, so there is no overlap of the job streams. They populate different tables in different datamarts housed in different named SQL databases on a single occurrance of SQL 2000.
We have Decision Stream logging set to the most detailed level for every step in every job stream. ALL steps run to completion SUCCESSFULLY. No Failures, no error messages.
If we check the list of processes in TASK MANAGER after each individual job stream completes, there are no RUNDSNODE.EXE still running. If we let all processes run without checking Task Manager in between, the next day we find a RUNDSNODE process still listed as ACTIVE - but we have no way of knowing which job stream spawned it. If we look through the logs, all is as it should be and everything ran successfully.
If we run each and every process during the day, in Production or development, no processes remain in Task Manager - we cannot duplicate this situation manually.
Does anyone have a clue as to what would cause the semminly hung RUNDSNODE process?
Or how to tell from TASK MANAGER what time it entered the system?
Thanks.
