If “Error 032659” appears while converting an Excel file to a table, the number alone does not identify a dependable, universal cause; it is not an Excel worksheet error with one standard fix. If you are using ArcGIS Pro’s Excel To Table tool, read the complete geoprocessing error and messages, then check the workbook, sheet selection, output location, and file access using the steps below.
What Error 032659 Tells You—and What It Does Not
Excel To Table is an ArcGIS geoprocessing tool that reads a worksheet or named range from an Excel workbook and writes the records to a table, commonly inside a file geodatabase. A code displayed during that process belongs to the software reporting it. It does not, by itself, prove that the workbook is corrupt, that Excel needs reinstalling, or that a particular cell is at fault.
That distinction matters because the visible code may be accompanied by a more useful message, such as an input file that cannot be found, an output that already exists, an unsupported or unreadable sheet, or a permissions problem. The exact wording and the tool that produced it are essential clues. If the error came from another application or an add-in rather than ArcGIS Pro, ArcGIS-specific troubleshooting may not apply.
In ArcGIS Pro, open the failed run in the Geoprocessing pane and inspect its messages, not just the short notification. Record the full error text, the tool name, the input workbook path, the selected sheet, and the output path. Those details make it possible to distinguish a workbook-reading issue from an output or environment issue.
Start with the Full Geoprocessing Message
Run the tool again only if needed, and open the history entry for the failed geoprocessing operation. In the Messages section, look for earlier warnings or errors that appear before the final code. A final error can be a consequence of a more specific problem reported just above it. Also confirm that the operation really was Excel To Table: a similar workflow, such as importing a spreadsheet through another tool or an add-in, can produce a different message.
- Input details: Check that the path points to the intended workbook, that its extension is .xls or .xlsx, and that the workbook is still present.
- Sheet or range: Confirm that the selected worksheet or named range exists and contains the records you expect.
- Output details: Note whether the output is a geodatabase table or another destination, and whether a table with that name already exists.
- Context: Record whether the file is local, on a network share, in a synced folder, or open in another program.
If the full message names a specific issue, address that issue first rather than changing several workbook settings at once. A small controlled test can help: try importing a simple copy of the workbook, with one worksheet and a few plain rows, to a new output table in a local file geodatabase. If that succeeds, the original workbook’s structure or location is more likely to be relevant than the basic tool setup.
Check the Workbook and Worksheet Structure
Excel tables are flexible, but data-import tools work best when a worksheet resembles a simple database table. Put one field name in each cell of the first row, then place one record per row beneath it. Avoid using the same worksheet to combine a title, explanatory notes, several separate tables, and the data you want to import. If the first rows are headings or notes, the tool may interpret the wrong row as field names or include unwanted records.
- Use a single, nonblank heading for each column. Avoid duplicate headings and headings that are only spaces.
- Remove merged cells from the data area; a merged heading can leave some column positions blank or make the layout ambiguous.
- Keep each column’s values consistent. For example, a column intended to contain dates should not mix dates with comments such as “unknown.”
- Remove completely blank rows and columns within the intended data range, and check that the data does not stop and restart below a gap.
- Save the workbook in a supported Excel format and close it before retrying, especially if it is stored somewhere with restrictive file locking.
Mixed data types deserve particular attention. A column might look consistently numeric in Excel while containing a text entry such as “N/A” near the bottom. Import drivers can infer a column’s type from some of its values, so entries of a different type may be read unexpectedly or become empty. Make the column consistent, or create a clearly defined text field in a cleaned copy if preserving mixed values is necessary. Do not assume that Excel’s display formatting changes the underlying value into the type you need.
Verify the Input Path, Sheet, and Output Destination
In ArcGIS Pro, open the tool from the Analysis tab’s Tools button and search for Excel To Table. Select the workbook as the input and choose the intended worksheet or range in the tool’s input options. Then specify a valid output table, preferably in a file geodatabase while diagnosing the problem. The output name is a table name, not a worksheet name, and it must meet the naming rules of its destination.
Make sure the input path is current and accessible to the Windows account running ArcGIS Pro. A workbook moved after a previous run, an unavailable network drive, a cloud-sync placeholder that is not downloaded, or a folder without read access can prevent the tool from opening the input. For a diagnostic run, copy the workbook to a local folder with a short, ordinary path and try again. This is a test to isolate access or path complications, not a requirement that all workbooks be stored locally.
Also check the output destination. A table with the same name may already exist, the geodatabase could be read-only, or the account may lack permission to write there. Choose a new output name and a writable local geodatabase to test. If that works, investigate the original destination and existing table rather than repeatedly changing the Excel file.
Use a Small, Clean Test to Isolate the Cause
When the complete message is unclear, change one factor at a time. Make a copy of the workbook so the source remains untouched. In that copy, create a new worksheet with three or four columns, simple headings, and a few representative records. Include a sample of the troublesome values if you know which column is suspect. Save the copy, close Excel, and import it to a newly named table in a local file geodatabase.
If the small worksheet imports successfully, the basic tool and output process can work. Next, test the original workbook from a local path, then test a cleaned copy of the original sheet. These comparisons can narrow the issue to the file location, workbook structure, or particular values. If even a small clean workbook fails, check the complete ArcGIS Pro messages, the selected output workspace, and whether the input file can be opened normally. Restarting ArcGIS Pro may clear a temporary lock, but it will not repair a malformed worksheet or missing access rights.
For a large sheet, test a small subset rather than immediately changing file formats. Excel worksheets have a maximum of 1,048,576 rows, but a workbook can still be slow or cumbersome to process well below that limit. If the source is far larger than a typical worksheet workflow, consider whether a database or another data format better matches the size and structure of the data.
After Import: Check the Result, Not Just the Run Status
A successful tool run does not guarantee that every value was interpreted exactly as intended. Open the output table in ArcGIS Pro and compare its field names, field types, record count, and representative values with the source worksheet. Pay particular attention to identifiers with leading zeros, long numeric-looking codes, dates, and columns that contained mixed values. A postal code such as 00421 is an identifier, not a quantity; if treated as a number, its leading zeros may not be preserved.
Excel formatting can make values appear uniform without changing their underlying types. Before import, decide whether each column represents text, a number, a date, or another meaningful type. Preserve identifiers as text when their formatting is significant. If a date or number is important, verify a few actual output values rather than relying only on how Excel displayed them. Keep the original workbook as the source of record and document any cleanup performed on a copy.
Common Misconceptions and When to Escalate
Do not treat “032659” as proof that Excel itself is damaged, and do not assume that changing the extension from .xlsx to .xls will fix an import. Renaming a file does not convert its format. Likewise, reinstalling Office or ArcGIS is a disproportionate first step when the error may be caused by a sheet name, file path, existing output, or inconsistent data.
If the error persists with a clean test workbook, a local input path, and a new writable output, save the full geoprocessing messages and note the ArcGIS Pro version. Consult Esri’s current documentation or support channels with those details, including a small sanitized workbook if sharing one is appropriate. Remove confidential or personal data before sending a sample. The complete message and a reproducible minimal example are much more useful for diagnosis than the number alone.
Frequently Asked Questions
Is Error 032659 an Excel error?
No single Excel worksheet problem can be identified from that number alone. If it appears during ArcGIS Pro’s Excel To Table operation, treat it as a message from that workflow and use the full geoprocessing text to identify the specific issue.
Where do I find the full error in ArcGIS Pro?
Open the failed geoprocessing run from the tool’s history or the Geoprocessing pane and inspect its Messages section. Read any warnings and errors that precede the final code, as they may explain the failure more clearly.
Does Excel To Table require the workbook to be open?
No. A sensible troubleshooting test is to save and close the workbook before running the import. Closing it can avoid a file lock or unsaved changes, but it will not resolve unrelated problems such as an invalid output path.
Why are some imported values blank or different?
Mixed types, blank rows, merged cells, or a mismatch between displayed formatting and the underlying cell values can affect how data is read. Check the source column for inconsistent entries and compare several output values with the original.
Should I convert the workbook to CSV?
Only if the data is a single simple table and you do not need workbook features such as multiple sheets or cell formatting. CSV is plain text and does not preserve multiple worksheets, formulas as formulas, or Excel formatting; try a clean workbook and inspect the full message before converting as a workaround.
Related
- Contact List Format in Excel: Columns, Setup, and Tips
- Contact List Excel Sheet: How to Build and Use One
- Contact List Excel Spreadsheet: Create and Manage It
Try it: the Formula Explainer: paste any formula and see each function and reference in plain English.
More in Errors & fixes
- Hyperlink Not Working in PowerPoint? Fix the Common CausesIf a hyperlink is not working in PowerPoint, first test it in Slide Show view: in editing view,…
- Excel CONCAT to Remove a File Name SuffixCONCAT in Excel joins text; it does not remove a file-name suffix by itself. To remove the last…
- Excel IFERROR: Return a Blank Instead of an Error ValueTo show a blank when an Excel formula returns an error, wrap it in IFERROR and use an…
- Mode Not Working in Excel? Causes, Checks and FixesIf MODE is not working in Excel, the most common reason is that the selected range contains no…
- Excel Filter Not Working? Fix the Most Common CausesIf an Excel filter is not working, first check that it covers the complete data range and that…
- Why Won’t Hyperlinks Work in Excel? Causes and FixesHyperlinks in Excel usually fail because the link points to a moved or mistyped destination, Excel is waiting…
Sources: Function behaviour and menu paths: Microsoft Support documentation for Excel. Method & sources
Spotted an error in this guide? Let us know.