Question

I have created a powershell module (.psm1) file that includes a few other powershell scripts. We use it for sharepoint.

So basically, here’s what happens:

1. I have a deploy script that retrieves the module location from the registry
2. It loads the module using the Import-Module cmdlet (using -force switch)
3. This module in turn loads the Sharepoint 2010 snap in and a few other scripts that I created
4. It runs runs a deployment script that references functions from the included scripts
5. It also runs a command line application and sends the output directly to the screen

The script will usually work the first time. However, after a few number of tries the commandline tool will stop working and sending output to the screen altogether. And if I try to run a commandline tool (not a cmd-let) after running my script, it don’t worky anymore: no output, nothing is done. Its just the same as hitting enter on a blank prompt. anything powershell specific or running GUI applications will work fine but running any console application will not produce any concievable results. the only solution to this, is to just close my powershell and open it again. it will work for usually once and I will have to close it again. our users certainly wont be happy about that..

The most ‘notable’ things on the script:

• scriptblocks are used extensively (for logging), a script block is sent to a handler that executes it using invokecommand and logs the step
• its manipulating sharepoint objects
• all objects are properly disposed of
• no static variables are created nor changed
• There are a few global variables shared across all scripts

What I have tried:
I striped my code to a bare minimum: loading an xml file, and restaring a few windows services but I’m still getting this intermittently. I have no idea which part of the code could cause this. I would love to post the code, but our company policy forbids me to. so my aplogies..

Update as per the comment below:

here’s roughly how I use codeblocks. I have this function below that is used everytime I want to make the user aware of a task that I’m executing and what it outcome is.

function DoTask($someString, $scriptBlock, $param)
{
   try
   {
      OutputTaskDescription $someString
      InvokeCommand $scriptBlock -ArgumentList $param
      OutputResultOK
   }
   catch
   {
      OutputResultError $_.tostring()
   }
}

it could then be used like this:

$stringVar = "something"
$SpSite = new-spsite
deploySomething 'Deploying something' -param $spsite -ScriptBlock {
   dosomethingToObject $stringvar
   dosomethingToObject $spSite.Name
}

it would then output something like:

Deploying Something ------------- OK
Deploying Something ------------- ERROR

Also notice that I pass the $spsite in the argument list and I just use the string directly. I still don’t understand how this works but it seems like I can access all primitive typed variables even without passing them as arguments but I have to pass more complex objects are params, else they dont have any value.

Update:
after much searching and days of pain. I have found others with the same pain. My code exhibits the same exact symptoms as described here:
http://connect.microsoft.com/PowerShell/feedback/details/496326/stability-problem-any-application-run-fails-with-lastexitcode-1073741502

I guess there is no solution yet to this problem.

Answer 1

After a little while I’ve noticed that if I’ve ran some very memory intensive functions, I too have gotten that behavior where everything you try to execute just goes to the prompt again. I’d recommend setting Set-PsDebug -Trace 2 to see what those functions are actually doing. I fixed my issue by doing this and figuring out how to make my functions more efficient.