I have been trying to connect to a computer and it will show me the unattended host it will connect and once i try to start a session if gives me the below error over and over. I looked up the error code and sll it says is i am using an old version of the desktop client however that is not true since I am using the newest BETA version because the normal client does not work in the current release of Windows 10. I would appreciatte any help on this as this product quite frankly has been a complete beast to use.
[2019-01-24 5:53:33 AM] Starting session 669445922...
[2019-01-24 5:53:35 AM] Pick-up communication error. Error code (7), last error (0).
I have seen this post before stating the resolution was the rescue console was out of date, I have ensured I am running the most current console.
Console version: 7.13.3413 (64 bit)
OS: Win 10 Pro (64 bit)
Version:1809 OS build: 17763.292
Issue: when using tech console, creating a PIN# and sending to user, user sees normal process, sounds alert as if connection is ready. On console, pressing the green play button results in the following error in the log, no connection can be made. This has been tested with multiple connections on mulitple computers with same results. I can run a console on another PC and it will work so it is not an account issue, verified by logmein support team.
I believe it may be a firewall or PC setting however I cannot figure it out, looking for suggestions. It was working on the PC when I first installed, PC is 2 weeks old. Not Windows updates are listed in update log between time it was working and stopped working. Not running Macafe protection, only Win Defender.
[2019-01-24 8:42:05 AM] === Console started (7.13.3413 64-bit) ===
[2019-01-24 8:42:05 AM] Host site: beta.logmeinrescue.com
[2019-01-24 8:42:09 AM] Console configuration has been retrieved
[2019-01-24 8:42:15 AM] Console ready
[2019-01-24 8:42:35 AM] Generating PIN Code...
[2019-01-24 8:42:35 AM] Private code 831650 has been generated
[2019-01-24 8:43:28 AM] Starting session 669470552...
[2019-01-24 8:43:31 AM] Pick-up communication error. Error code (7), last error (0).
[2019-01-24 8:43:32 AM] Starting session 669470552...
[2019-01-24 8:43:34 AM] Pick-up communication error. Error code (7), last error (0).
[2019-01-24 8:43:37 AM] Starting session 669470552...
[2019-01-24 8:43:39 AM] Pick-up communication error. Error code (7), last error (0).
[2019-01-24 8:43:43 AM] Chat log has been retrieved
[2019-01-24 8:43:50 AM] Ending session 669470552...
[2019-01-24 8:43:51 AM] Session 669470552 has been closed
@Timyarb That specific error is caused by an outaded LMI client. Please update the software on the problem PC, and then test again.
Reference support documentation: https://help.logmein.com/articles/en_US/FAQ/Why-do-I-get-Closing-session-communication-error-Error-c...
Thanks for the response, when you say the "LMI Client" are you reffering to the Logmein Rescue console? If so, the console states it is up to date, where do you recommend I find an updated version?
@Dwarne_ACS Sorry if I missed any details of your original posting. If this is not a sigle client causing the error on multiple PCs when attempting to connect, then the article referenced would be accurate. If this is only happening on a single Technician device, then I'm not sure yet what might be causing that. Did you say McAfee was still installed there? Have you tried creating a new user profile on the problem PC for testing purposes?