topic Re: Trade Area - Unhandled Exception!!! in ArcGIS Solutions Questions

Trade Area - Unhandled Exception!!!

SantoshKV — Wed, 13 Oct 2010 11:41:35 GMT

Hi,

I'm working on Business Analyst V 9.3 to get drive time polygon (trade areas) for around 200 stores at 4 different time intervals.. I get unhandled exception saying cant execute the component... I'm struggling to get the output since two days and have run nearly 15 iterations in different way. I've successfully completed getting the dr time poly for 500+ stores. Any solutions/suggestions? Thanks in advance.

Error message stack:
Can't execute component
Failed to execute Drivetime / Drive-distance
Executing of "Drive Time" GP function failed
Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
--------------------------------------------------------------------------------
Last call:
at esriBA9.Common.BaseGPFunction.ExecuteInternally(IArray paramvalues, ITrackCancel trackcancel, IGPEnvironmentManager envMgr, IGPMessages messages)

Re: Trade Area - Unhandled Exception!!!

Jason_RobinsonRobinson — Wed, 13 Oct 2010 22:11:26 GMT

I would suggest making sure that for your version of Business Analyst/ArcGIS Desktop that you make sure you have the latest patches.

Business Analyst
http://resources.arcgis.com/content/patches-and-service-packs?fa=listPatches&PID=78

ArcGIS Desktop
http://resources.arcgis.com/content/patches-and-service-packs?fa=listPatches&PID=15

Can you let me know what the drive time ring parameters that you are using?

Re: Trade Area - Unhandled Exception!!!

SusanZwillinger — Wed, 20 Oct 2010 13:25:39 GMT

I've had some issues with Drive Time that were related to the Tele Atlas data. It is possible that the data is not allowing Network Analyst to create the Service Area if a store point is located near a street segment that has a routing restriction. In these cases, problems with one of your drive time calculations would cause the whole process to fail. Unfortunately, in this case, there is probably no way to know which store is causing the problem, so your best bet is to batch the process with smaller groups of stores so that you can determine which area has the problem. After the batch process completes you can merge all of the trade areas into a single map layer.

It could also be a memory issue if you have very large drive time minutes for your settings. Again, doing a smaller subset of the stores in a batch process would be the way to go.

Regards,
-Susan-