Append + ERROR 000210: Cannot create output

3300
2
04-28-2011 06:12 PM
SteveVidal
New Contributor II
I have a model (i.e. created in model builder) that appends data to an existing feature class. The input and outputs for that tool are layers in an mxd. So I have a pair mxd + toolbox, and enable geoprocessing when I publish the mxd.

Now when I run this model in ArcMap, it works fine. But here comes the rub... When I publish it, it works initially and then stops working with the ubiqitous (ERROR 000210: Cannot create output)

If I publish the model again, it still doesn't work. However if I create a brand new mxd, then it works initially and then stops working again!!!

So basically, the model works 100% of the time in ArcMap, works fine initially on the server, but once it stops working on the server, no amount of rebooting or re-publishing can fix it! I have to rebuild a brand new mxd and republish it... until it goes bad again!

My own gut-feel is that somehow the server side processing logic "loses" the current workspace, which in theory it is supposed to get from the model. But all the datasources in the model point to the right sde, and also, the initial steps in the model query the output table just fine.

Has anyone seen/heard anything similar? I have found a post with a similar issue where the fix was to set the current workspace in python, but in my case I generate the model from model builder. Is there a trick to find out what the current workspace is when the tool is running?

Needless to say, this is driving me nuts... so any clue would be greatly appreciated. Here is the trace from the model when it fails:

-----------------------------
Job Status: esriJobFailed

Job Messages:


esriJobMessageTypeInformative: Submitted.
esriJobMessageTypeInformative: Executing...
esriJobMessageTypeInformative: Executing (Upload_Alcolmeters): UploadAlcolmeters 100
esriJobMessageTypeInformative: Start Time: Fri Apr 29 11:29:28 2011
esriJobMessageTypeInformative: Executing (Summary Statistics): Statistics ITAS_Alcolmeters d:\arcgisserver\arcgisjobs\itas_datatransfer_gpserver\j07d45e0d4dfc4b9daac329ee6638e868\scratch\Alcolmeters_Statistics "UploadEntryId MAX" #
esriJobMessageTypeInformative: Start Time: Fri Apr 29 11:29:28 2011
esriJobMessageTypeInformative: Succeeded at Fri Apr 29 11:29:28 2011 (Elapsed Time: 0.00 seconds)
esriJobMessageTypeInformative: Executing (Get Field Value): GetFieldValue d:\arcgisserver\arcgisjobs\itas_datatransfer_gpserver\j07d45e0d4dfc4b9daac329ee6638e868\scratch\Alcolmeters_Statistics MAX_UploadEntryId Long 0
esriJobMessageTypeInformative: Start Time: Fri Apr 29 11:29:28 2011
esriJobMessageTypeInformative: Succeeded at Fri Apr 29 11:29:28 2011 (Elapsed Time: 0.00 seconds)
esriJobMessageTypeInformative: Executing (Table Select): TableSelect vwAlcolmetersUpload d:\arcgisserver\arcgisjobs\itas_datatransfer_gpserver\j07d45e0d4dfc4b9daac329ee6638e868\scratch\Alcolmeters_TableSelect "UploadEntryId > 1 and UploadEntryId <= 1 + 100"
esriJobMessageTypeInformative: Start Time: Fri Apr 29 11:29:28 2011
esriJobMessageTypeInformative: Succeeded at Fri Apr 29 11:29:28 2011 (Elapsed Time: 0.00 seconds)
esriJobMessageTypeInformative: Executing (Make XY Event Layer): MakeXYEventLayer d:\arcgisserver\arcgisjobs\itas_datatransfer_gpserver\j07d45e0d4dfc4b9daac329ee6638e868\scratch\Alcolmeters_TableSelect Longitude Latitude Alcolmeterss_XYLayer "GEOGCS['GCS_GDA_1994',DATUM['D_GDA_1994',SPHEROID['GRS_1980',6378137.0,298.257222101]],PRIMEM['Greenwich',0.0],UNIT['Degree',0.0174532925199433]];-400 -400 1000000000;-100000 10000;-100000 10000;8.98315284119521E-09;0.001;0.001;IsHighPrecision" #
esriJobMessageTypeInformative: Start Time: Fri Apr 29 11:29:28 2011
esriJobMessageTypeInformative: Succeeded at Fri Apr 29 11:29:28 2011 (Elapsed Time: 0.00 seconds)
esriJobMessageTypeInformative: Executing (Get Count): GetCount Alcolmeterss_XYLayer
esriJobMessageTypeInformative: Start Time: Fri Apr 29 11:29:28 2011
esriJobMessageTypeInformative: Row Count = 83
esriJobMessageTypeInformative: Succeeded at Fri Apr 29 11:29:28 2011 (Elapsed Time: 0.00 seconds)
esriJobMessageTypeInformative: Executing (Make Feature Layer): MakeFeatureLayer Alcolmeterss_XYLayer Alcolmeters_FeatureLayer # # "UploadEntryId UploadEntryId VISIBLE NONE;OrgUnitId OrgUnitId VISIBLE NONE;FileName FileName VISIBLE NONE;SerialNumber SerialNumber VISIBLE NONE;Gender Gender VISIBLE NONE;ReadingDate ReadingDate VISIBLE NONE;ReadingTime ReadingTime VISIBLE NONE;Result Result VISIBLE NONE;ResultLevel ResultLevel VISIBLE NONE;WeekDay WeekDay VISIBLE NONE;Month Month VISIBLE NONE;Year Year VISIBLE NONE;Latitude Latitude VISIBLE NONE;Longitude Longitude VISIBLE NONE;ESRI_OID ESRI_OID VISIBLE NONE"
esriJobMessageTypeInformative: Start Time: Fri Apr 29 11:29:28 2011
esriJobMessageTypeInformative: Succeeded at Fri Apr 29 11:29:28 2011 (Elapsed Time: 0.00 seconds)
esriJobMessageTypeInformative: Executing (Append): Append Alcolmeters_FeatureLayer ITAS_Alcolmeters TEST # #
esriJobMessageTypeInformative: Start Time: Fri Apr 29 11:29:28 2011
esriJobMessageTypeError: ERROR 000210: Cannot create output Database Connections\ITAS_SYS_GIS.sde\ITAS_SYS_GIS.DBO.ITAS_Alcolmeters
esriJobMessageTypeError: Failed to execute (Append).
esriJobMessageTypeInformative: Failed at Fri Apr 29 11:29:40 2011 (Elapsed Time: 12.00 seconds)
esriJobMessageTypeError: Failed to execute (Upload_Alcolmeters).
esriJobMessageTypeInformative: Failed at Fri Apr 29 11:29:40 2011 (Elapsed Time: 12.00 seconds)
esriJobMessageTypeError: Failed.
-----------------------------
0 Kudos
2 Replies
GrantCrosswell
New Contributor III
Did you get to resolve this issue?
I have the same with a staff member running a buffer & append?

Thank you for any assistance.
0 Kudos
ParikshitRanade1
New Contributor
0 Kudos