topic Re: ArcCatalog forgetting Geoprocessing Options in Geoprocessing Questions

ArcCatalog forgetting Geoprocessing Options

BillRichards — Sun, 29 Dec 2013 20:44:56 GMT

In an attempt to sort out my previously posted issue, I discovered that even though I uncheck the "Enable Background Processing", ArcCatalog seems to occasionally forget that setting as well as the Editor and Debugger settings when I close and re-open ArcCatalog. Why is ArcCatalog behaving so erratically? Is this a time for an uninstall and re-install?

Win7 64bit
ArcGIS Desktop 10.1
Python 32bit installed with the installation...

Bill D. Richards
Geology/Geography
North Idaho College

Re: ArcCatalog forgetting Geoprocessing Options

JakeSkinner — Mon, 30 Dec 2013 09:42:33 GMT

Hi Bill,

Are you running specific tools when the geoprocessing runs in the foreground? Take a look at the section 'System tools may execute in foreground even when background is enabled' in the following link:

http://resources.arcgis.com/en/help/main/10.2/index.html#//00210000003q000000

Re: ArcCatalog forgetting Geoprocessing Options

curtvprice — Mon, 30 Dec 2013 18:05:58 GMT

I discovered that even though I uncheck the "Enable Background Processing", ArcCatalog seems to occasionally forget that setting as well as the Editor and Debugger settings when I close and re-open ArcCatalog.

A reinstall really should be your last resort, as it is major surgery on your desktop. These user settings are stored and managed on a per-user basis in the %APPDATA% folder and your HCKU registry keys, so a reinstall may not even have any effect!

In ArcMap, and ArcCatalog geoprocessing options are written on exit - if you change them in ArcMap, this will change them for ArcCatalog as well (next startup). The last app to save "wins" -- this is another argument for not running multiple apps at once unless you have to.

The geoprocessing environment is handled differently: in ArcMap, these settings are saved in the map document, in ArcCatalog, they are saved when you close ArcCatalog. The ArcCatalog GP environment is used as the default when ArcMap creates a new map document.

I recommend closing all ArcGIS apps, (and making sure there are no "headless" versions running in task manager - the best fix for that is to log out and log in again, or maybe even restart). Then, try [thread=90079]resetting your application profile.[/thread]

I recommend doing this whenever you apply a service pack or update. And sometimes just every few months - just to keep things cleaned up!

Re: ArcCatalog forgetting Geoprocessing Options

BillRichards — Sat, 04 Jan 2014 17:32:05 GMT

A reinstall really should be your last resort, as it is major surgery on your desktop. These user settings are stored and managed on a per-user basis in the %APPDATA% folder and your HCKU registry keys, so a reinstall may not even have any effect!

In ArcMap, and ArcCatalog geoprocessing options are written on exit - if you change them in ArcMap, this will change them for ArcCatalog as well (next startup). The last app to save "wins" -- this is another argument for not running multiple apps at once unless you have to.

The geoprocessing environment is handled differently: in ArcMap, these settings are saved in the map document, in ArcCatalog, they are saved when you close ArcCatalog. The ArcCatalog GP environment is used as the default when ArcMap creates a new map document.

I recommend closing all ArcGIS apps, (and making sure there are no "headless" versions running in task manager - the best fix for that is to log out and log in again, or maybe even restart). Then, try [thread=90079]resetting your application profile.[/thread]

I recommend doing this whenever you apply a service pack or update. And sometimes just every few months - just to keep things cleaned up!

Thanks for the ideas. By changing the environment in ArcMAP as well, the settings seem to be "sticking" . The application profile information might be a next resort if the issue returns --- As well, the "History" logs actually were invaluable in tracking down my python tool execution differences between a "debug" session vs. "run"....