Trimble Business Center

Hello

I am hoping someone can help me with this issue. I am working with the trial version of TBC and attempting to import a .JXL file. I have created the project and tried both the import option and drag and drop - both with the same results. (See the attachment for the error_

I am new to this software, so it is possible I am doing something wrong, but I don't think so.

Thanks

Bob

Drag and drop should work.

It doesn't matter if you use the latest TBC version. What matters is that you have the latest JXL/JOB importer installed. Even an old TBC can import the latest Access version with that.

Either check inside TBC on the Tab "Support" -> "Check for Updates" that it doesn't show any office updates.

Or just download the latest version from here https://help.trimblegeospatial.com/TrimbleAccess/latest/en/Downloads-software.htm under "Office Software Updates" and proactively install it.

If it still fails, we can investigate further.

Morning

I opened my version of TBC (See screenshot of version below) and tried both processes - Import and drag and drop - same error message. I did move the file, so it is also local, directly on my C: drive. I am going to try one more time with a fresh install and running the Office Cleanup Utility now.

I appreciate the response.

Thanks!!

Surprisingly the cleanup and reinstall worked. Data imported.

Thanks for the input!!!

Bob

First off sometimes trial don't have import tab. If you do have import tab then copy files whole folder to your c drive and work on job. Network sometimes will give you a error message. Trimble don't support network errors reason is because file path names are to long. And networks are all set up different. I work on my c drive then when complete with my point cloud I copy to network to finish my Basemap. I hope this helps you I cleared 13 errors my doing this and din't have to send surveyors back out in the field.

Network could be an issue, it shouldn't but is for TBC now and then. Usually a network path is shorter than a potential local folder somewhere in your "c:\users\20 character name\Documents" or the like. I can see the potential problem if it is a OneDrive, Dropbox, GoogleDrive etc. folder, since those services can put a lock on a file in the wrong moment. But normal local network drives or just a drive mapped to a folder on the C drive must work without excuse. It's unclear why TBC stumbles with those on occasion.

On the previous job halve a dozen surveyors did work on a locally installed server for several years without an issue. Importing JOB/JXL from there and working with and saving TBC projects to it. For projects with point clouds we did copy them to a local folder but only due to speed/performance reasons. Only lately point clouds on network drives have become an issue, potentially emptying the project file.