topic Re: Clean up step: Version is currently in use in ArcGIS Workflow Manager Questions

Clean up step: Version is currently in use

AllWeatherHeather — Fri, 19 Sep 2014 15:41:33 GMT

I have a clean up step in one of my workflows and even though ArcMap is closed on the computer and no other users are connected to my data version I am getting the following error. When I look in ArcMap at the Version Manager I do not see any locks. Any idea what I am missing?

Re: Clean up step: Version is currently in use

TopeBello — Mon, 22 Sep 2014 21:36:50 GMT

Hi Heather,

What version of ArcGIS Workflow Manager are you on? This issue was resolved in Workflow Manager at a service pack of version 10.0.

Thanks,

Tope

Re: Clean up step: Version is currently in use

AllWeatherHeather — Tue, 23 Sep 2014 19:56:03 GMT

I am using Workflow Manager 10.2.2 Build 3239

Re: Clean up step: Version is currently in use

TopeBello — Tue, 23 Sep 2014 20:41:35 GMT

Heather,

I am unable to reproduce this using a workflow that has the following steps - Create Version, Edit Data and Clean Up Version.

In the past we have seen issues if you have complex layers in the map causing the lock to the version maintained beyond need. Can you log a tech support incident on this? I think we will need to troubleshoot this to figure out the source of the problem.

Thanks,

Tope

Re: Clean up step: Version is currently in use

AllWeatherHeather — Wed, 24 Sep 2014 17:24:04 GMT

Tope,

I am now seeing this issue on many of my workflows... I will have to create a simple one to do some more testing.

Thanks,
Heather

Re: Clean up step: Version is currently in use

TopeBello — Wed, 24 Sep 2014 17:29:07 GMT

Heather,

Let me know how your tests go. I can also try out a few tests here too. What types of layers do you have in your map? When you get these locks, can you take a look at the task manager to confirm that there are no applications (ArcMap/ArcCatalog) keeping the lock active.

Thanks,

Tope

Re: Clean up step: Version is currently in use

AllWeatherHeather — Wed, 24 Sep 2014 18:24:15 GMT

Tope,

I did some more testing with my workflows and the issue goes away if I close down Workflow Manager and reopen it. Also, if I run each step manually (R-click, Run Step) there are no issues. Do you know if there is a way to pause a workflow? We have custom reconcile and post steps that run before the clean up and I wonder if they haven't completely finished before it tries to delete the job version.

Thanks,

Heather

Re: Clean up step: Version is currently in use

TopeBello — Thu, 25 Sep 2014 00:25:04 GMT

Heather,

You are not able to pause the execution of a step in current version of Workflow Manager. Closing the application doesn't seem like an acceptable work around, unless the steps happen at different times in your workflow. You can try running the steps one at a time (disable auto execute) and then inspect the database locks after each step that you execute in the workflow. This could help narrow down the culprit.

Is your reconcile and post step using the GP tools or did you create a custom step for this? If it is, you can get the developer that created it to debug to ensure there are no locks after completion.

Thanks,

Tope

Re: Clean up step: Version is currently in use

AllWeatherHeather — Fri, 17 Oct 2014 13:44:14 GMT

Tope,

I did some more testing and there is a lock on the version that is maintained at the end of our "Custom Reconcile" step and is subsequently unlocked after the "Custom Post Step". Clean Up is in the workflow after this and although the version manager tells me that the version is not locked I get an error that the version cannot be deleted because it is in use. As before, if I close Workflow Manager and relaunch it there is no issue.

Next I will try making a simpler workflow and see if I get the same issue.

Thanks,

Heather

Re: Clean up step: Version is currently in use

AllWeatherHeather — Mon, 20 Oct 2014 15:16:09 GMT

Tope,

Can you tell me what the difference is between an error stating "The version is currently in use" and "The operation is not allowed while editing"? I did some testing over the weekend with creating locks on versions and came across these two different error messages.

Thanks,
Heather

Re: Clean up step: Version is currently in use

TopeBello — Mon, 20 Oct 2014 16:19:55 GMT

Hi Heather,

The "version is currently in use" is a lock at the DBM/SDE level where something is created a lock on the database. The "operation is not allowed while editing" means that you have to explicitly stop an active session. If you have started an editing session, you will need to stop it where you are getting this error.

Thanks,

Tope

Re: Clean up step: Version is currently in use

AllWeatherHeather — Tue, 28 Oct 2014 02:27:23 GMT

Tope,

Due to project deadlines I am going to have to drop the clean up step out of my workflows. Is there a way I can script and schedule the deletion of job Mxds and versions? I was hoping we could run a weekly clean up to remove these components related to closed jobs.

Thanks,

Heather

Re: Clean up step: Version is currently in use

TopeBello — Mon, 03 Nov 2014 05:40:52 GMT

Hi Heather,

One of our colleagues developed some tools that can help with managing large volumes of jobs.There are tools for deleting jobs, creating jobs, and other job management capabilities. I believe you can run these scripts as scheduled tasks using windows schedule.

Take a look at the tools here and see if it helps - http://www.arcgis.com/home/item.html?id=387ce7914cde4744b549b934959a0b5f

Thanks,

Tope

Re: Clean up step: Version is currently in use

SerjStol — Mon, 14 Aug 2023 12:50:19 GMT

These are no longer accessible? We have issue with Deleting Versions. We can't use CleanUp step /v because a different user to who created the job will be deleting/finishing the job. The settings allow you to enter credentials of SDE user to delete the version, however we do not want these extra clicks and giving SDE credentials to all editor users.

Therefore, we created a custom GP tool to Delete Versions and configured it using ExecuteGP step, however, sometimes this step executes twice by the WFM, with 5s gap, and the return code is -1, even though the version is infact deleted by the second run, but the user is the stuck in a loop of trying to Delete the Version but is not aware that it was deleted already. Any ideas why is this happening? I appreciate this product is no longer supported but there is limited information online so I am asking... Thanks