Table of Contents Error Messages...1

Transcription

1 Table of Contents Error Messages...1 Error: SMS Backup Too Large...1 Compatibility Mode Error...2 Error message when opening SMS on Windows 10: load library failed with error 1114, a dynmaic link.dll...3 Error Opening Data Location...4 Unexpected Read Error when importing AgData files into SMS...5 PDF Printer Not Activated. Error Code SMS - Known Issues...7

2 Error Messages Error: SMS Backup Too Large Device/Drive Formatting Problem/Issue: File or backup that is 4GB or larger cannot be saved or placed on USB Drive or External Hard Drive. Error says that the file is too large when there is remaining room on the drive. See Example Below: Cause: USB is formatted to a FAT format and needs to be formatted to a NTFS. FAT is an older formatting method that is not designed for use with today's larger file sizes. NTFS was designed to allow for larger files to be stored and saved on to drives. Fix: Simply change the formatting of the drive from FAT to NTFS in order to ensure proper formatting. 1. Double-click on Computer or C: Drive. 2. Right-click on the flash drive or memory card, then select Format. 3. In the File System list, Change FAT32 to NTFS. 4. ClickStart. 5. Click OK to start formatting. Note: Formatting will wipe all data off of existing card. If you need to save any data you will want to save those items in another location before saving. Content last reviewed on: 4/23/16 Reviewed by: TJA Error Messages 1

3 Compatibility Mode Error Description: When the user opens SMS and it gives the following error, "SMS- Windows Compatibility Mode Error." Below are things to try to get rid of the message if the user has already unchecked the box in the compatibility tab that says, "Run this program in compatibility mode for." Steps to Repair: Option 1 1. Right-click on the SMS icon on the desktop and go to properties. 2. Click on the compatibility tab and check the box that says run this program in compatibility mode for. Click ok. 3. Restart the computer 4. Right-click on the SMS Advanced icon again after the computer is powered back up. Go to properties. 5. In the compatibility tab uncheck run this program in compatibility mode for and then click ok. 6. Start SMS Option 2 1. Right-click on the SMS icon on the desktop and go to properties 2. In the Compatibility tab if the Run this program in compatibility mode for is already checked and greyed out then click on Change settings for all users. 3. Uncheck run this program in compatibility mode for and click ok 4. Click ok again and start SMS Option 3 1. Right-click on the SMS icon on the desktop and go to properties 2. Run the compatibility mode troubleshooter that is in the compatibility tab 3. Run it using the recommended settings 4. After it is complete then start SMS Content last reviewed on: 6/17/16 Reviewed by: SSW Compatibility Mode Error 2

4 Error message when opening SMS on Windows 10: load library failed with error 1114, a dynmaic link.dll. Error message when opening SMS on Windows 10: load library failed with error 1114, a dynmaic link.dll. 1. Right-click on the Desktop and click on Switchable Graphics Card Settings (should be the second one in the list). You should see a screen like the one below after clicking on it: 2. Click on Add Application and search for the ALMapping.exe file. This file can be found in: C:\Program Files (x86)\ag Leader Technology\SMS 3. Leave the Graphics Setting on Based on power supply. Click apply and try to open SMS. Content last reviewed on: 6/17/16 Reviewed by: SSW Error message when opening SMS on Windows 10: load library failed with error 1114, a dynmaic link 3.dll.

5 Error Opening Data Location Overview: When opening SMS after updating or installing it gives the error: "Can't Open Data Location- Data Too Old or Corrupt. Please Contact Technical Support or Your Service provider." This error occurs when the data folder that SMS is trying to access is from an older version of SMS and can't be migrated because versions have been skipped. Solution: There are a couple of solutions for this issue. If the data was from a trial version or is no longer needed the data folder can be deleted by following the steps below. 1. Go to your C: drive and follow this path: C:\Program Data\Ag Leader\SMS\Data 1. If you don't see the Program Data folder, see Showing Hidden Files and Folders 2. Delete or rename the Data folder in the SMS folder. 3. Open SMS and it will be blank with no data. If the data is still wanted then we need to uninstall the version that is currently installed and install the version that is one version newer than the data is from. 1. To uninstall SMS, Control Panel> Programs >Programs and Features> Uninstall a program --- Highlight the program name and select Uninstall at the top of the list. 2. Next determine the version the data folder is from. You can do this by either looking at older backups and dates of the backups or sometimes if you follow this path: C:\Program Files (x86)\ag Leader Technology\SMS\Patches and there will be folders that will correlate to the versions that were installed. Example: 14_50 is version 14.5 and 15_20 is version 15_ When you discover the version the data is from, uninstall the version that installed currently. You can install the version one newer than that one. So if the data is from v14.5 then you can install v15.2 for the data to migrate. Content last reviewed on: 3/21/2018 Reviewed by: TJA Error Opening Data Location 4

6 Unexpected Read Error when importing AgData files into SMS Issue: When reading agdata files, the error below can occur: Cause: When the customer pulls the USB card out from the display before the export has fully completed. This is more prevalent when large files are being exported out. There can be a delay from when the process bar is completed on the display to when the file is actually exported to the USB card. Solution: SMS will not be able to import the current file. Ideally the customer will go back out to the display and Copy All Log files to get their data back onto the card, making sure to wait a few moments after the display has indicated that the file has been exported. A good rule of thumb would be to wait seconds before pulling the USB. If the original file was exported over 30 days ago and they do not have a monitor backup from within those 30 days, you will want to get a current backup from display. The new backup and current agdata file can then be submitted to SMS testing in order to determine if anything can be recovered. Content last reviewed on: 6/17/16 Reviewed by: SSW Unexpected Read Error when importing AgData files into SMS 5

7 PDF Printer Not Activated. Error Code -30 PDF Printer Not Activated. Error Code -30 Cause: Major windows updates. Most commonly seen when computer updates to Windows 10. To Resolve: 1. Close SMS 2. Open Control Panel 3. Go to 'Uninstall a Program' or 'Programs and Features' 4. Right click on 'Ag Leader Technology SMS' and pick 'Change' 5. An installation wizard will open, click next 6. When asked to modify, repair, or remove select 'Repair' 7. Click Next and Install 8. Once the repair is finished the PDF printer should now work. Additional Troubleshooting: 1. Restart the computer and repeat the process outlined above. 2. Check for windows updates. The PDF Printer SMS uses will show up in the optional updates. SMS uses 'AMYUNI Technologies - Amyuni Document Converter 500'. Content last reviewed on: 10/19/2016 Reviewed by: KLC PDF Printer Not Activated. Error Code -30 6

8 SMS - Known Issues Jump to section below: SMS Version 18.5 AGCO data import SMS Version 18.0 Guidance Lines Soil Survey NCCPI Corn and Soybeans Attribute SMS Version 17.5 Profit/Loss Analysis SMS Version 17.2 Importing Soil Survey Data into Google Earth SMS Version 16.7 Soil Survey Download SMS Version 16.5 GS3 Reference Layer Export Crash Comparison Analysis Issue Internet Backgrounds not appearing automatically SMS Version 16.1 Internet Backgrounds causing SMS to Crash SMS Version 15.2 Internet Background Image and Road Map Issue SMS Version 14.5 C++ Update Error Information SMS v18.5 Known Issues AGCO data import What we know: In v18.5 AGCO task data may not import properly when using the AGCO import option SMS will skip the file when imported and no data will be processed Current workaround If the file is skipped the generic task data importer can be used to import this data You may be prompted for some manual entries based on the data type imported We are looking into potential solutions at this time SMS v18.0 Known Issues Guidance Lines What we know: In v17.5 and v18.0 there is an issue with the 'Create Guidance along Boundary Edge' tool The issue is with creating a 'curve' type guidance line that only contains 2 vertices. If you add a vertex to the boundary along the edge that you are trying to use for the guidance line, then it will work. The issue will ONLY occur if the boundary edges have less than 2 vertices SMS - Known Issues 7

9 Current workaround Create a map of the boundary, go to edit layer, add vertices to the edge of the boundary. Once finished, create the guidance lines. This issue will be fixed in the next release of SMS. Soil Survey NCCPI Corn and Soybeans Attribute The Web Soil Survey changed how they are displaying the NCCPI Corn and Soybeans values in certain areas by splitting the attribute out. In the areas that they split the attribute out, you will see NCCPI Corn and Soybeans values displayed separately instead of together on the site. How this affects the user in SMS: What to do In SMS the NCCPI Corn and Soybeans attribute is not split into two attributes. If the user is downloading Soil Survey data in an area that is affected by this, then the NCCPI Corn and Soybeans attribute will only display the value of zero. If the user is downloading Soil Survey data in an area that is not affected, then they will see the NCCPI Corn and Soybeans attribute in the Soil Survey data with the correct values. Ag Leader is working with the source that we get the Soil Survey data from to come up with a solution in SMS. SMS v17.5 Known Issues Profit/Loss Analysis If the user sees #NAN values in the results of the Profit/Loss Analysis, this means that somewhere it is dividing some part of the data by a zero spatial area. The fix is to update to v18.0. SMS v17.2 Known Issues Importing Soil Survey Data Into Google Earth Google Earth will give an error when trying to import Soil Survey data from SMS Advanced/Basic. What we know The issue will occur with the 17.0 and 17.2 Soil Survey KML/KMZ export The attribute NCCPI-Corn and Soybean is causing the issue SMS - Known Issues 8

10 Current workaround Remove the NCCPI-Corn and Soybean attribute from the Selected Items in the Export Settings before exporting the KML/KMZ file. This issue was fixed in version SMS v16.7 Known Issues Soil Survey Download The tool used to download soil survey data automatically in SMS is not working in any version prior to version 17. When attempting to download soil maps in SMS, an error saying " Soil Survey data could not be downloaded for (field name) because of a possible issue with the download service or your internet connection. Please try again." What we know: The error listed above occurs when attempting to download soil survey data for any field in SMS v16.7 or older versions This issue is resolved in SMS v17.0 Current workaround: Users can update to SMS v17.0 and issue will no longer occur Users can also manually download soil type maps and import them into SMS if unable to update to v17.0. Users can get soil type maps for free from the source listed below USDA Geospatial Data Gateway What should be done when this happens: Inform users of the cause Look into update options Cover the option to manually download/import soil survey maps outlined above SMS v16.5 Known Issues GS3 Reference Layer Export Crash Documented 8/2/16 A bug was recently discovered within SMS v16.5 when attempting to export specific variety tracking data to John Deere Greenstar 3 displays. SMS is crashing when this data is exported and, afterwards, the desired information is not present on the memory card. What we know: In SMS v16.5, when users attempt to export out specific data for variety tracking to John Deere GS3 displays, the software would crash upon export It was discovered that if the dataset exported out contained only a single GPS point the software would crash SMS - Known Issues 9

11 This is not limited to variety tracking export but all datasets that can be exported as a reference layer to the GS3 display Current workaround: If the dataset containing the single data point is removed, SMS will export the remainder of data successfully What should be done when this happens: Inform the user that this is known issue and should be resolved in the upcoming release of SMS Explain that removing the dataset with a single point will result in the remainder of the data being exported successfully Comparison Analysis Issue (Advanced Only) Documented 7/15/16 Recently an issue was discovered in SMS v16.5. When using the comparison analysis and entering in manual ranges, SMS is not displaying the values correctly and the first few decimal places are getting cut off. See an example below. What We Know: SMS - Known Issues 10

12 In SMS v16.5, the first few characters are getting cut of when using a manual range in the Comparison Analysis This issue does not occur in earlier versions or when using an attribute/property not requiring the user to enter in manual ranges (soil type, product name, etc.) The cut off characters are showing in both the table and chart portions of the comparison analysis This issue has been submitted to testing and the issue should be resolved in the next release of SMS Current Workaround: Currently there is no workaround to get these characters to show within the comparison analysis tool Customers can use queries to gather some specific information on a field by field basis What should be done when this happens: Inform the user that this is a known issue and should be resolved in the upcoming release of SMS Explain that queries can be used as a temporary measure to gather limited information until SMS is released in a few weeks Internet Backgrounds Not Appearing Automatically Documented 6/27/16 Recently a bug was discovered in SMS v16.5. When creating a map in SMS v16.5, the background satellite image does not show up automatically, only when you refresh the map does the image come in. What We Know: In SMS v16.5, background images will not show up until the created map is "refreshed" (clicking on background source button, changing background type, choose a new attribute, zooming in/out, changing map types, etc.) Issue only appears to be occurring in SMS v16.5, v16.1 is working correctly Batch print appears to be working correctly This issue has been submitted to testing in order to determine cause and potential solution Current Workaround: Users will need to perform one of the actions listed above to "refresh" the map in order to view background images What should be done when this happens: Inform the user that this is a known issue and a fix should, tentatively, be in place in the next release of SMS Explain to them that performing one of the above steps will result in the images appearing SMS V16.1 Known Issues Internet Backgrounds Causing SMS to Crash Documented 5/15/16 SMS - Known Issues 11

13 When creating a new map, users have been seeing poor performance in SMS. There has been two main issues occurring so far. What we know: Users have been reporting background images that are all black after creating a map. Users have been reporting SMS closing or crashing after users hit the "Create Map" button Workaround Up to this point the issue can be resolved by changing the map source from automatic to source 2 and clearing the existing backgrounds This can be done by going to Tools - General Options - Mapping 1 then changing the Background Source to Source 2 and then hitting the Clear Internet Backgrounds Unfortunately, after the user preforms these steps, up to this point, we have been unable to replicate the problem and attempt to determine the cause. What should be done when this happens: If you happen to run into this issue, troubleshoot the issues as normal and if the standard steps do not resolve the issue, hold off performing the steps above and first make a copy of the entire data folder. Then have the user send that copy into technical support to test. Once the copy is made, go ahead and have the user clear their cache and change the source to get around the issue. If you are unsure of the data location, please call for support. SMS v15.2 Known Issues Internet Background Image and Road Map Issue Documented 5/6/15 - Fixed in v15.5 We have identified an issue with the automatic Internet backgrounds in SMS. When users manually choose source 1 and view the background images (either road/aerial combination or aerial maps only), the downloaded image appears to be of poor quality. Also when users select source 2 and view roads only, the road map appears to be of poor quality. What we know: Priority="64" SemiHidden="false" UnhideWhenUsed="false" Name="Medium Shading 2 Accent 4" /> Â This issue only occurs when manually selecting a specific background source (see below) SMS - Known Issues 12

14 Source 1 - Images Source 2 - Road Maps When using the 'Automatic' source (see below), SMS chooses the 'best' image for each option and this issue should not occur: Priority="64" SemiHidden="false" UnhideWhenUsed="false" Name="Medium Shading 2 Accent 4" /> Current Workaround: Have the user set the Background Source to 'Automatic' in General Options - Mapping 1, click the Clear Internet Backgrounds button and re-map their data to view the best possible image What should be done when this happens: SMS - Known Issues 13

15 Suggest to the user to change the source to automatic as mentioned in the current workaround section This issue was resolved with a change made in SMS v15.5 to better select the best background source Suggest users to update versions for best results SMS v14.5 Known Issues C++ Update Error Information Some users will experience an error when attempting to update to SMS v14.5. This error will prevent users from proceeding with the update and force them into updating via alternative routes. Note, this issue will occur with both the True Update-based update as well as the manual download from the Ag Leader website, CD installs are unaffected. The specific error is shown below: The error will occur at the beginning or shortly after the start of the update. This message is caused by a change made in the web and true update installs and will not occur in newer SMS version installs. In order to proceed past this issue, follow the steps below: 1. Download SMS v14.5 installer here 2. Allow download to finish, then extract the zipped folder 3. Run the Setup.exe file contained within the newly created folder 4. Allow the install to proceed and the error above should not occur Content last reviewed on: 6/15/18 Reviewed by: TJA SMS - Known Issues 14