Hi.

i'm trying to use the FIM PowerShell Workflow Activity from CodePlex, but cannot get the Transcript-command working

Start-Transcript -Path C:\FIM\PowerShell\log.txt -Append
Stop-Transcript

This gives a PostProsessing error

EXCEPTION DATA\r\n\r\nMESSAGE: Exception of type 'Microsoft.ResourceManagement.Workflow.WorkflowExtensionException' was thrown.\r\n\r\n**METHOD:System.Workflow.ComponentModel.ActivityExecutionStatus Execute(System.Workflow.ComponentModel.ActivityExecutionContext)\r\n\r\n**METHOD:System.Workflow.ComponentModel.ActivityExecutionStatus Execute(T, System.Workflow.ComponentModel.ActivityExecutionContext)\r\n\r\n**METHOD:System.Workflow.ComponentModel.ActivityExecutionStatus Execute(System.Workflow.ComponentModel.Activity, System.Workflow.ComponentModel.ActivityExecutionContext)\r\n\r\n**METHOD:Boolean Run(System.Workflow.ComponentModel.IWorkflowCoreRuntime)\r\n\r\n**METHOD:Void Run()\r\n\r\n
------------------------------------------------------------

Any ideas why? Other scripts works perfectly.

Check the event log, there should be more detail as to what failed. Did you make sure the user running the workflow has the ability to browse to that directory and read/write the file ... also not so sure this would work with multiple workflows running at the same time, unless the FIM WF engine is synchronous and I didn't know...

Check the event log, there should be more detail as to what failed.

That same error is in the evet log, but nothing more.

Did you make sure the user running the workflow has the ability to browse to that directory and read/write the file ... also not so sure this would work with multiple workflows running at the same time, unless the FIM WF engine is synchronous and I didn't know...

This works, so it's not permission issue

"ABC" | Out-File  C:\FIM\PowerShell\log.txt -Append

try {
Start-Transcript -Path C:\FIM\PowerShell\log.txt -Append
Stop-Transcript
} catch {
 $_ | Format-List -Property * | Out-String | Out-File C:\FIM\PowerShell\error.txt -Append
}

Can you try this in your workflow and see if it generates the error info in the error file ...

It seems that it isn't supported this way

Start-Transcript : This host does not support transcription.
At C:\FIM\PowerShell\Test.ps1:2 char:17
+ Start-Transcript <<<<  -Path C:\FIM\PowerShell\log.txt -Append
    + CategoryInfo          : NotImplemented: (:) [Start-Transcript], PSNotSuppo
rtedException
    + FullyQualifiedErrorId : NotSupported,Microsoft.PowerShell.Commands.StartTr
anscriptCommand

It seems that it isn't supported this way

Start-Transcript : This host does not support transcription.
At C:\FIM\PowerShell\Test.ps1:2 char:17
+ Start-Transcript <<<<  -Path C:\FIM\PowerShell\log.txt -Append
    + CategoryInfo          : NotImplemented: (:) [Start-Transcript], PSNotSuppo
rtedException
    + FullyQualifiedErrorId : NotSupported,Microsoft.PowerShell.Commands.StartTr
anscriptCommand

Correct. Transcription is a host feature which I expect this activity doesn't support.

Thanks Adam and Brian