Ethan Posted August 24, 2016 Report Share Posted August 24, 2016 (edited) Hello-- I have been getting repeated errors when trying to use the Make Time Series Statistics tool, related to the existence or non-existence of the tables 'tempsum' and 'temptstable.' The former usually happens the first time I try to execute the tool, then 'tempsum' appears in ArcCatalog. Once tempsum exists, rerunning the tool does not produce the same error, but is replaced with an error on temptstable. Here's the full error (after the successful execution of Create Feature Class): Executing: MakeQueryTable C:\Users\Ethan\Desktop\GIS_semester_project\Hula_sem_proj.mdb\TimeSeries temptstable USE_KEY_FIELDS OBJECTID # "TimeSeries.VarID=1 AND (TimeSeries.TsTime>=#07-24-2002 00:00:00# AND TimeSeries.TsTime<=#07-24-2002 00:00:00#)" Start Time: Wed Aug 24 18:01:44 2016 Failed to execute. Parameters are not valid. ERROR 000725: Table Name: Dataset temptstable already exists. Failed to execute (MakeQueryTable). Failed at Wed Aug 24 18:01:44 2016 (Elapsed Time: 0.01 seconds) Error HRESULT E_FAIL has been returned from a call to a COM component. Failed to execute (MakeTimeSeriesStatistics). Failed at Wed Aug 24 18:01:44 2016 (Elapsed Time: 0.37 seconds) I cannot see temptstable anywhere in the file tree. The name seems to indicate that it is a temporary table used for querying the TimeSeries table over the period of interest, and the error seems to indicate that it is not temporary. My inputs are the "Well" feature class and "TimeSeries" table. This process was successful one time--since then I cannot successfully run the tool again. I would ultimately like to automate the creation of water level maps over many time periods. Any ideas? Thanks, Ethan Edited August 24, 2016 by Ethan sp. error Quote Link to comment Share on other sites More sharing options...
calberts Posted August 24, 2016 Report Share Posted August 24, 2016 Are you creating the output feature class inside a GeoDatabase? I have seen the same error when trying to create a feature class in a non-geodatabase location. Quote Link to comment Share on other sites More sharing options...
Doug Gallup Posted August 24, 2016 Report Share Posted August 24, 2016 In addition, try turning on "Overwrite the outputs of geoprocessing options" in the Geoprocessing, Geoprocessing Options... menu item, if it's already off. Quote Link to comment Share on other sites More sharing options...
Ethan Posted August 25, 2016 Author Report Share Posted August 25, 2016 calberts, I had tried in various locations, but will stick with a location within the geodatabase. Doug, I have now checked the "Overwrite..." option. Now I am not seeing the error. Big thanks to you both. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.