Trying to publish gp service via modelbuilder gp results... locked outputs

[RoyceSimpson]

I've got a model, that I can successfully run in Arcmap over and over (because I've checked the geoprocessing option to "Overwrite the outputs of geoprocessing operations".  However when I publish this to our ArcGIS Server (AGS) as a gp service, I can run it once then the outputs get locked and I can't successfully run it again. If I stop and restart the gp service in AGS I can run the gp task one time, then the outputs get locked again and I'm dead in the water.

Is there somehow a way to replicate the ArcMap "Overwrite the outputs of geoprocessing operations" setting in AGS to allow these outputs to get overwritten?

Thanks,

-Royce

[DavidColey]

Royce, are you outputting to an inMemory feature class?

[RoyceSimpson]

The output is a dbf file called "clipResults.dbf".  There are also two associated lock files for each of our AGS servers in that cluster:  "clipResults.dbf.ARETE.6352.9956.sr.lock" and "clipResults.dbf.COL.15756.21172.sr.lock".

If I try to run the gp service task and those locks are there, I get the following AGS error.  The only way to not get the error is to stop and restart the service, which clearly isn't anything but a very short term solution:

Error executing tool.: ERROR 000258: Output \\lcgfs02\gisserverdata\gp\output\landcover\clipResults.dbf already exists Failed to execute (Table to Table). Failed to execute (Model).

[DavidColey · Accepted solution]

Right, so that dbf has to be output as an inMemory table, it can't remain as physical dbf somewhere.  I have a model that basically does a select by attribute and then a re-select by locataion. It's set up like this:

the output point locations parameter is specified in the tools as

in_memory\OutputPoints

When I publish that result to server from the Results window it works every time becasue the output feature is an inMemory feature.  I'm sure it will work the same with a dbf.

[RoyceSimpson]

I'm trying that method as we speak!  I can't output to "dbf" though and still have it as "in_memory"... so I took the "dbf" extension off and ran the model and it worked.  I'm republishing now.  Crossing fingers.

[RoyceSimpson]

Holy Shzam!  That worked.  "in_memory" is what fixed it!  woot!  Thanks David.

[DavidColey]

Thanks man, they're tricky aren't they?  Are you going to Dev Summit next week?

[RoyceSimpson]

No... UC for me. 

[DavidColey]

great, have fun.  I'm heading to Dev... still haven't forgotten about that Collector setup either, just haven't got to it yet...

[RoyceSimpson]

Ah yes, Collector.  I've got esri looking into it right now.  So far, it's looking like an Oracle bug.  Will keep the thread updated as needed.