Trouble Getting "Reach" to Run on 10.2

[Vig K]

Hi Friends: I am running ArcMap 10.2 and am having trouble getting the centrality/reach tool to finish running. Attached below is the error report. It has created an adjaceny matrix .dbf, and a Featureclass polygon shapefile, but I am not getting a column "R" with the reach values. I feel I am close to a result but clearly missing something.

Any help or advice would be greatly appreciated. 

Thank You

Vig    

Executing: Centrality SampleLots false HWY2012_ND true false false false false PIN # Length # "On the network" 1 # "Y:\Vig\South Elgin\GIS\ND-Test3" ReachTest2 #

Start Time: Tue Nov 19 17:55:32 2013

Running script Centrality...

[started] Copying input buildings

[finished]

[1 started] Computing adjacency list

... [started] Converting polygons to network locations

... [finished]

Adjacency list already computed on previous run

[1 finished]

[2 started] Building graph from adjacency list

[2 finished]

[3 started] Retrieving necessary node attributes

427 out of 814 input points not recorded in graph

[3 finished]

[4 started] Running centrality computation

[4 finished]

[5 started] Writing out results

[5 failed]

Not successful

Completed script Centrality...

Succeeded at Tue Nov 19 17:55:57 2013 (Elapsed Time: 24.81 seconds)

[Andres]

 It looks like the issue is in writing to the table. 10.2 should work fine, no service packs needed. Could you try to choose an entirely new output folder (and just in case one that doesn't have any empty spaces in the name) and try again? The writing to table errors are often related to either overwriting issues or path names. Let me know if it works or not and we can try to troubleshoot from there on.

Andres

[Andres]

Vig,

Your output also mentions that 427 out of 814 input points were not recorded in the graph, which signals that a lot of points are not getting snapped to the network. It is usually ok if only a few points get left out, but here it seems quite a large percentage that might cause issues.

Andres

On Wednesday, November 20, 2013 8:09:19 AM UTC+8, Vig K wrote:

[Patrick McGrath]

Vig,

In the past I've had trouble writing UNA outputs to network drives at my organization. You might try using an output folder on your C: drive.

-Patrick