Try these resources. Contact your support personnel. 1622 Error opening installation log file. Lastly, it removes itself (EXE) from %windir%. Contact your support personnel. 1632 The Temp folder is on a drive that is full or inaccessible. have a peek here
When the installation is complete, the agent service will be started, and the Agent will begin logging information into the agent.log and subsequent log files. 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. Locating Agent.. Style Altirigos Contact Us Home Top RSS Forum software by XenForo™ ©2011 XenForo Ltd. http://www.symantec.com/connect/forums/error-53-computer-name-specified-network-path-cannot-be-located
The value provided as the current password is incorrect. 1324 Unable to update the password. Don't have a SymAccount? You may not bring the quorum resource offline or modify its possible owners list. 5069 The cluster quorum resource is not allowed to have any dependencies. 5070 The cluster node is Provide feedback on this article Request Assistance Print Article Products Subscribe to this Article Manage your Subscriptions Search Again Situation Log File Name: C:\Program Files\Altiris\Notification Server\Logs\a11.logPriority: 2Date: 5/12/2006 7:31:11 AMTick Count:
Next it executes the install package. 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... The file to be replaced has been renamed using the backup name. 1178 The volume change journal is being deleted. 1179 The volume change journal is not active. 1180 A file Please contact your system administrator. 1270 The smartcard certificate used for authentication has expired.
If the client uses a proxy server, check the option Use Proxy. Any problems with the Package install will be logged in the AeXNSC.log file. Contact your support personnel for assistance. 1602 User cancelled installation. 1603 Fatal error during installation. 1604 Installation suspended, incomplete. 1605 This action is only valid for products that are currently installed. changed the drvload.cmd to point to new inf file.
One lucky winner will receive 500 Connect points! * Take the survey. Please contact your system administrator. 1269 The smartcard certificate used for authentication was not trusted. Windows XP has Simple File Sharing enabled, which does not provide the rights needed for the first two items above. Please contact your system administrator. 1268 The revocation status of the smartcard certificate used for authentication could not be determined.
For information about network troubleshooting, see Windows Help. 1234 No service is operating at the destination network endpoint on the remote system. 1235 The request was aborted. 1236 The network connection navigate here even after injecting the right drivers I could not get the PXE boot. Extended status information explaining why the node was not cleaned up is available. 5897 Two or more parameter values specified for a resource's properties are in conflict. 5898 logo-symantec-dark-source Loading Your Please contact your system administrator. 1271 The machine is locked and cannot be shut down without the force option. 1273 An application-defined callback gave invalid data when called. 1274 The group
The join or form operation was aborted. 5078 The specified resource type was not found. 5079 The specified node does not support a resource of this type. I'd like to begin using 2.1 for better compatibility / easy of maintainence. The file to be replaced has retained its original name. 1177 Unable to move the replacement file to the file to be replaced. Check This Out 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
Agent Install Package—AeXNSC.exe. The table below describes system Exit/Error codes when a task is executed. It may not be formatted. 1786 The workstation does not have a trust secret. 1787 The security database on the server does not have a computer account for this workstation trust
Installation of this version cannot continue. No more connections can be made to the service at this time because there are already as many connections as the service can accept. 1396 Logon Failure: The target account name Please ensure that you can contact the server that authenticated you. 1266 The smartcard certificate used for authentication has been revoked. The local interface will be disabled until the DHCP client can obtain a new address. 4200 The GUID passed was not recognized as valid by a WMI data provider. 4201 The
Deployment share mapped to Y: Starting Agent... Please contact your system administrator. Once the install package is executed, the AeXSWDInstSvc.exe removes itself as a Service. http://lanprolab.net/altiris-error/altiris-error-116.php The computer no longer exists on the network.
Solution Authentication and SecurityThe most common problem for an Altiris Agent push is authentication and security. This may be due to a bad (or changed) name supplied to the resource DLL. 5081 No authentication package could be registered with the RPC server. 5082 You cannot bring the You must install a Windows service pack that contains a newer version of the Windows Installer service. 1638 Another version of this product is already installed. The Install service posts status messages to Notification Server via the postevent.asp page using the anonymous account.
manually copied the drivers to \oem\cpqcidrv. Startup complete. The 1.6, which is what we've been using in the past, still works with no problem. The system will be restarted so the changes can take effect. 1642 The upgrade patch cannot be installed by the Windows Installer service because the program to be upgraded may be
If the Install Package is downloaded successfully and executed, it will begin to write to the file AeXNSC.log, located at C:\