JimFromCanada
Programmer
Regarding these two previous posts from June 2024 and July 2024 (I can't post a follow-up within those topics, likely due to age):
The culprit was seemingly a 'ghost' node which did not exist but was somehow in the database acting as a backup server.
The reason why the IFS errors were so sporadic and inconsistent was due to this 'ghost' server and how often the hosts file would be updated on the terminals.
The processing of any IFS activities would halt seemingly at random and interrupt workflows. It appeared as though messages were actually being redirected to this non-existent IFS server mid-workflow.
For searchability, this primarily manifested itself as 'IFS_ADAPTER_ERROR' but there were other breadcrumbs that were also frequent including 'IFS error status -20', 'IFS_RECEIVE_TIMEOUT', 'IFS_PROXY_ERROR', '0xc70700d7' and more.
There was an issue with having "Log Transactions" enabled at the interface level due to the volume of logging (it would max out the 4GB log file relatively quickly) but the issue was fundamentally due to a non-existent backup server interrupting the IFS requests by having all requests sent to a specific, not-in-use IP address.
The culprit was seemingly a 'ghost' node which did not exist but was somehow in the database acting as a backup server.
The reason why the IFS errors were so sporadic and inconsistent was due to this 'ghost' server and how often the hosts file would be updated on the terminals.
The processing of any IFS activities would halt seemingly at random and interrupt workflows. It appeared as though messages were actually being redirected to this non-existent IFS server mid-workflow.
For searchability, this primarily manifested itself as 'IFS_ADAPTER_ERROR' but there were other breadcrumbs that were also frequent including 'IFS error status -20', 'IFS_RECEIVE_TIMEOUT', 'IFS_PROXY_ERROR', '0xc70700d7' and more.
There was an issue with having "Log Transactions" enabled at the interface level due to the volume of logging (it would max out the 4GB log file relatively quickly) but the issue was fundamentally due to a non-existent backup server interrupting the IFS requests by having all requests sent to a specific, not-in-use IP address.
