CODEWITHSUNDEEP
tfsms-release-management
ZoolWay
ZoolWay

Reputation: 5505

TFS Release, running PowerShell, cannot create DtlDownloads

I am trying to get some automatic deployments up and running using TFS 15 (on-premise). I have a powershell script on the deployment target to call.

The deployments starts fine by downloading the artifact. But when the agent runs the script it wants to create a folder C:\Windows\DtlDownloads (thats not part of my script but part of preparing things for TFS I guess). That fails:

##[debug]System.AggregateException: Failed to install 'VisualStudioRemoteDeployer20597940-38b2-4ba8-9a4d-fcc894308730' from service executable path VisualStudioRemoteDeployer.exe . Consult the logs below:
Access to the path 'DtlDownloads' is denied.
CategoryInfo :PermissionDenied: (C:\Windows\DtlDownloads:String) [New-Item], UnauthorizedAccessException
FullyQualifiedErrorId :CreateDirectoryUnauthorizedAccessError,Microsoft.PowerShell.Commands.NewItemCommand

The user used to logon is a server-local user named deploy who is also a local administrator on that machine. I also checked the effective access for that user on the windows folder and it should be able to create directories.

Something similar happens with the copy step. Robocopy signals two errors:

2017/03/16 08:57:21 ERROR 5 (0x00000005) Getting File System Type of Destination \\server.domain.com\c$\abc\def\ 
Access is denied.

and 

2017/03/16 08:57:21 ERROR 5 (0x00000005) Creating Destination Directory \\server.domain.com\c$\abc\def\ 
Access is denied.

The second is a bit unexpected as the folder def already exists but I guess it is a follow up because getting the type failed beforehand.

The user itself must have been recognized because I get different errors when using invalid credentials. I have enabled WinRM using Enable-PSRemoting and ConfigureWinRM.ps1 from WinRM-Http-Https-Without-Makecert.

What could still restrict the permissions?

Update: Using a domain user instead of a local one of that server solves the issue. But I do not understand why. Can someone explain or even provide information how to make it work with a local user?

Upvotes: 1

Views: 1683

Answers (3)

David Fidge
David Fidge

Reputation: 467

Running "winrm quickconfig" fixed this problem for me

winrm quickconfig

https://learn.microsoft.com/en-us/windows/win32/winrm/installation-and-configuration-for-windows-remote-management

Upvotes: 0

Zodraz
Zodraz

Reputation: 131

One problem could be if that you have the agent as a service, that service has not the proper privileges, like being on Network Account. Try to change that to the user account which has administrative privileges.

Upvotes: 1

PatrickLu-MSFT
PatrickLu-MSFT

Reputation: 51183

The username of either a domain or a local administrative account on the target host(s).

  • Formats such as username, domain\username, machine-name\username, and .\username are supported.
  • UPN formats such as [email protected] and built-in system accounts such as NT Authority\System are not supported.

Source Link

Both the domain account and local admin should be work. Please double check your format and give a try with another format.

Upvotes: 1

Related Questions