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". Hopefully someone will be able to point me (and our database) in the right direction.We try to install the lsagent on Windows 10 pc with the cloud relay key for remote scanning. For the life of me I just can't seem to figure it out though. I've already tried going through all the troubleshooting pages, but I know I'm just missing the database part. Re-running the 10.3.2 Lansweeper Setup file will have the "Upgrade" option greyed out. If I try the Advanced install and uncheck the "New Lansweeper" options, it says "No existing Lansweeper LocalDb database found". I still have the lansweeperdb.mdf file present, and I have old backups if needed too. In , it showed that the LocalDB instance was deleted: However, the biggest question mark is that in Services.msc, I do not see the Lansweeper LocalDB Service! I used to be able to access the database in SSMS using Windows Authentication, but that doesn't work anymore and I don't know the password to lansweeperuser (I did try mysecretpassword0*). The errorlog shows that the database server could not be found. For reference, we use an SQL Server (localdb)\.\LSInstance and we only use this one server for Lansweeper. I found that this was due to the update somehow deleting our database instance. However, now it is stuck at "Update in progress". We were previously on 10.2.4 and we upgraded to 10.3.2. I sent an email to support too, but thought I'd run over here in case this was an easy fix.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |