GeoCue Group’s repository of articles for the GeoCue workflow management product, covering tools, tips, and workflows.
Around update 11, Bentley made it mandatory to login to the Bentley CONNECTION Client in order to obtain a valid license for the Bentley product. Doing so broke the ability for the dispatch service user to launch MicroStation. The fix is to login to the machine one time as the GeoCue Dispatch user, login to…
The task or subtask messages column of the GeoCue Dispatch Manager states, “No more valid machines available for processing” or ” No other valid machines available for re-processing”. The task, such as Archiving, is configured, to dispatch to only the machine from which it was started. An error was encountered during archiving and no additional…
When executing a TerraScan macro in GeoCue the Working Segment in progress gets a write lock, while the neighboring working segments get read locked, if neighbors are required. There is no progress bar, but the locks will release and the Production State will update to reflect the step upon completion. The Dispatch Manager can provide…
On the “Machines” tab in GeoCue Dispatch Manager the error message, “The specified user for the remote GeoCue Client service login does not have permission to write to the specified remote cache folder.”, is showing for a machine. Ensure the Dispatch User, as set on the machine in question, has permission to read/write to the…
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…
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…
