Hi all,
We have configure the File Listener Startup Option Node based Classification Start up and selected Node Type as BackgroundProcessing. Test Connectivity is failing. Please us know if any specific configuration is missing.
Hi all,
We have configure the File Listener Startup Option Node based Classification Start up and selected Node Type as BackgroundProcessing. Test Connectivity is failing. Please us know if any specific configuration is missing.
@Abhay Kumar Alandkar To troubleshoot file listener test connectivity you can follow these steps: 1. Click on ‘Test connectivity’ to confirm that your system can find the directory. The system attempts to create the listener thread on the current node and tries to access the device and directory. The test results are displayed including the parameters used in the test the steps attempted and the outcome of each step. 2. If the file listener fails to start this might be indicated by ‘Time out borrowing service requestor’ or ‘Unable to create listener’ messages in the log file. Consider increasing the requestor pool size on the Pooling tab of the service package data instance. 3. Ensure that the source location path is configured correctly. 4. For more detailed troubleshooting you can enable file listener debug loggers from Admin Studio and start tracing the file listener.
If the issue persists you might want to check the ‘Startup option’ field on the ‘Properties’ tab of the listener. If ‘Node based startup’ is selected ensure that the correct node is added to the list. If ‘Host based startup’ is selected ensure that the correct host is added to the list. Remember to restart the listener for the changes to take effect.
This is a GenAI-powered tool. All generated answers require validation against the provided references.