Altiris System Error 53
Contents |
PKI Service Identity Access Manager Shop Online Cyber Security Services Managed Security Services DeepSight Intelligence Incident Response Security Simulation Website Security SSL Certificates Complete Website Security Code Signing Certificates Norton Shopping Guarantee Buy SSL Products
Windows Pe System Error 53
A-Z Services Services Home Business Critical Services Consulting Services Customer Success Services system error 53 winpe Cyber Security Services Education Services Solutions Solutions Home Topics Encryption Everywhere Internet of Things Next Generation Endpoint Office 365
System Error 53 Has Occurred Net Use
Industries Automotive Cyber Insurance Education Financial Services Global Service Providers Industrial Control Systems Healthcare Retail Government Federal Government State & Local Support Center Technical Support Symantec Connect Buying Programs Upgrades Maintenance system error 53 net view & Renewals Training Security Center Security Center Home Blogs ISTR Threats Virus Definitions and Security Updates Removal Tools Partner Find a Partner Become a Partner Login Required Login into Partner Portal Partner Licensing Partner Renewals Partner Training Margin Builder Opportunity Registration Financial Benefits English 中文(简体) 中文(繁體) Česká English Français Deutsch Magyar Italiano 日本語 한국어 Polski Português Pусский Español Site: Symantec Enterprise Small Business system error 53 has occurred mapping network drive Norton United States Search Support Home Support Home MySymantec Licensing Products A-Z SYM16-015 Security Advisory Login Profile Subscriptions Logout Login Forgot Password? Don't have a SymAccount? Create a SymAccount now!' WinPE automation error "System Error 53 - path was not found" when mapping drive to Windows 2008 server TECH43019 January 25th, 2010 http://www.symantec.com/docs/TECH43019 Support / WinPE automation error "System Error 53 - path was not found" when mapping drive to Windows 2008 server Did this article resolve your issue? Thank you for your feedback! Provide feedback on this article Request Assistance Print Article Products Subscribe to this Article Manage your Subscriptions Search Again Situation Create/ Restore jobs failwiththe followingerrors: Client Side: System Error 53 - path was not found On the DS Console side: File could not be opened (code 41) WinPE failed to map the images folder located on the Windows 2008 server. However, when manually entering the path using a"net use" command, the WinPE map drive map and function correctly. Cause Mapping adriveto a folder ona Windows 2008 server,requires FQDN for the username. Solution Edit the mapdrv.bat located on (\Program Files\ Altiris\eXpress\Deployment Server\PXE\Master I
be down. Please try the request again. Your cache administrator is webmaster. Generated Fri, 30 Sep 2016 09:57:14 GMT by s_bd40 (squid/3.5.20)
11, 2008. Kai Mallea New Member Hey all, When performing a PXE boot using a newly-created WinPE 2.1 menu item, I receive "System error 53 The network path was not found" OR ""System error http://www.altirigos.com/forums/threads/pxe-boot-system-error-53-or-1231-upon-map-to-express-share.10044/ 1231 has occurred. The network location cannot be reached." However, if I manually type NET http://support.dameware.com/kb/article.aspx?ID=300059 USE Y: \\server\share with username/pw credentials, immediately afterwards, it maps fine.... The wpeinit.log says the following (this from a Lenovo T41): - Installing device pci\ven8086&dev101e\... X:\Windows\INF\oem14.inf succeeded. - Spent 5138ms installing network drivers - QueryAdapterStatus: no adapters operational - Spent 0ms confirming network initialization; status 0x003d0001 - STATUS: SUCCESS (0x003d0001) It seems as though the NIC doesn't have enough time system error to initialize (shrug). Has anyone seen this before? It doesn't seem to be hardware-specific as it's occurred on two different Lenovo model laptops (T41, T400), an HP desktop and a Virtual Machine configured to use an Intel e1000 NIC. I recently upgraded from DS6.8 to DS 6.9 SP1 (w/ Hotfixes). I have two PXE boot menu items -- one from Windows PE 1.6 and the other Windows PE 2.1. The 1.6, which is what we've system error 5 been using in the past, still works with no problem. I'd like to begin using 2.1 for better compatibility / easy of maintainence. Kai Mallea, Nov 11, 2008 #1 Kai Mallea New Member Okay, so I modified the mapdrv.bat in the boot.wim and added a wait command: await 15 "Waiting for %d seconds..." Looks like that fixes that: Mapping network drives... Waiting for d seconds... The command completed successfully. Deployment share mapped to Y: Starting Agent... Locating Agent.. Searching Deployment Share for Agent... > 6.8.378 .. "Y:\Agents\Aclient\altiris-dagent-*.x86.exe" > 6.9.355 .. "Y:\Agents\Aclient\altiris-dagent-*.x86.exe" > Highest ver=6.9.355 > Hhighest file=Y:\Agents\AClient\altiris-dagent-6.9.355.x86.exe Copying agent 6.9.355 from Deployment Share at Y:\agents\aclient... Starting Remote Agent X:\dagent\dagent.exe... Launching dagent [d]... Calling custom actions... Startup complete. HOWEVER, now the DAgent just sits there saying "Client Record Updated." Doesn't show up in DS. If I boot up 1.6, it comes up fine. Grrr. If it's not one thing it's another! I have all public hotfixes applied. Kai Mallea, Nov 11, 2008 #2 bhavani New Member unable to PXE boot getting DHCP retry error absolutely its the drivers the problem. even after injecting the right drivers I could not get the PXE boot. but I tried ctrl+c on the error. manually copied the drivers to \oem\cpqcidrv. changed the drvload.cmd to point to new inf file. ran the starnet.cmd again and I was able to
Troubleshooting "System Error: 53 - Network Path not found" errors The information in this article applies to: DameWare Remote Support DameWare Mini Remote Control System Error: 53 ERROR_BAD_NETPATH The network path was not found. System errors are Microsoft Windows Operating System errors. Microsoft system error: 53 is not directly related to 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 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 (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 f