Select to view content in your preferred language

New Python Toolbox will Crash Arc Catalog

2494
15
08-29-2013 03:49 AM
JosephArmbruster
Occasional Contributor
Has anyone else experienced this?

- Fire up ArcCatalog or ArcMap
- Create a new Python Toolbox (do not modify anything in the default toolbox)
- Close ArcMap / ArcCatalog
- Start ArcCatalog - it will crash with a send report error box.
- Start ArcMap - it will load just fine

Notes:
- I am using ArcGIS 10.1.1.3143.
- If I copy/paste my custom toolbox code into the .pyt, it works fine from within ArcMap but ArcCatalog continues to crash.
Tags (2)
15 Replies
ManuelRazo
Deactivated User
I might be late coming to this but I just started fighting this battle about 2 weeks ago.  My script was running fine then one day it just wouldn't run a python toolbox anymore and ArcCatalog started crashing constantly, even with regular toolboxes I created.  We went back and forth with ESRI technical help and couldn't get the issue resolved.  We just installed 10.2.2 and everthing seems to working fine now.  The strange thing about all this is that I have 10.1 installed on my personal laptop and can add python toolboxes all day long with no issues.
SuzanneKelly1
Deactivated User
I am unable to fix the problem. ArcCatalog crashes upon opening. I deleted the .dat file in ArcToolbox and changed the Geoprocessing Results to Never Save.

When someone else logs into the computer they are able to open ArcCatalog independently without any issues. When the original user logs in and opens ArcCatalog, it crashes. However, ArcCatalog works fine via ArcMap.

I created a .dmp file but this forum won't allow me to attach it.

Any ideas?

z
0 Kudos
JosephArmbruster
Occasional Contributor
There is no workaround that I could find for this.  The best you can do is perform the regular ESRI folder.

I've deleted the .dat file and changed the Geoprocessing results to Never Save. ArcCatalog still crashes when opened, but works just fine via ArcMap.

Any ideas?

Running 10.1 and did use a new tool from Esri before this started.

Thanks,

sk
0 Kudos
RebeccaStrauch__GISP
MVP Emeritus
Ok, looking through our bug queue, these are issues we've fixed in 10.2 or 10.2.1 (which we're working on right now, its not released yet). However, they're easy enough to work around by deleting a file 

When ArcCatalog opens, the tree opens to one particular folder. Make sure there are no PYTs in that folder. 
If there are any, move or delete them. You can find what directory this is by looking if the registry if you aren't sure: 
HKEY_Current_User\Software\Esri\Desktop10.1\ArcCatalog\Settings\  LastLocation
or 
Try deleting the ArcToolbox.dat found here: 
C:\Users\[USER NAME]\AppData\Roaming\ESRI\Desktop10.1\ArcToolbox\ArcToolbox.dat 
(this will reset your ArcCatalog profile) 




Hi Kevin,
Looks like the bug may have come back in 10.2.2, at least if 10.2.2 was installed without doing a (manual) full uninstall and cleanup from 10.2.1.

However, your fix of deleting the the .dat file (from \Desktop10.2 version of path) work for me. yea!

So a +1 from me.
0 Kudos
KevinHibma
Esri Regular Contributor
Hmmmm, I dont have any more information saying this is a problem thats come back.
However, it's a little telling about the problem that deleting the .DAT file "fixes" the issue.
If you, Becky, or anyone else still have a .DAT file that causes a crash could you please attach to the forum here?  We can debug and try to figure out whats inside that might be causing the failure.
0 Kudos
RebeccaStrauch__GISP
MVP Emeritus
Kevin, I've attached the .dat file I moved/deleted.

BTW - I haven't tested any of my other 10.2.2 installs yet, but I'll let you know if I have the same issue or not.

Update: I tried it on a couple other machines, without any issue.  The difference was the one tha had issues had a Desktop10.1 folder in the \roaming\esri folder besides a Disktop10.2 folder.  I have on othr machine that has thee two folder, but haven't had a change to test yet...will do it now.

Update 2:  the other machine that had the two folders did not have any issue.  So that is not the problem  So no idea whay the server had the issue, or why deleting th .dat file fixed it, but happy it did.
0 Kudos