ServerChecker Exception

[Ryan Zerby]

I am using the powershell agent type on a small number of servers (13). If I run a configuration job manually, they all come back as 'current.' However, if I let otter run until it performs the check, I get a mix of current and unknown. I have included my only role, and the error I am getting.

Here is my only role:

General

{
Ensure-Directory c:\Temp;
}

Here is the stack trace for Category "ServerChecker"

System.Management.Automation.RemoteException: Method invocation failed because [System.IO.DirectoryInfo] doesn't contain a method named 'EnumerateFileSystemInfos'.
at System.Management.Automation.Runspaces.AsyncResult.EndInvoke()
at System.Management.Automation.PowerShell.EndInvoke(IAsyncResult asyncResult)
at System.Threading.Tasks.TaskFactory1.FromAsyncCoreLogic(IAsyncResult iar, Func2 endFunction, Action1 endAction, Task1 promise, Boolean requiresSynchronization)
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Inedo.Agents.PowerShell.PowerShellExtensions.<InvokeAsync>d__1.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Inedo.Agents.PowerShell.PowerShellAgentClient.<ExecuteScriptAsync>d__12.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Inedo.Agents.PowerShell.PowerShellFileOperationsExecuter.<GetFileSystemInfosAsync>d__21.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Inedo.Agents.PowerShell.PowerShellAgentClient.<CheckAndUpdateAgent>d__9.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Inedo.Otter.Extensions.Agents.PowerShell.PowerShellAgent.<CheckAndUpdateAgent>d__18.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Inedo.Otter.Service.Servers.ServerCheckerTimedExecuter.<CheckPowerShellAgentAsync>d__12.MoveNext()

[Alana]

Well... the error is a bit strange, because EnumerateFileSystemInfos is in fact a method on System.IO.DirectoryInfo. It's a core .NET class, so this error is "impossible" then...

I'm wondering if there's an older version of powershell or .net on the server? There has to be some other difference between the servers I would think...

You can trigger the RoutineServerChecker under Admin > Service. Hopefully you'll find some clues by running it repeatedly...