Tentacle Connectivity Problem on 3.06

Legacy Uncategorised
1

Hi,

We’ve upgraded to Octopus 3 and 16/17 Tentacles have all upgraded fine.

I’ve got one server left that’s throwing an error when I try the connectivity check:

Running health check
10:13:00Info
Sending health check request
10:13:04Error
Get-WmiObject : Invalid class
10:13:04Error
At C:\Octopus\Work\20150729091301-1\Script.ps1:17 char:15
10:13:04Error

  • Get-WmiObject <<<<  win32_logicaldisk | ? { ($_.DriveType -eq 3) -and ($_

10:13:04Error
.FreeSpace -ne $null)} | % {
10:13:04Error
+ CategoryInfo : InvalidOperation: (:slight_smile: [Get-WmiObject], Managemen
10:13:04Error
tException
10:13:04Error
+ FullyQualifiedErrorId : GetWMIManagementException,Microsoft.PowerShell.C
10:13:04Error
ommands.GetWmiObjectCommand
10:13:04Error
10:13:04Fatal
The remote script failed with exit code 1

Any ideas why this is?

Thanks.

2

A little more info:

It appears to be failing at:

Get-WmiObject win32_logicaldisk

Not entirely sure why this isn’t working, the server is 2008 R2.

3

Hi Dan

Thanks for getting in touch.

That’s an interesting one, a couple of things to check.

Does this machine have a different version of Powershell on it to the others ?
Can you run those commands on it directly ?

Regards

Damian

4

Hi,

I’ve got at least two tentacles running the same version of windows and powershell. I’ve tried running “Get-WmiObject win32_logicaldisk” on both machines and only the problem one returns Invalid Class. The other works fine.

5

Hi Dan,

Thanks for the reply. I’m taking this one from Damian (yep, there are two of us!)

It does sound like there’s something unusual going on - I’m searching for solutions.

Is there any chance that tentacle machine has an NFS mapped drive? This blog post seems to suggest that could cause an issue.

Damo