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.

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.

------------------------------
Clayton Bradshaw
------------------------------

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.

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 think you need to update Access on the controllers as well.

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.

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.

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

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.

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.

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

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.