GeoCue Support » Archives for GeoCue Support » Page 31
Requeuing in the Command Dispatch System (CDS) will occur any time a subtask requires neighbors and suitable lock cannot be obtained. Multiple requeues often occur when there are a small number of entities and many resources available in the CDS. Neighbor overedge processing will cause surrounding tiles to become read locked while that tile is…
The message column for a subtask in the GeoCue Dispatch Manager displays, “Dispatch control executable exited with error code #”, where # is typically -1 or -7. Find the corresponding entity in the GeoCue Client. Select the step in the checklist corresponding to that which was set in progress to create the subtask. Review the…
The Run Macro step completes with an exception, “Macro file does not exist.” as seen in the System Message column of the Checklist Step Details pane. Verify that the macro file associated with the assigned macro still exists in the project folder i.e. “\80XXX\1”. The macro will show in red in the macro catalog if…
On the “Machines” tab in GeoCue Dispatch Manager the error message, “The specified remote client cache path does not exist.” is showing for a machine. The error message indicates that there in an issue with the remote cache folder setup in the GeoCue Client Configuration. Type “configure client” into Windows search and open the GeoCue…
User sees large voids when displaying point cloud data in LP360. This usually occurs when combining dense and sparse point cloud datasets or displaying terrestrial scanner points clouds. The reason points don’t display properly is that points close to each other spatially are not physically near to one another in the LAS file structure. Here…
Selecting any button related to the WMSCatalog results in the error message, “Opening XML for WMSCatalog failed. (22530)”. [Window Title]LP360 Error[Main Instruction]Opening XML for WMSCatalog failed. (22530)[Expanded Information]Exception Information:HRESULT: 0x800401f3Description:Interface not supported (9027)[V] Expand this [ ] Do not show exceptions again. [OK][Footer]Press ‘Ctrl+C’ to copy message to clipboard. Locate and rename the C:\Users\%USER%\AppData\Roaming\LP360\wmscatalog.xml, where…
User encounters an error message when starting ArcMap with the LP360 for ArcGIS extension stating, “Error setting active layer”. If the user clicks through this error message, basic functionality and display issues will occur, often times leading to software crashes. The crash is happening because ArcMap and/or LP360 is not properly installed and/or registered. Re-installing…
Attempting to populate LAS Working Segments in GeoCue results in an exception message in the system message column of the checklist step details pane for the Populate step stating, “System.OutOfMemoryException: Array dimensions exceeded supported range. at NIIRS10.LASLib.LASStructArray6..ctor(Int32 size, Int32 numExtraBytes, Byte formatOnDisk) in N:\GeoCue 2017.1\iDEMS\iDEMSShared\LASLib\LASstructures.cs:line 2844 at NIIRS10.LASLib.LAS.AllocatePointDataRecordArray(LAS las, Int32 size) in N:\GeoCue…
The GNSS LED on the True View system isn’t turning green. on systems with the readout display the message gets stuck on, “Getting location”. A solid green GNSS LED on the True View indicates that it has good satellite reception. A blinking yellow GNSS LED can be caused by a number of things. The following…
LP360 and True View EVO use OpenGL v2.0 and/or v4.4 depending on the module. As outlined in the system requirements, the graphics card being used on your machine must support these in order for the products to function properly. To check what versions of OpenGL are supported by your graphics card: Download GLview from realtech…