NO MACHINE FOUND

Sep 11, 2014 at 8:51 AM
Edited Sep 11, 2014 at 9:05 AM
Problem is that an instance is found but is not scanned and no xml file is written to disk. I can't see any errors in the event logs on my computer or the Server. I have tried multiple user accounts all with same problem.

I am running the script on windows7, sql server 2012 is running on windows server 2008 r2. Both is on the same domain.

Command used to execute
.\Get-SqlServerInventory ToClixml.ps1 -Computername SERVER -LoggingPreference verbose -directorypath c:\inventory


2014-09-11 10:42:15.7209 ? Starting Script: C:\users\administrator\documents\WindowsPowerShell\Get-SqlServerInventoryToClixml.ps1
2014-09-11 10:42:15.7299 ? Beginning SQL Server Inventory
2014-09-11 10:42:15.7329 ? -LoggingPreference: verbose
2014-09-11 10:42:15.7359 ? -ComputerName: SERVER
2014-09-11 10:42:15.7389 ? -MaxConcurrencyThrottle: 4
2014-09-11 10:42:15.7419 ? -PrivateOnly: False
2014-09-11 10:42:15.8149 ? -ParentProgressId: -1
2014-09-11 10:42:15.8179 ? -IncludeDatabaseObjectPermissions: False
2014-09-11 10:42:15.8209 ? -IncludeDatabaseObjectInformation: False
2014-09-11 10:42:15.8239 ? -IncludeDatabaseSystemObjects: False
2014-09-11 10:42:15.8299 ? Beginning network scan
2014-09-11 10:42:15.8339 ? -ComputerName: SERVER
2014-09-11 10:42:15.8359 ? -PrivateOnly: False
2014-09-11 10:42:15.8389 ? -MaxConcurrencyThrottle: 4
2014-09-11 10:42:15.8419 ? -ResolveAliases: True
2014-09-11 10:42:15.8449 ? Resolving IP address for SERVER
2014-09-11 10:42:15.8930 ? Testing PING connectivity to 1 addresses
2014-09-11 10:42:15.9000 $ Testing PING connectivity to SERVER.DOMAIN.LOCAL (XX.XX.XX.XX) [1 of 1]
2014-09-11 10:42:18.1652 $ PING response from SERVER.DOMAIN.LOCAL (XX.XX.XX.XX): True
2014-09-11 10:42:18.4432 $ PING connectivity test complete
2014-09-11 10:42:18.4512 ? Testing WMI connectivity to 1 addresses
2014-09-11 10:42:18.4572 $ Testing WMI connectivity to SERVER.DOMAIN.LOCAL (XX.XX.XX.XX) [1 of 1]
2014-09-11 10:42:18.7132 $ WMI response from SERVER.DOMAIN.LOCAL (XX.XX.XX.XX): True
2014-09-11 10:42:18.9753 $ WMI connectivity test complete
2014-09-11 10:42:18.9893 ? Network scan complete
2014-09-11 10:42:18.9943 ? -IP Addresses Scanned: 1
2014-09-11 10:42:18.9983 ? -PING Replies: 1
2014-09-11 10:42:19.0023 ? -WMI Replies: 1
2014-09-11 10:42:19.0063 ? Beginning SQL Service discovery scan
2014-09-11 10:42:19.0573 ? Scanning SERVER.DOMAIN.LOCAL at IP address XX.XX.XX.XX for SQL Services [Device 1 of 1]
2014-09-11 10:42:19.5643 ? Found SQL Server named instance SERVER.DOMAIN.LOCAL\BI at IP address XX.XX.XX.XX
2014-09-11 10:42:19.5713 ? Found SQL Server Agent named instance SERVER.DOMAIN.LOCAL\BI at IP address XX.XX.XX.XX
2014-09-11 10:42:19.8964 ? SQL Server service discovery complete
2014-09-11 10:42:19.9024 ? -SQL Server Instance Count: 1
2014-09-11 10:42:19.9064 ? -SQL Server Agent Instance Count: 1
2014-09-11 10:42:19.9114 ? Beginning scan of 0 instance(s)
2014-09-11 10:42:20.2184 ? Instance scan complete (Success: 0; Failure: 0)
2014-09-11 10:42:20.2304 ? Writing Inventory to disk
2014-09-11 10:42:20.2354 + No machines found!
2014-09-11 10:42:20.2384 ? End Script: C:\users\administrator\documents\WindowsPowerShell\Get-SqlServerInventoryToClixml.ps1
Sep 15, 2014 at 9:27 AM
Hi,
I have just been investigating a similar problem. After a bit of digging around I noticed that someone had installed the SQL 2014 SMO objects on the server. There are no 2014 instances installed.

You can check which versions are installed in here C:\Windows\assembly and look for Microsoft.SqlServer.Smo.

I'm just experimenting with a local fix for this.

Thanks
Paul.
Sep 16, 2014 at 10:52 AM
I have installed SQL Server 2014 on my computer so thanks for the help. Please let me know when our fix is finished :)
Sep 22, 2014 at 5:36 PM
Hello,

I believe I may have observed a similar failure state. Specifically, I am remotely scanning a SQL Server 2014 host. The logs indicate SQL Power Doc works as expected during ping, WMI, and SQL instance detection phases, but then does not see the instance when its begins to actually scan the instance.

I have SQL Server 2014 Feature Pack installed on the host performing the scanning.

Any guidance or workarounds appreciated.

Thank you
2014-09-22 17:29:55.5221 ? Starting Script: C:\Users\pa_user\Documents\WindowsPowerShell\Get-SqlServerInventoryToClixml.ps1
2014-09-22 17:29:55.5318 ? Beginning SQL Server Inventory
2014-09-22 17:29:55.5348 ?  -LoggingPreference: Verbose
2014-09-22 17:29:55.5367 ?  -ComputerName: host
2014-09-22 17:29:55.5396 ?  -MaxConcurrencyThrottle: 4
2014-09-22 17:29:55.5416 ?  -PrivateOnly: False
2014-09-22 17:29:55.5436 ?  -ParentProgressId: -1
2014-09-22 17:29:55.5455 ?  -IncludeDatabaseObjectPermissions: False
2014-09-22 17:29:55.5465 ?  -IncludeDatabaseObjectInformation: False
2014-09-22 17:29:55.5484 ?  -IncludeDatabaseSystemObjects: False
2014-09-22 17:29:55.5621 ? Beginning network scan
2014-09-22 17:29:55.5650 ?  -ComputerName: host
2014-09-22 17:29:55.5670 ?  -PrivateOnly: False
2014-09-22 17:29:55.5689 ?  -MaxConcurrencyThrottle: 4
2014-09-22 17:29:55.5768 ?  -ResolveAliases: True
2014-09-22 17:29:55.5787 ? Resolving IP address for host
2014-09-22 17:29:55.7398 ? Testing PING connectivity to 1 addresses
2014-09-22 17:29:55.7496 $ Testing PING connectivity to host.example.com (10.1.31.53) [1 of 1]
2014-09-22 17:29:58.0173 $ PING response from host.example.com (10.1.31.53): True
2014-09-22 17:29:58.2722 $ PING connectivity test complete
2014-09-22 17:29:58.2771 ? Testing WMI connectivity to 1 addresses
2014-09-22 17:29:58.4108 $ Testing WMI connectivity to host.example.com (10.1.31.53) [1 of 1]
2014-09-22 17:29:58.6736 $ WMI response from host.example.com (10.1.31.53): True
2014-09-22 17:29:58.9333 $ WMI connectivity test complete
2014-09-22 17:29:58.9363 ? Network scan complete
2014-09-22 17:29:58.9392 ?  -IP Addresses Scanned: 1
2014-09-22 17:29:58.9421 ?  -PING Replies: 1
2014-09-22 17:29:58.9441 ?  -WMI Replies: 1
2014-09-22 17:29:58.9470 ? Beginning SQL Service discovery scan
2014-09-22 17:29:59.0456 ? Scanning host.example.com at IP address 10.1.31.53 for SQL Services [Device 1 of 1]
2014-09-22 17:29:59.5681 ? Found SQL Server default instance host.example.com at IP address 10.1.31.53
2014-09-22 17:29:59.5701 ? Found SQL Server Agent default instance host.example.com at IP address 10.1.31.53
2014-09-22 17:29:59.8289 ? SQL Server service discovery complete
2014-09-22 17:29:59.8328 ?  -SQL Server Instance Count: 1
2014-09-22 17:29:59.8347 ?  -SQL Server Agent Instance Count: 1
2014-09-22 17:29:59.8416 ? Beginning scan of 0 instance(s)
2014-09-22 17:30:00.3074 ? Instance scan complete (Success: 0; Failure: 0)
2014-09-22 17:30:00.3406 ? Writing Inventory to disk
2014-09-22 17:30:00.3435 + No machines found!
2014-09-22 17:30:00.3484 ? End Script: C:\Users\pa_user\Documents\WindowsPowerShell\Get-SqlServerInventoryToClixml.ps1
Sep 22, 2014 at 5:50 PM
False alarm -- I just needed to start a new PowerShell ISE instance after installing the SQL Server 2014 Feature Pack.

My old Powershell ISE instance still had a mix of SQL Server 2008/2012 management assemblies loaded, confirmed via procexp.exe. The new PowerShell ISE instance has only 2014 assemblies loaded.
Oct 14, 2014 at 3:58 PM
I'm getting the same issue with SMO on clustered instances. It seems to work fine on my one stand alone VM, but when I try to connect to the clusters (win 2008R2, SQL 2008R2) using the active node names it either throws an SMO error or it finds no machines when the Get-SQLServerInventory runs. 2 clusters get through the WMI discovery and find no machines when they get to the cluster while the other 2 clusters get the SMO error. I tried running from my machine and on the active node. I get the following error from the SMO Test and SMO assemblies are version 10.0.0.0 in c:\windows\assembly on the nodes:

The following exception was thrown when trying to enumerate the collection: "An exception occurred in SMO while trying
to manage a service.".
At line:1 char:1
  • <<<< $ManagedComputer.Services | Format-Table -Property DisplayName, StartMode, ServiceState, ProcessId
    • CategoryInfo : NotSpecified: (:) [], ExtendedTypeSystemException
    • FullyQualifiedErrorId : ExceptionInGetEnumerator
Coordinator
Nov 11, 2014 at 5:59 PM
mrbru2,
Usually this error happens when you try to connect to a version of SQL Server that is newer than the version of SMO that's being used for the connection. What version number of SQL Power Doc are you using? It's also possible this is a code issue that needs to be fixed.

--Kendal