I recently encountered an issue when opening a JXL file in Trimble Business Center (TBC) that resulted in the following error message:
"Unable to execute a command object because it threw an exception… target
Parameter name: The dependency target with serial 0 is not in the concordance AND not in constructing mode."
After troubleshooting, I discovered that the problem was caused by renamed point numbers that were still referenced in some aspects of the JXL file. Specifically, LivePolylineRecord elements contained old point numbers that no longer existed, causing TBC to throw an error.
Solution: Manually Correcting the Point References
To fix the issue, I manually edited the JXL file in a text/XML editor and updated the old point numbers to match the correct ones. Here's an example of the problematic records before and after the correction:
Old (Incorrect) Values:
<LivePolylineRecord ID="0000038b" TimeStamp="2025-02-02T10:24:06">
<Name>UT_STRUC1</Name>
<Deleted>false</Deleted>
<StartPoint>333898</StartPoint>
<Parts>
<LinePart>
<EndPoint>333899</EndPoint>
</LinePart>
<LinePart>
<EndPoint>3338100</EndPoint>
</LinePart>
</Parts>
</LivePolylineRecord>
New (Corrected) Values:
<LivePolylineRecord ID="0000038b" TimeStamp="2025-02-02T10:24:06">
<Name>UT_STRUC1</Name>
<Deleted>false</Deleted>
<StartPoint>3338098</StartPoint>
<Parts>
<LinePart>
<EndPoint>3338099</EndPoint>
</LinePart>
<LinePart>
<EndPoint>33380100</EndPoint>
</LinePart>
</Parts>
</LivePolylineRecord>
Once I corrected all outdated point references in LivePolylineRecord elements, the JXL file opened in TBC without any errors.
Key Takeaways
• If you encounter this error, check for renamed points in your JOB file.
• Inspect elements like <LivePolylineRecord> to ensure that all referenced point numbers actually exist in the file.
Hopefully, this will help someone facing the same issue in the future! Let me know if you have any questions.
------------------------------
Yahsha Breedlove
------------------------------