This section provide solutions to the issues you might encounter when using PlateSpin Recon:
Refresh Inventory or Monitoring fails for a machine whose operating system has been reformatted
PlateSpin Recon fails to inventory the FC SAN disk connected to a Citrix XenServer 4.0 machine
Inventory of Solaris or Linux machines might fail with an error
The Queue Length metrics are not collected for Virtual Center and ESX
Monitoring a Windows machine fails with an error related to access to the registry keys
The loop7 partitions of Citrix XenServer are inventoried and monitored as a new disk
Unable to detect the processor model for a Windows operating system installed on Connoi hardware
Issues when attempting to add servers to the PlateSpin Recon Inventory
A warning message is logged in the monitoring log while monitoring the Windows XP machines
Monitoring of data collection for the newly added disks or volumes is delayed for Windows machines
The data for the counters related to disk utilization might not be collected for Solaris servers
The data of a few disk counters for the disconnected disks on Solaris is incorrectly displayed
Monitoring of a Windows machine displays the “Category does not exist” error in the monitoring log
W3P Service consumes high memory or is terminated with system memory out of exception
Unable to generate Cost allocation report with Allocation rater
Monitoring of a Linux machine by using sudo user credentials might fail
Refresh Inventory and Monitoring of machines inventoried by using the CSV file might fail
Logs Explorer might display the warning, “Client data may be out of date”
The PlateSpin Recon Monitoring service is terminated because of the out of memory exception
Creating scenarios for forecasted projects might fail with the out of memory exception
Generating Analysis reports from the PostgreSQL database might take a considerable time
The storage type for disks attached to AIX machines is displayed as Unknown
Importing of a snapshot that contains Citrix Xen virtual machines fails
The operating system type for Windows 2003 R2 and Windows 2008 R2 devices is displayed as Unknown
Inventorying a host machine with VMs cloned within the same host machine throws a warning message
Inventorying a host machine with VMs shared across multiple host machines throws a warning message
The operating system type for OES VM is incorrectly displayed in the VM Details Report
Deploying or undeploying add-on on a large set of machines might result in an error
The operating system type for some virtual machines might not be displayed
Monitoring Red Hat Enterprise Linux servers with sudo user account fails
Refresh Inventory or Monitoring fails for a machine whose operating system has been reformatted
Delete the existing object of the machine whose operating system has been reformatted.
Inventory or monitor the machine.
For more information on how to inventory or monitor a machine, see Section 3.2, Discovering and Inventorying Data Center Resources.
Disk partitions for Citrix XenServer are not displayed
PlateSpin Recon fails to inventory the FC SAN disk connected to a Citrix XenServer 4.0 machine
Inventory of Solaris or Linux machines might fail with an error
Disk IO metrics are not available for ESX 3.0
The Queue Length metrics are not collected for Virtual Center and ESX
Monitoring a Windows machine fails with an error related to access to the registry keys
Access to the registry key key_number is denied.
Disk partition counters report errors for the AIX machines
PhysicalDisk_PartitionedSpaceGB
PhysicalDisk_UnpartitionedSpaceGB
PhysicalDisk_PercentPartitionedSpace
PhysicalDisk_PercentUnpartitionedSpace counters
Additionally, a warning message is displayed in the logs. The warning message also includes the solution for the issue.
The loop7 partitions of Citrix XenServer are inventoried and monitored as a new disk
Unable to detect the processor model for a Windows operating system installed on Connoi hardware
Issues when attempting to add servers to the PlateSpin Recon Inventory
Network Path Not found
Access Denied
The RPC Server is unavailable
Failed. The Network location cannot be reached
Importing a machine from PlateSpin Recon snapshot fails
Cannot import MachineObject 'MACHINE-NAME [MACHINE-NAME]'
A warning message is logged in the monitoring log while monitoring the Windows XP machines
The interface is unknown counter_name.
Monitoring of data collection for the newly added disks or volumes is delayed for Windows machines
In the Data Center Explorer, navigate to target Windows machine.
Right-click the target machine, then click Stop Monitoring.
Right-click the target machine again, then click Start Monitoring.
The data for the counters related to disk utilization might not be collected for Solaris servers
The data of a few disk counters for the disconnected disks on Solaris is incorrectly displayed
DiskBytesPerSecond
DiskAverageQueueLength
DiskTransfersPerSecond
DiskPercentIdleTime
Disk IO%
Run the devfsadm -C command.
Reboot the machine.
Monitoring of a Windows machine might fail
The network path was not found
Generating of the Disk Analysis report or the raters based on disk usage for Windows machines might fail
The component Disk Space Used(GB) does not have enough hourly summary data for the machine IP_address.
Deploy the Disk Utilization add-on on the target Windows machine.
For more information about deploying the Disk Utilization add-on, see Section 3.12, Collecting Disk Utilization Counters for Windows Machines.
Monitor the Windows machine for a minimum duration of one hour.
Generate the Disk Analysis report or the rater.
Monitoring of a Windows machine displays the “Category does not exist” error in the monitoring log
Right-click the Windows machine object on which you have manually undeployed the Windows Disk Counters Add-On.
Click Undeploy Add-On.
Right-click the Windows machine object.
Click Stop Monitoring.
Right-click the Windows machine object.
Click Start Monitoring.
net view \\IPaddress_of_remote_machine
In the Registry Editor, navigate to HKLM\SYSTEM\CurrentControlSet\Services\ReconWinMonitoring\Performance.
Change the value of the registry key Disable Performance Counters to 0.
Restart the Remote Registry service.
Event ID 1015 Source Perflib Event ID 1015 Source Perflib Type Error Description The timeout waiting for the performance data collection function"<function name>" in the "<dll name>" Library to finish has expired. There may be a problem with this extensible counter or the service it is collecting data from or the system may have been very busy when this call was attempted.
In the Registry Editor, navigate to HKLM\SYSTEM\CurrentControlSet\Services\<service-name>\Performance.
Increase the value of Collect Timeout.
Restart the Remote Registry service.
W3P Service consumes high memory or is terminated with system memory out of exception
Disk Space % in scenarios is shown as 0 even though Disk Space (GB) has a value when you view the chart for a workload
The chart for the Disk Space (%) utilization, viewed on the server template and the assigned workloads to that template, always shows zero (0) for y.
The workload assignment report on the server template shows empty (--) values for the Disk Used (%) column.
Monitoring of a virtual machine that runs on a Windows 2008 SP1 Hyper-V displays an error for the % Total Run Time counter
Cannot get instance information for counter % Total Run Time in category Hyper-V Hypervisor Virtual Processor on computer w2k8vm204
Monitoring of a Windows virtual machine that runs on a Citrix XEN server might displays an error for the Xen_NetworkInterface_BytesTotalPerSecond and Xen_PhysicalDisk_DiskBytesPerSecond counters
The HANDLE_INVALID exception when monitoring the following counters:
Xen_NetworkInterface_BytesTotalPerSecond
Xen_PhysicalDisk_DiskBytesPerSecond.
The data is not collected for the Xen_Processor_PercentProcessorTime counter even though there is no exception.
Deploying or undeploying of the Windows Disk Counters add-on fails if you select to perform it on Windows Server 2008 SP2 Hyper-V host and its guest virtual machine
Unable to generate Cost allocation report with Allocation rater
Error was encountered during calculation for chargeback.
All the appropriate warning messages are logged in the Cost Allocation report’s job log file located in the Recon_server_installation_directory\logs\workflow directory.
Monitoring of a Linux machine by using sudo user credentials might fail
sudo: sorry, you must have a tty to run sudo
At the Linux console prompt, execute visudo.
This opens the /etc/sudoers configuration file in the vi editor.
Comment out the following line:
Defaults requiretty
In the Data Center Explorer view of Recon PlateSpin Client, right click the Linux machine, then click Stop Monitoring.
Right-click the Linux machine, then click Start Monitoring.
The value of HyperV_NetworkInterface_BytesTotalPerSecond is incorrect for virtual machines that are configured to a legacy network adapter and run on Windows Server 2008 SP1/SP2/R2 Hyper-V host
Restarting of Remote Registry service after deployment or undeployment of the Windows Disk Counters Add-On fails with errors
On the target machine, open the Registry Editor.
Navigate to the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ReconWinMonitoring key. If the key exists, it indicates that the %SystemRoot%\PlateSpinRecon-DiskUtil directory exists. Do the following:
From the command prompt of the target machine, go to %systemroot%\PlateSpinRecon-DiskUtil.
Execute the following command:
HWInputMon.exe -Uninstall false
Delete the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ReconWinMonitoring key.
Delete the %SystemRoot%\PlateSpinRecon-DiskUtil directory.
The deployment or undeployment of the Windows Disk Counters add-on might result in the error, “The process cannot access the file because it is being used by another process”
The process cannot access the file because it is being used by another process
Refresh Inventory and Monitoring of machines inventoried by using the CSV file might fail
Delete the problematic machines from the PlateSpin Recon Client, specify a unique credential description for the machines listed in the CSV file, then inventory the machines again.
Attach the correct credentials to the problematic machines.
In the Data Center Explorer, right-click the problematic machine, then click Attach Credentials.
The Attach Credentials dialog box is displayed.
Specify the credentials for the machine, then click OK.
Performing Stop Monitoring and Start Monitoring jobs in immediate successions on a large set of UNIX machines might result in an error
/bin/sh: ./lininfo.shSLESPlateSpinRecon_server_name: No such file or directory counter_name
PlateSpin Recon Client might incorrectly display the status of a job as running even after the job has been completed
Stopping of the PlateSpin Recon Monitoring service might take considerable time or restarting of the PlateSpin Recon Monitoring service might fail
When you try to restart the PlateSpin Recon Monitoring service, the service might fail to restart because the restart process first tries to stop the service, which takes considerable time to complete.
If you had initiated the restart action for the PlateSpin Recon Monitoring service, you must start the service after it becomes responsive (the service actions are available for selection).
WARNING:You must not try to terminate the PlateSpin Recon Monitoring Service process because it might lead to data inconsistency.
Logs Explorer might display the warning, “Client data may be out of date”
Client data may be out of date.
The PlateSpin Recon Monitoring service is terminated because of the out of memory exception
Loading of the PlateSpin Recon job from the Portability Suite might display a credential-specific error
Unable to login to VMware Virtual Infrastructure web... Please ensure that the username and password are correct.
The error is displayed in the PlateSpin Portability Suite.
In the Peer-to-Peer Conversion Job window, click the Job Configuration panel > the Credentials link.
Specify the password.
Click OK.
Inventory of Solaris machine fails
Creating scenarios for forecasted projects might fail with the out of memory exception
Generating Analysis reports from the PostgreSQL database might take a considerable time
Open the PlateSpin.PowerRecon.Monitoring.Database.config file using a Text editor.
The PlateSpin.PowerRecon.Monitoring.Database.config file is located in the PlateSpin_Recon_installation_directory\configs\ directory on the PlateSpin Recon Server.
Change the value of Pooling to True.
Restart the PlateSpin Recon Monitoring Service.
The storage type for disks attached to AIX machines is displayed as Unknown
Importing of a snapshot that contains Citrix Xen virtual machines fails
Inventory the Citrix Xen virtual machines only without inventorying the host machine.
Inventory first the Citrix Xen host machine and subsequently the Citrix Xen virtual machines.
The operating system type for Windows 2003 R2 and Windows 2008 R2 devices is displayed as Unknown
In Consolidation Project Samples, right-click Inventory Summary and select Edit Report Template.
The Edit Report Template window is displayed.
Navigate to the Views panel, select OS Summary view and click Edit.
The Create View window is displayed.
Click Customize.
The Settings window is displayed.
Add the required operating system to the list of operating systems and click OK.
NOTE:Ensure that the Internal name you give to the operating system is either Windows 2003 R2 or Windows 2008 R2.
Monitoring Linux machines that are inventoried by using sudo user credentials throws a warning message
root'''s password: Memory_AvailableBytes
Inventorying a host machine with VMs that are either migrated from other host machines or cloned across multiple host machines throws a warning message
Machine with HostName: [HostName] and MachineID: [MachineID] Skipped due to duplicate SMBIOSUUID of [SMBIOSUUID] is already present in the Host with HostName: [HostName] and HostMachineID: [HostMachineID]If the machine is Moved/Migrated from other Host to this Host then please do a refresh inventory on Host: [HostName] and then Refresh Inventory this Host again to identify/discover the VM associated with the present host. And if the machine is cloned across various host then please change the SMBIOSUUID in order to identify/discover the VM associated with the present host
If the VM has been moved or migrated from a machine with hostname: host1 to a machine with hostname: host3, perform a refresh inventory of the machine from where the VM is migrated (host1) followed by a refresh inventory of the machine to which the VM is migrated (host3).
If the VM has been cloned across multiple hosts and has the same SMBIOS UUID across the hosts, edit the SMBIOS UUID of the VM to make it unique. Otherwise, you might encounter errors. For example, the VM might get associated with the wrong host. For more information on the errors, see the following scenarios:
Inventorying a VM that is cloned across multiple host machines might incorrectly associate the VM with a host machine to which it does not belong
Refresh Inventorying a host machine having a cloned VM with a duplicate SMBIOS UUID throws a warning message
Generating cost allocation report with allocation rater throws a warning message when VMs with duplicate SMBIOS UUID are inventoried before Inventorying the host machine
The rater [rater name] cannot be evaluated - could not find the parent virtual server for the machine.
Inventorying a host machine with VMs cloned within the same host machine throws a warning message
The machine with id:[MachineID] has been skipped because there are two or more virtual machines with the same SMBIOSUUID:[SMBIOSUUID] in the container. To discover all the virtual machines within the container, you must ensure that the virtual machines have unique SMBIOSUUID
Inventorying a host machine with VMs shared across multiple host machines throws a warning message
Machine with HostName: [HostName] and MachineID: [MachineId] Skipped due to duplicate SMBIOSUUID of [SMBIOSUUID] is already present in Recon DB. Possible Reason might be it is shared VM across Host.If it is a shared VM it will only be associated with a single Host.
Generating Virtual Infrastructure report for a group generates reports for all the nodes in the Data Center Explorer of the Recon server
The operating system type for OES VM is incorrectly displayed in the VM Details Report
For 32-bit OES VM: SUSE
For 64-bit OES VM: Unknown
Deploying or undeploying add-on on a large set of machines might result in an error
"Failed to lazily initialize a collection" error
For information on how to deploy and undeploy the add-on, see the following sections:
The operating system type for some virtual machines might not be displayed
VM Sprawl Report
The properties page of an inventoried Hyper-V or XenServer hypervisor
To view the operating system type for the virtual machines both in the VM Sprawl Report and in the properties page of the inventoried hypervisor: Before you inventory the hypervisor, ensure that the relevant hypervisor tools (Hyper-V tools or XenServer tools) are installed on the virtual machines.
To view the operating system type for the virtual machines only in the properties page of the inventoried hypervisor: Inventory each of the virtual machines using their IP Address.
Creating scenarios for forecasted projects might fail
Unable to create consolidation plan for scenario. Forecasted values are out of range, please try creating project or scenario without forecasting.
Object reference not set to an instance of an object.
This is a known issue with Exponential and Linear forecasting.
Create a project or a scenario without forecasting.
Create a project or a scenario by using a forecasting type other than Exponential or Linear forecasting.
Monitoring Red Hat Enterprise Linux servers with sudo user account fails
sudo: sorry, you must have a tty to run sudo
Defaults requiretty