6.3 Troubleshooting Workload Inventory (Discovery)

Problems or Messages

Solutions

 
“Discover Server Details {hostname}” Failed
Progress: 0%
Status: NotStarted

This error can occur for several reasons and each has a unique solution:

  • For environments using a local proxy with authentication, bypass the proxy or add the proper permissions. See Knowledge Base article Q20339 for more details.

  • If local or domain policies restrict required permissions, follow the steps outlined in Knowledge Base article Q20862.

Workload Discovery fails with error message

Could not find file output.xml

or

Network path not found

There are several possible reasons for the “Could not find file output.xml” error:

  • Anti-virus software on the source could be interfering with the discovery. Disable the anti-virus software to determine whether or not it is the cause of the problem. See Disabling Anti-Virus Software.

  • File and Printer Sharing for Microsoft Networks might not be enabled. Enable it under the Network Interface Card properties.

  • The C$ and/or Admin$ shares on the source might not be accessible. Ensure that PlateSpin Forge can access those shares. See Enabling File/Share Permissions and Access.

  • Change the flag ForceMachineDiscoveryUsingService to true in the web.config file in the \Program Files\PlateSpin Portability Suite Server\Web folder.

  • The Server or the Workstation service might not be running. If this is the case, enable them and set the startup mode to automatic.

  • The Windows remote registry service is disabled. Start the service and set the startup type to automatic.

6.3.1 Disabling Anti-Virus Software

Anti-virus software might occasionally block some of the PlateSpin Forge functionality related to WMI and Remote Registry.In order to ensure that workload inventory is successful, it might be necessary to first disable the anti-virus service on a workload.In addition, anti-virus software might occasionally lock access to certain files, allowing access only to certain processes or executables. This might occasionally obstruct file-based data replication. In this case, when you configure the workload protection, you can select services to disable, such as services installed and used by anti-virus software. These services are only disabled for the duration of the file transfer, and are restarted when the process completes. This is not necessary during block-level data replication.

6.3.2 Enabling File/Share Permissions and Access

To successfully protect a workload, PlateSpin Forge needs to successfully deploy and install the OFX Controller and, if you require block-level replication, a dedicated block-based component. Upon deployment of these components to a workload, as well as during the Add Workload process, PlateSpin Forge uses the workload’s administrative shares. PlateSpin Forge needs administrative access to the shares, using either a local administrator account or a domain admin account for this to work.

To ensure that the Administrative shares are enabled:

  1. Right-click My Computer on the desktop and select Manage.

  2. Expand System Tools > Shared Folders > Shares

  3. In the Shared Folders directory, you should see C$ and Admin$, among other shares.

After confirming that the shares are enabled, ensure that they are accessible from within the Forge Management VM:

  1. Go to your Forge Management VM.

    See Accessing the Forge Management VM in the Appliance Host in your Appliance Setup and Maintenance Guide.

  2. Click Start > Run, type server>\C$, then click OK.

  3. If prompted, use the same credentials as those you will use to add the workload to the PlateSpin Forge workload inventory.

    The directory is opened and you should be able to browse and modify its contents.

  4. Repeat the process for all shares with the exception of the IPC$ share.

    Windows uses the IPC$ share for credential validation and authentication purposes. It is not mapped to a folder or file on the workload, so the test will always fail; however, the share should still be visible.

PlateSpin Forge does not modify the existing content of the volume; however, it creates its own directory, to which it requires access and permissions.