Azure Automation Access load locally stored dlls

Question

Azure Automation Access load locally stored dlls

Rohit Jarodia 26

Hi, I am trying to load some DLLs in my script which is stored locally, and running the script using a hybrid runbook worker. getting below error

Add-Type : Cannot bind parameter 'Path' to the target. Exception setting "Path": "Cannot find path

AnuragSingh-MSFT 21,546 Reputation points Moderator

2022-07-26T14:24:21.98+00:00

@Rohit Jarodia , thank you for reaching out to Microsoft Q&A for this question.
Can you please share additional details to help me understand the issue better?

1. What is the Runbook type and version being used here (Python 2/3, Powershell 2/3 etc.)?
2. Can you please share the runbook script too to help me understand the function/method used to load dll.

Please let us know if you have any questions.

Rohit Jarodia 26

@AnuragSingh-MSFT Thanks for replying back, Below is the current scenario

I have one hybrid runbook worker where i am trying to run below runbook (Powershell 5.1) :

Param($user)  
  
$Usr = Get-ADUser -identity $user  
  
write-output $usr  #This is working  
  
#loading dll  
Add-Type -Path "C:\Temp\Microsoft.SharePoint.Client\Microsoft.SharePoint.Client.dll"  
		Add-Type -Path "C:\Temp\Microsoft.SharePoint.Client\Microsoft.SharePoint.Client.Runtime.dll"  
		Add-Type -Path "C:\Temp\Microsoft.SharePoint.Client\Microsoft.SharePoint.Client.Publishing.dll"  
  
#Load Custom Modules  
		Import-Module "C:\temp\custom.psm1"   #This is failing and throwing error - Path not found

Somehow the script is unable to see the local file system. Is it anything i am doing wrong or its the feature.

Accepted answer

1 additional answer

Your answer

AnuragSingh-MSFT 21,546 Reputation points Moderator

2022-07-26T14:24:21.98+00:00

@Rohit Jarodia , thank you for reaching out to Microsoft Q&A for this question.
Can you please share additional details to help me understand the issue better?

1. What is the Runbook type and version being used here (Python 2/3, Powershell 2/3 etc.)?
2. Can you please share the runbook script too to help me understand the function/method used to load dll.

Please let us know if you have any questions.
Rohit Jarodia 26 Reputation points

2022-07-27T07:37:06.997+00:00

@AnuragSingh-MSFT Thanks for replying back, Below is the current scenario

I have one hybrid runbook worker where i am trying to run below runbook (Powershell 5.1) :

Param($user) $Usr = Get-ADUser -identity $user write-output $usr #This is working #loading dll Add-Type -Path "C:\Temp\Microsoft.SharePoint.Client\Microsoft.SharePoint.Client.dll" Add-Type -Path "C:\Temp\Microsoft.SharePoint.Client\Microsoft.SharePoint.Client.Runtime.dll" Add-Type -Path "C:\Temp\Microsoft.SharePoint.Client\Microsoft.SharePoint.Client.Publishing.dll" #Load Custom Modules Import-Module "C:\temp\custom.psm1" #This is failing and throwing error - Path not found

Somehow the script is unable to see the local file system. Is it anything i am doing wrong or its the feature.

Answer 1

AnuragSingh-MSFT 21,546 Moderator

@Rohit Jarodia , thank you for the details. Please check if you are running the runbook on the Hybrid worker. For example, I have the following runbook:

For test, I am using the "Test Pane" feature as highlighted in the image above.
In the Test Pane, ensure that the "Hybrid Worker" option is selected and you have selected the "Hybrid Worker Group" on which you want to execute the runbook:

Note that, when selecting the Hybrid Worker Group, you cannot control the machine which will pick up the job for execution. Therefore, if you have more than 1 server in the selected "hybrid Worker Group", ensure that all of them have the dlls and psm1 module available in the mentioned location (as available in the runbook script).

Please let me know if you have any questions.

---
Please 'Accept as answer' and ‘Upvote’ if it helped so that it can help others in the community looking for help on similar topics.

Rohit Jarodia 26 Reputation points

2022-07-28T11:23:18.037+00:00

@AnuragSingh-MSFT : Thank you for the reply. I tried doing the suggested steps. However, I am getting below error

is anything i need to do extra to give permission to the local file system?
AnuragSingh-MSFT 21,546 Reputation points Moderator

2022-07-29T09:54:42.98+00:00

@Rohit Jarodia , thank you for the reply. Just to be sure, please check and confirm the path being used in you script.

There is nothing extra that needs to be done for the runbook job to access local resources. One thing that could happen is that you are using a Hybrid Worker Credential which does not have permission to access local resources. Can you please confirm if you are using the "Default" credential to run the jobs? If you are using Custom credential, please check if it has access to the path.

In case the suggestion above does not help, I would suggest reaching out to Azure Support for 1:1 help. Please let me know if you are facing issues opening a support ticket.
Rohit Jarodia 26 Reputation points

2022-08-01T07:36:38.7+00:00

@AnuragSingh-MSFT : Thank you for the reply. You are correct, i am utilising Azure Automation credentials. The issue still not solved and throwing same error. I just wanted to understand if Run-AS accounts is necessary ?
AnuragSingh-MSFT 21,546 Reputation points Moderator

2022-08-01T11:04:59.057+00:00

@Rohit Jarodia , No, setting run-as account is not necessary. You can leave it as "Default", which would use the "Local System" of the Hybrid Worker Machine to run jobs locally on this machine. In case you are using a different run-as account (where using "default account" does not work for you, maybe because of special permission requirements), ensure that you have provided the permissions to this account: Use runbook authentication with Hybrid Worker Credentials

---
Please 'Accept as answer' and ‘Upvote’ if it helped so that it can help others in the community looking for help on similar topics.

Answer 2

Hi,

The PowerShell script needs to load the assembly before it can use classes that the assembly exposes. To load assembly use Add-Type cmdlet.

Add-Type -Path "WinSCPnet.dll"

If you need to run the script from a different directory, you must specify a full path to the assembly. You can get the path from the script file path using the $PSScriptRoot automatic variable.

Add-Type -Path (Join-Path $PSScriptRoot "WinSCPnet.dll")

----------------------------------------------------------------------------------------------------------------------------------

--If the reply is helpful, please Upvote and Accept as answer--

Share via

Azure Automation Access load locally stored dlls

1 additional answer

Your answer