WorksManager

Has anyone had trouble getting SiteWorks work order spj files prior to October 2025 to sync from data collectors up to the WorksManager/ TCC filespace? The log files and xml files for the work order are syncing, but the spj files are not. Our dealer and their Trimble support people know about the issue for the project that first showed a problem, but they are less than responsive and certainly not proactive about solving the problem. Can anyone explain how Siteworks and the WorksManager/ TCC filespace communicate to identify if an spj file needs synced or not?

Has anyone had trouble getting SiteWorks work order spj files prior to October 2025 to sync from data collectors up to the WorksManager/ TCC filespace? The log files and xml files for the work order are syncing, but the spj files are not. Our dealer and their Trimble support people know about the issue for the project that first showed a problem, but they are less than responsive and certainly not proactive about solving the problem. Can anyone explain how Siteworks and the WorksManager/ TCC filespace communicate to identify if an spj file needs synced or not?

Has anyone had trouble getting SiteWorks work order spj files prior to October 2025 to sync from data collectors up to the WorksManager/ TCC filespace? The log files and xml files for the work order are syncing, but the spj files are not. Our dealer and their Trimble support people know about the issue for the project that first showed a problem, but they are less than responsive and certainly not proactive about solving the problem. Can anyone explain how Siteworks and the WorksManager/ TCC filespace communicate to identify if an spj file needs synced or not?

We have had this issue in the past, but not necessarily specific to a "prior" date.   

• Back up the project on the controller locally on the device
• Delete the device xml files in the root and the project
• Remove the device from all projects on WM
• Delete the device from your account
• Check TCCexplorer to make sure the device is gone.  If its not delete it.
• Give it about 10 minutes for the Trimble databases to update
• Re add the controller to the WM account
• Add the Controller to the project.
• Sync the device and it should work now.

Has anyone had trouble getting SiteWorks work order spj files prior to October 2025 to sync from data collectors up to the WorksManager/ TCC filespace? The log files and xml files for the work order are syncing, but the spj files are not. Our dealer and their Trimble support people know about the issue for the project that first showed a problem, but they are less than responsive and certainly not proactive about solving the problem. Can anyone explain how Siteworks and the WorksManager/ TCC filespace communicate to identify if an spj file needs synced or not?

@Madhavan B, any updates from the WM team? I can't get a response from Trimble through the support ticket email...

And thanks for the suggestions @Karen Anne De Guzman and @Matt Eklund. It is always a good time to clean up old junk!

We have had this issue in the past, but not necessarily specific to a "prior" date.   

• Back up the project on the controller locally on the device
• Delete the device xml files in the root and the project
• Remove the device from all projects on WM
• Delete the device from your account
• Check TCCexplorer to make sure the device is gone.  If its not delete it.
• Give it about 10 minutes for the Trimble databases to update
• Re add the controller to the WM account
• Add the Controller to the project.
• Sync the device and it should work now.

Has anyone had trouble getting SiteWorks work order spj files prior to October 2025 to sync from data collectors up to the WorksManager/ TCC filespace? The log files and xml files for the work order are syncing, but the spj files are not. Our dealer and their Trimble support people know about the issue for the project that first showed a problem, but they are less than responsive and certainly not proactive about solving the problem. Can anyone explain how Siteworks and the WorksManager/ TCC filespace communicate to identify if an spj file needs synced or not?

@M_Hufford Did you try to send a support request through your dealer? That's the formal way Trimble wants customers to request support. 

@Madhavan B, any updates from the WM team? I can't get a response from Trimble through the support ticket email...

And thanks for the suggestions @Karen Anne De Guzman and @Matt Eklund. It is always a good time to clean up old junk!

We have had this issue in the past, but not necessarily specific to a "prior" date.   

• Back up the project on the controller locally on the device
• Delete the device xml files in the root and the project
• Remove the device from all projects on WM
• Delete the device from your account
• Check TCCexplorer to make sure the device is gone.  If its not delete it.
• Give it about 10 minutes for the Trimble databases to update
• Re add the controller to the WM account
• Add the Controller to the project.
• Sync the device and it should work now.

Has anyone had trouble getting SiteWorks work order spj files prior to October 2025 to sync from data collectors up to the WorksManager/ TCC filespace? The log files and xml files for the work order are syncing, but the spj files are not. Our dealer and their Trimble support people know about the issue for the project that first showed a problem, but they are less than responsive and certainly not proactive about solving the problem. Can anyone explain how Siteworks and the WorksManager/ TCC filespace communicate to identify if an spj file needs synced or not?

@Madhavan B, any updates from the WM team? I can't get a response from Trimble through the support ticket email...

And thanks for the suggestions @Karen Anne De Guzman and @Matt Eklund. It is always a good time to clean up old junk!

We have had this issue in the past, but not necessarily specific to a "prior" date.   

• Back up the project on the controller locally on the device
• Delete the device xml files in the root and the project
• Remove the device from all projects on WM
• Delete the device from your account
• Check TCCexplorer to make sure the device is gone.  If its not delete it.
• Give it about 10 minutes for the Trimble databases to update
• Re add the controller to the WM account
• Add the Controller to the project.
• Sync the device and it should work now.

Has anyone had trouble getting SiteWorks work order spj files prior to October 2025 to sync from data collectors up to the WorksManager/ TCC filespace? The log files and xml files for the work order are syncing, but the spj files are not. Our dealer and their Trimble support people know about the issue for the project that first showed a problem, but they are less than responsive and certainly not proactive about solving the problem. Can anyone explain how Siteworks and the WorksManager/ TCC filespace communicate to identify if an spj file needs synced or not?

@M_Hufford There are two active Trimble Support cases related to this issue.  They have been looked at by the WorksManager team who have reviewed it and believe it to be a Siteworks issue, not syncing the most up to date SPJ file.  The Support tickets now have to be escalated to the Siteworks team to look into.  I would suggest requesting future updates from the Support ticket rather than the community page as the support ticket is monitored daily by the support staff and the support tickets are linked to any escalated tickets with the development teams (Siteworks, Worksmanager etc) . 

- - - -

Best Regards,

Adam Roulston

@Madhavan B, any updates from the WM team? I can't get a response from Trimble through the support ticket email...

And thanks for the suggestions @Karen Anne De Guzman and @Matt Eklund. It is always a good time to clean up old junk!

We have had this issue in the past, but not necessarily specific to a "prior" date.   

• Back up the project on the controller locally on the device
• Delete the device xml files in the root and the project
• Remove the device from all projects on WM
• Delete the device from your account
• Check TCCexplorer to make sure the device is gone.  If its not delete it.
• Give it about 10 minutes for the Trimble databases to update
• Re add the controller to the WM account
• Add the Controller to the project.
• Sync the device and it should work now.

Has anyone had trouble getting SiteWorks work order spj files prior to October 2025 to sync from data collectors up to the WorksManager/ TCC filespace? The log files and xml files for the work order are syncing, but the spj files are not. Our dealer and their Trimble support people know about the issue for the project that first showed a problem, but they are less than responsive and certainly not proactive about solving the problem. Can anyone explain how Siteworks and the WorksManager/ TCC filespace communicate to identify if an spj file needs synced or not?