---
title: "Error Code: 2"
slug: "error-code-2"
updated: 2026-04-28T11:25:02Z
published: 2026-04-28T11:25:02Z
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.workspot.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Error Code: 2

# Domain Join Fails During Provisioning: “The system cannot find the file specified.”

## Summary

Newly provisioned Windows VMs failed at the **domain join** step with **Error Code: 2 – “The system cannot find the file specified.”** The issue was traced to an **incorrectly formatted OU (Organizational Unit) path** configured in **WorkspotConfigEditor**. Correcting the OU path to a valid **LDAP/X.500 distinguished name (DN)** format resolved the problem, and provisioning succeeded.

---

## Symptoms / Error

- Provisioning workflow fails at domain join.
- Error returned: **Error Code: 2 – “The system cannot find the file specified.”**

---

## Cause

The OU path string configured in **WorkspotConfigEditor** was **incorrectly formatted,** **or the wrong path was entered**, so the domain join process could not create/move the computer object into the specified OU. Workspot Agent domain join settings require the OU to be provided as a **full LDAP distinguished name**, such as:

`OU=MyOu,OU=MyParentOu,DC=MyDomain,DC=MyCompany,DC=com`

---

## Resolution

Update the OU path in **WorkspotConfigEditor** to the correct **LDAP/X.500 distinguished name** format.

Reference Link - [https://docs.workspot.com/docs/clone-workspot-agent-issues-troubleshooting-1#agent-installation-and-configuration](https://docs.workspot.com/docs/clone-workspot-agent-issues-troubleshooting-1#agent-installation-and-configuration)

---

## Validation / How to Confirm

### 1) Check the domain join log on the VM

The primary log for domain join troubleshooting is: C:\Windows\Debug\netsetup.log

Microsoft specifically recommends **Netsetup.log** as a key resource for investigating domain join failures.

What to look for:

- Errors referencing invalid LDAP paths / OU lookup failures
- Failures in locating/using the target OU DN during join

### 2) Confirm OU DN from Active Directory

From **Active Directory Users and Computers (ADUC)**:

- Locate the OU
- Get its **distinguishedName** (Attribute Editor)
- Use that DN exactly in WorkspotConfigEditor