My TBC Started Misbehaving

How up to date are you with your TBC.  I was having problems with path names a couple weeks ago which I am pretty sure were caused by a Windows update. I looked at my TBC check for updates and there was one there for something like Trimble shared resources. Ran that and everything seems to be fine now. 

For the background mapping problem I don't have a clue.

@bobwesterman I have a perpetual license but it only goes up to version 5.90 which is what I have installed.  I may renew the maintenance later this year before it goes to subscription only, but I don't see why things that were working fine before suddenly broke.  I would be genuinely surprised if it was a Windows issue.

Posted by: @bstrand

↑

 I would be genuinely surprised if it was a Windows issue.

Well if the TBC hasn't changed, what else has?

@bobwesterman Nothing that I know of, but I'll keep poking around.  I did install a thing in the TBC updater Called Trimble Shared something but that didn't seem to fix anything.

Posted by: @bstrand

↑

@bobwesterman Nothing that I know of, but I'll keep poking around.  I did install a thing in the TBC updater Called Trimble Shared something but that didn't seem to fix anything.

One thing I would definitely recommend if you do decide to upgrade.  Make sure you run the Trimble cleanup tool before doing the new install.  A lot has changed in TBC since version 5.9.

I ran into serious problems going from 2024 to 2025.

The cleanup tool fixed them.

@bobwesterman I normally just uninstall the whole thing and reinstall.  There's a website where you can download a zip file of your version so if you save that you can reinstall it anytime.  That's what I've been doing anyway.

I think I found the problem with the .fxl now.  I must have broken a code at some point because when I make a dummy new .fxl it processes fine.

OK, found the broken code so that fixed that problem.  Maybe there is a way to see it that I don't know about, but TBC offered zero explanation as to what specifically was going on.  I had to delete every single code 1 at a time and then try to process with the file to ID the broken code.  So dumb...

Chatgpt actually suggested this method of finding out what the deal was.

Posted by: @bstrand

↑

@bobwesterman I normally just uninstall the whole thing and reinstall.  There's a website where you can download a zip file of your version so if you save that you can reinstall it anytime.  That's what I've been doing anyway.

I think I found the problem with the .fxl now.  I must have broken a code at some point because when I make a dummy new .fxl it processes fine.

We keep the last few versions on the Server in case we need to reinstall. The clean up utility does the whole uninstall and then some, looking for all the registry stuff that sometimes gets missed in the regular uninstall. I used to only do that if there was a problem, but now I've been doing the cleanup for every major version.

It doesn't take much longer and will find thing that were missed from previous uninstalls, avoiding problems before you know they are there.