Troubleshooting

The deployment may fail with several error messages and due to a number of reasons listed in the table below:

Error message

Possible causes

The network path was not found (error code 0x35)

 

Client is not reachable on the network, firewall blocks communication

Inbound ports 135, 137, 138, 139 and 445 are not open in firewall on the client or Windows Firewall: Allow inbound file and printer sharing exception is not used

Client's host name could not be resolved, use valid FQDN computer names

Access is denied (error code 0x5)

The user name or password is incorrect (error code 0x52e)

 

When deploying from a server joined to a domain to a client joined to the domain, use credentials of a user that is member of Domain Admin group in format Domain\DomainAdmin

When deploying from a server to a client that is not in the same domain, disable remote UAC filtering on target computer.

When deploying from a server to a client that is not in the same domain, use credentials of a local user that is member of Administrators group in format Admin. Target computer name will be automatically prepended to the login.

No password set for administrator account

Insufficient access rights

ADMIN$ administrative share is not available

IPC$ administrative share is not available

Use simple file sharing is enabled

The installation package is not supported by this processor type (error code 1633)

The installation package is not supported on this platform. Create and download the installation package with the correct platform (64-bit or 32-bit operating system) in ECA Web Console.

The semaphore timeout period has expired

Client cannot access the network share with deployment package because SMB 1.0 is disabled on the share.

Follow the appropriate troubleshooting steps according to the possible cause:

Possible cause

Troubleshooting steps

Client is not reachable on the network

Ping the client from the ECA Server; if you get a response, try to log on to the client machine remotely (for example, via remote desktop).

Firewall blocks communication

Check the firewall settings on both the server and the client, as well as any other firewall that exists between these two machines (if applicable).

After successful deployment, ports 2222 and 2223 are not open in firewall. Make sure that these ports are open on all firewalls between the two machines (client and server).

Client's host name could not be resolved

Possible solutions to DNS issues can include but are not limited to:

Using the nslookup command of the IP address and hostname of the server and/or the clients having Agent deployment issues. The results should match the information from the machine. For instance, an nslookup of a hostname should resolve to the IP address that an ipconfig command shows on the host in question. The nslookup command will need to be run on the clients and the server.

Manually examining DNS records for duplicates.

No password set for administrator account

Set a proper password for the administrator account (do not use a blank password).

Insufficient access rights

Try using the Domain Administrator's credentials when creating an Agent deployment task. If the client machine is in a Workgroup, use the local Administrator account on that particular machine.

For Windows 7 and later, the Administrator user account must be activated in order to run the Agent deployment task. You can create a local user that is a member of Administrators group or to enable built-in local Administrator account.

To activate the Administrator user account:

1.Open an administrative command prompt

2.Enter the following command: net user administrator /active:yes

ADMIN$ administrative share is not available

The client machine must have the shared resource ADMIN$ activated. Make sure it is present among the other shares (Start > Control Panel > Administrative Tools > Computer Management > Shared Folders > Shares).

IPC$ administrative share is not available

Verify that the server can access IPC$ by issuing the following from a command prompt on the server:

net use \\clientname\IPC$ where clientname is the name of the target computer.

Use simple file sharing is enabled

If you are getting the Access denied error message and your environment is mixed (contains both a Domain and Workgroup), disable Use simple file sharing or Use Sharing Wizard on all machines that are having problems with Agent deployment. For example, in Windows 7 do the following:

Click Start, type folder into the Search box, and then click Folder Options. Click the View tab and in the Advanced settings box, scroll down the list and deselect the check box next to Use Sharing Wizard.

SMB 1.0 is disabled - deployment to Windows XP/Server 2003

When deploying to older operating systems (Windows XP/Server 2003), turn on SMB 1.0/CIFS File Sharing Support feature on the computer with the deployment package.