The path to the macro folder is as follows
C:\ProgramData\Trimble\MacroCommands
In that folder there is a \Trimble folder - that is where TBC installs macros that ship with the product installation.
I typically have a \Temp Macros folder also in which I install non standard macros or macros from other sources etc.
TBC reads all folders in this location and loads all macros.
If you installed the same macro in two locations then it triggers he Traceback issue that you have seen.
If you have an old / out of date macro that has been updated then you can also see the Traceback issue that you have seen.
If you see a Traceback issue on start up then
1) Go to this folder / set of folders and see if the Macro that is flagged in the Traceback error is installed twice - if yes, then keep the version in the \Trimble Folder and delete the one in the other folders. You may want to cut and paste the Macro files from that location and move them to some Temp location on your PC until you know you have the latest version etc
2) If after removal of duplicates you find that you still get a Traceback issue at start up then your macro is out of date - you can check the Macros Forum for a newer version or you can go to www.RockpileSolutions.com and install their TML Status Macro which will then help you keep Macros in check moving forwards.
If you are still seeing issues after following these steps, please let me know.
Macros typically include the following files
1) a .py extension file (and sometimes a .pydll
2) a .xaml extension file
3) a .png extension file
All files have the same name but a different extension. Not all three files are 100% necessary so not all macros have the three files depending on how they were created.
There is one other thing that we have seen that I know the team have been solving, but I am not sure of the current status - and that is when you download files from the web servers, they get a protection state on them sometimes, to remove that protection state you find the macro files, right click and select properties and in the Attributes section where it normally shows [ ] Read Only and [ ] Hidden it also shows something else (not under Advanced) - I apologize but I cannot recall what it says - but there is an option to unprotect or similar - if it is shown, do the unprotect type function and you will then be OK - this can also be a cause of the Traceback error
Alan