00161: Versioned feature layer does not have a versioned view

The layer you are attempting to publish to a spatial database server (SDS) references versioned data, but the data is not accessed through a versioned view. SDS requires versioned data to be accessed through a versioned view.

Solution

Use the Create Versioned View geoprocessing tool to create a versioned view on your table or feature class.

You can also create versioned views from ArcGIS for Desktop.

Learn more about creating versioned views from ArcGIS for Desktop

More information

This problem occurs when older versions of ArcSDE geodatabases are manually created, and the version views are not created by hand. In this case, the version view does not exist, changes to the data cannot be seen through SQL, and SDS cannot access the delta tables. SDS only knows to query the table name that is published. If you publish a versioned class, it will simply query the base table and never see the correct edits that reside in the delta tables.

Versioned views incorporate database views, stored procedures, triggers, and functions to allow you to read or edit versioned data in a geodatabase table or feature class using Structured Query Language (SQL). When you query a versioned view, you can see the data in the base (business) table and the edits that are stored in the delta tables. The triggers used by the versioned views update the delta tables when you edit the versioned view using SQL. Unlike database or spatial views, versioned views are not used to change the table's schema or limit access to it; rather, they are used to facilitate access to a certain version of a table or feature class.

Learn more about versioned views

Learn more about authoring feature services for SDS

12/18/2014