Hi had the same problem, this is the answer from alcatel:
Hi Heiko,
This is in reference to the issues with getting backtraces Eva tool running.
Thank you for your update.
I have tried to reach you but was not successful.
As per our analysis we found that issue may be due to the corrupted Eva_tool.dct file in the OXE. This issue can be resolve by replacing the corrupted Eva_tool.dct and Eva tool file with a new Eva_tool.dct and Eva tool file.
1. Login to system via root. , remove the existing Eva_tool.dct and Eva_tool FILE from /usr2/oneshot/mtcl and /usr2/servers respectively.
2. Do ftp to the oxe using Swinst login and transfer the new files to the following location (FTP to the system using Swinst user id and password. Transfer the new Eva_tool.dct and Eva_tool.)
Locations of the file:
Eva_tool ( /usr2/servers)
Eva_tool.dct ( /usr2/oneshot/mtcl)
3. Then login to root and give the rights as chmod 755 file name.
Example:
[root@xa000000 servers]# cd /usr2/servers/
[root@xa000000 servers]# chmod 755 Eva_tool
[root@xa000000 servers]# cd /usr2/oneshot/mtcl/
[root@xa000000 mtcl]# chmod 755 Eva_tool.dct
Note: After this operation, re-boot of OXE is mandatory to take the changes in to account.
Please do the suggested in the site and update me your feedback.
Please feel free to contact me if you have any further issues. I will be waiting for your update.
Otherwise a quick fix from Elliot
As workaround you can copy the file /usr2/oneshot/mtcl/Eva_tool.dct to /usr2/oneshot/mtcl/Eva_tool.dct.bak
Then you can start and use the Eva_tool – of course without dictionary file – but you can use and guess the options from the displayed variable names. (e.g. reset password option)
