GeoCue Support has written 723 articles

RunMacro Exception: System.Exception: Unable to ReadFileNumber after 1000 attempts

Problem: Attempting to Run Macro in GeoCue results in a “RunMacro Exception: System.Exception: Unable to ReadFileNumber after 1000 attempts” error message in the System Messages of the Checklist Step history. Probable Resolution #1: Verify that the GeoCue temp folder has been set by opening Configure Client.  Also, verify that the path in “GeoCue Temp Folder”…

Share

Using FileZilla to Exchange Files with GeoCue Group Support

At times while working with GeoCue Group Support it may become necessary to exchange large files or large numbers of files. We suggest the use of an FTP Client to make this easier. If you don’t have your own, or are not familiar with using an FTP client we suggest using the FileZilla project. FileZilla…

Share

Connecting an LP360 Client to the License Server

To setup LP360 on a client machine that is going to connect to a license server you do not need to request an AUT file. Simply set the client to get it’s licenses from your existing LP360 License Server as outlined in the following steps. Install the software using one or more of the latest…

Share

Trajectories for Run Macro Step

Problem: When running a macro through TerraSlave from GeoCue, routines that depend upon trajectory information can fail to return any results.  These routines include “Cut Overlap-Cut by Offset option” and “Apply Corrections”. Cause: When assigning and running a macro through TerraSlave from GeoCue, there is no setting to select which trajectory layer to use as…

Share

Error updating columns (13498)

Problem: Adding LAS files to the LP360 Add Files dialog results in an error stating, “Error updating columns (13498)”. Probable Resolution: Something is missing from the header of the LAS file that is supposed to be there according to the file and the LAS specification. Most usually seen when the WKT flag is toggled, but…

Share

LP360 Error: The task ‘PointCloudStatsExtractor’ cannot be run

Problem: LP360 Errors when trying to run a Point Cloud Statistics Extractor PCT, stating, “The task ‘PointCloudStatsExtractor’ cannot be run. Reason: An Error occurred expanding environment variables in the path: “. Verify the Environment Variable is defined in the System Properties of this computer.” Probable Resolution: This error message likely indicates that the output dataset…

Share

LP360 Error: Validating Settings Failed. (8716)

Problem: LP360 Errors when trying to run a PCT, stating, “Validating Settings Failed. (8716)”. Clicking on “Expand this” will provide additional insight such as Exception Information: HRESULT: 0x80004005 Description: Invalid dataset name. (8737) Probable Resolution: This error message likely indicates that the output dataset (shapefile) has not been specified, or it is relying on the…

Share

TerraScan Raster Backdrop

If you choose to load backdrop images while editing in TerraScan (while through GeoCue’s Process in TerraScan, DirectDrive, or directly in MicroStation’s Raster Manager) and your images show up in the wrong place relative to your LAS points, MicroStation’s Raster Manager may be interpreting your TFW (sister file) or coordinates incorrectly.  Raster Manager defaults the…

Share

LP360 Error: Getting Spatial References Failed. (17124)

Problem: In LP360 for ArcGIS, while trying to Define the 3D Window’s Extent, LP360 errors stating, “Getting Spatial References Failed (17124)”. Expanding the error message dialog for more information reveals, “QI to ISpatialReference failed (21422)”. Probable Resolution: The most probable cause is the lack of a Spatial Reference System (SRS) specified on the LAS Layer…

Share

LP360 Error: Completing the construction of the profile line failed. (17020)

Problem: In LP360 for ArcGIS, while trying to Draw a Profile Line, LP360 errors stating, “Completing the construction of the profile line failed. (17020)”. Expanding the error message dialog for more information reveals, “QI to ISpatialReference failed (21422)”. Probable Resolution: The most probable cause is the lack of a Spatial Reference System (SRS) specified on…

Share