Persons get inserted into PersonHasQERResource, but the process is not executed.

henrik a johansson said:

Also, the Powershell-script in the process connects to our Skype-server but the server function on the process is "Microsoft Exchange connector". Should I change that to Powershell-connector?

I recommend doing that to make it easier to support your customization, but this not necessary as long as the PowerShell connector is installed on the Job Service executing your process.

In regards to your error message, I assume the parameter Session is defined in your PowerShell script?

Yes. As I wrote, the script works fine when assigning the resource individually.

Is it because the server only can take a certain amount of Powershell-sessions?

Yes. As I wrote, the script works fine when assigning the resource individually.

Is it because the server only can take a certain amount of Powershell-sessions?

Does it work when you run just one process at a time?

I think that you parameter Session is not set correctly in your process step.

How do I run "one process at a time"?

This is my session-line in the script:
$session = New-PSSession -ConnectionUri "skypepool.acme.com" -SessionOption $SkypeOptions -Authentication NegotiateWithImplicitCredential

What I meant was to test your process by assigning just one new entry to PersonHasQERResource and see if it works then.

By the way, are you using the PowerShellComponent or the PowerShellComponentNet4?

Yes, that works. By clicking several employees that have a row in PersonHasQERResource gets enabled in Skype.

I'm using PowerShellComponent. Not Net4. Good? Bad?

Good or bad depends on what version of PowerShell is needed.  PowerShellComponent is using PowerShell 2, PowerShellComponent4 is using PowerShell 3 or higher. In addition, the PowerShellShellComponentNet4 has more task available for example, some task for remote shell operations.

I've now changed it to "PowershellComponentNet4 - ExecuteScript". Should I maybe change it for just this process to something other than ExecuteScript, since it opens a session to a remote host?

Changing to PowershellComponentNet4 and PowershellConnector fixed it for me. When assigning Skype to a number of employees none of the jobs get frozen.

Where can I read more about the different tasks under PowershellComponentNet4?

In the Designer, all the task and parameters for each process component are listed.