Community
Error 17: #5
Tom Ziegler,
User (Posts: 2)
Sep 22, 2020 8:57:55 am EDT
Support level: Endpoint
Trying to remote install on a domain pc and I am getting the following error:
***** Start of log *****
Date: 22-Sep-20 08:52:02
Action: install/upgrade.
Checking files of the Host.
Login/password?
----------
Action for: LTWSPARE2607 (LTWSpare2607.algenol.local)
Connecting...
--> algenol\tzadmin
Error 17: #5
***** End of log *****
I have tried a custom MSI and the default MSI.
***** Start of log *****
Date: 22-Sep-20 08:52:02
Action: install/upgrade.
Checking files of the Host.
Login/password?
----------
Action for: LTWSPARE2607 (LTWSpare2607.algenol.local)
Connecting...
--> algenol\tzadmin
Error 17: #5
***** End of log *****
I have tried a custom MSI and the default MSI.
Hello Tom,
Thank you for your message.
The Error 17: #5 usually means that your NTLM user does not have enough privileges. Please, make sure that you have local admin rights on that machine. In addition, please double-check that admin$ (admin share) is allowed on the remote machine and you have access to it.
Hope that helps.
Thank you for your message.
The Error 17: #5 usually means that your NTLM user does not have enough privileges. Please, make sure that you have local admin rights on that machine. In addition, please double-check that admin$ (admin share) is allowed on the remote machine and you have access to it.
Hope that helps.
Tom Ziegler,
User (Posts: 2)
Sep 23, 2020 9:32:16 am EDT
Support level: Endpoint
The account I am entering for the remote push install is a domain admin account which has local admin rights and the admin share is available from the PC I am trying to push the remote install from. I decided to try it from one of the domain servers and that seems to work. Not sure why it is not working from my PC though.
Aaron Lorton,
User (Posts: 1)
Nov 25, 2020 3:52:37 pm EST
Support level: Pro
I was having the same issue/error with providing my administrator account credentials during the remote push dialog. My work around was to run the Remote Utilities viewer as another user, one with administrative rights. Then I was able to select the check box for "Use current security context" when pushing the client out.
David Silvera,
User (Posts: 25)
Jan 02, 2025 6:48:57 pm EST
Support level: Pro
Having this same error after I upgraded to 7.6.2.0 for the VIewer. I try to do a Remote Install... and then use Windows Credentials and use the domain admin, which I have always been using before upgrading. But keep getting this error from the original post.
Followed the suggestion of doing this from a Domain Server and it worked. I am logged into the server as the domain admin and installed the viewer.
Not sure why this error started after upgrading to 7.6.2.0.
But thought I would also share my experience.
Followed the suggestion of doing this from a Domain Server and it worked. I am logged into the server as the domain admin and installed the viewer.
Not sure why this error started after upgrading to 7.6.2.0.
But thought I would also share my experience.
* Website time zone: America/New_York (UTC -4)