Error Message on JXL Import

View Only

Kelsey Huff posted 11-13-2023 17:52

I am attempting to import a jxl file into an existing TBC project and get an error message about an unexpected error.

The error replicates in a blank TBC session.

I'm not sure how to interpret what I'm seeing in the error window:

Exception Count: 1
Exception Source: Trimble.Vce.Data.JobXML
Exception Type: System.NullReferenceException
Exception Message: Object reference not set to an instance of an object.
Exception Target Site: 옄

---- Stack Trace ----
.큉.옄(ProgressForm A_0)
Trimble.Vce.UI.Client.DLL : N 00215
.큉.RunWithProgressBar(ProgressBarProcessFunction function, Boolean canBeCanceled)
Trimble.Vce.UI.Client.DLL : N 00135
Trimble.Vce.Data.Import.ImportEngine.阷(IImportInfo A_0, List`1 A_1)
Trimble.Vce.Data.Import.DLL : N 02352
Trimble.Vce.Data.Import.ImportEngine.ImportFiles(IImportInfo[] importInfos)
Trimble.Vce.Data.Import.DLL : N 05363
Trimble.Vce.UI.BaseCommands.ImportService.ImportCmdFiles(IImportInfo[] infos, Boolean useCmdMarkers, Boolean showReportAfterwards, Boolean zoomExtentsAfterwards)
Trimble.Vce.UI.BaseCommands.DLL : N 06545
Trimble.Vce.UI.BaseCommands.ImportService.ImportFiles(IImportFilesServiceItem[] files)
Trimble.Vce.UI.BaseCommands.DLL : N 00210
Trimble.Vce.UI.ViewWindowBase.옄(Object A_0, DragEventArgs A_1)
Trimble.Vce.UI.Client.DLL : N 02042

---- Stack trace from the original exception which stopped progressBar----
Trimble.Vce.Data.JobXML.Nodes.StartRoundNode.Process(ProcessingContext context)
Trimble.Vce.Data.JobXML.DLL : N 00028
Trimble.Vce.Data.JobXML.ProcessingContext.ProcessRecord(XPathNavigator nav)
Trimble.Vce.Data.JobXML.DLL : N 00635
Trimble.Vce.Data.JobXML.DataReader.茁(XPathNavigator A_0, RawDataProcessorContext A_1, List`1 A_2, IList`1 A_3, ImportInformation A_4)
Trimble.Vce.Data.JobXML.DLL : N 02566
Trimble.Vce.Data.JobXML.DataReader.Read(ImportInformation importInformation, List`1 readFilter, IList`1 pointPairs)
Trimble.Vce.Data.JobXML.DLL : N 00552
Trimble.Vce.Data.JobXML.FileReader.茁(List`1 A_0)
Trimble.Vce.Data.JobXML.DLL : N 02678
Trimble.Vce.Data.JobXML.FileReader.Read()
Trimble.Vce.Data.JobXML.DLL : N 00011
Trimble.Vce.Data.JobXML.Importer.Import(String fileName, IProject iProject, ImportInformation importInformation, ICoordinateSystemUI iImportDlgs, Boolean& needRecomputeProject, Boolean ShouldAddFilenameToImportInformation)
Trimble.Vce.Data.JobXML.DLL : N 00258
Trimble.Vce.Data.JobXML.Importer.Import(String fileName, IProject iProject, ImportInformation importInformation, ICoordinateSystemUI iImportDlgs, Boolean& needRecomputeProject)
Trimble.Vce.Data.JobXML.DLL : N 00037
Trimble.Vce.Data.Import.ImportEngine.阷(IProgressBarControl A_0)
Trimble.Vce.Data.Import.DLL : N 00290
Trimble.Vce.UI.쟢.죑()
Trimble.Vce.UI.Client.DLL : N 00609

Ronny Schneider posted 11-15-2023 06:37

You're most likely trying to import a JXL of a new Access version that your TBC doesn't know about yet.

Close TBC and download and run the latest installer from this webpage and see if that solves your Import problem. (the latest installer includes all previous versions)

https://forms.trimble.com/support_trl.aspx?Nav=Collection-84865

Robert Hoy posted 11-15-2023 10:32

You might be importing Access data that is newer than the TBC files. Just "check for updates" in TBC to install update components for newer Access formats. No need to reinstall TBC!

Kelsey Huff posted 11-15-2023 11:46

Thanks for the responses Ronny and Robert.

My version of TBC is up-to-date and I've had my field crew export other files from the same project and have had no issues before or since this issue arose. For some reason every time they export a JXL from their collector of this particular day I get this error and am unable to view the data associated with it.

Ronny Schneider posted 11-15-2023 17:41

Can you please upload the JXL here.

Samuel Smith posted 01-06-2025 13:19

Kelsey,

We have managed to solve this issue. It occurs when a total station for some reason errors out or shuts down while rounds are being turned.

The indicator is a "StartRoundsRecord" with no closing tag, so it is immediately followed by an "EndRoundsRecord" tag.

Example:

        <StartRoundsRecord ID="000003be" TimeStamp="2025-01-02T10:55:17"/>

        <EndRoundsRecord ID="000003bf" TimeStamp="2025-01-02T10:55:17"/>

The solution is to search "StartRoundsRecord" and review to make sure they all have data, and if not delete the incomplete "StartRoundsRecord" and "EndRoundsRecord" tags as shown above.