Powershell Component - Execute Commandline

What version are you using?

And, can you please post the content of your Command parameter from the process step executing the PowerShell CommandLine?

What version are you using?

And, can you please post the content of your Command parameter from the process step executing the PowerShell CommandLine?

Hello,

I'm using version 8.1.1

The command parameter is this one:

'Value= "Get-Content -Path *Path which contains a txt file* -encoding UTF8 | Set-Content -Path *Path* -Encoding UTF8"'

This works without a problem in powershell, but not inside the component.

Thing is that the PowerShellComponent you are using is running against PowerShell 2.0 and the Get-Content cmdlet doesn't support the -encoding parameter. You need to use a task of the PowershellComponentNet4 to execute commands in .NET 4 based PowerShells (>2.0 and <6).

Secondly, the single quotes around your command parameter, they are not present in the parameter in OneIM or are they? If so, they need to be removed.

Hello,

the single quotes around are not part of the command.

I already tried PowershellComponentNet4 and I'm getting the same error message.

It seems like that the problem is the Path, I defined the path as follows:

C:\TestDirectory\TestFile

So for example:

Value = "Remove-Item C:\TestDirectory\TestFile"

What is the correct way to define the path inside a powershell component?

The parameter looks okay to me. In general, the syntax is the same as it is pure PowerShell. But you do have to escape double-quotes by doubling them.

Are you sure the directory/file exists on the Job Service? Did you check the generated parameter in the Job Queue, does it look okay?

Hello, the directory and file exists on the job service, I can successfully run the command line on the jobserver with powershell and it does what I want.

But what do you exactly mean with escaping the double-quotes by doubling them?

Like this?

Value = "Remove-Item -Path ""D:\TESTDirectory\TestFile"""

I already tried this, this also doesn't work.

Did you check the generated parameter in the Job Queue, does it look okay?

Did you turn on the Debug mode of the Job Service and checked the Job Service Log for more information then?

If your PowerShell-command would contain a double-quote like Remove-Item "C:\TestDirectory\TestFile" you would need to write the parameter as

Value = "Remove-Item ""C:\TestDirectory\TestFile"""

Hello, I already tried it the way you mentioned, the generated parameter in the Job Queue looks alright:

Command ==> Remove-Item -Path "C:\TestDirectory\TestFile"

And you can use this

• Remove-Item -Path "C:\TestDirectory\TestFile"

in a PowerShell and it is working, correct?

Yes, this works without a problem