Analysis - Desire Lines failure

[JimmyHearn]

Any one having or had any issues with Desire Lines? I tried to create this on some Customer to store locations, both through the GP and wizard fail. GP can kill AM, but also yields an error "ERROR 080040: Error while executing DesireLines Builder
Failed to execute (DesireLines)."
Wizard gives same pop up error "Error while executing DesireLines Builder"

Any ideas?

[KristenCarroll]

Dear Space_Ur_Face:
Desire Lines require that an assignment has been made between the customers and their store(s).  If you have not created this assignment, the process will err out.  The assignment can either be established while creating the customer layer, or manually afterwards, using the Customer Setup wizard.  Here is a link to learn more:  http://help.arcgis.com/en/arcgisdesktop/10.0/help/index.html#//00mm00000007000000.htm

In general, when troubleshooting issues, it is suggested that you run the same process using the sf_cust and sf_store tutorial data, found in: ?:\Program Files\ArcGIS\Desktop10.0\Business Analyst\Datasets (BA10) or ?:\Program Files\ArcGIS\Business Analyst\Datasets (BA 9.3.1).  If the analysis works when using the sf tutorial data, then the issue is likely with your input files.

Please let me know things go for you.

Best Regards,

Kristen C.
ESRI Support

[JimmyHearn]

Thanks kjbcarroll
The tutorail data works fine, so I began troubleshooting my data, I stripped out from the customer file all Nulls, and the excess fields. So my customer FC looks like this:
Customer ID|Store ID
I also removed all excess fields from my store layer so that I'm left with:
Store ID|Store Name

The store id's are provided for me and the match fine on a regular join. The analysis still errors out during the intialization.
I'm not sure what else could be wrong with my data, I looking at 92,000 records for 9 stores the data set does span the US, but I have a distance cut off set up.

I preformed a Check geometry on the FC and there were no issues.

[DavidBlackner]

Perhaps your version is corrupt, can you remove then reinstall the program? If that doesn't work try an import an older working version of the same code and see if there are any discrepancies.





product" rel="nofollow" target="_blank">http://www.glassdoor.com/Job/product-manager-jobs-SRCH_KO0,1... manager jobs

[BradPender]

I've had a similar problem since upgrading, the only difference from the sound of it is mine is slightly intermittent.  Approximately 10-15% of the time it works without a hitch and the remainder it throws the same, painfully generic, error message.  Interestingly, if it works the first time it will always fail and throw the error if you run it a second time with the exact same data and settings.

Executing the same process on the same data works flawlessly in the 9.3 version.  Like the original poster I've run the check geometry tool, reduced the record count to eliminate any possible memory issues, made sure the projections all match just in case, etc.

The work around for me was to simply export the data from the original large shape file to a new one containing just the points that would fall within the desired cut off.  That works about 99% of the time for me.  The other 1% of the time we've been able to restart ArcMap and repeat the process with success.

[KristenCarroll]

Here are a few more suggestions to help troubleshoot your files. 

1.  Try the process with only one store and its customers.  If it errs out, continue to step 2.  If it works, this may be an issue of system resources. 
2.  Continue working with just one store and its customers until the process works. 
3.  Export out the store/cust layers as shapefiles (or gdb) and add them back to the toc.  This does two things: It makes sure that the column headers are acceptable, i.e.:</=10 characters long, no spaces before, after or between any words, no punctuation save underscores, and do not begin with numbers.  And, if missing, exporting the layers and readding them to the toc will create an OID field.  Retest.  If it errs again, go to step 4.
4.  Make sure you are working with formal customer and store layers.  If the layers have not gone through the store/cust wizards, bring them through.  Retest.  If it errs again, go to step 5.
5.  Let BA create a store assignment as a test.  This is done after both layers are created, via Customer Set up > by closest store assignment > tag the store layer > finish.  Retest.  If it errs again, go to step 6.
6. Convert the store/cust layers to gdb and retry.  If it errs, go to step 7.
7.  If you are choosing to create the distance field using either drive time or drive distance, try again using straight line.  If the driving calcs err but the straight line analysis work, verify that you have Network Analyst installed and registered.
8.  If you are using driving calcs and NA is registered, try breaking up your files.  It may be that you just need to run fewer stores and their customers at one time.
9.  If you are using driving calcs, make sure your temp drives are cleaned out.  (Right click on Start > Explore > right click on Local Disc C > Properties > Disk Cleanup).

Please let me know how things go for you.

Best Regards.

Kristen C.
ESRI Support