Windows Engines never become available on Solaris or Linux Managers
Article ID: KB0086726
Updated On:
| Products | Versions |
|---|---|
| TIBCO DataSynapse GridServer | - |
| Not Applicable | - |
Description
Resolution:
If Windows Engines never become available when connected Solaris or Linux managers, one possibility is that there are duplicate files in the file deployment hierarchy. Check the Windows Engine logs to see if the Engines repeatedly log in, transfer files, and log out. If so, you may have duplicate files with identical case insensitive names, such as AFile.txt and afile.txt.
On Solaris or Linux, these will appears as different files, but on Windows they will appear as the same file, causing them to be repeatedly transferred and preventing the Engines from ever stabilizing. To correct this issue, rename one of the files.
If Windows Engines never become available when connected Solaris or Linux managers, one possibility is that there are duplicate files in the file deployment hierarchy. Check the Windows Engine logs to see if the Engines repeatedly log in, transfer files, and log out. If so, you may have duplicate files with identical case insensitive names, such as AFile.txt and afile.txt.
On Solaris or Linux, these will appears as different files, but on Windows they will appear as the same file, causing them to be repeatedly transferred and preventing the Engines from ever stabilizing. To correct this issue, rename one of the files.
Issue/Introduction
Windows Engines never become available on Solaris or Linux Managers
Feedback
Yes
No
Powered by
