Frozen exe crashes when importing arcpy

bwayneo

Hello,

 

I have created a Python application that I would like to distribute within our organization. I have created a frozen exe using cx_Freeze, but the exe crashes in GeoprocessingLib.dll. I have isolated the problem to a very simple example. Here is the Python code:

 

test.py:

<SPAN class="keyword token">import</SPAN> arcpy
<SPAN class="keyword token">print</SPAN><SPAN class="punctuation token">(</SPAN><SPAN class="string token">'Hello world!'</SPAN><SPAN class="punctuation token">)</SPAN>
<SPAN class="line-numbers-rows"><SPAN>‍</SPAN><SPAN>‍</SPAN></SPAN>

And here is the command to create the frozen exe:

cxfreeze test.py

 

Here are the error details from Windows Event Viewer:

Faulting application name: test.exe, version: 0.0.0.0, time stamp: 0x0001e4e4

Faulting module name: GeoprocessingLib.dll, version: 10.1.1.3300, time stamp: 0x52e02880

Exception code: 0xc0000005

Fault offset: 0x00154eda

Faulting process id: 0x1804

Faulting application start time: 0x01d250b28e4a7d73

Faulting application path: Z:\lethpy-trees\lethpy\gistools\dist\test.exe

Faulting module path: C:\Users\11157\AppData\Local\Temp\_MEI50322\GeoprocessingLib.dll

Report Id: cdb968dd-bca5-11e6-82d8-3417ebaaaccc

Faulting package full name:

Faulting package-relative application ID:

 

I have tried both cx_Freeze and pyInstaller to create the standalone exe, but the problem is the same. We are using ArcGIS 10.1 SP1.

 

Any help would be appreciated.

RebeccaStrauch__GISP

To help you get started, here is a doc I put together a while back Tip: Python Addin - getting custom tools/toolbox to work - GPToolDialog    I

Also check out E360 Video Search | Esri Videos   (filtered for "python addin") and I found some videos about python addins on you tube last night (happens to be a class from Univ of Alaska - Fairbanks) that I think could be helpful. 

My suggestion, use the wizard to set up the structure...add a few "spare" buttons (i.e. have it stub out the button) if wanting to use a toolbar and buttons.  Easier to do that at the start and delete if not needed (my opinion), since the names will automatically be unique (versus copy-past a new one).

Make sure you get your script working, and working in the toolbox (i.e. add script, have it give the user GUI for parameters, etc).  If it doesn't work there, putting into an addin isn't going to make it better. But you can always tweak, add, or whatever and refresh the .addin (and load back into your Catalog OR Map).

Word of caution...the toolbar/tools will work in Pro (if you update for the new Python software see /blogs/dan_patterson/2016/05/09/the-links  for links to what you will need for Pro) but Addins themselves are not supported.  I'm hoping this will change, but the issue is with the ribbon style menus of Pro and trying to modify/customize those...at least that is what I've been told.  Hopefully they will accommodate this in the future...hope hope)