Known Problems 4/9/2008
The following are intermittent problems that some users may run into. We are working on finding and fixing these problems in Snap-Plus.
Problem: Sometimes (we've noticed this after updating the program) a year in a rotation will have a much higher than expected soil loss and PI value.
Workaround: To fix the wrong value, you just need to clear the PI and Rotation Summary results for the field (for instance by re-selecting the yield goal) and then clicking the "Calculate all years" button.
Problem: Corn Silage and Soybean to small grain cover crops in older data no longer have "Field Cultivation" for tillage.
Workaround: You will need to change the tillage to one of the two "Spring Cultivation" tillages.
Problem: Some fields created in Snap-Plus version 1.119 and earlier might have the slope length in meters rather than in feet due to a problem in earlier soil lookup data.
Workaround: If you see slope lengths that seem shorter than they should be, there is now a tool in Snap-Plus to reset all slopes and slope lengths back the correct Snap-Plus default values. Choose "Reset Farm Slopes and Lengths" from the Snap-Plus Tools menu.
Problem: During the program upgrade, I get errors about missing soil tests or BrayP1 adjustment where the farm and field reported don't actually match (ie the field is actually part of a different farm).
Workaround: This is a problem with the upgrade process and only affects the PI and soil loss results. You just need to re-run the models for each farm. Data should not be affected.
Problem: One or more messages saying "Follow 590 N-use guidelines for high-leaching potential soil…" remain
in the "Field Notes" column after upgrading.
Workaround: The upgrade process should remove the first line of N restriction warnings in the field notes for each field,
but some fields may have many lines of N restriction warnings due to changing the soil type on the field data page.
These extra lines of warnings must be deleted by hand.
Problem: Sometimes I get an error saying "Can't close R2 profile for SnapPlus", or "Rusle2 exception" or
"Access violation in module 'ntdll.dll'".
Work around: This usually means that Snap-Plus' copy of Rusle2 has stopped responding. Right
now the workaround is to close the program and restart.
Problem: I get an "I/O error 103" message when I try to create a report.
Work around: The report should still be created and saved, so the message is most likely benign.
This error also shows up when using soil test import, but you should be able to get around it by importing again
if it doesn't work right the first time. You might also get an "Index out of bounds" error when you quit
Snap-Plus as a result of this problem. This appears to happen only on Windows XP when your account does not
have administrative privileges. The work around is to make sure you are logged in as an administrative user.
Problem: Sometimes my selected crops and counties disappear from the farm screen.
Work around: This bug should not affect program operation on fields you already have set up.
But you do need to fix it before you create new fields. To do so, go to the farm screen, and reselect your counties and crops.
Problem: When I close the program, I get a message about sending a bug
report to Microsoft and/or a series of error dialogs.
Work around: You just have to follow through and close the dialogs. You do not need to send any reports to Microsoft.






