Calling Card Continues to Open, Unable to Connect

On all of our computers, since this weekend, whenever we try to connect with the Calling Card, on our end we elevate to a system service and it says it works fine. On the customer end it says the elevation failed. When we try to connect, customer doesn't get permission pop up and it immediately says that permission for access was refused.

Upon closing and rebooting machine, the calling card will now continue to pop up and open, no matter how many times we close it, and it will say unable to connect. The only way to stop it from trying to open continuously is to uninstall it.

This issue happens even after an uninstall and reinstall of the calling card and occurs on Windows 7 and Windows 10 machines.

Find more posts tagged with

Comments

sv5

Hello Mattis!

Our latest version is much higher, 7.11.756. I suppose that your company has a direct, forced previous version setting in our Backoffice. You can ask our helpdesk to set this setting to the latest one. So I advise you to call our helpdesk to get the latest version.

Regards,
Sandor

Mattis

OK, just connected to one of the clients.

Seems we're on version 7.0.454, however I can see that the last check for updates was today (is there a later version?)

Mattis

Yep, we've seen this same issue start to occur only over the last few days. So far all of the people impacted are running Windows 10.

I'll see if I can obtain the version of Calling Card that's installed, it tends to be set to auto-update, but possible that users have ignored the prompt.

sv5

Hello RakataTech!

Thank you for your feedback.

Could you provide us your Calling Cards's version number? You can get it from the Calling Card if you press CTRL+L on its chat field.

Could you try to reproduce this issue in our Beta site too? If you log in Beta, than the newest Calling Card can be generated from the Admin Center. I think that workaround steps would just help in case of Unattended Session stuck.

Best Regards,

Sandor

hermand25

Was given this from phone support to remove the applet from being "Stuck"

Remove a stuck applet

Symptoms

Rescue applet launches upon every Windows startup. When closing the applet window it immediately re-launches

Cause: If a technician ends a LogMeIn Rescue session while disconnected from their client (either during the process of a reboot or because of connectivity problems), it is possible that the applet may not remove itself properly

To remove the stuck applet:

Run services.msc
Look for a service referencing LogMeIn Rescue
Right click on the service and select 'properties'
Copy the service name
Open a Command Prompt with admin privileges
Enter: sc delete (followed by a space) then paste the UA service name by right clicking in the command prompt window

DeleteService SUCCESS is displayed

Reboot required

You must reboot to complete the removal process

Optional:

Once the machine reboots you can delete the temporary files installed by the applet:

Navigate to C:\Users\%username%\AppData\Local and delete the LogMeIn Rescue Applet folder.

Note

The AppData folder is hidden by default. Check folder options > view > select "show hidden files"

hermand25

Same issue, even force closing and restarting the computer doesnt work.

Quick Links

Join the conversation!

If you found this discussion useful, why not register/sign-in? It only takes a minute to share your feedback, ask a question, or vote for a new feature!