It will work straight after this is done. The next fix, which seems to be resolving the issue on most desktops but is again un-workable as a fix is: One thing which seems to work for some PCs is restarting the lsagent service twice - not once, but twice! I have found a number of 'odd' fixes but none of them are that feasible due to the number of devices which have lsagent installed. I can confirm the minimum requirements are in place: Was also seeing the same error on previous Lansweeper & lsagent versions. I'm running the latest version of Lansweeper (9.1.41.1) and Lsagent 9.1.0.8. We have internal server scanning working and scanning for years but we wanna keep trace with the home work and laptop not showing for weeks.ĭid you ever figure this out? I have the same problem here. I've restart both side and i still have a no go, always the same TLS error. On both side ive enabled TLS 1.2 and ive created the registry key under SCHANNELĪnd i create a DWORD ENABLED at 1 and a DWORD DisabledByDefault at 0 EchoException: CompanyHasNoDefaultGroupAvailable `1 : CompanyHasNoDefaultGroupAvailable (le détail de l'erreur est égal à ExceptionDetail, probablement créé par IncludeExceptionDetailInFaults=True, dont la valeur est : Verify that at least TLS 1.2 is enabled and retry. 15:23:55,460 ERROR A communication error occurred. 15:23:54,792 DEBUG ServicePointManager.ServerCertificateValidationCallback 15:23:54,570 DEBUG CreateFactoryInstance for endpoint, EchoService 15:23:54,553 DEBUG Attach ServerCertificateValidationCallback 15:23:54,513 DEBUG Created Rela圜ommunicationSender to URL But when i try to scan the remote pc i always got the same error: On the server side i succefully enable the cloud key relay it said "LSagent access granted". We try to install the lsagent on Windows 10 pc with the cloud relay key for remote scanning.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |