Teamviewer not running on partner computer.' This is a big problem for us because we need 247 connectivity. Thanks for the advice/hint to make me look at what the Application log had in it. I have users that are able to connect to a remote machine however, myself and at least one other cannot connect and get the message 'A connection could not be established. Reason Unknown.' Have tried logging out of TV and back in but no change. As of today I have confirmed that rebooting the remote machines makes the 50 that were showing offline show online again, but these ones still say 'A connection could not be established. Why/how the system was looking at this project during the start of the SSAS service, I don't understand.Īnyway.I removed the folders that were related to this project and now the service starts successfully. I had same issue - due to change of IDs on remote machines. Therefore, please try using a standard TeamViewer account. Worked fine Some things can be so simple. I tried everything I could think of on my router setup (I have a dynamic IP address), but finally, just tried using the actual numeric ID for the remote computer rather than the assigned name. Now that I was changing the server to Multi, it wasn't happy. Could you please check how the users TeamViewer account has been created If the new sign-in method is used ( sign in via Google or Microsoft email account ), Google and Microsoft accounts are only compatible for personal use at the moment. Then, I started getting the same 'Partner could not be contacted at the given network address'. For some reason, the system was picking up this project existed that had been tied to the Name Instance and was a Tabular project. I uninstalled and re-installed SSAS as MultiDimensiona for this instancel. In Visual Studio I had already created a project against this instance as tabular before I ran into the server issue as I was experimenting with a MultiDimensional project. I didn't really want this as the default instance was already that. Long story.I had originally created the SSAS for the Named Instance as a Tabular server. The idea to look at the Application log gave me enough info to try to guess what the error was (though I still don't understand why it had this problem) so I could get past it.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |