Platespin System Generated Error 53
Contents |
Favorite Rating: Network Path not
System Error 53 Has Occurred Net Use
Found error during discoveryThis document (7920732) is provided system error 53 net view subject to the disclaimer at the end of this document. Environment PlateSpin Migrate, Protect, system error 53 has occurred mapping network drive or Forge used to discover source Windows workloads. Situation "Network Path not found" error returned during the discovery process:This error is likely
System Error 53 Windows 10
to occur if the Remote Registry Service has not been started or if the Administrative shares (i.e. \\
Net Use System Error 53 Has Occurred. The Network Path Was Not Found
being discovered and ensure that the Administrative shares are enabled on the server being discovered. For more information on how to enable Administrative shares, please see Microsoft KB Article 842715.For additional tips on troubleshooting the PowerConvert discoveryprocess, please see TID 7920291. DisclaimerThis Support Knowledgebase provides a valuable tool for NetIQ/Novell/SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND. Document ID:7920732Creation Date:19-JUN-06Modified Date:27-APR-12NetIQPlateSpin ForgePlateSpin MigratePlateSpin Protect Did this document solve your problem? Provide Feedback © Micro Focus Careers Legal close Feedback Print Full Simple Request a Call Follow Us Facebook YouTube Twitter LinkedIn Newsletter Subscription RSS
Troubleshooting "System Error: 53 - Network Path not found" errors The information in this article applies to: DameWare Remote Support system error 53 has occurred windows 8 DameWare Mini Remote Control System Error: 53 ERROR_BAD_NETPATH The network path was
Net Use Error 5
not found. System errors are Microsoft Windows Operating System errors. Microsoft system error: 53 is not directly related to system error 53 has occurred windows 10 DameWare remote support software, but is a fairly common error message. The Remote Registry not running is the root cause of Microsoft Error 53. The following are some common things to http://www.novell.com/support/kb/doc.php?id=7920732 check when trying to resolve a System Error: 53 - Network path not found. Verify that File & Printer Sharing is enabled on the remote machine. Ensure all the necessary File & Printer Sharing ports are open on all routers/firewalls between the local and remote machines, and in any type of firewall software on the remote machine. Confirm that the Operating System http://support.dameware.com/kb/article.aspx?ID=300059 (O/S) is properly configured with regard to Names Resolution. This is important because DameWare software uses the O/S for all Names Resolution. For Example: Open a CMD prompt, then Ping the remote machine by its Host Name. Enable NetBios (i.e. NetBios over IP (NetBT/WINS), NetBios over IPX, etc.). For DameWare NT Utilities (DNTU) or DameWare Remote Support (DRS) Event Log, Properties, Processes, Registry, Services, or Software Views, verify that the Remote Registry Service is Enabled and Started manually on the remote machine. Note: this Service is not started by default under Vista. For the aforementioned views in DNTU/DRS, simply ensure the Remote Registry Service is running on the remote machine. Otherwise, this error can be easily duplicated outside of DameWare software by attempting to access the Admin$ share on the remote machine. For example: Open a CMD prompt on the local machine. Type: Net Use \\RemoteMachine\Admin$ or Net Use \\IP-Address\Admin$ Also note that File & Printer Sharing is required for all of the functionality within the DNTU/DRS software, and also by Microsoft's APIs used in the DameWare Mini Remote Control (DMRC) program to remotely in
unable to contact the PlateSpin Server. A common cause is incorrect information entered during the https://www.netiq.com/documentation/platespin-migrate-12/migrate_user/data/bgwivfi.html registration process. To restart the registration process, enter RegisterMachine.bat. Ping to confirm basic connectivity with the PlateSpin Server. My physical server has completed the registration process, but is not seen in PlateSpin Migrate Client The full registration process can take some time to complete. After the second error 5 command prompt window has closed on the physical server, wait a few minutes before clicking the Refresh button in PlateSpin Migrate Client. Problems discovering source and target servers KB Article 7920291 contains troubleshooting checklists for discovering the following: Linux servers and VMware ESX Servers Windows-based source and target system error 53 servers The article also has instructions for troubleshooting WMI connections and checking if DCOM is enabled. "Package <…> Not Found" during discovery of existing Windows servers Check for IIS configuration and network settings. Could not find file "\\{servername}\admin$\{randomID}.xml" This error might occur on Windows Server 2000 or 2003 hosts. In some cases, either of these troubleshooting steps addresses the issue: Ensure that the Admin$ share on the PlateSpin Server host is accessible. If not, enable it and try the discovery again. - OR - 1. From any Web browser, open https://Your_PlateSpin_Server/platespinconfiguration. 2. Locate and edit the ForceMachineDiscoveryUsingService entry and change it to true. 3. Save the value and retry the discovery. Related KB Articles: ID Description 7920339 ERRMSG: Discovery fails with "The request failed with HTTP status 407" message 7920862 ERRMSG: Recoverable Error: ControllerConnectionBroken during discovery 7920291 ERRMSG: Server details discovery problems