Sage 300 CRE®

The hh2 Synchronization Client is installed on your Sage server to provide a secure, real-time link between your Sage 300 Construction and Real Estate (CRE) database and Procore. These best practices were developed in collaboration with hh2 to help ensure a successful integration and consistent data synchronization.

By following these guidelines—which cover system requirements, recommended update frequencies, and security software configurations—you can proactively resolve common connection issues and minimize sync timeouts.

System requirements for hh2 can be found here under Server Specifications heading.

Hh2 will push out critical updates as needed however security software as well as other conditions on your server may prevent those updates from fully installing. 

Be prepared to update the hh2 Synchronization Client manually when troubleshooting with ERP support or set up a regular update cadence. Recommended frequency: monthly or at least quarterly updates.

Ensure that Sage 300 CRE Windows permissions and anti-virus/security software exclusions are configured according to Sage’s recommendations:

• Sage 300 Construction and Real Estate and Sage Estimating Required Permissions https://support.na.sage.com/selfservice/viewdocument.do?externalID=18211

• What Sage 300 Construction and Real Estate and Sage Estimating files and folders should I exclude from my antivirus software scan? https://support.na.sage.com/selfservice/viewdocument.do?externalID=17258 

• In addition to the files and folders specified in Sage’s documentation, you may apply the same permissions and AV exclusions to the following folders:

  • C:\ProgramData\Digital Business Integration

  • C:\ProgramData\MongoDB

  • C:\Program Files\Digital Business Integration

  • C:\Program Files\MongoDB\

• Both Sage and hh2 Services are designed to use the Windows local SYSTEM account. Procore ERP Support can help assess whether elevated permission would be necessary.

• Occasionally, clients may notice that the hh2 Synchronization service does not respond following a server reboot. Setting the service’s Property “Startup type:” as Automatic (Delayed Start) may help.

• Restart the hh2 Synchronization service:

  •  After restarting Actian/Pervasive PSQL services or ntdbsmgr64.exe.

  •  If the Actian/Pervasive PSQL Monitor Utility is used to end sessions (aka “kicking everybody out”)

• Stop the hh2 Synchronization service: Before running a backup or carrying out any operation that requires exclusive access to your Sage database, you should stop the hh2 Synchronization service on the Sage server and start it again when you’ve completed your work.

• If you use other hh2 products such as Payroll or HR: Take care not to duplicate mappings for one company folder in separate Local Connections going to the same hh2 Cloud Account. 

• If you use version Sage 23.2 or greater can take advantage of the improved Commitment/CCO API Export method. This new process improves syncing performance on these objects between systems. Reach out to ERP support to request this be enabled.

• If Sage is encountering errors, it’s likely this will affect hh2 and the Procore Integration:

  •  The most common error to cause problems is the “Possible Relationship Inconsistency” error. This Sage Knowledgebase article gives very detailed information about this error and how to resolve it:
    Error: "Possible relationship inconsistencies" during a task or "File previously aborted" in system log 

  • Sage licensing issues also cause Timeout errors: See Sage’s Knowledgebase for information about upgrading to a new version. In the meantime, you can resolve this error as it arises by following these instructions: How to resolve Sage License Expiration

•  After any Sage errors are resolved, further steps are required to get hh2 running properly again: How to resolve timeout errors on the Sage Server

• Migrations, Upgrades, and Data Folder Relocation: If you need to migrate to a new server or update your Sage software, here are instructions for managing hh2 during that transition.

• Key Changes: Any time you make changes to key fields, such as Job IDs, Vendor IDs, Cost Codes, Categories etc. both hh2 and Procore will need to be involved from the beginning to coordinate a smooth transition. Please reach out to ERP Support before beginning this process with your Sage consultant.

Please contact Procore ERP Support by filling out this form with any questions. You can also reach out via live chat or phone by calling +1 (833) 277-6267 and choosing option 3 for ERP support.