Trimble Business Center

Hello, Our survey department just universally updated our workstation's versions of TBC to the newest 2023.11 and now we are not able to import our Access .job files.  We have tried multiple different .job files from two different data collectors running similar but different versions of Access.  One is on Access 23.10 and the other is on Access 23.00.  One is a T7 and the other is a TSC5.  The T7 is running 23.00 and the TSC5 is running 23.10.  We get the following error when importing the .job files.  See below for a screen shot of the error message.  Thank you for your help.

I'm not sure how to resolve importing the JOB files, but I'd recommend trying exporting JobXML (.jxl) files and importing them into TBC. 

Importing a JXL may work.

TBC does convert the JOB in the background temporarily into a JXL and reads the data from there. If the importer/converter isn't UpToDate you need to install it from here:

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

It's possible that the latest TBC installer doesn't include the latest Access converter, two different products. Every time there is a new Access version you need to update the importer/converter. That way you can import even the latest Access JOB version into an older TBC version.

You could also try "Check for Update" on the "Support" tab, but I doubt it'll show up there.

That issue pops up quite regularly here on the forum.

------------------------------
Ronny Schneider
------------------------------

I updated to 2023.11 this morning and began processing my data. and received the same error.  I was able to import the JXL file but not the JOB file. Not ideal but at least the data it in.

I think you need to update Access on the controllers as well.

Hello,

Thank you everyone for the responses.  I have tried all the fixes suggested without success.  My Trimble dealer tech support provided the following and this proved true.

The upgrade to the latest TBC causes some type of issue with mapped drives.  So if you are importing from a mapped drive, for some reason this causes a problem with the import .job and convert and write to jxl.  The jxl is temporarily written to the same location as the .job file and it can't do so through the mapped drive.  The solution as presented to me was to disconnect the mapped drive and reconnect.  I can't test this theory as I don't have administrative rights to do that due to the size of our IT maintenance and management.

But I was able to test that this is in fact likely the case.  When I copied the .job to my local computer C: drive and imported that way, everything went fine.  So it appears to have to do with the mapped drive.

I hope this helps.

Thank you. I too am not able to remap my network drives but copying the file to my local drive did resolve the issue.

Thank you! I have also had this problem and its an easy fix.

------------------------------
David Strong
------------------------------