The PowerShell script failed with below exception

Question

I'm receiving the following errors on all SQL Express Servers (every machine that has SQL Express inside).
it seems that the discovery has found SQL Express but could not connect to the instance.
details on the alerts:
Date and Time:
10/22/2013 12:04:22 PM
Log Name:
Operations Manager
Source:
Health Service Modules
Generating Rule:
Collect Power Shell Module Events
Event Number:
22406
Level:
 Error
Logging Computer:
SQLEXPRESS.DOMAIN.COM
User:
N/A
Description:
The PowerShell script failed with below exception
System.Management.Automation.RuntimeException: Exception calling "Fill" with "1" argument(s): "A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not
accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified)"
At line:44 char:19
+ $SqlAdapter.Fill <<<< ($DataSet)|out-null
at System.Management.Automation.FlowControlNode.Execute(Array input, Pipe outputPipe, ExecutionContext context)
at System.Management.Automation.ParseTreeNode.Execute(Array input, Pipe outputPipe, ArrayList& resultList, ExecutionContext context)
at System.Management.Automation.StatementListNode.ExecuteStatement(ParseTreeNode statement, Array input, Pipe outputPipe, ArrayList& resultList, ExecutionContext context)
Script Name: StolenServerMemory2008.ps1
One or more workflows were affected by this.
Workflow name: Microsoft.SQLServer.2008.DBEngine.StolenServerMemoryMonitor
Instance name: SQLEXPRESS
Instance ID: {9705795C-4F3B-C2EF-AA7D-C736B40FD6A4}
Management group: SCOMGROUP 

Answer 1

Some additional inf.
http://stackoverflow.com/questions/6466974/unable-to-connect-to-sql-express-error-26-error-locating-server-instance-speci?rq=1
anyway you can disable this rule/monitor as no control from monitoring solution in that case. Or try to rewrite the same monitor...
The problem in your case is when function tries to get Max Server Memory MB by connecting to master DB, but you can replace it with performance counter like Target Server Memory (KB)...
just see the function main in StolenServerMemory2008.ps1 and what you need to replace
$api = New-Object -comObject "MOM.ScriptAPI"
$bag = $api.CreatePropertyBag()
$msg = [Environment]::NewLine
$err = [Environment]::NewLine
#try {
$maxMemoryMB = GetMaxServerMemoryMB $ComputerName $InstanceName
$stolenPages = (Get-Counter ("\" + $PerformanceCounterObject + ":Buffer Manager\Stolen Pages")).CounterSamples[0].CookedValue
$pakeSizeKB = 8
[double]$stolenMemoryMB = $stolenPages * $pakeSizeKB / 1024                                      
[double]$stolenMemoryPercent = 0
if($maxMemoryMB -gt 0){
[double]$stolenMemoryPercent= 100.0 * $stolenMemoryMB / $maxMemoryMB
$bag.AddValue("StolenMemoryMB", $stolenMemoryMB)
$bag.AddValue("StolenMemoryPercent", $stolenMemoryPercent)                                  
$msg += "StolenMemoryMB=$stolenMemoryMB StolenMemoryPercent=$stolenMemoryPercent"
$msg += [Environment]::NewLine                          
#debug $api.LogScriptEvent("SQL 2008 Stolen Server Memory data source", $SCRIPT_EVENT_ID, $INFORMATION_EVENT_TYPE, $msg + $err)                     
#catch {
#             $header = "Managegement Group: $Target/ManagementGroup/Name$. Script: {0}" -f ($MyInvocation.MyCommand).Name.ToString()
#             $msg += "Error occured during SQL 2008 Stolen Server Memory data source executing.{0}Computer:{1} {0}Reason: {2}" -f [Environment]::NewLine, $env:COMPUTERNAME, $_.Exception.Message
#             $api.LogScriptEvent($header, $SCRIPT_EVENT_ID, $ERROR_EVENT_TYPE, $msg + $err)                           
$bag