Cannot perform Multi-step run profile

[TheUniquePaulSmith]

To reproduce create a 2 step run profile starting with an Export then a Delta Import.
The Delta Import will fail. Looking through the source, I believe the issue is that End-ExportScript-Lync.ps1 line 46 removes the PSSession however the object still exists in a closed state so then Begin-ImportScript-Lync.ps1 on line 137 references that because the scope of the variable is global, and line 134 never replaced the object reference due to error.

Below is a snippet of the reproduced problem

So solution would be to also check for Closed session
if ((!$session) -or ($session.State -eq "Closed")) { Write-Host "Open new Session" }

[thomashouston]

Hello, is it possible this issue could also be seen when running an Export run profile, followed immediately by a Delta Import run profile? Every couple of days our Skype PSMA hangs and we have to kill the miiserver.exe process. Also, do you think it will be an easy fix?

[thomashouston]

When we enabled verbose logging, the last Information event logged before it hangs is either:

Method Name : ExportBridge : CloseExportConnection
Initiated Close Export Connection method

or

Method Name : PowerShellRuntime : Initialize
The verbose record: LyncPowerShellConnector - End-Export Script: Execution Started...

[NileshGhodekar]

From the first set events mentioned, looks like the program control is still in FIM code and from the second set of events mentioned it does not make sense to report an event for End-Export Script in the PowerShellRuntime : Initialize method. So you should open a support case for FIM/MIM and have them investigate this. Also if you think that this may be related to two running two run profiles one after another, you can try putting a time (5+ minutes) delay between the runs and see if the issue goes away.

[TheUniquePaulSmith]

@thomashouston I think that's a different issue.. I also experience that as well, and what I notice is that event log shows that the script halted and the Management Agent gets stuck running during Export. The only solution is to force kill miiserver.exe when that occurs

[thomashouston]

@NileshGhodekar I have opened a support case with Premier.

[AndKjell]

I wouldn't use the two-step run profiles where you do export-import in one single profile. Not related to the PowerShell ECMA2 connector, but in general. I've seen many customers trying this and failing. When I was the PM for the sync engine I saw several of these cases and the answer (from me) was always to separate these to two different profiles.

[LindbergM]

Hello, is it possible this issue could also be seen when running an Export run profile, followed immediately by a Delta Import run profile? Every couple of days our Skype PSMA hangs and we have to kill the miiserver.exe process. Also, do you think it will be an easy fix?

@thomashouston I experience the same issue that you did or do, did you have any luck with your support case?

[thomashouston]

Hi @LindbergM, I wasn't able to reproduce the issue offline, so didn't get very far with Premier, unfortunately.

[TheUniquePaulSmith]

@LindbergM, @thomashouston, I suspect the issue you are referring to is the following one I just logged. (Issue #32 )

This issue (#19) i've identified and documented and when I have time will put in a pull request to resolve