The full logging output looks like this:
Executing (Find Nearest Features Listed in Field): ArcGISPointsFindNearestFeaturesListedInField H:\Sea_Ice\Geodatabase.mdb\SurvLegSegmPoints_NSIDC_Stereo UBIcePolygon # # UBIceDist # Negative # # # # "Updated point features"
Start Time: Thu Oct 08 17:43:05 2009
Running script ArcGISPointsFindNearestFeaturesListedInField...
NameError: global name 'nearFeatures' is not defined
<type 'exceptions.NameError'>: global name 'nearFeatures' is not defined
Failed to execute (Find Nearest Features Listed in Field).
End Time: Thu Oct 08 17:43:08 2009 (Elapsed Time: 3.00 seconds)
This is a bug that only occurs when no fields are specified to be copied from the near features to the point features. I did not catch it during 0.7 testing because my tests always specified at least one field to copy from the near features. This is unfortunate because it will be common for users to not use that option.
As a workaround, you can create temporary field in your point features and instruct the tool to copy a field from the near features to that field.
This will be fixed in MGET 0.8a2.
