I recently used untools 3.5.1 to create a utility network at version UN5 using the asset package to geodatabase. I copied this UN5 dataset into my test sql server sde environment. The main reason I wanted UN5 is to use the UN within my 10.9.1 enterprise. But now when trying to publish as a feature service the analyze complains that the dataset version is later than is supported by my server. I just installed ArcGIS Server UN patch 8 and still have the problem. My thinking is that it’s not the UN version, but that the dataset was created with Pro 3.5 with perhaps unsupported data types. Does this sound right? I know 2.9 is the supported Pro that works with 10.9.1 but I doubt it would support untools 3.5.1. Is there any work around for what I’m trying to do? The conundrum is I need a recent version of Pro to go through the workflow of migrating and creating a UN, but I need to use the created UN in an older version of enterprise.
Thanks,
Solved! Go to Solution.
Hi Robert and Mike,
The exact error was: 00396: The dataset version is later than is supported by your server.
The attribute rules was the issue. It was the validation rule invalid geometry. After removing that from all the fc's I was able to publish. I guess follow up question is does removing this have any implications other than not finding invalid geometry?
Thank you both, I really appreciate it!
Can you post the exact analyzer message and the link to the error message (if there is one)?
There are other things that raise the min client version of your classes, such as attribute rules. Could be something like those causing the issue.
Hi Robert and Mike,
The exact error was: 00396: The dataset version is later than is supported by your server.
The attribute rules was the issue. It was the validation rule invalid geometry. After removing that from all the fc's I was able to publish. I guess follow up question is does removing this have any implications other than not finding invalid geometry?
Thank you both, I really appreciate it!
Those are batch rules, they are up to you to run. They are really for data migration, once in the UN, you should not be able to introduce an invalid geometry.