topic Re: Table is not multiversioned error in ArcGIS Pro Questions

Table is not multiversioned error

DrewGuardi — Tue, 13 Dec 2022 16:52:41 GMT

I am trying to edit the vertices of line segments in a layer. After I modify the vertices and try to save the edit I get the following error: "Modify vertices failed. The table is not multiversioned." I've attached a screen shot of the error message. How do I go about fixing this?

Re: Table is not multiversioned error

Robert_LeClair — Wed, 14 Dec 2022 21:58:15 GMT

The only thing I can see in the internals that would cause this is an nonversioned feature class inside of a versioned feature dataset. Solution is reregister the feature dataset as versioned - this would registered the nonversioned feature class as versioned. Or remove the feature class from the versioned feature dataset and do the edits outside of the feature dataset.

Re: Table is not multiversioned error

DrewGuardi — Thu, 15 Dec 2022 18:36:29 GMT

I checked the properties of the geodatabase and it says that the database version is not supported. I assume this may be the cause of the problem. However, I'm not sure of the best way to fix it.

Re: Table is not multiversioned error

Robert_LeClair — Thu, 15 Dec 2022 18:43:56 GMT

Hmmm...that could be the case then. Here is a link to supported databases and versions.

Re: Table is not multiversioned error

TychoGranville — Thu, 22 Dec 2022 17:54:16 GMT

This just happened to me. Last week I was editing a (versioned) polygon layer, this week I get that error and can't edit *anything* in my production (SQL Sever) DB. Tried different machines, different Projects, different FCs. Haven't tried re-versioning, I'll have to do that off-hours.

The technical help doc is classic -

https://pro.arcgis.com/en/pro-app/latest/tool-reference/tool-errors-and-warnings/160001-170000/tool-errors-and-warnings-160326-160350-160334.htm

Anyone have ideas? I'll contact tech support but based on the document above I'm not real hopeful.

Thanks,

Tycho

Re: Table is not multiversioned error

Robert_LeClair — Thu, 22 Dec 2022 18:25:27 GMT

Tycho - another thing to explore is for your *.sde connection in the Catalog Pane, right-click on the file as the SDE user and select Geodatabase Connection Properties and check the Versioning Type. Is it set for Traditional or Branch? If Branch, choose Traditional and retry your workflow.

Re: Table is not multiversioned error

TychoGranville — Thu, 22 Dec 2022 19:04:20 GMT

It's still set to Traditional. Our testing Enterprise GeoDB - set up the same way - still lets me edit FCs.

Re: Table is not multiversioned error

Robert_LeClair — Thu, 22 Dec 2022 22:16:12 GMT

In the off-hours, reregister the Feature Dataset as versioned on your Production eGDB and see if the error persists.

Re: Table is not multiversioned error

TychoGranville — Sun, 25 Dec 2022 19:43:19 GMT

That did the trick.

Thanks,

Tycho

Re: Table is not multiversioned error

JasminePrater — Mon, 13 Mar 2023 14:13:31 GMT

This solution worked for us. Thank you!

Re: Table is not multiversioned error

Craig_Schellenbach — Wed, 22 Mar 2023 18:28:52 GMT

FYI: I also got this error when we tried to use the Append tool into a versioned SDE database when the shapefile we were importing was in a different coordinate system.

@DaraBurlo 🙂

Re: Table is not multiversioned error

VickyS — Thu, 05 Oct 2023 08:12:21 GMT

This error occurs when we add a new feature class to a feature dataset that is already versioned. The fix is to go to the feature dataset 'manage' options and tick 'versioned'.

The box has a white fill when the feature dataset has versioning enabled but contains non versioned feature classes. If versioning is enabled on all feature classes it displays a tick.

A warning to reenable versioning when created a new dataset would be useful.

Re: Table is not multiversioned error

KeithAddison1 — Mon, 15 Apr 2024 15:00:00 GMT

I seemingly get this error at random since upgrading to 3.2. I'll try to edit a field and it will fail with this message. I'll close, reopen and it will not be a problem for a bit then come up again for some reason. Sometimes field calculator can do the edit where the manual attempt fails. No one else has and edit session going on this data or is even looking at it. Nothing about our data has ever been versioned or registered as such, so why would this come up?

Re: Table is not multiversioned error

AntonioBurden — Wed, 11 Mar 2026 21:26:08 GMT

@Robert_LeClair would moving the dataset to another GDB and dataset fix this issue? What's actually happening to the issue when this occurs?

Re: Table is not multiversioned error

Robert_LeClair — Fri, 13 Mar 2026 21:14:20 GMT

@AntonioBurden - it's not my dataset/issue. But you could create a new FDS certainly, copy/move the feature class to the new FDS and retry the workflow. What is the result?