Skip to content

Why certain PowerShell Snapins do not load properly in Drop Downs and WebServices


The Appsetting differs between ClientWebService Calls and "Standard" PowerShell calls.

This may cause problems if you try to run Commands that depend on PowerShell Snap-ins such as SharePoint or FIM.


  • The Config FilePath used by ZP:
    C:\Program Files\Zipper\ZervicePoint\ProcessSystem\Zipper.ZervicePoint.ProcessSystem.WorkflowService.exe.config

    Config FilePath used by "Standard" powershell:

  • A workaround is to run the code as a background job:

FIM Example

$result = Start-Job -ScriptBlock {
    param (
    # Import FIM Module
    # perform search

} | Wait-Job | Receive-Job

# return result to dropdown or webservice