rahul

• Aug 7th, 2015

 

1. We can try to telnet the specific server where we found the corruption of ICA file corruption e.g telnet servername 1494.... if good we will get reply like ICA ICA ICA.

2. For Windows server 2008 we need to do is to go to another XenApp server and export the ICA-tcp listener registry key and import it into the registry of the server which has the bad ICA listener.
Registry location to export, import or delete the reg key for the ICA-Tcp listener
HKEY_ LOCAL _ MACHINESYSTEM Control SetControlTerminal ServerWinStationsICA-tcp

3. In case we have one server in your farm. So, run XenApp repair (Control Panel – Add Remove Programs or Programs and Features – Uninstall a program) This will recreate the listener for you as well (works for both 2003 and 2008 servers).

FOR IMA basic setups:
1. try to manually start the IMA service.
2. try to recreate LHC.
3. try to telnet that the faulty Xenapp server from any other server. telnet 2512.
4. you can also use cmd netstat -a. to see 2512 port is listening...

pranay

• Oct 11th, 2015

 

ICA is server to client communication and IMA is sever to server communication. ICA majorly depends on the client (receiver) and IMA depends on the LHC and datastore. For troubleshooting IMA you can typein services.msc on the affected server and restart the service.

Awais

• Nov 11th, 2015

 

Please check the service account for IMA service may be its expired. If it has been expired then use DSMAINT CONFIG command to reset. then try to recreate LHC. Please check logs on the server.