this is becoming a big issue, as it happens infrequently, but once it happens, there is no clear way to get LMIR to work again and LMIR is my primary tool for supporting customers. here's a few facts about what is happening as far as i can tell
a customer will connect either via calling card or PIN. the applet will launch and typically say "Initializing" or "Connecting" in the status area on the top left. nothing will ever show in the main "chat" area where chat messages and other updates show up throughout the session. after about 10 seconds, the applet window will close. after another 10 seconds or so, it will open up and display the same behavior ("Initializing" on the top left and nothing in the main "chat" area). it will continue to do this until "LMI_Rescue_srv.exe"/"CaillingCard_srv.exe" is killed. killing "CallingCard.exe"/"LMI_Rescue.exe" does not stop it from happening. it will kill the applet, but it will come back. also, every time a new remote session is attempted, a new temp folder (LMI###) is created in C:\Windows. also, a new service appears in the list of installed services (services.msc) and in the list of startup services (msconfig). also, the primary service my company performs is virus removals, so it's likely that the computer was infected with a virus at some point. i'm not prepared to assign a causal relationship at this point, though, since the last couple times i've seen this, the computer was clean (but was probably infected at some point in the past) so let's call it inconclusive
here are things i've attempted to resolve this issue:
advanced revo uninstall of the calling card, search the registry for and delete all keys and folders containing "CallingCard", "CallingCard_srv", "LMI_rescue", "LMI_Rescue_srv" and "LogMeIn". of course after all of this, i reboot and attempt to establish a LMIR connection and it doesn't work.
also potentially of note, is that every time i'm digging through the registry for this, there are always several registry folders call "LEGACY_LMIRESCUE###" or something very similar, where ### is a very long string of seemingly random alphanumeric characters. but what's (to me) noteworthy about these, is that the permissions have been changed on all of these to deny write access, so i always have to go through and change the permissions before deleting them. that may be entirely normal, but it may also be useful information
any tips or solutions would be very appreciated. if there's any more information i need to provide, i'll give whatever i can. i've yet to be able to reproduce this issue on command (if i were able to, i'd probably have figured it out), though, so getting some information, like logs, probably won't be possible. but let me know if there's any more information i can provide
