SYSTEMS MANAGEMENTError code Error description Suggested next step3328 The deploy operation failed. The Verify that the account used to deployadministrator is unable to copy the update has write access to thethe file to the remote system. temp directory on the target machine.3329 The administrator is unable to See the “Step 1: Connectivity” sectionconnect to the remote system. in this article.3330 The administrator is unable to Verify that the account used to deployaccess the specified share on the update has write access to thethe remote system.temp directory on the target machine.3331 The administrator is unable to For Windows targets, see theexecute the WMI method to “Minimum WMI permissions” sectioncreate the process on the remote in this article.system or unable to execute theSSH client.3332 The remote system did not For Windows targets, see theexecute the remote process. “Minimum WMI permissions” sectionin this article.3335 The administrator is unable to Verify that the account used to deploycreate a temporary file to hold the update has write access to theexecution results on the remote temp directory on the target machine.system.3340 The administrator is unable to If a firewall is configured, refer to theconnect to the remote device. ITA readme.txt for additional informationabout configuring firewalls to enableremote connection.3341 The administrator is unable to Verify that the account used to deployretrieve the results from the the update has write access to thetemporary file that contains the temp directory on the target machine.remote program execution output.3342 The administrator has invalid For Windows targets, see thepermissions to run the remote “Minimum WMI permissions” sectioncommand.in this article.3353 An invalid username was Verify that the credentials providedspecified.correspond to an account that hasadministrative rights on the targetsystem.Tester dialog box. From this dialog box, administrators should click theConnect button to open the Connect dialog box, in which they can enterthe details of the target system being tested (see Figure 2).Administrators should enter “\\IP of remote system\root\cimv2”in the Namespace field and the proper username, password, andauthority in the Credentials section—these should be the samecredentials that are set up in ITA. The other fields on this screencan be left in the default state. Administrators should then click theConnect button to establish a connection to the target system.If an error message occurs at this point, the provided credentialsmost likely do not have access to the target system. If the connectionwas successful, administrators will see the Wbemtest main screen.They should then click the Execute Method button, which will opena small dialog box prompting for an object path. Administratorsshould enter “win32_process” (making sure there are no spacesbefore or after this phrase) and click the OK button. This actionbrings up the Execute Method dialog box, in which administratorsshould use the Method drop-down menu to select the Createmethod and then click the Edit In Parameters button. The objecteditor, shown Figure 3, will then appear. Administrators shouldscroll down through the Properties list box, select the CommandLineproperty, and click the Edit Property button.In the Property Editor dialog box, administrators need to changethe Value section by setting the radio button to “Not NULL” andentering “Ping /t 127.0.0.1” in the text area (see Figure 4). Next,3354 And invalid password was Verify that the credentials providedspecified.correspond to an account that hasadministrative rights on the targetsystem.3360 An exception occurred during Choose the Trust option in ITA.remote Dell OpenManage ServerAdministrator command-lineinterface (CLI) processing.3365 Invalid network credentials were Verify that the credentials providedspecified when connecting the correspond to an account that hasshare.administrative rights on the targetsystem.3366 The administrator has invalid Verify that the credentials providedauthentication rights.correspond to an account that hasadministrative rights on the targetsystem.3367 There are insufficient privileges For Windows targets, see thefor WMI to execute processes “Minimum WMI permissions” sectionon the remote system.in this article. Check that the followingitems are configured correctly: theprivilege “Replace a Process LevelToken” in the Local Security Settingsmust grant access to the Local Serviceand the Network Service; and the LocalSecurity Settings, WMI SecuritySettings, and any other security settingsthat deviate from the default settingsmust be set to default.3369 The path of the remote Server Make sure that omexec.exe is in theAdministrator CLI executable that default path of the remote system. Ais attempting to execute on the reboot after installation of Serverremote system is invalid.Administrator should help ensure thatthe path is correct.Figure 1. Error codes and troubleshooting tips for failed WMI updatesFigure 2. Wbemtest Connect dialog box20DELL <strong>POWER</strong> <strong>SOLUTIONS</strong> Reprinted from Dell Power Solutions, August 2005. Copyright © 2005 Dell Inc. All rights reserved. August 2005
Dave is on vacation.He’s been notified of a problem with his company’s servers.He’s able to manage those servers from anywhere.He’s not cutting his vacation short.He’s right here.MANAGE FROM ANYWHERE.The Dell remote console switch provides thetraditional functionality of KVM switching withthe added benefit of KVM Over IP. Using Dell’sremote console software, simply point-and-clickto take control of your servers.Whether you’re at the rack, in your office oracross the globe your data center will always bewithin your reach.Take control of your servers withthe Dell Remote Console Switch.Digital Availability. Easy aswww.dell.comDell and the Dell logo are trademarks of Dell Inc.
Change language